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.

Bug 1523070

Summary: Documentation of the <disk>'s 'snapshot' attribute is misleading
Product: Red Hat Enterprise Linux 7 Reporter: lijuan men <lmen>
Component: libvirtAssignee: Peter Krempa <pkrempa>
Status: CLOSED ERRATA QA Contact: lijuan men <lmen>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: dyuan, jdenemar, lmiksik, pkrempa, rbalakri, xuzhang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-3.9.0-6.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 11:02:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description lijuan men 2017-12-07 07:30:45 UTC
Description of problem:
the information about 'snapshot' attribute is not coincident between libvirt.org and actual feature 

Version-Release number of selected component (if applicable):
libvirt-3.9.0-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Set the value of 'snapshot' attribute as 'yes'. Edit the guest xml as:
 <disk type='file' device='disk' ***snapshot='yes'***>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/b.qcow2'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>

can't save the xml,the error is:
error: unsupported configuration: unknown disk snapshot setting 'yes'

2.in the libvirt.org,it said:
"for example, snapshot='yes' with a transient disk generally does not make sense"

from this sentence,I think 'snapshot' supports the value 'yes'

Actual results:
the information in step1 and step2 is not coincident
Maybe the libvirt.org has inaccurate information

Expected results:


Additional info:

Comment 3 Peter Krempa 2017-12-07 13:35:55 UTC
Fixed upstream:

commit 1e98d450f27ae0131ac2ac8aa1c1d7a254d22dd1 
Author: Peter Krempa <pkrempa>
Date:   Thu Dec 7 14:16:10 2017 +0100

    docs: domain: Fix documentation of the 'snapshot' attribute for <disk>
    
    Emphasise the valid values by wrapping them in <code> and reword the
    last sentence so that the invalid value example can be dropped.

Comment 6 lijuan men 2018-01-11 08:09:03 UTC
version:
libvirt-3.9.0-7.el7.x86_64

verify the bug,there is no value 'yes' in the doc

Comment 10 errata-xmlrpc 2018-04-10 11:02:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0704