Resources st-maas-1a980f7,st-maas-d9bdc8d violate uniqueness

Bug #1881106 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack HA Cluster Charm
Fix Released
Critical
Liam Young

Bug Description

I deployed hacluster-masakari with

  maas_url: &maas-url "http://8.8.8.8"
  maas_credentials: &maas-credentials "fake"
  hacluster-masakari:
    charm: cs:hacluster
    bindings:
      pacemaker-remote: *ceph-public-space
    options:
      maas_url: *maas-url
      maas_credentials: *maas-credentials

Then I ran

juju config hacluster-masakari maas_url="http://192.168.210.4:5240/MAAS"

which resulted in unit in error and log shows this

2020-05-28 10:29:12 DEBUG juju-log Checking monitor host configuration
2020-05-28 10:29:17 DEBUG config-changed WARNING: Resources st-maas-1a980f7,st-maas-d9bdc8d violate uniqueness for parameter "apikey": "fake"
2020-05-28 10:29:17 DEBUG config-changed WARNING: Resources st-maas-1a980f7,st-maas-d9bdc8d violate uniqueness for parameter "hostnames": "node1 node1.maas node3 node3.maas node4 node4.maas node5 node5.maas"
2020-05-28 10:29:17 DEBUG config-changed Traceback (most recent call last):
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/config-changed", line 660, in <module>
2020-05-28 10:29:17 DEBUG config-changed hooks.execute(sys.argv)
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/charmhelpers/core/hookenv.py", line 943, in execute
2020-05-28 10:29:17 DEBUG config-changed self._hooks[hook_name]()
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/config-changed", line 200, in config_changed
2020-05-28 10:29:17 DEBUG config-changed configure_stonith()
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/utils.py", line 509, in configure_stonith
2020-05-28 10:29:17 DEBUG config-changed if configure_pacemaker_remote_stonith_resource():
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/utils.py", line 799, in configure_pacemaker_remote_stonith_resource
2020-05-28 10:29:17 DEBUG config-changed stonith_resource = configure_maas_stonith_resource(hostnames)
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/utils.py", line 653, in configure_maas_stonith_resource
2020-05-28 10:29:17 DEBUG config-changed pcmk.commit(cmd, failure_is_fatal=True)
2020-05-28 10:29:17 DEBUG config-changed File "/var/lib/juju/agents/unit-hacluster-masakari-0/charm/hooks/pcmk.py", line 68, in commit
2020-05-28 10:29:17 DEBUG config-changed return subprocess.check_call(cmd.split())
2020-05-28 10:29:17 DEBUG config-changed File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
2020-05-28 10:29:17 DEBUG config-changed raise CalledProcessError(retcode, cmd)
2020-05-28 10:29:17 DEBUG config-changed subprocess.CalledProcessError: Command '['crm', 'configure', 'primitive', 'st-maas-d9bdc8d', 'stonith:external/maas', 'params', "url='http://192.168.210.4:5240/MAAS'", "apikey='fake'", "hostnames='node1", 'node1.maas', 'node3', 'node3.maas', 'node4', 'node4.maas', 'node5', "node5.maas'", 'op', 'monitor', 'interval=25', 'start-delay=25', 'timeout=25']' returned non-zero exit status 1.
2020-05-28 10:29:18 ERROR juju.worker.uniter.operation runhook.go:132 hook "config-changed" failed: exit status 1

hacluster-masakari error 3 hacluster jujucharms 68 ubuntu

Tags: cdo-qa
Liam Young (gnuoy)
Changed in charm-hacluster:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Liam Young (gnuoy)
milestone: none → 20.05
milestone: 20.05 → 20.08
Revision history for this message
Liam Young (gnuoy) wrote :
Changed in charm-hacluster:
status: In Progress → Fix Committed
tags: added: cdo-qa
Changed in charm-hacluster:
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.