Bug 1649329
| Summary: | [RFE] foreman-maintain should be self-updating | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Rich Jerrido <rjerrido> |
| Component: | Satellite Maintain | Assignee: | Amit Upadhye <aupadhye> |
| Status: | CLOSED ERRATA | QA Contact: | Jameer Pathan <jpathan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3.1 | CC: | apatel, aupadhye, bkearney, cdonnell, fgarciad, greartes, inecas, kgaikwad, mbacovsk, mmccune, rakumar, smallamp, spetrosi |
| Target Milestone: | 6.8.0 | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-0.6.4 | Doc Type: | Enhancement |
| Doc Text: |
The `satellite-maintain` package now upgrades itself automatically when you enter `satellite-maintain upgrade check` or `satellite-maintain upgrade run` commands. Optionally, you can use the `--disable-self-upgrade` option to skip the auto-update of the `satellite-maintain` package.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 12:38:20 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: | |||
| Bug Blocks: | 1827137 | ||
|
Description
Rich Jerrido
2018-11-13 12:05:58 UTC
Hello Rich, A couple of questions with respect to auto-updating foreman-maintain. 1. Since foreman-maintain ships in a separate repository that's not tied to a satellite release, if the user periodically does yum update, she should always be on latest foreman-maintain right? 2. What would be the source for determining a newer version of foreman-maintain? External API would be out of scope. Would `yum check-update rubygem-foreman_maintain` be reasonable? Anurag 1) yes, but most customers don't randomly or periodically 'yum update'. They often only do it during Satellite upgrades so this often gets missed. 2) `yum check-update rubygem-foreman_maintain` should be fine, I'd definitely rely on yum. will be interesting to see if you can get a process to spawn yum to update itself, but if that proves difficult we can at least error out and say to the user: 'there is a new version of rubygem-foreman_maintain, please yum update this package to ensure you have the latest version' or something to that effect. Also note: There may be cases and times users don't want to auto-update (bugs or compatibility issues that we didn't handle) so we need an option to skip or whitelist. +1 to what Mike said. *** Bug 1674937 has been marked as a duplicate of this bug. *** Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28649 has been resolved. # foreman-maintain upgrade check --target-version 6.8.z Checking for new version of satellite-maintain... rubygem-foreman_maintain.noarch 1:0.6.5-1.el7sat Sat6-CI_Red_Hat_Satellite_6_8_Composes_Satellite_Maintenance_Next_RHEL7 Updating satellite-maintain package. The satellite-maintain package successfully updated. Re-run satellite-maintain with required options! Verified: - Satellite 6.8.0 snap 4 - rubygem-foreman_maintain-0.6.4-1.el7sat.noarch.rpm Observations: - Whenever user will run foreman-maintain upgrade command with run/check option, it'll check if there is any update available and if so then it will auto-update foreman-maintain and will ask user to re-run the command. - Users can skip auto-update of foreman-maintain package using --disable-self-upgrade option. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Satellite 6.8 Satellite Maintenance Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4365 |