Description of problem: Running an update from z10 to passed_phase2, after rabbitmq was updated to rabbitmq-server.x86_64 0:3.7.28-2.el7ost from rabbitmq-server-3.6.15-4.el7ost.noarch 2021-05-05 18:26:29 | 2021-05-05 18:26:29,321 INFO: ---> Package rabbitmq-server.noarch 0:3.6.15-4.el7ost will be updated 2021-05-05 18:26:29 | 2021-05-05 18:26:29,322 INFO: ---> Package rabbitmq-server.x86_64 0:3.7.28-2.el7ost will be an update We get an systemd unit error trying to restart epmd. 2021-05-05 18:39:42 | 2021-05-05 18:39:42,339 INFO: dib-run-parts Wed May 5 18:39:42 UTC 2021 Running /usr/libexec/os-refresh-config/configure.d/40-stop-running-epmd 2021-05-05 18:39:42 | 2021-05-05 18:39:42,346 INFO: + RESTART_RABBITMQ= 2021-05-05 18:39:42 | 2021-05-05 18:39:42,346 INFO: + systemctl is-active rabbitmq-server 2021-05-05 18:39:42 | 2021-05-05 18:39:42,353 INFO: active 2021-05-05 18:39:42 | 2021-05-05 18:39:42,353 INFO: + RESTART_RABBITMQ=yes 2021-05-05 18:39:42 | 2021-05-05 18:39:42,354 INFO: + systemctl stop rabbitmq-server 2021-05-05 18:39:47 | 2021-05-05 18:39:47,271 INFO: + pgrep -u rabbitmq -f 'epmd.*-daemon' 2021-05-05 18:39:47 | 2021-05-05 18:39:47,271 INFO: + xargs -r kill 2021-05-05 18:39:47 | 2021-05-05 18:39:47,290 INFO: + systemctl try-restart 'epmd@*' 2021-05-05 18:39:47 | 2021-05-05 18:39:47,304 INFO: Failed to try-restart epmd.0.0.service: Unit is not loaded properly: Invalid argument. 2021-05-05 18:39:47 | 2021-05-05 18:39:47,304 INFO: See system logs and 'systemctl status epmd.0.0.service' for details. 2021-05-05 18:39:47 | 2021-05-05 18:39:47,305 INFO: [2021-05-05 18:39:47,304] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1] 2021-05-05 18:39:47 | 2021-05-05 18:39:47,306 INFO: 2021-05-05 18:39:47 | 2021-05-05 18:39:47,306 INFO: [2021-05-05 18:39:47,305] (os-refresh-config) [ERROR] Aborting... 2021-05-05 18:39:47 | 2021-05-05 18:39:47,317 DEBUG: An exception occurred
For Update the workaround would be: - run the undercloud update, let it fails, run the systemctl daemon-reload command, and run it again. For FFU from 10-13, the workaround would be the same.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 13.0 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2385