[aws] adding a machine post-bootstrap on the controller model closes of api port in controller security group
Bug #1598164 reported by
Dimiter Naydenov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Critical
|
Dimiter Naydenov | ||
Bug Description
Bootstrap juju 2.0 on aws, switch to the controller model, add a machine, run juju status.
Expected: success
Actual: controller instance's api port 17070 is no longer reachable, so status hangs forever.
Adding machines to other hosted models is fine.
It seems this is pre-existing for a while.
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #1 |
| tags: | added: add-machine addressability ec2-provider tech-debt |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → 2.0-beta12 |
| Changed in juju-core: | |
| assignee: | nobody → Dimiter Naydenov (dimitern) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #2 |
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #3 |
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #4 |
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #5 |
| tags: | added: blocker |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| tags: | removed: blocker |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta12 → none |
| milestone: | none → 2.0-beta12 |
To post a comment you must log in.
Using the AWS web console, once the issue is reproduced you can observe the ingress rule on the controller security group for tcp port 17070 switches to port "0", effectively closing the port.