Cluster stays in waiting state and then goes into error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
High
|
Sergey Reshetnyak |
Bug Description
I create a cluster using this guide http://
2015-07-17 09:31:20.510 DEBUG sahara.
81a7-d38e-
Seems it can not ssh to the instances since port 22 isn't opened. 'nova list' and 'nova secgroup-list' show 3 active instances and 3 security groups. But these groups are not assigned to the instances. After I assign them manually the cluster turns to active state.
I tested it on devstack (master branch) using nova-net.
Please let me know if I can provide any further information.
Changed in sahara: | |
assignee: | nobody → Sergey Reshetnyak (sreshetniak) |
milestone: | none → liberty-3 |
Changed in sahara: | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
Changed in sahara: | |
status: | Fix Committed → Fix Released |
Changed in sahara: | |
milestone: | liberty-3 → 3.0.0 |
we have discussed this issue and we are wondering if the automatic security groups were turned on for this test?
we are having some difficulty assessing the proper response as this could be seen as an operator/ configuration issue, assuming that the ports were not opened. if, however, the automatic security groups are not working with nova networking then this would be a bug.
also, there is another possibility here, and that is for sahara to check whether the proper security groups are in place for ssh to occur.
regardless, we would like to know a little more about the setup. in specific, were automatic security groups enabled?