IBM Cloud Infrastructure Center GUI login failed with 504 error code after management node is restarted

Cannot log in to the IBM® Cloud Infrastructure Center GUI. The web page hangs for about 10 - 15 minutes and eventually fails with error code 504 after the management node is restarted. Error log in /etc/nova/nova-api.log on management node:

Aug 16 16:34:00 cic4mgt.fpet.pokprv.stglabs.ibm.com systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 16:34:00 cic4mgt.fpet.pokprv.stglabs.ibm.com systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com systemd[1]: rabbitmq-server.service: Service RestartSec=10s expired, scheduling restart.
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com systemd[1]: rabbitmq-server.service: Scheduled restart job, restart counter is at 85.
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com rabbitmq-server[34479]: 2022-08-16 16:34:11.544178
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com rabbitmq-server[34479]:     args: []
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com rabbitmq-server[34479]:     format: "Can't set short node name!\nPlease check your configuration\n"
Aug 16 16:34:11 cic4mgt.fpet.pokprv.stglabs.ibm.com rabbitmq-server[34479]:     label: {error_logger,info_msg}

The error for this issue is caused by a mismatch of information in the /etc/rabbitmq/rabbitmq-env.conf with the management node configuration during the RabbitMQ service restart.

Check whether the file /etc/rabbitmq/rabbitmq-env.conf exists on the management node. Delete the file if it exists. Restart the RabbitMQ service by using icic-services rabbitmq restart .