Bug 1474564
Summary: | Failed to start virt-who service in RHEL6 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Liushihui <shihliu> |
Component: | Subscriptions - virt-who | Assignee: | Barnaby Court <bcourt> |
Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | bbuckingham, csnyder, cwelton, egolov, ehelms, hsun, jcallaha, pgagne, sgao, yuefliu |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | virt-who-0.20.4-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:54:17 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
Liushihui
2017-07-25 00:47:15 UTC
What version of RHEL 6 was this tested on and which RHEL 6 repositories were enabled? Evgeni added a fix for this in the PR added as an external tracker. This issue is caused by missing python-argparse package, can install it by manual, but it's more better if virt-who spec file can add "Requires" for this package. I used released RHEL6 to do the test. Thanks. verified it, python-argparse is required for virt-who already, # rpm -qp --requires virt-who-0.20.4-1.el6sat.noarch.rpm /bin/sh /bin/sh /bin/sh /bin/sh /usr/bin/python chkconfig chkconfig config(virt-who) = 0.20.4-1.el6sat initscripts libvirt-python m2crypto python(abi) = 2.6 python-argparse python-requests python-rhsm >= 1.10.10 python-setuptools python-suds rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 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/RHSA-2018:0336
|