Collection of side effects

[schaefi]

After the Migration

• Configuration files marked as %config in spec files will have a .rpmnew version but won't be replaced. It's in the responsibility of the customer to adapt those. Example: custom /etc/motd file in pubcloud images

• Repositories without an upgrade path stay in the migrated system and are outdated. It's a user responsibility to update those to point to the new distribution if required at all. Example: static nvidia repos in pubcloud images

• Instance metadata in the cloud console will still point to the old system. If you run a sles12 instance in the cloud and migrate it, only the system itself knows it got migrated. But the cloud console will not be able to show you a change of the operating system. Example: See AMI ID in EC2 console of a sles12 on demand image after migration to sle15. There is nothing we can do against it

Please add your findings here

[schaefi]

In reference to #55 we don't support the migration on systems that uses a root filesystem or setup which is not directly reachable from the grub bootloader. The loopback boot support used with the migration must be able to load the image from the root filesystem. If this is not possible for reasons shown in the following list, the migration system will not boot:

• unsupported fs from the grub space
• encrypted root filesystem

[schaefi]

• No support for upgrading intermediate distribution states like Beta or RC.

[schaefi]

• As stated previously I consider a 12 Sp1 -> SLE 15 upgrade out of scope. It also breaks our advertised "skip a service pack" capabilities, SP1 to 15 upgrade would skip 3 service packs.