Bug 2042899

Here is the rough plan of attack we are thinking to tackle the underlying issues:

 1) We do not plan to re-instate the whitelist option for packages update but will look at making --assumeyes work to allow for unattended package updates. Note that this will still run the installer and should be considered when trying to do so before running upgrade.

 2) We will modify our update procedure to run 'dnf update --downloadonly' before stopping services. This will allow services to continue to be up for as long as possible, while downloading and caching the package updates (thus not affecting the running system). Then the upgrade will stop services, run install from the cached packages and run the installer.

 3) We will add a command to download package updates into cache. That is, we'll allow package update to run with --downloadonly for those who want to download and stage packages but not incur the installer run directly or in preparation.

Upstream bug assigned to ehelms

Upstream bug assigned to ehelms

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

Part 2 has been implemented as https://bugzilla.redhat.com/show_bug.cgi?id=2211502

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla 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 bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional discussion; however, it may be closed in a future iteration.

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.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days