Section Number and Name: 3.6. Migrating from CFME 5.6 to 5.9
Describe the issue: It seems with the recent ruby update to 2.3.6 there is some additional change that affects the evm process starting up, due to a df command run by evm which hangs indefinitely due to package/location changes.
● evmserverd.service - EVM server daemon
Loaded: loaded (/usr/lib/systemd/system/evmserverd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-04-18 06:46:40 EDT; 6min ago
Process: 49233 ExecStart=/bin/sh -c /bin/evmserver.sh start (code=exited, status=0/SUCCESS)
Main PID: 49258 (ruby)
├─49258 MIQ Server
└─50712 df --all --local --human-readable --print-type
Suggestions for improvement: Simply rebooting the appliance fixes the location/package change issues and allows evm to start.
I suggest we add an appliance reboot step to all current migration procedures to overcome this issue. So to be sure lets add a step to reboot the appliance after starting evmserverd in each migration section in all the above docs.
So all these migration sections:
migrating_to_red_hat_cloudforms_4.2 5.5/5.6 - 5.7
migrating_to_red_hat_cloudforms_4.5 5.6/5.7 - 5.8
migrating_to_red_hat_cloudforms_4.6 5.5/5.6/5.7/5.8 - 5.9
this should then cover any CFME version a customer may be running which may not have the latest ruby update yet.
I have tested 5.6 to 126.96.36.199, 188.8.131.52 and 184.108.40.206 which have the latest ruby 2.3.6 all these see the same failing evm result and are fixed by an appliance reboot.
This looks like this issue . I was able to reproduce the same strace on an appliance with the issue. When we update we would need to reboot to start using the new version of systemd to get the fix applied to the running services.
This looks good to me, rebooting both VMDB and non-VMDB is correct.