Bug 1915234 - [OCP on RHV] when choosing version to update channel, there is Ok button instead of Update button
Summary: [OCP on RHV] when choosing version to update channel, there is Ok button inst...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.z
Assignee: Steve Goodman
QA Contact: michal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-12 10:07 UTC by michal
Modified: 2022-02-16 11:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-10 11:24:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:0678 0 None None None 2021-03-10 11:24:36 UTC

Description michal 2021-01-12 10:07:55 UTC
Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version:

$ openshift-install version
<your output here>

Platform:

#Please specify the platform type: aws, libvirt, openstack or baremetal etc.

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)
* UPI (semi-manual installation on customized infrastructure)

What happened?

#Enter text here.

#See the troubleshooting documentation (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md) for ideas about what information to collect.

#For example, 

# If the installer fails to create resources (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-create-resources), attach the relevant portions of your `.openshift_install.log.`
# If the installer fails to bootstrap the cluster (https://github.com/openshift/installer/blob/master/docs/user/troubleshootingbootstrap.md), attach the bootstrap log bundle.
# If the installer fails to complete installation after bootstrapping completes (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-initialize-the-cluster), attach the must-gather log bundle using `oc adm must-gather`

# Always at least include the `.openshift_install.log`

What did you expect to happen?

#Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

#Enter text here.

Comment 1 Steve Goodman 2021-02-15 13:45:17 UTC
Michal,

Please provide more info, at least the topic where the bug appears.

Comment 3 Steve Goodman 2021-02-23 04:56:39 UTC
Michal,

Do you know if this applies to 4.5?

You can see the pull request at https://github.com/openshift/openshift-docs/pull/29663. Please approve.

Comment 4 michal 2021-02-24 19:45:59 UTC
I checked it, and I think that we need to change it also to 4.6 version.
will we have 4.7z documentation? or this fix related to 4.7 documentation?

Comment 5 Steve Goodman 2021-03-01 13:05:06 UTC
The PR applies to 4.6 and 4.7, including 4.7.z. The PR states that in the description.

It should also apply to 4.8, unless something is changing.

The only question is if it also applies to 4.5.

Comment 7 michal 2021-03-02 07:30:00 UTC
the button change from ok to update

Comment 9 errata-xmlrpc 2021-03-10 11:24:01 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 (OpenShift Container Platform 4.7.1 bug fix update), 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-2021:0678


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