Description of problem: When creating aodh gnocchi_aggregation_by_metrics_threshold alarm, the parameter --metrics is needed. When creating aodh gnocchi_aggregation_by_resources_threshold alarm, parameter --metric is needed. This difference blocks the automation and looks like a typo. Version-Release number of selected component (if applicable): openstack-aodh-listener-5.0.0-3.el7ost.noarch python-aodh-5.0.0-3.el7ost.noarch openstack-aodh-evaluator-5.0.0-3.el7ost.noarch puppet-aodh-11.3.0-3.el7ost.noarch openstack-aodh-api-5.0.0-3.el7ost.noarch python-aodhclient-0.9.0-1.el7ost.noarch openstack-aodh-common-5.0.0-3.el7ost.noarch openstack-aodh-notifier-5.0.0-3.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Try to create aodh alarm create --name 'MyAlarm_gnocchi_aggregation_by_metrics_threshold' --type gnocchi_aggregation_by_metrics_threshold --aggregation-method 'min' --threshold 4.000000 --resource-type metric --metrics disk.usage --query '{'=': {'name': 'disk.usage'}}' Works ok, alarm is created. 2. Try to create aodh alarm create --name 'MyAlarm_gnocchi_aggregation_by_resources_threshold' --type gnocchi_aggregation_by_resources_threshold --aggregation-method 'min' --threshold 4.000000 --resource-type metric --metrics disk.usage --query '{'=': {'name': 'disk.usage'}}' Get error: "aodh alarm create: error: gnocchi_aggregation_by_resources_threshold requires --metric, --threshold, --aggregation-method, --query and --resource-type" 3. Actual results: Get an error Expected results: Either metrics or metric for both cases Additional info:
To test that we should run both command with "--metric" instead of "--metrics".
No more error when running both with --metric Verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045