Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Error occurs when detach a disk on a running VM(rhel6.7). This disk is mounted to a mount point.
After detached, it's still in the mount list but removed from device list.
Same on Ubuntu. But could not reproduce on rhel7.2.
Meanwhile, on Azure, the disk will be detached even it is busy. But on hyper-v,
the disk will be detached only when it is not in use.
Version-Release number of selected component (if applicable):
WALinuxAgent-2.0.16-1.el6
How reproducible:
Always
Steps to Reproduce:
1. Attach a disk to a running VM.
2. Mount the disk.
# mount /dev/sdc1 /mnt/newdisk
3. Detach the disk on the azure portal.
4. Check the disk on VM
# mount | grep /dev/sdc1
/dev/sdc1 on /mnt/newdisk1 type ext4 (rw)
# fdisk -l | grep sdc
#
# ls /mnt/newdisk
ls: reading directory /mnt/newdisk1: Input/output error
#
Actual results:
After detached, it's still in the mount list but removed from device list. And it returns an error
when do any manipulation on the mount point.
Expected results:
After detached, it shouldn't be in the mount list any more.
on Azure, the disk should not be detached when it is busy.
Additional info: