Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1783987 - hammer virt-who-config deploy fails since foreman-protector does not allow virt-who to be installed
Summary: hammer virt-who-config deploy fails since foreman-protector does not allow vi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.6.0
Hardware: All
OS: All
high
high
Target Milestone: 6.7.0
Assignee: Amit Upadhye
QA Contact: Kunxin Huang
satellite-doc-list
URL:
Whiteboard:
: 1768250 1789483 1805463 1811585 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-16 12:26 UTC by roarora
Modified: 2024-01-06 04:27 UTC (History)
17 users (show)

Fixed In Version: tfm-rubygem-foreman_virt_who_configure-0.5.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 13:38:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28517 0 Normal Closed hammer virt-who-config deploy fails since foreman-protector does not allow virt-who to be installed 2021-01-12 08:12:11 UTC
Red Hat Knowledge Base (Solution) 4591281 0 None None None 2019-12-16 12:29:09 UTC

Description roarora 2019-12-16 12:26:30 UTC 
Description of problem:

hammer virt-who-config deploy fails since it cannot install virt-who package due  to being blocked by foreman-protector yum plugin. 

--------------------------------
[root@sat66 ~]# hammer virt-who-config deploy --id 1 --organization-id 1
[1/5] Installing virt-who
Loaded plugins: foreman-protector, product-id, search-disabled-repos, subscription-manager

WARNING: Excluding 16155 updates due to foreman-protector.
Use foreman-maintain packages install/update <package>
to safely install packages without restrictions.
Use foreman-maintain upgrade run for full upgrade.

No package virt-who available.
Error: Nothing to do
virt-who package virt-who is not installed does not meet minimum requirements, please make sure this host is properly subscribed and has access to satellite-tools repository, minimal virt-who version is 0.24.2
Finished
There were some errors during configuration:
Newer version of virt-who is required, minimum version is 0.24.2
Unable to install virt-who package, make sure the host is properly subscribed and has access to satellite-tools repository
-------------------------------- 

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


How reproducible:
Always

Steps to Reproduce:
1. Install satellite 6.6
2. make and deploy a virt-who configuration

Actual results:
hammer virt-who-config deploy fails

Expected results:
virt-who should be whitelisted so that hammer virt-who-config deploy succeeds without needing to unlock/lock
Comment 4 roarora 2020-01-08 09:46:19 UTC 
*** Bug 1768250 has been marked as a duplicate of this bug. ***
Comment 6 John Berninger 2020-01-11 03:39:48 UTC 
*** Bug 1789483 has been marked as a duplicate of this bug. ***
Comment 7 Brad Buckingham 2020-02-25 18:51:44 UTC 
*** Bug 1805463 has been marked as a duplicate of this bug. ***
Comment 10 Brad Buckingham 2020-03-09 14:28:29 UTC 
*** Bug 1811585 has been marked as a duplicate of this bug. ***
Comment 20 Bryan Kearney 2020-04-14 13:38:57 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/RHSA-2020:1454
Comment 23 Red Hat Bugzilla 2024-01-06 04:27:22 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.