Re: Upgrade sles 12sp4 - sles 15

2019-03-20 Thread Mark Pace
The way I calculate the number of orphans was flawed.  It's only 371 -
still seems like a whole bunch.

On Wed, Mar 20, 2019 at 9:56 AM Mark Pace  wrote:

> Recommended as part of the upgrade is to look for Orphaned packages.
>
> zypper packages --orphaned
>
> Frankly I'm amazed/terrified at the number of Orphaned Packages!  700+
> Can this be right?  And how do I know they aren't really being used?
>
>
>
> On Tue, Mar 19, 2019 at 9:02 AM Mark Pace  wrote:
>
>> So this morning - I tried the following.
>> Added - media_upgrade=1  to the parmfile.
>>
>> Then when asked I pointed the installed to the Packages dvd1 source.
>> Currently the installer is happily running installing packages.
>>
>> There was some message about the registration may now be incomplete, but
>> I think I can deal with that afterwards.
>>
>> On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi 
>> wrote:
>>
>>> Maybe this will help:
>>>
>>>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>>>
>>> Additionally, there are the following extensions which are not covered by
>>> SUSE support agreements, available at no additional cost and without an
>>> extra registration key:
>>>   SUSE Package Hub: https://packagehub.suse.com/
>>>   SUSE Linux Enterprise Software Development Kit
>>>
>>> Lori Grimaldi
>>> Linux on zSeries Americas Team, Team Lead - Senior
>>> IBM Services
>>> Notes:  leter...@us.ibm.com
>>> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
>>> Email Address: leter...@us.ibm.com
>>> IBM
>>>
>>>
>>>
>>>
>>>
>>> From:   Paul Dembry 
>>> To: LINUX-390@VM.MARIST.EDU
>>> Date:   03/18/2019 01:36 PM
>>> Subject:Re: Upgrade sles 12sp4 - sles 15
>>> Sent by:    Linux on 390 Port 
>>>
>>>
>>>
>>> > Any progress is good progress.
>>> Unless you are a lemming :-)
>>> Paul
>>>
>>> -Original Message-
>>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>>> Mark
>>> Pace
>>> Sent: Monday, March 18, 2019 10:11 AM
>>> To: LINUX-390@VM.MARIST.EDU
>>> Subject: Re: Upgrade sles 12sp4 - sles 15
>>>
>>> Thank you, Lori -
>>> I tried the SUSEConnect --clean  and then register again - and now I
>>> have a
>>> different error message.
>>>
>>> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
>>> activated on the system.
>>>
>>> So I need to go figure out what this means.
>>>
>>> Thank you again.  Any progress is good progress.
>>>
>>> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
>>> wrote:
>>>
>>> > I had a problem opened with Microfocus and here is what we did to
>>> resolve:
>>> >
>>> > - Ran SUSEConnect --cleanup
>>> > - Re-Registered system into SCC
>>> > - Upgraded SLES12SP3 to SP4 via zypper migration
>>> > - Upgraded SLES12SP4 to SLES15 via off-line mode
>>> > - Cleaned up gpg key V# warning according
>>> >
>>>
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA&s=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk&e=
>>>
>>> >
>>> > Lori Grimaldi
>>> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
>>> > Notes:  leter...@us.ibm.com
>>> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
>>> > leter...@us.ibm.com IBM
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > From:   Mark Pace 
>>> > To: LINUX-390@VM.MARIST.EDU
>>> > Date:   03/18/2019 10:00 AM
>>> > Subject:Re: Upgrade sles 12sp4 - sles 15
>>> > Sent by:Linux on 390 Port 
>>> >
>>> >
>>> >
>>> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
>>> > Product Registration.  It came back as already registered.  I then
>>> > used Register Again to make sure it was registered.
>>> >
>>> > I may either create a local SMT server, or just build a new SLES 15
>>> > and manually migrate.

Re: Upgrade sles 12sp4 - sles 15

2019-03-20 Thread Mark Pace
Recommended as part of the upgrade is to look for Orphaned packages.

zypper packages --orphaned

Frankly I'm amazed/terrified at the number of Orphaned Packages!  700+
Can this be right?  And how do I know they aren't really being used?



On Tue, Mar 19, 2019 at 9:02 AM Mark Pace  wrote:

> So this morning - I tried the following.
> Added - media_upgrade=1  to the parmfile.
>
> Then when asked I pointed the installed to the Packages dvd1 source.
> Currently the installer is happily running installing packages.
>
> There was some message about the registration may now be incomplete, but I
> think I can deal with that afterwards.
>
> On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:
>
>> Maybe this will help:
>>
>>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>>
>> Additionally, there are the following extensions which are not covered by
>> SUSE support agreements, available at no additional cost and without an
>> extra registration key:
>>   SUSE Package Hub: https://packagehub.suse.com/
>>   SUSE Linux Enterprise Software Development Kit
>>
>> Lori Grimaldi
>> Linux on zSeries Americas Team, Team Lead - Senior
>> IBM Services
>> Notes:  leter...@us.ibm.com
>> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
>> Email Address: leter...@us.ibm.com
>> IBM
>>
>>
>>
>>
>>
>> From:   Paul Dembry 
>> To: LINUX-390@VM.MARIST.EDU
>> Date:   03/18/2019 01:36 PM
>> Subject:Re: Upgrade sles 12sp4 - sles 15
>> Sent by:Linux on 390 Port 
>>
>>
>>
>> > Any progress is good progress.
>> Unless you are a lemming :-)
>> Paul
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Mark
>> Pace
>> Sent: Monday, March 18, 2019 10:11 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Upgrade sles 12sp4 - sles 15
>>
>> Thank you, Lori -
>> I tried the SUSEConnect --clean  and then register again - and now I have
>> a
>> different error message.
>>
>> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
>> activated on the system.
>>
>> So I need to go figure out what this means.
>>
>> Thank you again.  Any progress is good progress.
>>
>> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
>> wrote:
>>
>> > I had a problem opened with Microfocus and here is what we did to
>> resolve:
>> >
>> > - Ran SUSEConnect --cleanup
>> > - Re-Registered system into SCC
>> > - Upgraded SLES12SP3 to SP4 via zypper migration
>> > - Upgraded SLES12SP4 to SLES15 via off-line mode
>> > - Cleaned up gpg key V# warning according
>> >
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA&s=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk&e=
>>
>> >
>> > Lori Grimaldi
>> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
>> > Notes:  leter...@us.ibm.com
>> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
>> > leter...@us.ibm.com IBM
>> >
>> >
>> >
>> >
>> >
>> > From:   Mark Pace 
>> > To: LINUX-390@VM.MARIST.EDU
>> > Date:   03/18/2019 10:00 AM
>> > Subject:Re: Upgrade sles 12sp4 - sles 15
>> > Sent by:Linux on 390 Port 
>> >
>> >
>> >
>> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
>> > Product Registration.  It came back as already registered.  I then
>> > used Register Again to make sure it was registered.
>> >
>> > I may either create a local SMT server, or just build a new SLES 15
>> > and manually migrate.
>> >
>> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>> >
>> > > On 3/15/19 4:25 PM, Mark Pace wrote:
>> > > > This is then end - the lines before this are the panel being
>> displayed.
>> > >
>> > > I think there are a number of lines before then that would be
>> > > useful, but given what you're showing, I have to ask if this system
>> > > is registered, with either SCC or a local SMT server? The sense I'm
>> > > getting is that YaST is asking the registration server what
>> > 

Re: Upgrade sles 12sp4 - sles 15

2019-03-19 Thread Mark Pace
So this morning - I tried the following.
Added - media_upgrade=1  to the parmfile.

Then when asked I pointed the installed to the Packages dvd1 source.
Currently the installer is happily running installing packages.

There was some message about the registration may now be incomplete, but I
think I can deal with that afterwards.

On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:

> Maybe this will help:
>
>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>
> Additionally, there are the following extensions which are not covered by
> SUSE support agreements, available at no additional cost and without an
> extra registration key:
>   SUSE Package Hub: https://packagehub.suse.com/
>   SUSE Linux Enterprise Software Development Kit
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Paul Dembry 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 01:36 PM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> > Any progress is good progress.
> Unless you are a lemming :-)
> Paul
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
> Pace
> Sent: Monday, March 18, 2019 10:11 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Upgrade sles 12sp4 - sles 15
>
> Thank you, Lori -
> I tried the SUSEConnect --clean  and then register again - and now I have a
> different error message.
>
> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
> activated on the system.
>
> So I need to go figure out what this means.
>
> Thank you again.  Any progress is good progress.
>
> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
> wrote:
>
> > I had a problem opened with Microfocus and here is what we did to
> resolve:
> >
> > - Ran SUSEConnect --cleanup
> > - Re-Registered system into SCC
> > - Upgraded SLES12SP3 to SP4 via zypper migration
> > - Upgraded SLES12SP4 to SLES15 via off-line mode
> > - Cleaned up gpg key V# warning according
> >
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA&s=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk&e=
>
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
> > leter...@us.ibm.com IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/18/2019 10:00 AM
> > Subject:Re: Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
> > Product Registration.  It came back as already registered.  I then
> > used Register Again to make sure it was registered.
> >
> > I may either create a local SMT server, or just build a new SLES 15
> > and manually migrate.
> >
> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
> >
> > > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > > This is then end - the lines before this are the panel being
> displayed.
> > >
> > > I think there are a number of lines before then that would be
> > > useful, but given what you're showing, I have to ask if this system
> > > is registered, with either SCC or a local SMT server? The sense I'm
> > > getting is that YaST is asking the registration server what
> > > migration products are available for the currently installed
> > > product(s), and is getting a null answer, possibly because it's not
> registered:
> > > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
> >
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> > ine.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUF
> > vEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid
> > 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
> > >(31420) [Ruby]
> > > registration/registration.rb:182 Received possible migrations paths:
> > >[]*
> > >
> > >
> > > Mark Post
> > >
> > > -

Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Mark Pace
I'm doing this upgrade from 12sp4, not sp3.

On Mon, Mar 18, 2019 at 1:48 PM Lori Grimaldi  wrote:

> Maybe this will help:
>
>https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/
>
> Additionally, there are the following extensions which are not covered by
> SUSE support agreements, available at no additional cost and without an
> extra registration key:
>   SUSE Package Hub: https://packagehub.suse.com/
>   SUSE Linux Enterprise Software Development Kit
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Paul Dembry 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 01:36 PM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> > Any progress is good progress.
> Unless you are a lemming :-)
> Paul
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
> Pace
> Sent: Monday, March 18, 2019 10:11 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Upgrade sles 12sp4 - sles 15
>
> Thank you, Lori -
> I tried the SUSEConnect --clean  and then register again - and now I have a
> different error message.
>
> The requested products 'Suse Package Hub 12 SP4 s390x' have not been
> activated on the system.
>
> So I need to go figure out what this means.
>
> Thank you again.  Any progress is good progress.
>
> On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi 
> wrote:
>
> > I had a problem opened with Microfocus and here is what we did to
> resolve:
> >
> > - Ran SUSEConnect --cleanup
> > - Re-Registered system into SCC
> > - Upgraded SLES12SP3 to SP4 via zypper migration
> > - Upgraded SLES12SP4 to SLES15 via off-line mode
> > - Cleaned up gpg key V# warning according
> >
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA&s=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk&e=
>
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
> > leter...@us.ibm.com IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/18/2019 10:00 AM
> > Subject:Re: Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
> > Product Registration.  It came back as already registered.  I then
> > used Register Again to make sure it was registered.
> >
> > I may either create a local SMT server, or just build a new SLES 15
> > and manually migrate.
> >
> > On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
> >
> > > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > > This is then end - the lines before this are the panel being
> displayed.
> > >
> > > I think there are a number of lines before then that would be
> > > useful, but given what you're showing, I have to ask if this system
> > > is registered, with either SCC or a local SMT server? The sense I'm
> > > getting is that YaST is asking the registration server what
> > > migration products are available for the currently installed
> > > product(s), and is getting a null answer, possibly because it's not
> registered:
> > > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
> >
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> > ine.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUF
> > vEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid
> > 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
> > >(31420) [Ruby]
> > > registration/registration.rb:182 Received possible migrations paths:
> > >[]*
> > >
> > >
> > > Mark Post
> > >
> > > 
> > > -- For LINUX-390 subscribe / signoff / archive access instructions,
> > > send email to lists...@vm.marist.edu with the message: INFO
> > > LINUX-390 or visit
> > >
> >
>

Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Lori Grimaldi
Maybe this will help:

   https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP3/

Additionally, there are the following extensions which are not covered by
SUSE support agreements, available at no additional cost and without an
extra registration key:
  SUSE Package Hub: https://packagehub.suse.com/
  SUSE Linux Enterprise Software Development Kit

Lori Grimaldi
Linux on zSeries Americas Team, Team Lead - Senior
IBM Services
Notes:  leter...@us.ibm.com
Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
Email Address: leter...@us.ibm.com
IBM





From:   Paul Dembry 
To: LINUX-390@VM.MARIST.EDU
Date:   03/18/2019 01:36 PM
Subject:Re: Upgrade sles 12sp4 - sles 15
Sent by:Linux on 390 Port 



> Any progress is good progress.
Unless you are a lemming :-)
Paul

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
Pace
Sent: Monday, March 18, 2019 10:11 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Upgrade sles 12sp4 - sles 15

Thank you, Lori -
I tried the SUSEConnect --clean  and then register again - and now I have a
different error message.

The requested products 'Suse Package Hub 12 SP4 s390x' have not been
activated on the system.

So I need to go figure out what this means.

Thank you again.  Any progress is good progress.

On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi  wrote:

> I had a problem opened with Microfocus and here is what we did to
resolve:
>
> - Ran SUSEConnect --cleanup
> - Re-Registered system into SCC
> - Upgraded SLES12SP3 to SP4 via zypper migration
> - Upgraded SLES12SP4 to SLES15 via off-line mode
> - Cleaned up gpg key V# warning according
>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.suse.com_releasenotes_x86-5F64_SUSE-2DSLES_15_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=Hqe7wtWVuyxouUKULbOQJQARQXQCGj0jhZvI_V86APA&s=tMAUzCDn-1yIZemens8r9HwK0cSyEf1A8pMtOLVAbmk&e=

>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address:
> leter...@us.ibm.com IBM
>
>
>
>
>
> From:   Mark Pace 
> To:     LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 10:00 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Thanks, Mark.  Unfortunately that was not the issue.  I used Yast
> Product Registration.  It came back as already registered.  I then
> used Register Again to make sure it was registered.
>
> I may either create a local SMT server, or just build a new SLES 15
> and manually migrate.
>
> On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>
> > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > This is then end - the lines before this are the panel being
displayed.
> >
> > I think there are a number of lines before then that would be
> > useful, but given what you're showing, I have to ask if this system
> > is registered, with either SCC or a local SMT server? The sense I'm
> > getting is that YaST is asking the registration server what
> > migration products are available for the currently installed
> > product(s), and is getting a null answer, possibly because it's not
registered:
> > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> ine.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUF
> vEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid
> 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
> >(31420) [Ruby]
> > registration/registration.rb:182 Received possible migrations paths:
> >[]*
> >
> >
> > Mark Post
> >
> > 
> > -- For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO
> > LINUX-390 or visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htb
> in_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3b
> hw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUj
> X1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For

Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Paul Dembry
> Any progress is good progress.
Unless you are a lemming :-)
Paul

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Pace
Sent: Monday, March 18, 2019 10:11 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Upgrade sles 12sp4 - sles 15

Thank you, Lori -
I tried the SUSEConnect --clean  and then register again - and now I have a 
different error message.

The requested products 'Suse Package Hub 12 SP4 s390x' have not been activated 
on the system.

So I need to go figure out what this means.

Thank you again.  Any progress is good progress.

On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi  wrote:

> I had a problem opened with Microfocus and here is what we did to resolve:
>
> - Ran SUSEConnect --cleanup
> - Re-Registered system into SCC
> - Upgraded SLES12SP3 to SP4 via zypper migration
> - Upgraded SLES12SP4 to SLES15 via off-line mode
> - Cleaned up gpg key V# warning according 
> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666 Email Address: 
> leter...@us.ibm.com IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 10:00 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Thanks, Mark.  Unfortunately that was not the issue.  I used Yast 
> Product Registration.  It came back as already registered.  I then 
> used Register Again to make sure it was registered.
>
> I may either create a local SMT server, or just build a new SLES 15 
> and manually migrate.
>
> On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>
> > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > This is then end - the lines before this are the panel being displayed.
> >
> > I think there are a number of lines before then that would be 
> > useful, but given what you're showing, I have to ask if this system 
> > is registered, with either SCC or a local SMT server? The sense I'm 
> > getting is that YaST is asking the registration server what 
> > migration products are available for the currently installed 
> > product(s), and is getting a null answer, possibly because it's not 
> > registered:
> > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com <
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainl
> ine.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUF
> vEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid
> 9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
> >(31420) [Ruby]
> > registration/registration.rb:182 Received possible migrations paths: 
> >[]*
> >
> >
> > Mark Post
> >
> > 
> > -- For LINUX-390 subscribe / signoff / archive access instructions, 
> > send email to lists...@vm.marist.edu with the message: INFO 
> > LINUX-390 or visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htb
> in_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3b
> hw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUj
> X1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent 
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htb
> in_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3b
> hw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUj
> X1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


--
The postings on this site are my own and don’t necessarily represent Mainline’s 
positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Mark Pace
Thank you, Lori -
I tried the SUSEConnect --clean  and then register again - and now I have a
different error message.

The requested products 'Suse Package Hub 12 SP4 s390x' have not been
activated on the system.

So I need to go figure out what this means.

Thank you again.  Any progress is good progress.

On Mon, Mar 18, 2019 at 12:36 PM Lori Grimaldi  wrote:

> I had a problem opened with Microfocus and here is what we did to resolve:
>
> - Ran SUSEConnect --cleanup
> - Re-Registered system into SCC
> - Upgraded SLES12SP3 to SP4 via zypper migration
> - Upgraded SLES12SP4 to SLES15 via off-line mode
> - Cleaned up gpg key V# warning according
> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To:     LINUX-390@VM.MARIST.EDU
> Date:   03/18/2019 10:00 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Thanks, Mark.  Unfortunately that was not the issue.  I used Yast Product
> Registration.  It came back as already registered.  I then used Register
> Again to make sure it was registered.
>
> I may either create a local SMT server, or just build a new SLES 15 and
> manually migrate.
>
> On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:
>
> > On 3/15/19 4:25 PM, Mark Pace wrote:
> > > This is then end - the lines before this are the panel being displayed.
> >
> > I think there are a number of lines before then that would be useful,
> > but given what you're showing, I have to ask if this system is
> > registered, with either SCC or a local SMT server? The sense I'm getting
> > is that YaST is asking the registration server what migration products
> > are available for the currently installed product(s), and is getting a
> > null answer, possibly because it's not registered:
> > *2019-03-15 16:23:16 <1> sles003.s390.mainline.com
> > <
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainline.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
> >(31420) [Ruby]
> > registration/registration.rb:182 Received possible migrations paths: []*
> >
> >
> > Mark Post
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Lori Grimaldi
I had a problem opened with Microfocus and here is what we did to resolve:

- Ran SUSEConnect --cleanup
- Re-Registered system into SCC
- Upgraded SLES12SP3 to SP4 via zypper migration
- Upgraded SLES12SP4 to SLES15 via off-line mode
- Cleaned up gpg key V# warning according
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/

Lori Grimaldi
Linux on zSeries Americas Team, Team Lead - Senior
IBM Services
Notes:  leter...@us.ibm.com
Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
Email Address: leter...@us.ibm.com
IBM





From:   Mark Pace 
To: LINUX-390@VM.MARIST.EDU
Date:   03/18/2019 10:00 AM
Subject:Re: Upgrade sles 12sp4 - sles 15
Sent by:Linux on 390 Port 



Thanks, Mark.  Unfortunately that was not the issue.  I used Yast Product
Registration.  It came back as already registered.  I then used Register
Again to make sure it was registered.

I may either create a local SMT server, or just build a new SLES 15 and
manually migrate.

On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:

> On 3/15/19 4:25 PM, Mark Pace wrote:
> > This is then end - the lines before this are the panel being displayed.
>
> I think there are a number of lines before then that would be useful,
> but given what you're showing, I have to ask if this system is
> registered, with either SCC or a local SMT server? The sense I'm getting
> is that YaST is asking the registration server what migration products
> are available for the currently installed product(s), and is getting a
> null answer, possibly because it's not registered:
> *2019-03-15 16:23:16 <1> sles003.s390.mainline.com
> <
https://urldefense.proofpoint.com/v2/url?u=http-3A__sles003.s390.mainline.com&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=tUid9VAs-uO5lMrs4DZMC2_yCwFqva2y_KKH03uf51Y&e=
>(31420) [Ruby]
> registration/registration.rb:182 Received possible migrations paths: []*
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=

>


--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=UeUdErz6SEwDmmv1KCoDqn6gCwC1beUjX1EFnrwpo5s&s=RDeB4YyOhULyuKMQKad_mcJ0VtMW6Ie5AzVj01arbR4&e=





--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-18 Thread Mark Pace
Thanks, Mark.  Unfortunately that was not the issue.  I used Yast Product
Registration.  It came back as already registered.  I then used Register
Again to make sure it was registered.

I may either create a local SMT server, or just build a new SLES 15 and
manually migrate.

On Fri, Mar 15, 2019 at 7:15 PM Mark Post  wrote:

> On 3/15/19 4:25 PM, Mark Pace wrote:
> > This is then end - the lines before this are the panel being displayed.
>
> I think there are a number of lines before then that would be useful,
> but given what you're showing, I have to ask if this system is
> registered, with either SCC or a local SMT server? The sense I'm getting
> is that YaST is asking the registration server what migration products
> are available for the currently installed product(s), and is getting a
> null answer, possibly because it's not registered:
> *2019-03-15 16:23:16 <1> sles003.s390.mainline.com
> (31420) [Ruby]
> registration/registration.rb:182 Received possible migrations paths: []*
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Post
On 3/15/19 4:25 PM, Mark Pace wrote:
> This is then end - the lines before this are the panel being displayed.

I think there are a number of lines before then that would be useful,
but given what you're showing, I have to ask if this system is
registered, with either SCC or a local SMT server? The sense I'm getting
is that YaST is asking the registration server what migration products
are available for the currently installed product(s), and is getting a
null answer, possibly because it's not registered:
*2019-03-15 16:23:16 <1> sles003.s390.mainline.com
(31420) [Ruby]
registration/registration.rb:182 Received possible migrations paths: []*


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
This is then end - the lines before this are the panel being displayed.

2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
ui/migration_repos_workflow.rb:337 Installed products: [#,
#]
2019-03-15 16:23:15 <2> sles003.s390.mainline.com(31420) [ui-shortcuts]
YShortcutManager.cc(checkShortcuts):85 Not enough widgets with valid
shortcut characters - no check
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/registration.rb:174 Offline migration for: #.
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:55 Current language: en_US
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:76 Language for HTTP requests set to "en-US"
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/registration.rb:308 Using custom registration URL: "
https://scc.suse.com";
2019-03-15 16:23:15 <1> sles003.s390.mainline.com(31420) [Ruby]
registration/helpers.rb:118 Boot reg_ssl_verify option: nil
*2019-03-15 16:23:16 <1> sles003.s390.mainline.com
(31420) [Ruby]
registration/registration.rb:182 Received possible migrations paths: []*
*2019-03-15 16:23:16 <3> sles003.s390.mainline.com
(31420) [Ruby]
ui/migration_repos_workflow.rb:342 No migration product found.*
2019-03-15 16:23:16 <1> sles003.s390.mainline.com(31420) [ui]
YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for
YPushButton "OK" at 0x3ff9c1b2b70 from function key F10


On Fri, Mar 15, 2019 at 4:03 PM Mark Pace  wrote:

> Thanks for the heads up, Mark.
>
> On Fri, Mar 15, 2019 at 2:43 PM Mark Post  wrote:
>
>> On 3/15/19 2:22 PM, Mark Pace wrote:
>> > That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
>> > the log will be a little smaller.
>>
>> In the case of an upgrade (or any installation for that matter), when
>> you're booting the installer for the new version, those logs won't be
>> the same as what is in the /var/log/ directory on the "real" system.
>>
>> That means that to be able to look at them, you need to have "usessh"
>> and "sshpassword" is your parameter file, even if you're using VNC or
>> some other method to do the actual install/upgrade. Then, when the error
>> comes up, you can look at /var/log/ which will be in the ramdisk, as
>> opposed to /mnt/var/log/ which will be on the "real" system.
>>
>>
>> Mark Post
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
Thanks for the heads up, Mark.

On Fri, Mar 15, 2019 at 2:43 PM Mark Post  wrote:

> On 3/15/19 2:22 PM, Mark Pace wrote:
> > That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
> > the log will be a little smaller.
>
> In the case of an upgrade (or any installation for that matter), when
> you're booting the installer for the new version, those logs won't be
> the same as what is in the /var/log/ directory on the "real" system.
>
> That means that to be able to look at them, you need to have "usessh"
> and "sshpassword" is your parameter file, even if you're using VNC or
> some other method to do the actual install/upgrade. Then, when the error
> comes up, you can look at /var/log/ which will be in the ramdisk, as
> opposed to /mnt/var/log/ which will be on the "real" system.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Post
On 3/15/19 2:22 PM, Mark Pace wrote:
> That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
> the log will be a little smaller.

In the case of an upgrade (or any installation for that matter), when
you're booting the installer for the new version, those logs won't be
the same as what is in the /var/log/ directory on the "real" system.

That means that to be able to look at them, you need to have "usessh"
and "sshpassword" is your parameter file, even if you're using VNC or
some other method to do the actual install/upgrade. Then, when the error
comes up, you can look at /var/log/ which will be in the ramdisk, as
opposed to /mnt/var/log/ which will be on the "real" system.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
That log is nearly 2MB.  I think I'll erase it and try again.  Hopefully
the log will be a little smaller.

On Fri, Mar 15, 2019 at 11:31 AM Mark Post  wrote:

> On 3/15/19 9:50 AM, Mark Pace wrote:
> > Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> > Upgrade=1
> >
> > Doing upgrade via VNC -
> >
> > Everything looks pretty normal at the beginning. But once I select the
> > partition to be upgraded I receive a pop-up - Error No migration product
> > found.
>
> This is the first I've heard of it. One of our customers does a lot of
> testing of just this scenario during the beta testing, so I'm a little
> surprised to hear of problems doing that.
>
> The logs under /var/log/YaST2/ would provide some insight into what YaST
> is trying to do before it gives up and displays that dialog box.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
My boot is on the / filesystem  - there is 3.5GB available

Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda1 6.7G  2.9G  3.5G  45% /

On Fri, Mar 15, 2019 at 11:28 AM Lori Grimaldi  wrote:

> What about increasing the /boot disk?
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/15/2019 11:18 AM
> Subject:Re: Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Yes, I had done a
> zypper up   before hand, and rebooting to be sure it was up to date.
>
> On Fri, Mar 15, 2019 at 10:39 AM Lori Grimaldi 
> wrote:
>
> > Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
> > cylinder /boot disk also.
> >
> > Lori Grimaldi
> > Linux on zSeries Americas Team, Team Lead - Senior
> > IBM Services
> > Notes:  leter...@us.ibm.com
> > Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> > Email Address: leter...@us.ibm.com
> > IBM
> >
> >
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@VM.MARIST.EDU
> > Date:   03/15/2019 09:53 AM
> > Subject:Upgrade sles 12sp4 - sles 15
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> > Upgrade=1
> >
> > Doing upgrade via VNC -
> >
> > Everything looks pretty normal at the beginning. But once I select the
> > partition to be upgraded I receive a pop-up - Error No migration product
> > found.
> >
> > On the CMS console I am also receive message - warning: Unsupported
> version
> > of key: V3
> >
> > Once I click OK it returns to the Select for Update panel.
> >
> > Rinse and repeat.
> >
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc&s=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE&e=
>
> >
> >
> >
> >
> >
> > --
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> > visit
> >
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA&s=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ&e=
>
> >
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA&s=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ&e=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Marcy Cortes
What does “zypper pd” show?


From: Mark Post mailto:mp...@suse.com>>
Date: Friday, Mar 15, 2019, 8:30 AM
To: LINUX-390@VM.MARIST.EDU 
mailto:LINUX-390@VM.MARIST.EDU>>
Subject: Re: [LINUX-390] Upgrade sles 12sp4 - sles 15

On 3/15/19 9:50 AM, Mark Pace wrote:
> Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> Upgrade=1
>
> Doing upgrade via VNC -
>
> Everything looks pretty normal at the beginning. But once I select the
> partition to be upgraded I receive a pop-up - Error No migration product
> found.

This is the first I've heard of it. One of our customers does a lot of
testing of just this scenario during the beta testing, so I'm a little
surprised to hear of problems doing that.

The logs under /var/log/YaST2/ would provide some insight into what YaST
is trying to do before it gives up and displays that dialog box.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Post
On 3/15/19 9:50 AM, Mark Pace wrote:
> Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> Upgrade=1
>
> Doing upgrade via VNC -
>
> Everything looks pretty normal at the beginning. But once I select the
> partition to be upgraded I receive a pop-up - Error No migration product
> found.

This is the first I've heard of it. One of our customers does a lot of
testing of just this scenario during the beta testing, so I'm a little
surprised to hear of problems doing that.

The logs under /var/log/YaST2/ would provide some insight into what YaST
is trying to do before it gives up and displays that dialog box.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Lori Grimaldi
What about increasing the /boot disk?

Lori Grimaldi
Linux on zSeries Americas Team, Team Lead - Senior
IBM Services
Notes:  leter...@us.ibm.com
Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
Email Address: leter...@us.ibm.com
IBM





From:   Mark Pace 
To: LINUX-390@VM.MARIST.EDU
Date:   03/15/2019 11:18 AM
Subject:Re: Upgrade sles 12sp4 - sles 15
Sent by:Linux on 390 Port 



Yes, I had done a
zypper up   before hand, and rebooting to be sure it was up to date.

On Fri, Mar 15, 2019 at 10:39 AM Lori Grimaldi  wrote:

> Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
> cylinder /boot disk also.
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/15/2019 09:53 AM
> Subject:Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> Upgrade=1
>
> Doing upgrade via VNC -
>
> Everything looks pretty normal at the beginning. But once I select the
> partition to be upgraded I receive a pop-up - Error No migration product
> found.
>
> On the CMS console I am also receive message - warning: Unsupported
version
> of key: V3
>
> Once I click OK it returns to the Select for Update panel.
>
> Rinse and repeat.
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc&s=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE&e=

>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA&s=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ&e=

>


--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=3cxl5g-G--2vqbnwWSlnZuVYUi3Q7PcNlmXbfvZpIUA&s=hvJXb4719rzVv1aY5HFGoSTruRo4PIhYuw-BG1WmGTQ&e=





--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
Yes, I had done a
zypper up   before hand, and rebooting to be sure it was up to date.

On Fri, Mar 15, 2019 at 10:39 AM Lori Grimaldi  wrote:

> Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
> cylinder /boot disk also.
>
> Lori Grimaldi
> Linux on zSeries Americas Team, Team Lead - Senior
> IBM Services
> Notes:  leter...@us.ibm.com
> Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
> Email Address: leter...@us.ibm.com
> IBM
>
>
>
>
>
> From:   Mark Pace 
> To: LINUX-390@VM.MARIST.EDU
> Date:   03/15/2019 09:53 AM
> Subject:Upgrade sles 12sp4 - sles 15
> Sent by:Linux on 390 Port 
>
>
>
> Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
> Upgrade=1
>
> Doing upgrade via VNC -
>
> Everything looks pretty normal at the beginning. But once I select the
> partition to be upgraded I receive a pop-up - Error No migration product
> found.
>
> On the CMS console I am also receive message - warning: Unsupported version
> of key: V3
>
> Once I click OK it returns to the Select for Update panel.
>
> Rinse and repeat.
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc&s=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE&e=
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Lori Grimaldi
Have you patched SLES 12 SP4 before upgrading?  I had to add a 1500
cylinder /boot disk also.

Lori Grimaldi
Linux on zSeries Americas Team, Team Lead - Senior
IBM Services
Notes:  leter...@us.ibm.com
Office/Fax: (845) 336-0930  Cell/Text: (845) 594-3666
Email Address: leter...@us.ibm.com
IBM





From:   Mark Pace 
To: LINUX-390@VM.MARIST.EDU
Date:   03/15/2019 09:53 AM
Subject:Upgrade sles 12sp4 - sles 15
Sent by:Linux on 390 Port 



Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
Upgrade=1

Doing upgrade via VNC -

Everything looks pretty normal at the beginning. But once I select the
partition to be upgraded I receive a pop-up - Error No migration product
found.

On the CMS console I am also receive message - warning: Unsupported version
of key: V3

Once I click OK it returns to the Select for Update panel.

Rinse and repeat.


--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marist.edu_htbin_wlvindex-3FLINUX-2D390&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=0O2Q0N3bhw8wToDxvSVQtC4OUFvEgeKgNzzJ7wh_xG4&m=U_1sDo75GuRPuk9FncSLcW9eeFWLSAuslv6VwtHl1Vc&s=nuKt8NpKQobxZbUG6vADHnV2iOrK-pbFzbNvr1SEuYE&e=





--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Upgrade sles 12sp4 - sles 15

2019-03-15 Thread Mark Pace
Has anyone done a successful upgrade from sles12 sp4 to sles 15 via
Upgrade=1

Doing upgrade via VNC -

Everything looks pretty normal at the beginning. But once I select the
partition to be upgraded I receive a pop-up - Error No migration product
found.

On the CMS console I am also receive message - warning: Unsupported version
of key: V3

Once I click OK it returns to the Select for Update panel.

Rinse and repeat.


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390