Bug 2264216
| Summary: | Host content view environment is reset on any host edit when hostgroup assigns a CVE | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jeremy Lenz <jlenz> |
| Component: | Hosts - Content | Assignee: | Quinn James <qjames> |
| Status: | CLOSED MIGRATED | QA Contact: | Vladimír Sedmík <vsedmik> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | Nightly | CC: | arunas.z.vaznevicius, gformisa, jlenz, jpasqual, qjames, rlavi, vsedmik, zhunting |
| Target Milestone: | stream | Keywords: | MigratedToJIRA, UserExperience |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 17:03:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jeremy Lenz
2024-02-14 15:42:15 UTC
Created from redmine issue https://projects.theforeman.org/issues/36897 Upstream bug assigned to None Verified in Stream snap 50.0 Steps: 1. Have two (or more) LCEs and two (or more) CVs promoted to one of the LCE. 2. Have two (or more) host groups (nested or not) that assign one of the LCE and CV. 3. Create a host using the HG, check it inherits the LCE/CV from the HG. 4. Change the CV assignment of the host to another LCE/CV (via "Edit content view assignment" dialog or "Change content source" page). 5. Edit the host, change some parameter and Submit. Results: 1. The LCE/CV stays the stays the same after host edit independently from the HG settings. 2. No 'activerecord' nor 'nomethod' errors in log. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |