juju has no mechanism to report open-port failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
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.
caused by: request (https://<ip>:9696/
2019-01-24 13:57:30 INFO juju.provider.
2019-01-24 13:57:30 INFO juju.worker.
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
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
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.