Comment 0 for bug 1322573
Revision history for this message
| Kate Pimenova (kpimenova) wrote Sometimes nodes stays offline after stop deployment | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
Any last ISO.
It is reproduced not every time - float bug.
Steps to reproduce:
Сreate new cluster with any configuration, add controller and couple more nodes.
Click "Deploy changes" button - and VERY FAST click "stop deployment".
Wait till stop deployment success.
expected: nodes reboots, and it needs some time to wait till "pending addition" status again. Then we can redeploy.
observed:
- I didnt observe node reboot, actually I didn't observe any activity on the slave nodes. They all are in active status, not offline. I can log in on every node using console.
- on UI: all nodes have "offline" status. Redeploy is not possible. I can delete cluster and try to create new one - i don't see this nodes any more.
- in messages list on UI there are alert: " Fuel couldn't reach these nodes during deployment stopping: 'Untitled (b3:b5)', 'Untitled (9c:05)', 'Untitled (87:d8)', 'Untitled (54:e8)', 'Untitled (4c:0f)'"
this alert is placed before "Deployment of environment 'test' was successfully stopped"
- to return nodes to live - I need reset VMs