Description of problem: Setup OCP 4.3 with baremetal with PXE boot. The bootstrap node install the rhcos system and then boot from disk. After that. the bootstrap machine always be restarted. Version-Release number of the following components: https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.3/43.81.201911262150.0/x86_64/rhcos-43.81.201911262150.0-installer-kernel-x86_64 https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.3/43.81.201911262150.0/x86_64/rhcos-43.81.201911262150.0-installer-initramfs.x86_64.img https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.3/43.81.201911262150.0/x86_64/rhcos-43.81.201911262150.0-metal.x86_64.raw.gz registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-12-02-055401 How reproducible: always Steps to Reproduce: 1. the following is the pxeboot file: DEFAULT pxeboot TIMEOUT 20 PROMPT 0 LABEL pxeboot KERNEL rhcos/images/latest/installer-kernel APPEND ip=dhcp rd.neednet=1 initrd=rhcos/images/latest/installer-initramfs.img console=tty0 console=ttyS0 coreos.inst=yes coreos.inst.install_dev=sda coreos.inst.image_url=http://192.168.222.1:8000/rhcos/images/latest/metal-bios.raw.gz coreos.inst.ignition_url=http://192.168.222.1:8000/rhcos/ignitions/bootstrap.ign debug IPAPPEND 2 2. boot server with pxeboot 3. Actual results: after the rhcos is installed. the machine will restart and boot from disk. then the bootstrap enter the restart mode. since cannot ssh into the bootstrap rhcos. So very hard get the logs. please see picture. the machine will be there about 5 mins. and then be restarted with same behaviour Expected results: Additional info: it worked well with same config files when using 4.2 rhcos pxeboot image file. after I download the 4.3 rhcos pxeboot image. always met this issue.
Created attachment 1641688 [details] bootstrap restart after this
This is likely https://bugzilla.redhat.com/show_bug.cgi?id=1775388 which is being evaluated, can you confirm if the host has TPM 2.0 support enabled?
*** Bug 1779220 has been marked as a duplicate of this bug. ***
(In reply to Scott Dodson from comment #2) > This is likely https://bugzilla.redhat.com/show_bug.cgi?id=1775388 which is > being evaluated, can you confirm if the host has TPM 2.0 support enabled? I saw in bios setting--> system security show: TPM Information No TPM present
BTW, the TPM 2.0 is required for 4.3? Since our testing server cannot be supported for now. maybe this need hardware supported also I guess. is there a workaround to skip this?
Disk encryption will soon be disabled by default and new boot images will be generated with that change. In the meantime, you can use this MachineConfig snippet as a guide for how to disable disk encryption on nodes: ``` apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: labels: machineconfiguration.openshift.io/role: master name: 50-no-encrypt-master spec: config: ignition: version: 2.2.0 storage: files: - contents: source: data:text/plain;charset=utf-8;base64,Cg== filesystem: root mode: 0644 path: /etc/rhcos-no-clevis ```
Thanks the comment @micah BTW, where to add above MachineConfig ? in manifest/ folder by `openshift-install create manifests`?
(In reply to zhaozhanqi from comment #7) > Thanks the comment @micah > > BTW, where to add above MachineConfig ? in manifest/ folder by > `openshift-install create manifests`? Yeah, that should be the correct place.
Tried with the latest rhcos image Build 43.81.201912092147.0 this issue has been resolved.
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:0062