This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2192564 - Insights page or HostDetail's insights tab Remediate modal does not have consistent data-ouia-component-id
Summary: Insights page or HostDetail's insights tab Remediate modal does not have cons...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: Unspecified
Assignee: Shimon Shtein
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-02 09:57 UTC by Ladislav Vasina
Modified: 2024-06-06 16:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:13:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-17547 0 None Migrated None 2024-06-06 16:13:45 UTC

Description Ladislav Vasina 2023-05-02 09:57:58 UTC
Description of problem:
On the Insights page/Remediate modal or on the hosts/"Your host"/Insights tab/Remediate modal 
* <table> element,
* <tr> element of that table 
* Remediate button
* Cancel button
* If the recommendation has a resolution provided and you can choose some inputs, those inputs too

are changing its "data-ouia-component-id" every time you open this modal.

Version-Release number of selected component (if applicable):
satellite-6.13.0-6.el8sat.noarch
foreman-3.5.1.10-1.el8sat.noarch
Red Hat Enterprise Linux release 8.7 (Ootpa)

How reproducible:
Every time

Steps to Reproduce:
1. Generate insights recommendation:
- on host execute "chmod 777 /etc/ssh/sshd_config;insights-client"
- on the host, delete "best" option in /etc/dnf/dnf.conf
2. Run insights-client on the host
3. Sync recommendations on Configure/Insights page
4. Select some recommendation
5. Click Remediate button
5. Inspect the Remediation modal's elements and its data-ouia-component-id
6. Close the modal
7. Select a new recommendation to remediate or try to remediate the same recommendation

Actual results:
Remediation modal's elements and its data-ouia-component-id are changing

Expected results:
Remediation modal's elements and its data-ouia-component-id should not change and should be consistent.

Additional info:
This problem with the changing "data-ouia-component-id" appears in multiple places in Satellite. So it is going to be a more general problem with OUIA ids not just a problem with Insights page.

Comment 3 Brad Buckingham 2023-10-30 11:29:29 UTC
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 6 Eric Helms 2024-06-06 16:13:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.