Bug 1847624

Summary:	upgrade of crc cluster fails and retries indefinitely
Product:	OpenShift Container Platform	Reporter:	Cameron Meadors <cmeadors>
Component:	crc	Assignee:	Praveen Kumar <prkumar>
Status:	CLOSED EOL	QA Contact:	Tomáš Sedmík <tsedmik>
Severity:	medium	Docs Contact:	Kevin Owen <kowen>
Priority:	unspecified
Version:	4.4	CC:	cfergeau, gbraad, kowen, mifiedle, tsedmik, veillard
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-15 09:12:35 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:

Description Cameron Meadors 2020-06-16 17:24:56 UTC

Description of problem:

In place upgrade of a CRC cluster from 4.4.5 to 4.4.6 fails and retried indefinitely

Version-Release number of selected component (if applicable):
crc-linux-1.11.0-amd64

How reproducible:
I tired a new cluster and initiated an upgrade with the same results.

Steps to Reproduce:
1. Follow instructions to get a running CRC cluster up and running
2. Follow instructions to enable monitoring
3. Log in to console as kubeadmin
4. See that there is a update and click on upgrade

Actual results:
Upgrade progresses to 24% and fails and then retries infinitely.
I could not figure out how to cancel the upgrade once started.

Expected results:
Upgrade complete successfully


Additional info:
The error seems to be related to the Machine and MachineConfig operators.  SInce they are disabled in CRC, it seems reasonable for this to be a problem.

I am aware that the docs say that the upgrade process is to delete the old cluster download the new binary and build a new cluster, but the option was there and I wanted to see if it would work.  Maybe the option to upgrade should not be available if it will nevever work.

Documentation that I referred to is the official doc:

https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/1.11/html/getting_started_guide/index

Comment 1 Praveen Kumar 2020-06-17 05:51:24 UTC

@Cameron this option is present from the openshift side not from CRC side, will try to find a way to disable it completely if possible but as you pointed out in the documents there is no upgrade support path of openshift in CRC, you need to delete and start new version of CRC (if required openshift bundle is part of that release).

Comment 3 Praveen Kumar 2021-02-15 09:12:35 UTC

We do mention in the docs https://code-ready.github.io/crc/#differences-from-production-openshift-install_gsg there is no upgrade path for crc which can match production openshift cluster.