disks configuration spontaneous changed to the default

Bug #1400387 reported by Ilya Kharin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Python (Deprecated)

Bug Description

I have some strange issue with Fuel. The env consists of one controller node and two nodes with "compute" and "cinder" roles, the compute nodes also have a special configuration of disks. After some time of the operation of this environment I noticed that the configuration of disks was spontaneously changed for compute nodes to the default. However fortunately the changes was not deployed.

Fuel version: http://paste.openstack.org/show/4jwumNPKrtwOwO0yqYvT/

Ilya Kharin (akscram)
description: updated
description: updated
description: updated
Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

Could you please attach a diagnostic snapshot?

Changed in fuel:
status: New → Incomplete
assignee: nobody → Fuel Python Team (fuel-python)
milestone: none → 6.1
importance: Undecided → Medium
Ilya Kharin (akscram)
description: updated
Revision history for this message
Oleg S. Gelbukh (gelbuhos) wrote :

We've noticed that this situation occurs after we create a Cinder volume (LVM backed) in OpenStack. Nailgun agent detects that LVM volume as new device, and seems to rescan and rebuild disks configuration for the node. This rebuild overrides existing configuration.

See disks configurtion in Nailgun DB after the rebuild in attachment.

Revision history for this message
Ilya Kharin (akscram) wrote :

The size of the diagnostic snapshot is approximately 2.5GB I'm soon going to attach some extracts from it.

The problem had occurred after the master was upgraded from 5.1 to 5.1.1 (nightly build - you can look on the exact version that was posted on the paste earlier). The upgrade was made because of the fix of the *oslo.messaging* library in 5.1.1. After the upgrade the configuration of disks on the nodes with the "cinder" role began to change. Volumes (iSCSI disks) on the nodes began to appear as a disks in attributes of disks. I've attached the sample of the attributes configuration.

Revision history for this message
Roman Prykhodchenko (romcheg) wrote :

@Ilya: You can re-pack the snapshot to LZMA, that should significantly shrink its size.

Ryan Moe (rmoe)
Changed in fuel:
status: Incomplete → Confirmed
Revision history for this message
Oleg S. Gelbukh (gelbuhos) wrote :

Please, be informed that odd disk configuration caused not by creation of Cinder volume, but by attachment of such volume. Resulting device lands in /dev/disk/by-path and Nailgun agent discovers it as a new sdX device.

tags: added: release-notes
Revision history for this message
Irina Povolotskaya (ipovolotskaya) wrote :
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 6.1 → 7.0
Dmitry Pyzhov (dpyzhov)
tags: added: volumes
Dmitry Pyzhov (dpyzhov)
tags: removed: volumes
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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