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 'Last published' section causes confusions while verifying the content views associated with the Capsule.

It appears that the 'Last published' refers to the date when the content views were actually created, it does not represent the last publish/promote date.

It would be nice if we can rename 'Last published' to something else like 'Content View added/created' or anything that will help to understand what it actually stands for.

It's a regression.

How reproducible:

Go to Infrastructure --> Capsules --> Capsule --> Content --> Expand environment

Screenshot attached.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36629 has been resolved.

What are the testing steps for this pull request?
Check out PR
Create a CV, publish and promote it to an env associated with a smart-proxy so it syncs
Go to Infrastructure --> Smart Proxies --> <your smartproxy) --> Content --> Expand environment
Check if the created at matches the cv version synced to the env instead of the initial cv created at time

Verified in 6.15.0 snap 4.0

Now the Publish time of a particular CV version promoted to a particular LCE is shown on the Capsule Content page.

Created attachment 2009274 [details]
screenshot

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 (Important: Satellite 6.15.0 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-2024:2010