This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2042899 - The -y or --assumeyes option of foreman-maintain's packages update command does not work and halts for user input
Summary: The -y or --assumeyes option of foreman-maintain's packages update command do...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.9.0
Hardware: All
OS: Linux
high
high
Target Milestone: stream
Assignee: Eric Helms
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 10:22 UTC by raju kumar
Modified: 2024-10-05 04:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 02:21:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-16224 0 None Migrated None 2024-06-06 02:21:28 UTC
Red Hat Knowledge Base (Solution) 7049302 0 None None None 2023-12-27 02:30:44 UTC

Comment 9 Eric Helms 2023-04-05 16:37:01 UTC 
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.
Comment 10 Bryan Kearney 2023-04-06 00:02:32 UTC 
Upstream bug assigned to ehelms
Comment 11 Bryan Kearney 2023-04-06 00:02:34 UTC 
Upstream bug assigned to ehelms
Comment 12 Bryan Kearney 2023-06-06 08:02:13 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36282 has been resolved.
Comment 13 Eric Helms 2023-06-06 15:36:54 UTC 
Part 2 has been implemented as https://bugzilla.redhat.com/show_bug.cgi?id=2211502
Comment 14 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 16 Brad Buckingham 2024-02-11 20:37:14 UTC 
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.
Comment 18 Brad Buckingham 2024-03-20 19:49:35 UTC 
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.
Comment 19 Eric Helms 2024-06-06 02:21:30 UTC 
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.
Comment 20 Red Hat Bugzilla 2024-10-05 04:25:18 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.