Bug 2232171
| Summary: | rhosp-release is showing 'Beta' - RHEL 9 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jason Joyce <jjoyce> |
| Component: | rhosp-release | Assignee: | Jason Joyce <jjoyce> |
| Status: | CLOSED ERRATA | QA Contact: | Lon Hohberger <lhh> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 17.1 (Wallaby) | CC: | jamsmith, lhh |
| Target Milestone: | ga | Keywords: | Triaged |
| Target Release: | 17.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhosp-release-17.1.0-2.el9ost | Doc Type: | Known Issue |
| Doc Text: |
If you download RHOSP 17.1.0 GA in the first few days of its availability, you might find that the version description in the file /etc/rhosp/release incorrectly includes the Beta designation, as shown in the following example.
+
----
(overcloud) [stack@undercloud-0 ~]$ cat /etc/rhosp-release
Red Hat OpenStack Platform release
17.1.0 Beta (Wallaby)
----
+
Workaround: If your GA deployment is affected, run the following command: `# dnf -y update rhosp-release`
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-16 13:05:01 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: | 2232199 | ||
|
Description
Jason Joyce
2023-08-15 17:34:31 UTC
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 (Red Hat OpenStack Platform 17.1.0 bug fix advisory), 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-2023:4661 Our fix was to simply update the text in the rhosp-release package here - customers who have deployed OSP 17.1 should simply update it a la: # dnf -y update rhosp-release |