OES2018 yast2-oes-wagon

I went to patch my OES2018 test server today. It first wanted to update the package manager, which I did. Then I reran the command "zypper up -t patch", I got the following:

Problem: yast2-oes-registration-3.1.193-17.4.noarch requires yast2-oes-wagon, but this requirement cannot be provided
uninstallable providers: yast2-oes-wagon-3.1.2-4.2.noarch[nu_novell_com:OES2018-Updates]
Solution 1: Following actions will be done:
deinstallation of yast2-oes-registration-3.1.193-15.1.noarch
deinstallation of product:Open_Enterprise_Server-2018-0.x86_64
deinstallation of patterns-oes-novell-yast2-12-18.1.x86_64
deinstallation of patterns-oes-novell-base-12-18.1.x86_64
deinstallation of patterns-oes-novell-cifs-12-18.1.x86_64
deinstallation of patterns-oes-novell-edirectory-12-18.1.x86_64
deinstallation of patterns-oes-novell-imanager-12-18.1.x86_64
deinstallation of patterns-oes-novell-iprint-12-18.1.x86_64
deinstallation of patterns-oes-novell-lum-12-18.1.x86_64
deinstallation of patterns-oes-novell-ncpserver-12-18.1.x86_64
deinstallation of patterns-oes-novell-nrm-12-18.1.x86_64
deinstallation of patterns-oes-novell-nss-12-18.1.x86_64
deinstallation of patterns-oes-novell-nssad-12-18.1.x86_64
deinstallation of patterns-oes-novell-sms-12-18.1.x86_64
deinstallation of product:Open_Enterprise_Server-2018-0.x86_64
Solution 2: install yast2-oes-wagon-3.1.2-4.2.noarch (with vendor change)
SUSE LINUX Products GmbH, Nuernberg, Germany --> Novell, Inc.
Solution 3: do not install patch:oes2018-2018-24-1.noarch
Solution 4: break yast2-oes-registration-3.1.193-17.4.noarch by ignoring some of its dependencies


It looks like Solution 1 would uninstall OES leaving me with just a SLES server!!! What is the correct choice here? This is a completely vanilla OES server. No special installs or anything. Why would it have to uninstall OES?

Thanks,

Dan
  • While i don't get this message on a test box (maybe yours is an upgraded one) i'm pretty sure that "Solution 2" will be the way to go here. It's just about a vendor change (from SUSE to Novell) for the wagon stack which will be needed for upcoming OES2018SP1.
  • Thanks for the help, Mathias. It would be nice if they didn't lead off with the first solution of uninstalling OES! I'll try solution 2. I don't know what it means to have a 'vendor change' though and have no idea what a wagon stack is. Once again Linux is as cryptic as possible.

    Dan
  • Mathias, is there any way to get a confirmation from Micro Focus that nothing will break in OES if I chose solution 2? And why make it Solution 2 if this is the least impactful of the changes? Normally you would make the default or 'best' choice Solution 1 but here it looks like Solution 1 would thoroughly trash your OES server.

    I really don't want to go ahead with this update if it will cause problems.

    Thanks,

    Dan
  • dchunt wrote:

    > I really don't want to go ahead with this update if it will cause
    > problems.


    Have you checked to ensure you are using the correct repositories?

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
  • On 06.12.2018 20:24, dchunt wrote:
    >
    > Thanks for the help, Mathias. It would be nice if they didn't lead off
    > with the first solution of uninstalling OES!


    That's not "them", that is some weird coded logic in zypper.

    > I'll try solution 2. I
    > don't know what it means to have a 'vendor change' though and have no
    > idea what a wagon stack is. Once again Linux is as cryptic as possible.


    Each package comes with a vendor string to it, and changes to that
    trigger an error so that the user is asked what to do. And yes, that
    dialog is junk, and as counter-intuitive as possible.

    Wagon is the yast module used for service pack updates. (Don't ask why
    it's named like this).

    And yes, solution 2 is almost 99.9% the right one here, *but* I've never
    seen that message on any of my OES2018 servers (and they're patched up),
    so I really wonder why you see it.

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • I'd guess you'd have to open a service request to get an official statement. Apparently noone of us is seeing this behaviour and this doesn't surprise me too much as on a system which has initially been installed with OES2018 there shouldn't be an existing wagon rpm.
    If your sytem has been upgraded from let's say OES2015 there might be an older, existing one which could trigger the vendor change message. As Kevin states you should also check your repos. There should NOT be a "native" SLES channel, just
    OES2018-Pool
    OES2018-Updates
    OES2018-SLES12-SP2-Pool
    OES2018-SLES12-SP2-Updates

    Nevertheless i'm very confident that the option to accept the vendor change will simply do it.
  • In article <rwhOD.2032$C62.215@novprvlin0914.provo.novell.com>, Massimo
    Rosen wrote:
    > Wagon is the yast module used for service pack updates. (Don't ask why
    > it's named like this).


    My guess is that it has to do with moving vans, to take you from one
    version to the next, as we use it to move to the next SP level
    From: old American western way of the wagon trains used.

    > And yes, solution 2 is almost 99.9% the right one here, *but* I've never
    > seen that message on any of my OES2018 servers (and they're patched up),
    > so I really wonder why you see it.

    I haven't see it either, but it is clearly installed on them

    # rpm -qa |grep wagon
    yast2-oes-wagon-control-OES-3.1.2-4.2.noarch
    yast2-oes-wagon-3.1.2-4.2.noarch



    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please show
    your appreciation by clicking on the star below. Thanks!

  • Sorry for the delay in getting back to you. Here is what I see when I do a "zypper lr". I left the 'Alias' column off so things would fit better here.

    Name | Enabled | GPG Check | Refresh
    -------------------------------------------------------- --------- ----------- --------
    OES2018-2018-0 | No | ---- | ----
    OES2018-Pool | Yes | (r ) Yes | Yes
    OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Pool | No | ---- | ----
    OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Updates | No | ---- | ----
    OES2018-SLE-Manager-Tools-12-SP2-Pool | No | ---- | ----
    OES2018-SLE-Manager-Tools-12-SP2-Updates | No | ---- | ----
    OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Pool | No | ---- | ----
    OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Updates | No | ---- | ----
    OES2018-SLE-Module-Containers-12-SP2-Pool | Yes | (r ) Yes | Yes
    OES2018-SLE-Module-Containers-12-SP2-Updates | Yes | (r ) Yes | Yes
    OES2018-SLE-Modules-Web-Scripting-12-SP2-Pool | No | ---- | ----
    OES2018-SLE-Modules-Web-Scripting-12-SP2-Updates | No | ---- | ----
    OES2018-SLE-SDK-12-SP2-Debuginfo-Pool | No | ---- | ----
    OES2018-SLE-SDK-12-SP2-Debuginfo-Updates | No | ---- | ----
    OES2018-SLE-SDK-12-SP2-Pool | No | ---- | ----
    OES2018-SLE-SDK-12-SP2-Updates | No | ---- | ----
    OES2018-SLES12-SP2-Debuginfo-Pool | No | ---- | ----
    OES2018-SLES12-SP2-Debuginfo-Updates | No | ---- | ----
    OES2018-SLES12-SP2-Pool | Yes | (r ) Yes | Yes
    OES2018-SLES12-SP2-Updates | Yes | (r ) Yes | Yes
    OES2018-Updates | Yes | (r ) Yes | Yes


    So, there are only 'OES2018-* entries. Why are most of the repositories not enabled? Should they all be enabled?

    Also, these servers have been upgraded from earlier versions of SLES/OES. Have all of you guys only been working on servers that had OES2018 newly installed?

    Thanks,

    Dan
  • Man I deliberately put the list in Courier New so it would line up but when I posted it, it reverted to proportional font. That stinks.

    Dan
  • dchunt;2493122 wrote:
    Man I deliberately put the list in Courier New so it would line up but when I posted it, it reverted to proportional font. That stinks.

    Dan


    Hi Dan,

    There is an easy solution...

    If you click on the Advanced button at the lower right below where you compose your message you will be presented with additional formatting options. The one you want is # (Wrap
     tags around selected text). 
     tags will ensure a fixed font is used and will prevent lines from wrapping. 

    You can experiment without actually posting by using the Preview Post button which is available when you switch to advanced mode.