Improvements for migration instructions #4129
Description
Documentation Update Required
There are some inconsistencies or gaps on Legacy Uyuni Server Migration to Container
What does the documentation say now?
First, there is a box "Procedure: Initial Preparation on the Legacy Server" about how to shut down services on the old Uyuni, however, as the same page says, there is no need to shut down services during the prepare phase and even in the final migration, the current mgradm seems to shut down the services itself, so I think that box should be deleted. Instead, as the migration seems to fail in many cases and after that, the source system has both Postgres and spacewalk-services stopped, there could be a note how to start them if the final migration fails: sudo service postgresql start and sudo spacewalk-service start for instance.
Second, mgr-storage-server part should mention that the device must have no filesystem, it fails if there already is an XFS filesystem, for instance. At least I made the mistake to format and mount them while installing Tumbleweed.
Third, mgradm migrate command kept asking for CA password, it is not mentioned in the documentation and at least I was puzzled whether
- CA password of the source system should be entered
- a new secure CA password should be entered (but why would it ask it every time with --prepare flag?)
- it is a known bug and it should not ask CA password, at least not before the final migration
Finally, at least based on my experience, mgradm migrate seems to fail very often, an up-to-date list of known issues and straight links how to report issues on mgradm itself or in the documentation would be helpful.
What change is required?
Clarifications for the previous, whether there is no need to manually shut down services on the source, note that mgr-storage-server requires a device with no filesystem and some note about CA password.