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.

Bug 1827137

Summary: [RFE] foreman-maintain upgrades itself automatically
Product: Red Hat Satellite Reporter: Tahlia Richardson <trichard>
Component: DocumentationAssignee: Suyog Sainkar <ssainkar>
Status: CLOSED CURRENTRELEASE QA Contact: Jameer Pathan <jpathan>
Severity: unspecified Docs Contact: Sergei Petrosian <spetrosi>
Priority: unspecified    
Version: 6.8.0CC: dvoss, jpathan, mawerner, spetrosi, ssainkar
Target Milestone: 6.8.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-24 19:19:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1649329    
Bug Blocks:    

Comment 1 Sergei Petrosian 2020-04-23 10:48:53 UTC
The step to clean yum cache will not be needed too.

 Clean yum cache:

# yum clean all

What is the user story for disabling the auto-update? Sounds like something that support can ask CU to do to troubleshoot errors. I do not think that we must document disabling this smart feature at all.

Comment 2 Tahlia Richardson 2020-04-23 11:37:04 UTC
(In reply to Sergei Petrosian from comment #1)
> The step to clean yum cache will not be needed too.
> 
>  Clean yum cache:
> 
> # yum clean all
> 
> What is the user story for disabling the auto-update? Sounds like something
> that support can ask CU to do to troubleshoot errors. I do not think that we
> must document disabling this smart feature at all.

That's exactly what it's for, so I agree, let's not document it.

Comment 3 Tahlia Richardson 2020-06-09 08:48:50 UTC
(In reply to Tahlia Richardson from comment #2)
> (In reply to Sergei Petrosian from comment #1)
> > The step to clean yum cache will not be needed too.
> > 
> >  Clean yum cache:
> > 
> > # yum clean all
> > 
> > What is the user story for disabling the auto-update? Sounds like something
> > that support can ask CU to do to troubleshoot errors. I do not think that we
> > must document disabling this smart feature at all.
> 
> That's exactly what it's for, so I agree, let's not document it.

To be clear, what we've agreed not to document here is *disabling* the auto-update. We still need to document the auto-update itself as outlined in the description:

> Section Number and Name: Wherever foreman-maintain/satellite-maintain is
> mentioned.
> 
> Describe the issue: The foreman-maintain package will upgrade itself when
> you run a satellite upgrade or upgrade-check, so the user doesn't have to do
> it manually.
> 
> Suggestions for improvement: We have a step, in a few places, to upgrade the
> rubygem-foreman_maintain package. We can remove this.

Comment 12 Suyog Sainkar 2020-08-24 19:19:57 UTC
The enhancement note for this feature has been published live in the Release Notes: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8-beta/html-single/release_notes/index#enhancements