Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
It seems in 6.4 something changed to make Virt-who configuration objects tied to organizations, such that it is now required to specify the organization when using 'hammer virt-who-config deploy'
Version-Release number of selected component (if applicable): 6.4
How reproducible: Always
Steps to Reproduce:
1. Create an organization (other then the default) call virt-who-config
2. Create a virt-who config using the Satellite virt-who config plugin
3. Copy the deployment command to the clipboard and run it on satellite.
Actual results:
-bash-4.2# hammer virt-who-config deploy --id 1
Could not deploy the Virt Who configuration:
Resource config not found by id '1'
-bash-4.2#
Adding the organization id (ie hammer 'virt-who-config deploy --id 1 --organization-id 5') makes it work.
Expected results:
Either the command doesn't require the organization to be specified or the command in the "deploy" tab includes the organization
Additional info:
In 6.3 there was no requirement to specify the organization, is this a new requirement in 6.4? If so we need to update the command we are having people copy.
Configurations were always tight to organizations. Do you run that command under admin or some non-admin user? Non-admins always need to specify the organization if they are assigned to at least two I think.
Though I think it's a good RFE for generated hammer command to specify the organization.
Perry could you double check it's regression, I don't think anything has changed there. In fact I don't think this should be a blocker and might not even be necessary to ship in 6.4.z, though the fix would be minor, so no objections against that.
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-2019:1222