MOS7, MU3, adding mongoDB node failed

Bug #1606158 reported by ZHI BING WANG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
ZHI BING WANG

Bug Description

If the primary mongoDB role node got removed from the ENV, then added it back as MongoDB role, Fuel still considers it as the primary MongoDB node.

During deployment, it tries to create a new replica set and get the other mongo nodes to join. However, those nodes are still in old replica set, so the operation fails and the deployment fail.

To reproduce
create an ENV with Ceilometer and specify 3 Mongo nodes
Delete the primary Mongo node
Then add it back to the ENV
The deployment will fail

ZHI BING WANG (zwang)
tags: added: ceilometer customer-found mongo
Changed in fuel:
assignee: nobody → MOS Maintenance (mos-maintenance)
milestone: none → 7.0-updates
Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Anton Chevychalov (achevychalov)
Revision history for this message
Anton Chevychalov (achevychalov) wrote :

Unable to reproduce bug in test environment. Is MOS version in that bug correct? Please check it.

Changed in fuel:
status: New → Incomplete
Changed in fuel:
assignee: Anton Chevychalov (achevychalov) → ZHI BING WANG (zwang)
Revision history for this message
ZHI BING WANG (zwang) wrote :

Yes, it is MOS 7 , MU3, all correct.

Revision history for this message
Dmitry Klenov (dklenov) wrote :

@ZHI BING WANG, can you please provide diagnostic snapshot?

Dmitry Klenov (dklenov)
Changed in fuel:
importance: Undecided → Medium
Revision history for this message
ZHI BING WANG (zwang) wrote : Re: [Bug 1606158] Re: MOS7, MU3, adding mongoDB node failed

Hi Dmitry,

I am running a snapshot. However, I am not on site anymore. I will ask
someone there to upload it.

On Tue, Sep 13, 2016 at 4:57 AM, Dmitry Klenov <email address hidden> wrote:

> ** Changed in: fuel
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1606158
>
> Title:
> MOS7, MU3, adding mongoDB node failed
>
> Status in Fuel for OpenStack:
> Incomplete
>
> Bug description:
> If the primary mongoDB role node got removed from the ENV, then added
> it back as MongoDB role, Fuel still considers it as the primary
> MongoDB node.
>
> During deployment, it tries to create a new replica set and get the
> other mongo nodes to join. However, those nodes are still in old
> replica set, so the operation fails and the deployment fail.
>
> To reproduce
> create an ENV with Ceilometer and specify 3 Mongo nodes
> Delete the primary Mongo node
> Then add it back to the ENV
> The deployment will fail
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1606158/+subscriptions
>

--
Best regards,
Zhi Bing

Dmitry Pyzhov (dpyzhov)
Changed in fuel:
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Closed as invalid due to inactivity for more than a month.

Changed in fuel:
status: Incomplete → Invalid
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.