Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1365004 - Regenerate docs while building downstream package
Regenerate docs while building downstream package
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Michal Privoznik
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-08 07:04 EDT by Michal Privoznik
Modified: 2016-11-03 14:51 EDT (History)
3 users (show)

See Also:
Fixed In Version: libvirt-2.0.0-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 14:51:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 08:07:06 EDT

  None (edit)
Description Michal Privoznik 2016-08-08 07:04:07 EDT
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@redhat.com>
AuthorDate: Mon Aug 8 11:36:01 2016 +0200
Commit:     Michal Privoznik <mprivozn@redhat.com>
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@redhat.com>



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 3 Pei Zhang 2016-08-26 02:27:11 EDT
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 14:51:56 EDT
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.