Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1. Proposed title of this feature request
An option to quickly check for how many systems "leapp preupgrade" have been gracefully executed and where we have inhibitors to fix
2. What is the nature and description of the request?
An UI \ report template based option to see if for > 100 systems we "leapp preupgrade" have completed successfully or have some inhibitors to be fixed.
3. Why does the customer need this? (List the business requirements here)
When we use the Leapp preupgrade related REX jobs from Satellite UI, to check if > 100 systems can be leapp'ed to next major version or not, unless there are any connectivity issues present or unless the hosts does not have leapp packages installed,
* All the jobs related to "leapp preupgrade" will be successfully executed ( i.e. status of the job will show as successful in Sat UI ).
* Even if there is an inhibitor reported by leapp in the job output, The job status remains Successful and Users may misunderstand the success status and think that "leapp preupgrade" had no issues.
* Unless, the user is aware of the second point and goes through every single Preupgrade report for all those 100+ systems, There is no quick way present for the user to confirm if a job output had any inhibitors or it was flawless ( from leapp's perspective )
Hence after running "leapp preupgrade" job on multiple systems at once, The user should be able to fetch a consolidated report that shows a summary of the execution along with the fact that whether any Inhibitors were detected or not.
4. How would the customer like to achieve this? (List the functional requirements here)
Either via Report Template feature or perhaps some other feature in UI, that allows to extract the following data with only a couple of clicks in UI, after execution the Leapp Preupgrade job on 100+ systems:
Organization Name, Host Name, Job title, Leapp Inhibited ( Yes\No ), Inhibitor Details ( if we can fetch that some way )
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Depends on Point 4
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No as far as i can say
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as possible as many customers are trying\would try to use foreman_leapp plugin of satellite to do the RHEL7-RHEL8 or RHEL8-RHEL9 conversion and they would hopefully like an easy way to check the upgradability status for each host in a summarized form.
8. Is the sales team involved in this request and do they have any additional input?
No.
9. List any affected packages or components.
- foreman
- foreman_leapp
10. Would the customer be able to assist in testing this functionality if implemented?
RH Support can
11. Additional information:
NA
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.