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.
-bash-4.2# hammer virt-who-config deploy --id 1
Could not deploy the Virt Who configuration:
Resource config not found by id '1'
Adding the organization id (ie hammer 'virt-who-config deploy --id 1 --organization-id 5') makes it work.
Either the command doesn't require the organization to be specified or the command in the "deploy" tab includes the organization
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.
Created redmine issue https://projects.theforeman.org/issues/25096 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25096 has been resolved.
I never got a reply so removing a blocker flag. We now added the org to hammer command explicitly, which should solve it.
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.