SLES/Suse

Updating SLES SP1 to SP2 via zypper

Posted by phatdee on July 9, 2012
Posted in: SLES/Suse. Tagged: , , , . 3 comments

Here’s an easier way without needing to go through lame ass yast.

 

Online Migration with zypper¶

  1. When all requirements are met (see Section 7.5.1.1, “Requirements”), the “products” needed for the online migration have been added to /etc/products.d. Get a list of these products by running the following command:

    This command should at least return SUSE_SLES-SP2-migration. Depending on the scope of your installation, more products may be listed.
  2. Install the migration products retrieved on the previous step with the command zypper in -t product LIST_OF_PRODUCTS, for example
  3. Register the products installed in the previous step in order to get the respective update channels:
  4. Refresh repositories and services again:
  5. Check the list of repositories you can retrieve with zypper lr. At least the following repositories need to be Enabled:
    • SLES11-SP1-Pool
    • SLES11-SP1-Updates
    • SLES11-SP2-Core
    • SLES11-SP2-Updates

    Depending on the scope of your installation, further repositories for add-on products or extensions need to be enabled.

    If one of these repositories is not enabled (the SP2 ones are not enabled by default when following this workflow), enable them with zypper modifyrepo –enable REPOSITORY ALIAS, for example:

    If your setup contains 3rd party repositories that may not be compatible with SP2, disable them with zypper modifyrepo –disable REPOSITORY ALIAS.

  6. Now everything is in place to perform the distribution upgrade with zypper dup –from REPO 1 –from REPO 2 .... Make sure to list all needed repositories with --from, for example:

    Confirm with y to start the upgrade.

  7. Upon completion of the distribution upgrade from the previous step, a Minimal Migration has been performed (a minimal set of packages has been updated to the latest SP2 level). Skip this step if you do not intend to do a Full Migration.

    In order to do a Full Migration (updates all packages to the latest SP2 level), run the following command:

  8. Now that the upgrade to SP2 has been completed, you need to re-register your product:

  9. Last, reboot your system.
  10. Your system has been successfully updated to Service Pack 2.

 

Upgrading SLES 11 SP1 to SP2

Posted by phatdee on July 6, 2012
Posted in: SLES/Suse. Tagged: , , . 1 comment

I just spent the last day literally trying to fix a broken NIC after upgrading one of our SLES 11 SP1 systems to SP2.   I used the recommended method of using yast2 wagon.   Even though, I can’t stand using yast normally and I avoid it at all costs, figured I’d give it a shot here and once it worked figured out another method to avoid having to yast2 wagon on ~1000 hosts..  Anyways, hats off, after going through all the requires like registering the system with NCC etc..I was able to successfully (at least I thought) update the system to SP2.  Yay!

Yeah, the shit pretty much hit the fan when I went to reboot the system for the first time and yeah the fucking ethernet was no longer recognized.   Thinking no biggie, just comment out /etc/udev/rules.d files in 70-persisant-net reboot..and all should be fine.  Reboot, not so fine..still unable to find.

Was getting this little message on the bootup

Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-eth0 instead

 

The interesting part was every place I looked online and everyone was saying this is just a “warning”, yeah for what ever reasons, mine wasn’t a warning.I wish it would have been much easier than having to spend the next 10 hours in Vsphere console .

I could get the system to recognize the e1000 driver manually , but no matter what I did to try to load the module during bootup it would fail each and every reboot.  yast2 –>system–>editor sysconfig–>kernel–>load modules at bootup=e1000. save .exit . reboot.  FAIL

/etc/modprode.conf.local   FAIL

lsmod  – shows e1000, did it work. nope FAIL  try rmooving it rmmod e1000; re-add insmod e1000;   FAIL

boot.local  FAIL

After manually getting ntwork up, downloaded new source drivers for e1000 recompiled and made for same kernel everything…did that work NOPE FAIL

In vmware tried removing e1000 and just going with vmxnet3.   FAIL

installed vmware-tools, was trying to compile for 2.6.32 kernel ….FAIL

smashed keyboard   – SUCCESSFUL

So after all that bullshit, I ended up removing ALL nics from vmware edit settings, rebooted the box with no nics, then halted , re-added the e1000, booted and holy SHIT it worked.

fuck you Novell!   I’ve been plagued with your shit since SLES9.3.  Granted this was only the first system that I tried to update to SP2 and maybe the rest will not go so bad.  And if that’s the case, then all I can still say is fuck you Novell!   I’ve stuck with you, through thick and thin , but enough is enough.  Moving onto something that just works.  And SLES is not something that just works.