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 2022615 - [RFE] Need more clarity on foreman-maintain packages update warning
Summary: [RFE] Need more clarity on foreman-maintain packages update warning
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Ashish Humbe
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-12 07:48 UTC by mithun kalyat
Modified: 2024-10-05 04:25 UTC (History)
5 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_maintain pull 831 0 None Merged Correct the foreman-maintain packages update warning 2024-05-14 16:41:10 UTC
Red Hat Issue Tracker   SAT-24577 0 None Migrated None 2024-06-06 01:05:59 UTC

Description mithun kalyat 2021-11-12 07:48:04 UTC 
RFE Template :

1. Proposed title of this feature request  

Need more clarity on foreman-maintain packages update warning
      
2. Who is the customer behind the request?  
    Account: Statnett SF (acct #1061575)  
    TAM customer: no
    SRM customer: no  
    Strategic: no 
      
3. What is the nature and description of the request?  
      
Currently the message we get while running 'foreman-maintain packages update' is the following.

------
WARNING: No specific packages to update were provided
so we are going to update all available packages.
It is recommended to update everything only as part of upgrade
of the Satellite to the next version.
To Upgrade to next version use 'foreman-maintain upgrade'.
------

Need more clarity on:

1) Is it recommended to apply only the security patches on the RHEL server running Satellite? If 'foreman-maintain packages update' is not recommended, what would be the best practise to update the security patches.

2) Does "foreman-maintain packages update" work in the same manner as "yum update" would(RHEL minor version upgrade)? RHEL 7.8 to 7.9 as an example?

One of my customers raised this case and was not satisfied with the explanation from https://access.redhat.com/solutions/4591281. He is concerned about the above said warning message and looking for the best practices. Questions from the customer:

--> Is it really recommended not to update the OS but wait for a new satellite release?  That means satellite/capsule servers will have security issues.

--> Can we trust that RedHat will create new satellite releases each time there are important security fixes?

It would be great if we can add more details to the warning message, with reference to the points which I have mentioned 1 & 2.

      
4. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

No
      
5. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

No  
    
6. Is the sales team involved in this request and do they have any additional input?  

No  
      
7. Would the customer be able to assist in testing this functionality if implemented?  

Yes
Comment 2 Brad Buckingham 2023-07-21 21:06:39 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 4 Eric Helms 2024-06-06 01:06:01 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 5 Red Hat Bugzilla 2024-10-05 04:25:12 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.