Nodes in discovery, pending addition status after reset

Bug #1652935 reported by Yevgeniy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Sustaining

Bug Description

Fuel 9.1

Nodes in discovery, pending addition status after reset
Steps to reproduce:
1) Deploy environment with contrail plugin
2) Reset environment

Actual result:
Slave nodes in "pending addition status"

Expected result:
Slave nodes in "offline" status

Workaround:
Check nodes manually

Tags: ui
Revision history for this message
Yevgeniy (yshapovalov) wrote :
Changed in fuel:
assignee: nobody → Fuel UI Team (fuel-ui)
Yevgeniy (yshapovalov)
description: updated
Yevgeniy (yshapovalov)
description: updated
description: updated
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

@Yevgeniy, why should nodes go to offline? Have you shut them down? Even in this case it takes several minutes to update status to 'offline'. For how long have you waited for it?

Changed in fuel:
status: New → Incomplete
assignee: Fuel UI Team (fuel-ui) → Fuel Sustaining (fuel-sustaining-team)
Revision history for this message
Yevgeniy (yshapovalov) wrote :

@Dmitry, nodes reload after reseting of environment.

Revision history for this message
Alexey Shtokolov (ashtokolov) wrote :

@Yevgeniy, It's an expected behaviour.

"Reset environment" keeps the networks, cluster settings and roles assignment. So after reset all deployed nodes should reboot and come back to "discover" state and right after that to "pending addition" state due to assigned roles.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.