rabbitmq does not cluster due to dns issue - timing issue

Bug #1590085 reported by Narinder Gupta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OPNFV
Fix Released
Undecided
Unassigned
rabbitmq-server (Juju Charms Collection)
Fix Released
High
James Page

Bug Description

deploy rabbitmq with the openstack HA bundle with mitaka. After deployment found out that one of the service stuck at joining the cluster and stays there.

After debugging with Lam it seems.

rabbitmq-server/0 and rabbitmq-server/1 can resolved the dns name for each other and for rabbitmq-server/2 but not themselves

After addind the entry manually on rabbitmq-server/2 it worked.

Revision history for this message
Narinder Gupta (narindergupta) wrote :
James Page (james-page)
Changed in rabbitmq-server (Juju Charms Collection):
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Page (james-page)
milestone: none → 16.07
Revision history for this message
James Page (james-page) wrote :

Proposed fix for this bug is located in temp charm location:

  cs:~james-page/xenial/rabbitmq-server-bug1590085

Revision history for this message
Narinder Gupta (narindergupta) wrote : Re: [Bug 1590085] Re: rabbitmq does not cluster due to dns issue - timing issue

I tried this deployment with three different bundles and could not
reproduce issue with the temp charm.

Thanks and Regards,
Narinder Gupta (PMP) <email address hidden>
Canonical, Ltd. narindergupta [irc.freenode.net]
+1.281.736.5150 narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Thu, Jul 7, 2016 at 8:02 AM, James Page <email address hidden> wrote:

> Proposed fix for this bug is located in temp charm location:
>
> cs:~james-page/xenial/rabbitmq-server-bug1590085
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1590085
>
> Title:
> rabbitmq does not cluster due to dns issue - timing issue
>
> Status in OPNFV:
> New
> Status in rabbitmq-server package in Juju Charms Collection:
> In Progress
>
> Bug description:
> deploy rabbitmq with the openstack HA bundle with mitaka. After
> deployment found out that one of the service stuck at joining the
> cluster and stays there.
>
> After debugging with Lam it seems.
>
> rabbitmq-server/0 and rabbitmq-server/1 can resolved the dns name for
> each other and for rabbitmq-server/2 but not themselves
>
> After addind the entry manually on rabbitmq-server/2 it worked.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/opnfv/+bug/1590085/+subscriptions
>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-rabbitmq-server (master)

Reviewed: https://review.openstack.org/338865
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=0ded449e8d32428baf7992cfc6999f82e9996c1a
Submitter: Jenkins
Branch: master

commit 0ded449e8d32428baf7992cfc6999f82e9996c1a
Author: James Page <email address hidden>
Date: Thu Jul 7 11:48:52 2016 +0100

    Ensure rabbit hosts are resolvable

    The update_hosts_file function requires a full map of entries to
    write into /etc/hosts; the previous use of this function tried
    to write individual host entries only.

    Ensure that a full map of self + peers is written at appropriate
    points in a units lifecycle to ensure self and peer hostname
    resolvability.

    (also fixed a typo in a status message)

    Change-Id: If40b31a55641861a1e03985f318e012b545fcc25
    Closes-Bug: 1592200
    Closes-Bug: 1590085

Changed in rabbitmq-server (Juju Charms Collection):
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-rabbitmq-server (stable/16.04)

Fix proposed to branch: stable/16.04
Review: https://review.openstack.org/339597

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-rabbitmq-server (stable/16.04)

Reviewed: https://review.openstack.org/339597
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=c200f4fd13a141f79aef34c426c1e7e2633766ce
Submitter: Jenkins
Branch: stable/16.04

commit c200f4fd13a141f79aef34c426c1e7e2633766ce
Author: James Page <email address hidden>
Date: Thu Jul 7 11:48:52 2016 +0100

    Ensure rabbit hosts are resolvable

    The update_hosts_file function requires a full map of entries to
    write into /etc/hosts; the previous use of this function tried
    to write individual host entries only.

    Ensure that a full map of self + peers is written at appropriate
    points in a units lifecycle to ensure self and peer hostname
    resolvability.

    (also fixed a typo in a status message)

    Change-Id: If40b31a55641861a1e03985f318e012b545fcc25
    Closes-Bug: 1592200
    Closes-Bug: 1590085
    (cherry picked from commit 0ded449e8d32428baf7992cfc6999f82e9996c1a)

James Page (james-page)
Changed in rabbitmq-server (Juju Charms Collection):
status: Fix Committed → Fix Released
Changed in opnfv:
status: New → Fix Released
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.