Red Hat Bugzilla – Bug 1018278
Packaging errors in HA Agent
Last modified: 2016-06-12 19:16:54 EDT
There are some latent packaging issues in the HA agent that need to be addressed. This bug is for allowing those found issues to be submitted/merged to get the packaging in shape.
The first issue, which prompted this, is that the .spec.in file needs to be distributed in the tarball.
http://gerrit.ovirt.org/20120 - distribute .spec.in in tarball
Merged Change-Id: I86c804f39a23b4cc905d52f74fb7621bf9e80bc4
Can you please explain how this bug can be verified?
I checked with Sandro on this one, you should be able to:
"download the .src.rpm from the yum repository / brew and check if the included tarball contains the .spec.in
rpm -i ...src.rpm
tar tvf .....tar.gz|grep spec.in
This bug is currently attached to errata RHEA-2013:15591. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
ovirt-hosted-engine-ha is a new package; does not need errata for bugs during its development.
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.