Default partitioning is generated if agent reports of another hd on node

Bug #1394175 reported by Nikolay Markov on 2014-11-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Nikolay Markov

Bug Description

If somebody inserts new hard drive in some target node and reboots it - Nailgun regenerates partitioning to default and "Deploy Changes" button becomes available.

Desired behaviour: new disk is added as unallocated on UI.

Changed in fuel:
importance: Undecided → Medium
Nikolay Markov (nmarkov) on 2014-11-19
description: updated
Dmitry Pyzhov (dpyzhov) on 2015-02-17
Changed in fuel:
milestone: 6.1 → 7.0
Dmitry Pyzhov (dpyzhov) on 2015-03-23
tags: added: volumes
Dmitry Pyzhov (dpyzhov) on 2015-03-30
tags: added: module-volumes
removed: volumes
Aleksey Kasatkin (alekseyk-ru) wrote : is merged. No changes should be done on node (in nailgun DB) if disks are changed during/after deployment.

Changed in fuel:
status: Confirmed → New
assignee: Fuel Python Team (fuel-python) → Nikolay Markov (nmarkov)
Nikolay Markov (nmarkov) on 2015-04-09
Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints