Error message when try to deploy after memory adding to the node already added to the stack

Bug #1404844 reported by Alexander Kurenyshev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Python (Deprecated)

Bug Description

Steps to reproduce:

1) Go to the Fuel
2) Create a new cluster.
3) Add new nodes to the cluster.
4) Softly shutdown VM with compute role.
5) Add memory to the VM, for ex. resize to 8 GB. Run VM.
6) Wait for a loading. At Fuel UI memory size label of the node has changed.
7) Try to deploy.

Observed behaviour:
There is an error message says "Node ... has insufficient disk space".

Expected behaviour:
There is a message says need to reconfigure node because its parameters were changed.

Revision history for this message
Alexander Kurenyshev (akurenyshev) wrote :
Changed in fuel:
milestone: none → 6.0
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
importance: Undecided → Medium
milestone: 6.0 → 6.1
Revision history for this message
Dima Shulyak (dshulyak) wrote :

1. But error says about insufficien disk space, and not memory
2. If there is any bug with memory rediscovery - it should be fixed by nailgun (agent) devs

Changed in fuel:
status: New → Incomplete
Revision history for this message
Alexander Kurenyshev (akurenyshev) wrote :

1. Yes. And this is not correct, I think. When node is configuring, SWAP disk size depends on memory size. I mean there should be something useful, like "Node characteristics were changed. Delete and add again Node".
2. There is no problems with memory rediscovery.

Changed in fuel:
status: Incomplete → New
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

Task result messages are passed on UI from nailgun, so python guys should fix it.

Changed in fuel:
assignee: Fuel UI Team (fuel-ui) → Fuel Python Team (fuel-python)
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

Seems it depends on particular cluster configuration.
I could not reproduce it on ubuntu, non-HA, neutron-vlan, 1 ctrl/cind + 1 comp.
I has changed RAM size on Compute from 1 to 4 GB.

Volume manager have some algorithms for calculation of swap size etc. depending on RAM size. That could cause this issue.
Diag. snapshot would be helpful.

Changed in fuel:
status: New → Incomplete
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.