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 1365004 - Regenerate docs while building downstream package
Summary: Regenerate docs while building downstream package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-08 11:04 UTC by Michal Privoznik
Modified: 2016-11-03 18:51 UTC (History)
3 users (show)

Fixed In Version: libvirt-2.0.0-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 18:51:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 12:07:06 UTC

Description Michal Privoznik 2016-08-08 11:04:07 UTC 
Description of problem:
Even though downstream libvirt has gained support for multiple devices, the docs doesn't reflect that. Debugging the issue led to the following upstream commit:

commit e396de03f31d87f3e81c7820739951d50367ddb8
Author:     Michal Privoznik <mprivozn>
AuthorDate: Mon Aug 8 11:36:01 2016 +0200
Commit:     Michal Privoznik <mprivozn>
CommitDate: Mon Aug 8 11:49:35 2016 +0200

    docs: Distribute subsite.xsl
    
    So, I've ran into very interesting problem lately. When doing the
    following, I've encountered an error:
    
      libvirt.git $ make dist && tar -xJf libvirt-2.2.0.tar.xz && \
                    cd libvirt-2.2.0 && ./configure && \
                    rm docs/formatdomain.html && make -C docs
    
      make: Entering directory 'docs'
      make: *** No rule to make target 'formatdomain.html', needed by 'web'.  Stop.
      make: Leaving directory 'docs'
    
    I had no idea what was going on, so I've nailed down the commit
    that "broke it" via running git-bisect. It was this one:
    7659bd9221b9dd1cdf. But that shed no more light until I realized
    that the commit might actually just exposed a problem we had. And
    guess what - I've nailed it down. Of course we are not
    distributing subsite.xsl that's why make prints error message.
    Very misleading one I must say.
    
    Signed-off-by: Michal Privoznik <mprivozn>



However, in order to fix the issue in downstream package, we need a bug too.

Version-Release number of selected component (if applicable):

libvirt-2.0.0-4.el7

How reproducible:

100 %

Steps to Reproduce:
1. Install latest libvirt
2. Check that a feature is there and works (e.g. iommu device - bug 1235581)
3. Observe missing no reference to the feature in libvirt-docs

Actual results:
IOMMU device is not mentioned in libvirt-docs.


Expected results:
IOMMU device is mentioned in libvirt-docs.


Additional info:
Comment 1 Michal Privoznik 2016-08-08 11:09:25 UTC 
To POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2016-August/msg00624.html
Comment 3 Pei Zhang 2016-08-26 06:27:11 UTC 
Verified version :
libvirt-2.0.0-6.el7

I can reproduce and verify it like following :

1. Install libvirt-2.0.0-4.el7, check there is no IOMMU related info in doc

# rpm -q libvirt-docs
libvirt-docs-2.0.0-4.el7.x86_64

# cat /usr/share/doc/libvirt-docs-2.0.0/html/formatdomain.html | grep IOMMU


2. Install libvirt-2.0.0-6.el7, check there is information about IOMMU.

# rpm -q libvirt-docs
libvirt-docs-2.0.0-6.el7.x86_64

# cat /usr/share/doc/libvirt-docs-2.0.0/html/formatdomain.html | grep IOMMU

                    <a href="#elementsIommu">IOMMU devices</a>
          <a name="elementsIommu" shape="rect" id="elementsIommu">IOMMU devices</a>
      The <code>iommu</code> element can be used to add an IOMMU device.
......

Move to verified.
Comment 5 errata-xmlrpc 2016-11-03 18:51:56 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://rhn.redhat.com/errata/RHSA-2016-2577.html
Note You need to log in before you can comment on or make changes to this bug.