N->O After successful upgrade of the undercloud rabbitmq is non functionning.

Bug #1668910 reported by Sofer Athlan-Guyot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Won't Fix
Wishlist
Unassigned

Bug Description

Hi,

Install newton and upgrade the undercloud. Then the epmd socket is in error:

    ● epmd@0.0.0.0.socket loaded failed failed Erlang Port Mapper Daemon Activation Socket

I had to:

   systemctl stop rabbitmq

Get the pid of the left epmd process:

   ps fauxww | grep rabbitmq

kill it

   kill 11268

and then restart rabbitmq:

   systemctl restart rabbitmq-server

So, I think there is a problem during the upgrade where the rabbitmq process is not "properly" restarted.

Can anybody else check if it has the same problem with epmd socket ?

Revision history for this message
Michele Baldessari (michele) wrote :

I am moderately sure I have seen this also on fresh deploys and if systemctl status rabbitmq-server is active then we should be okay. I will double-check on new deployments.

Revision history for this message
Michele Baldessari (michele) wrote :

So I checked from an older newton undercloud sosreport and I have:
sos_commands/systemd/systemctl_list-units_--failed:* epmd@0.0.0.0.socket loaded failed failed Erlang Port Mapper Daemon Activation Socket
sos_commands/systemd/systemctl_list-units_--all: epmd@0.0.0.0.service loaded inactive dead Erlang Port Mapper Daemon
sos_commands/systemd/systemctl_list-units_--all: system-epmd.slice loaded inactive dead system-epmd.slice

So this is something that is just like that all the time, probably. Worth asking eck or peter about it though.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
Changed in tripleo:
importance: Critical → Low
Revision history for this message
Emilien Macchi (emilienm) wrote :

It sounds like the CI job that test undercloud upgrades doesn't hit it or?

See nova-scheduler:
http://logs.openstack.org/52/439052/2/check/gate-tripleo-ci-centos-7-undercloud-upgrades-nv/c9f6b7a/logs/var/log/nova/nova-scheduler.txt.gz#_2017-02-28_17_32_16_254

After the upgrade, nova is able to reconnect to rabbitmq.

Changed in tripleo:
importance: Low → High
Revision history for this message
Michele Baldessari (michele) wrote :

yeah i think this epmd socket activation is a false alarm. as long as rabbitmq is up it is all good as erlang will start the listener anyway. It'd be nice to remove the failed status, but nothing major here.

Changed in tripleo:
milestone: ocata-rc2 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Revision history for this message
Sofer Athlan-Guyot (sofer-athlan-guyot) wrote :

So yeah, it would be nice to get rid of the this false alarm in the systemd listing.

Changed in tripleo:
importance: High → Wishlist
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Revision history for this message
Sofer Athlan-Guyot (sofer-athlan-guyot) wrote :

Well, this is not a really important issue and may not be relevant anymore.

Changed in tripleo:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.