Red Hat Summit4.3. Communication Issue after Node Host Reboot
After rebooting a node host, the
rhc app create command can fail to create an application, resulting in the following error:
An error occurred while communicating with the server. This problem may only be temporary. Check that you have correctly specified your OpenShift server 'https://broker.example.com/broker/rest/domain/domain-name/applications'.
However, when verifying MCollective connectivity,
oo-mco commands on the broker host may continue to find the rebooted node host without any issues:
# oo-mco ping
node.example.com time=170.19 ms
---- ping statistics ----
1 replies max: 170.19 min: 170.19 avg: 170.19
The application creation failure can be due to a communication issue between ActiveMQ on the broker host (or dedicated ActiveMQ broker, if applicable) and MCollective on the rebooted node host. To resolve this issue, restart the
activemq service:
# service activemq restartNote
See https://bugzilla.redhat.com/show_bug.cgi?id=1028382 for more information on this issue and the described workaround.
