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.
Bug 1784297 - [machines] The format is none in the result of 'virsh vol-dumpxml $disk $pool' after disk creation in physical disk device
Summary: [machines] The format is none in the result of 'virsh vol-dumpxml $disk $pool...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Meina Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-17 07:54 UTC by YunmingYang
Modified: 2022-04-20 07:48 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 07:48:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description YunmingYang 2019-12-17 07:54:17 UTC 
Description of problem:
Prepare a storage pool whose type is physical disk device. Then create a disk in this pool, and set the disk format to 'linux'. After that, check the disk with 'virsh vol-dumpxml $disk $pool'

Version-Release number of selected component (if applicable):
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a storage pool whose type is physical disk device
2. Create a disk in the pool, and set the disk format to 'linux'
3. Check the disk with 'virsh vol-dumpxml $dump $pool'

Actual results:
In the disk xml, the format field is:
<format type='none'/>
Expected results:
In the disk xml, the format field is:
<format type='linux'/>
Additional info:
Comment 3 RHEL Program Management 2021-06-17 07:30:45 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 4 Simon Kobyda 2022-04-19 20:43:22 UTC 
This is a libvirt bug. It can be reproduced with virsh:

1. Have a disk storage pool. In my case "disk-pool":

<pool type='disk'>
  <name>disk-pool</name>
  <uuid>609d3a31-dee6-4fa1-b4a9-8730400ed9f2</uuid>
  <capacity unit='bytes'>10468864</capacity>
  <allocation unit='bytes'>0</allocation>
  <available unit='bytes'>10451456</available>
  <source>
    <device path='/dev/sda'>
      <freeExtent start='17408' end='10468864'/>
    </device>
    <format type='gpt'/>
  </source>
  <target>
    <path>/media</path>
  </target>
</pool>

2. # virsh vol-create-as --pool disk-pool --name sda1 --capacity 1 --format linux

3. # virsh pool-refresh disk-pool 

4. Check storage volume format:
# virsh vol-dumpxml --pool disk-pool --vol sda1

<volume type='block'>
  <name>sda1</name>
  <key>/dev/sda1</key>
  <source>
    <device path='/dev/sda'>
      <extent start='17408' end='17920'/>
    </device>
  </source>
  <capacity unit='bytes'>512</capacity>
  <allocation unit='bytes'>512</allocation>
  <physical unit='bytes'>512</physical>
  <target>
    <path>/dev/sda1</path>
    <format type='none'/>
    <permissions>
      <mode>0660</mode>
      <owner>0</owner>
      <group>6</group>
      <label>system_u:object_r:fixed_disk_device_t:s0</label>
    </permissions>
    <timestamps>
      <atime>1650400622.921208113</atime>
      <mtime>1650400622.921208113</mtime>
      <ctime>1650400622.921208113</ctime>
      <btime>0</btime>
    </timestamps>
  </target>
</volume>


Actual result: In step 5, storage volume format is "none" after storage pool refresh.
Expected result: In step 5, Storage volume format is "linux" after storage pool refresh.
Comment 6 Jaroslav Suchanek 2022-04-20 07:48:40 UTC 
I think, this is well described in the bug 1138516 comment 7 by John. Hence, there is nothing to be fixed here.
Note You need to log in before you can comment on or make changes to this bug.