I'm don't know what the ultimate goal for secgroup-add-rule is but right now it returns 500.
This appears to be leftover from https://review.openstack.org/#/c/50944/.
Traceback (most recent call last):
File "/opt/stack/trove/trove/common/wsgi.py", line 251, in execute_action
**action_args)
File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 395, in execute_action
return self.dispatch(self.controller, action, request, **action_args)
File "/opt/stack/trove/trove/openstack/common/wsgi.py", line 404, in dispatch
return method(*args, **kwargs)
File "/opt/stack/trove/trove/extensions/security_group/service.py", line 93, in create
CONF.trove_security_group_rule_protocol,
File "/opt/stack/oslo.config/oslo/config/cfg.py", line 1619, in __getattr__
raise NoSuchOptError(name)
NoSuchOptError: no such option: trove_security_group_rule_protocol
After deciding what secgroup-add-rule should do, I recommend a related bug be filed in python-troveclient to clean up the secgroup-add-rule subcommand (i.e. ports that aren't used etc).
Fix proposed to branch: master /review. openstack. org/84335
Review: https:/