-
Feature Request
-
Resolution: Unresolved
-
None
-
6.14.3
Description of problem:
This is a follow on to BZ 1902077. The customer would like a hammer command and satellite system role to confirm a CV synchronized to capsules properly. Currently, a sync issue is discovered when a user updates a host and discovers a problem.
Expected results:
The user could run a hammer command or system role that would confirm the package count is the same across all capsules and any other information needed to verify the sync was 100% successful.
This could be added to their automation to run after their regularly scheduled CV publishes and promotions.
[SAT-24099] [RFE] Add system role and hammer command to verify capsule CV sync status
Eric Helms
added a comment - 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@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Eric Helms
added a comment - 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@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Upon review of our valid but aging backlog, the Satellite Team has concluded that this issue does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the issue is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.