Bug 2227307 - [RFE]: Update the RHUA server during the update process
Summary: [RFE]: Update the RHUA server during the update process
Keywords:
Status: NEW
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: RHUA
Version: 4.4.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Gregg Tanzillo
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-28 16:20 UTC by Taft Sanders
Modified: 2023-08-01 13:25 UTC (History)
0 users

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHUI-434 0 None None None 2023-08-01 13:25:46 UTC

Description Taft Sanders 2023-07-28 16:20:08 UTC
Description of problem:
To make the update process simpler, it would be great to see the rhui-installer offer an option like --upgrade that would update the RHUA application and the OS in 1 step.

Version-Release number of selected component (if applicable):
rhui-tools-4.4.0.5-1.el8ui.noarch

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:
With a healthy installation of RHUA, running a command like 'rhui-installer --rerun --upgrade' would update the RHUA software and perform a dnf update with only the required repos as mentioned in the installation guide.

Expected results:
1 command to update the application and the OS at the same time.

Additional info:
In the RHUI documentation, we specify to patch the server prior to preforming the update process[1]. This would make it so a user could run 1 command to perform all actions necessary to update the RHUA node.
[1]: https://access.redhat.com/documentation/en-us/red_hat_update_infrastructure/4/html-single/migrating_red_hat_update_infrastructure/index#proc_updating-rhui-manager_assembly_upgrading-red-hat-update-infrastructure


Note You need to log in before you can comment on or make changes to this bug.