Red Hat Bugzilla – Bug 1211964
Gluster: storage device is shown with a locked symbol even when there are no partitions in the disk.
Last modified: 2016-07-14 22:04:55 EDT
Description of problem: Even when there are no paritions in the disk , the disk is still shown with locked symbol and user cannot use the disk for creating a brick. When a storage device is used for creating a brick , and once the brick is created and mounted if user tries to umount the brick, removes the lv, vg and pv the brick is still shown with locked symbol in the UI. Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch How reproducible: Always. Steps to Reproduce: 1. Add a rhel7 node to the UI. 2. click on sync button in the storage devices. 3. Now create a brick using the storage device. 4. Umount the brick, remove /etc/fstab entry, remove the lv, remove the vg, remove the pv, remove the partition inside the disk. 5. click on sync button. Actual results: The storage device on which the partition was removed is still shown with a locked symbol. Expected results: If there is no partition inside the disk, disk should not be shown with locked symbol. Additional info:
I removed the partition using fdisk. for ex:- step 1) fdisk /dev/sdd step 2) key press 'd' step 3) key press 'w' Now in the UI when i click 'sync' option I could able to see the device listed without any lock icon. It works for me. Can you check it out. If its works, can you/i close this bug?
I followed the same steps which is present in comment 1. Still i see the same issue. partition shows unlocked only when i run dd command on that disk. Until then it shows the device wit locked symbol.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag.
Tim, is this expected behaviour (comment 3) ?
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Ramesh, should we close this?
This problem is seen when there is a disk label even after removal of the disks partitions. dd command can be used to clean the first few bytes of the disks and it will remove the disk label. Closing this bug with the suggested workaround.