Bug 1313297 - [WALA][rhel6.7] error occurs when detach a disk on a running VM
Summary: [WALA][rhel6.7] error occurs when detach a disk on a running VM
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: WALinuxAgent
Version: 6.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Yue Zhang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 11:00 UTC by Hu Zhang
Modified: 2016-07-12 09:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-12 09:24:52 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Hu Zhang 2016-03-01 11:00:12 UTC
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:

Comment 4 Yuxin Sun 2016-07-12 05:30:00 UTC
This issue also exists in RHEL-7.3. Doesn't exist in RHEL-7.2.

Comment 5 Yuxin Sun 2016-07-12 09:24:52 UTC
Compare with Hyper-V, the phenomenon is the same on both Azure and Hyper-V. So we think it is not a bug. Close it and modify the test case.


Note You need to log in before you can comment on or make changes to this bug.