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:
The content view table and contentview version table does not have ouia-ID.  This is needed for a static id so automation can be written and executed cleanly.  Currently satellite has dynamic ouia component id which makes writing automation difficult due to it's changing id nature.

Version-Release number of selected component (if applicable):
7.0 snap 11

How reproducible:
100%

Steps to Reproduce:
1. create a cv
2. right click to inspect element on cv and cvv table

Actual results:
DOM only contains dynamic ouia component ID

Expected results:
DOM should also contain ouia-ID prop for static id

Additional info:
This change will help QE write more stable automation for the PF4 changes

Linking upstream redmine & moving to POST as upstream PR is merged.

Steps to retest

1. Create custom repo and sync it
2. Create a cv and publish
3. On cv page, right clicked and inspect element for the cv table
4. Drill into the cvv, right click and inspect element for the cv table

Expected:
cv page should have a static ouia-id for the table.
cvv page should have a static ouia-id for the table.

Actual:
cv page does have a static ouia-id for the table.
cvv page does have a static ouia-id for the table.

Verified on 6.11 snap 16

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 (Moderate: Satellite 6.11 Release), 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-2022:5498