mojo spec indicates aodh alarm failed to trigger when instance is stopped

[Ryan Beisner]

mojo spec indicates aodh alarm failed to trigger when instance is stopped

This is the designate-ha mojo spec, which also explicitly exercises aodh alarming. This could be a charm issue or a test case issue. Raised against both, pending further triage.

01:46:55.438 #############################################################################
01:46:55.438 Test AODH Alarms
01:46:55.438 #############################################################################
01:46:55.438
01:46:55.438
01:46:55.438 2018-02-23 22:18:52 [INFO] Pulling secrets from /tmp/tmp.9ZpdzFdDs2/LOCAL/mojo-openstack-specs/specs/full_stack/next_designate_ha/mitaka to /tmp/tmp.9ZpdzFdDs2/mojo-openstack-specs/trusty/osci-mojo/local
01:46:55.438 2018-02-23 22:18:52 [WARNING] Automatic secrets phase ran but secrets directory /tmp/tmp.9ZpdzFdDs2/LOCAL/mojo-openstack-specs/specs/full_stack/next_designate_ha/mitaka does not exist!
01:46:55.438 2018-02-23 22:18:52 [INFO] Running script validate_aodh.py
01:47:57.894 2018-02-23 22:19:55 [WARNING] No debug log matching debug-logs found. Using default.
01:47:59.908 2018-02-23 22:19:57 [ERROR] 2018-02-23 22:18:59 [INFO] Using keystone API V2 for overcloud auth
01:47:59.908 2018-02-23 22:19:00 [INFO] Using server 20180223214909 for aodh test
01:47:59.908 2018-02-23 22:19:00 [INFO] Deleting alarm mojo_instance_off if it exists
01:47:59.908 2018-02-23 22:19:00 [INFO] Creating alarm mojo_instance_off
01:47:59.908 2018-02-23 22:19:01 [INFO] Stopping server 20180223214909
01:47:59.908 Traceback (most recent call last):
01:47:59.908 File "/tmp/tmp.9ZpdzFdDs2/mojo-openstack-specs/trusty/osci-mojo/spec/specs/full_stack/next_designate_ha/mitaka/validate_aodh.py", line 60, in <module>
01:47:59.908 sys.exit(main(sys.argv))
01:47:59.908 File "/tmp/tmp.9ZpdzFdDs2/mojo-openstack-specs/trusty/osci-mojo/spec/specs/full_stack/next_designate_ha/mitaka/validate_aodh.py", line 56, in main
01:47:59.908 raise Exception("Alarm failed to trigger")
01:47:59.908 Exception: Alarm failed to trigger

[David Ames (thedac)]

Still not sure what the cause is however, the mojo run of trusty-mitaka has been failing for a while.

We need to investigate further.

[Pen Gale (pengale)]

Note: this error does not happen in the queens or rocky specs. It's possible that it is a bug that has been fixed since mitaka.

[Liam Young (gnuoy)]

Yep, existing bug in mitaka https://bugs.launchpad.net/charm-ceilometer/+bug/1773171