Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1795508

Summary:	upgrade from 4.2.14 to 4.2.16 - NodeInstallerDegraded: 1 nodes are failing
Product:	OpenShift Container Platform	Reporter:	Alexander Klein <alklein>
Component:	Multi-Arch	Assignee:	David Benoit <dbenoit>
Status:	CLOSED DUPLICATE	QA Contact:	Barry Donahue <bdonahue>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.z	CC:	psundara, wking
Target Milestone:	---
Target Release:	---
Hardware:	s390x
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-03 09:15:26 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 Alexander Klein 2020-01-28 07:33:59 UTC

Description of problem:
i manually upgraded the clusterversion from 4.2.14 to 4.2.16 with the command 

oc adm upgrade --to-image=quay.io/openshift-release-dev/ocp-release@sha256:04b79afdbb41579e0f969bf23cdb16483dbfadbc09a6a0fec60b94328d68135a  --allow-explicit-upgrade=true --force

it upgraded successfully

oc version
Client Version: openshift-clients-4.2.2-201910250432-8-g98a84c61
Server Version: 4.2.16
Kubernetes Version: v1.14.6+8bbaf43

But after installation the kube-apiserver operator remains in degraded state and showing
Reason: NodeInstallerDegradedInstallerPodFailed
Message: NodeInstallerDegraded: 1 nodes are failing on revision 10:
NodeInstallerDegraded: pods "installer-10-master-1.m3559ocp.lnxne.boe" not found

Comment 1 Prashanth Sundararaman 2020-02-03 14:25:26 UTC

could you try a 4.2.12 -> 4.2.16 upgrade? 4.2.14 is not a supported release.

Comment 2 Alexander Klein 2020-03-03 09:15:26 UTC

that worked, still a bit confused which versions are supported and which not.

Comment 3 W. Trevor King 2020-03-14 04:28:16 UTC

> still a bit confused which versions are supported and which not.

See [1] about presence in fast/stable channels being the sign of support.  And that shows that 4.2.14 on s390x is not supported:

$ curl -sH 'Accept:application/json' 'https://api.openshift.com/api/upgrades_info/v1/graph?channel=fast-4.2&arch=s390x' | jq -r '.nodes[] | select(.version | contains("4.2.14"))'
...no matches...

See also [2].

[1]: https://docs.openshift.com/container-platform/4.2/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor
[2]: https://github.com/openshift/cincinnati-graph-data/blob/dc2a3c4cd879b0eeb7153c50f8706ad45166e8ac/channels/fast-4.2.yaml#L37-L38

*** This bug has been marked as a duplicate of bug 1789260 ***