juju has no mechanism to report open-port failures

[Junien F]

Hi,

juju 2.5, openstack provider. Running open-port when you have reached your neutron secgroup rule quota leads to the following in the machine log :

2019-01-24 13:57:30 DEBUG juju.provider.openstack firewaller.go:909 error creating security group rule: failed to create a rule for the security group with id: d7881436-8435-43ac-993d-07e6200fd95b
caused by: request (https://<ip>:9696/v2.0/security-group-rules) returned unexpected status: 409; error info: {"NeutronError": {"type": "OverQuota", "message": "Quota exceeded for resources: ['security_group_rule'].", "detail": ""}}
2019-01-24 13:57:30 INFO juju.provider.openstack firewaller.go:384 opened ports in security group 31aab372-1594-4b2b-8279-911a62d7bea1-0: [8774/tcp]
2019-01-24 13:57:30 INFO juju.worker.firewaller firewaller.go:931 opened port ranges [8774/tcp] on "machine-0"

As you can see, the first line reports an error, but the ones following make it look like the port opening worked. And there's nothing in "juju status" telling you the port opening has failed.

Thanks

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.