Bug 1811846
Summary: | Default value for replicas in config.imageregistry changed for baremetal | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Oleg Bulatov <obulatov> | |
Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> | |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.4 | CC: | aos-bugs | |
Target Milestone: | --- | |||
Target Release: | 4.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: the operator was bootstrapping the registry with 0 replicas by for baremetal installations
Consequence: CI scripts were changing managementState and storage configuration, but keep replicas 0
Fix: keep replicas=1
Result: CI works
|
Story Points: | --- | |
Clone Of: | ||||
: | 1811848 (view as bug list) | Environment: | ||
Last Closed: | 2020-07-13 17:19:21 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: | 1811848 |
Description
Oleg Bulatov
2020-03-09 22:42:38 UTC
It seems this change not just made to baremetal/ovirt/vsphere/none, right? since I can see AWS/OSP also has such change. This is an amendment for the bug 1810317. bug 1810317 - on AWS, and other cloud providers whose storage can be used with more than 1 replica, there should be 2 replicas. It introduced a new bug: on baremetal (where we don't have any default storage configuration) the new default was 0 replicas. this bug - on baremetal/ovirt/vsphere/none replicas should equal to 1, despite the fact that the management state is Removed. Verified on 4.5.0-0.nightly-2020-03-30-203132: on a UPI on Baremetal cluster, the image registry replica is 1 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, 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-2020:2409 |