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

Bug 2050393

Summary: ZTP missing support for local image registry and custom machine config
Product: OpenShift Container Platform Reporter: Ian Miller <imiller>
Component: Telco EdgeAssignee: Ian Miller <imiller>
Telco Edge sub component: ZTP QA Contact: yliu1
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: keyoung
Version: 4.10   
Target Milestone: ---   
Target Release: 4.10.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: 2022-03-10 16:43:22 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: 2052710    

Comment 3 yliu1 2022-02-12 00:56:44 UTC 
Verified with latest ztp 4.10 image. 
CRs with expected contents are created successfully on spoke.

PGT used:
http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/ed8071fbac7cdf7e5b9e7d8272be1ea9a069cbc5/policygentemplates/group-du-sno-ranGen.yaml#L70-L115

Partitions added in siteconfig:
http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/ed8071fbac7cdf7e5b9e7d8272be1ea9a069cbc5/siteconfig/master-2.yaml#L39

Verified on spoke:
[core@master-2 ~]$ cat /etc/just_a_test.txt
It worked

[core@master-2 ~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
...
nvme0n1     259:0    0   1.5T  0 disk 
nvme3n1     259:1    0   1.5T  0 disk 
├─nvme3n1p1 259:2    0    30G  0 part 
├─nvme3n1p2 259:3    0    30G  0 part 
├─nvme3n1p3 259:4    0    30G  0 part 
└─nvme3n1p4 259:5    0    30G  0 part 

[yliu1@yliu1 ~]$ oc get storageclasses.storage.k8s.io -A
NAME     PROVISIONER                    RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
fs-lso   kubernetes.io/no-provisioner   Delete          WaitForFirstConsumer   false                  73m
[yliu1@yliu1 ~]$ oc get pv -A
NAME                CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
local-pv-3fdcc2a5   30Gi       RWO            Delete           Available           fs-lso                  73m
local-pv-529a8f77   30Gi       RWO            Delete           Available           fs-lso                  73m
local-pv-ef818af4   30Gi       RWO            Delete           Available           fs-lso                  73m
local-pv-f57519b2   30Gi       RWO            Delete           Available           fs-lso                  73m
[yliu1@yliu1 ~]$ oc get pvc -A
NAMESPACE   NAME               STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    AGE
default     registry-storage   Pending                                      $storageclass   73m
[yliu1@yliu1 ~]$ oc get configs.imageregistry.operator.openshift.io 
NAME      AGE
cluster   4h25m
Comment 5 errata-xmlrpc 2022-03-10 16:43:22 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.10.3 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-2022:0056