for swarm bay status always says none
Bug #1491072 reported by
Manjeet Singh Bhatia
This bug report is a duplicate of:
Bug #1489725: Unable to get the status of bay with model as Docker swarm.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
New
|
Undecided
|
Unassigned | ||
Bug Description
bay status is showing none even though bay is created. I attached screen shot below.
Revision history for this message
| Manjeet Singh Bhatia (manjeet-s-bhatia) wrote | #1 |
| Changed in magnum: | |
| assignee: | nobody → Manjeet Singh Bhatia (manjeet-s-bhatia) |
Revision history for this message
| Andrew Melton (andrew-melton) wrote | #2 |
| Changed in magnum: | |
| assignee: | Manjeet Singh Bhatia (manjeet-s-bhatia) → nobody |
| Changed in magnum: | |
| status: | New → Invalid |
| status: | Invalid → New |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on magnum (master) | #3 |
To post a comment you must log in.
I'm seeing similar behavior because the Heat Poller was throwing an exception trying to access the heat parameter 'number_of_minions' which is specific to the Kubernetes template. I suspect Mesos bays are broken in a very similar fashion.