Bug 1950543

Summary:	Document non-HA behaviors in the MCO (SingleNodeOpenshift)
Product:	OpenShift Container Platform	Reporter:	Zack Zlotnik <zzlotnik>
Component:	Machine Config Operator	Assignee:	Zack Zlotnik <zzlotnik>
Status:	CLOSED ERRATA	QA Contact:	Michael Nguyen <mnguyen>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.8	CC:	jerzhang
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 23:01:42 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 Zack Zlotnik 2021-04-16 20:35:22 UTC

As a non-HA cluster user, it will be easier to manage the cluster without running into issues if I am aware of Do's and Don'ts.

Some of the identified topics to include:
- Post installation (if we need to pause pool post post-install complete for non-HA install – which we should try to avoid).
- There are a number of instances where you could accidentally reboot that should be documented.

See https://issues.redhat.com/browse/GRPA-3225 for additional information.

Comment 2 Zack Zlotnik 2021-04-19 18:07:26 UTC

This was a doc-only change in the MCO repository, setting to VERIFIED.

Comment 5 errata-xmlrpc 2021-07-27 23:01:42 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438