RabbitMQ is not using erlang port mapper managed by systemd

Bug #1582265 reported by Alexey Lebedeff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Alexey Lebedeff
Mitaka
Won't Fix
Medium
Alexey Lebedeff
Newton
Confirmed
Medium
Alexey Lebedeff

Bug Description

Detailed bug description:
  After installing master node from fuel-9.0-mos-361-2016-05-14_12-18-00.iso, it could be seen that epmd (erlang port mapper) is running under 'rabbitmq' user, while it should run under separated user 'epmd' and be managed by systemd.

Steps to reproduce:
 Just install the master node

Expected results:
  "ps axu | grep epmd" should report epmd as a process running under 'epmd' user

Actual result:
 "ps axu | grep epmd" shows that epmd is running under 'rabbitmq' user
 <put your information here>

Reproducibility:
 100%

Impact:
 It should have no impact on completely standard installation. But any attempt to mess with additional erlang-based software can go wrong, and this can cause some random and hard-to-debug failures.

Description of the environment:
 rabbitmq-server packages version is 3.6.1-6.el7~mos1

Additional info:
 Upstream fix https://github.com/rabbitmq/rabbitmq-server/pull/801

Changed in mos:
importance: Undecided → Medium
assignee: nobody → Alexey Lebedeff (alebedev-a)
status: New → In Progress
status: In Progress → New
status: New → In Progress
milestone: none → 10.0
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Change abandoned on packages/trusty/rabbitmq-server (master)

Change abandoned by Alexey Lebedeff <email address hidden> on branch: master
Review: https://review.fuel-infra.org/20731
Reason: Test are moved to separate repository

no longer affects: mos/9.x
no longer affects: mos/10.0.x
no longer affects: mos
tags: added: 10.0-reviewed
Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

We discussed the issue with Alexey and decided that we will not make that change in 9.x, where we still use Ubuntu Trusty on OpenStack nodes. The issue will be fixed only on 10.0 which goes with Xenial.

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.