mongodb charm fails on replicata-set-relation-broken

Bug #1420852 reported by Jay R. Wren
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
MongoDB Charm
Fix Released
Critical
Mario Splivalo

Bug Description

Traceback (most recent call last):
  File "hooks/replica-set-relation-broken", line 1618, in <module>
    hooks.execute(sys.argv)
  File "/var/lib/juju/agents/unit-mongodb-0/charm/hooks/charmhelpers/core/hookenv.py", line 528, in execute
    self._hooks[hook_name]()
  File "hooks/replica-set-relation-broken", line 1231, in replica_set_relation_broken
    if am_i_primary():
  File "hooks/replica-set-relation-broken", line 1141, in am_i_primary
    r = run_admin_command(c, 'replSetGetStatus')
  File "hooks/replica-set-relation-broken", line 488, in run_admin_command
    return client.admin.command(cmdstr)
  File "/usr/lib/python2.7/dist-packages/pymongo/database.py", line 396, in command
    msg, allowable_errors)
  File "/usr/lib/python2.7/dist-packages/pymongo/helpers.py", line 147, in _check_command_response
    raise OperationFailure(msg % errmsg, code)
pymongo.errors.OperationFailure: command SON([('replSetGetStatus', 1)]) failed: not running with --replSet
root@nuc4:/var/lib/juju/agents/unit-mongodb-0/charm# echo hooks/$JUJU_HOOK_NAME
hooks/replica-set-relation-broken

I had run juju remove-service mongodb

Tags: sts

Related branches

Changed in mongodb (Juju Charms Collection):
assignee: nobody → Mario Splivalo (mariosplivalo)
status: New → Incomplete
Revision history for this message
Mario Splivalo (mariosplivalo) wrote :

Hello, Jay.

Can you please provide complete procedure on how you deployed mongodb? I'm assuming you just deployed a single-unit mongodb, and then tried to remove it?

I am assuming 'yes', because I was able to reproduce it that way, but I'd still like a confirmation.

tags: added: cts
Changed in mongodb (Juju Charms Collection):
status: Incomplete → Confirmed
Revision history for this message
Jay R. Wren (evarlast) wrote : Re: [Bug 1420852] Re: mongodb charm fails on replicata-set-relation-broken

Yes, that is what I did.

On Tue, Mar 24, 2015 at 12:41 PM, Mario Splivalo <
<email address hidden>> wrote:

> Hello, Jay.
>
> Can you please provide complete procedure on how you deployed mongodb?
> I'm assuming you just deployed a single-unit mongodb, and then tried to
> remove it?
>
> I am assuming 'yes', because I was able to reproduce it that way, but
> I'd still like a confirmation.
>
>
> ** Tags added: cts
>
> ** Changed in: mongodb (Juju Charms Collection)
> Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1420852
>
> Title:
> mongodb charm fails on replicata-set-relation-broken
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/mongodb/+bug/1420852/+subscriptions
>

tags: added: sts
removed: cts
affects: mongodb (Juju Charms Collection) → mongodb-charm
Changed in mongodb-charm:
importance: Undecided → Critical
Revision history for this message
Martin Hilton (martin-hilton) wrote :
Revision history for this message
Mario Splivalo (mariosplivalo) wrote :

The above merge only fixes removal of single-unit mongodb service/application; but in case the replicaset has been deployed replica-set-relation-broken will still fail.

I've created fresh MP which addresses removal od multi-unit mongodb applicataion:

https://code.launchpad.net/~mariosplivalo/mongodb-charm/+git/mongodb-charm/+merge/330777

Changed in mongodb-charm:
status: Confirmed → In Progress
Changed in mongodb-charm:
status: In Progress → Fix Committed
Changed in mongodb-charm:
status: Fix Committed → 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.