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.

Description of problem:
When running "hammer virt-who-config deploy" the first time, the deploy fails because it is unable to install the virt-who package because foremain-maintain has locked the packages.

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


How reproducible:
always

Steps to Reproduce:
1. Set up new Satellite 6.6
2. Create a virt-who configuration
3. attempt to deploy the configuration

Actual results:
deploy failed due to locked packages

Expected results:
virt-who package installed, configuration deployed

Additional info:

Hi John,

Thanks for opening the bugzilla.  This appears to be a duplicate of bug 1783987.  Please take a quick look.  If you agree, we can close this one and track the issue with bug 1783987.

IT is indeed a duplicate. Not sure why I didn't find the other one in my initial search, but I'm marking this one as a dupe.

*** This bug has been marked as a duplicate of bug 1783987 ***