Bug 1645144
| Summary: | Unable to delete virt-who configuration from satellite. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Suraj Patil <supatil> |
| Component: | Virt-who Configure Plugin | Assignee: | Marek Hulan <mhulan> |
| Status: | CLOSED ERRATA | QA Contact: | Perry Gagne <pgagne> |
| Severity: | high | Docs Contact: | satellite-doc-list |
| Priority: | high | ||
| Version: | 6.4 | CC: | ajambhul, ajoseph, akarimi, apitanga, avroy, brant.evans, dhjoshi, dsynk, egolov, gscarbor, hshukla, janarula, kuhuang, mhulan, ptrivedi, rajukuma, rbertolj, richard.zuber, sadas, saydas, smane, smutkule, vdeshpan |
| Target Milestone: | 6.5.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-foreman_virt_who_configure-0.3.2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:38:32 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1589736 | ||
|
Description
Suraj Patil
2018-11-01 13:41:13 UTC
It could be caused by existing audit records for a virt-who configuration. Potentially fixed by BZ 1589736 Oh I see now you're able to reproduce this even with the linked BZ. So try to see if you can still delete the configuration after you update it. There might be some issue with audit. Also let me know what's you virt_who_configure plugin version you tested with. Created redmine issue https://projects.theforeman.org/issues/25863 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25863 has been resolved. Verified fix in 6.5 snap 12. Created/deployed a virt-who config, and waited for hypervisor reports to come in. Was able to delete the config. 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 |