Bug 2115803

Summary: create-cluster-and-infraenv.service fails when agent-config.yaml does not contain NMStateConfig
Product: OpenShift Container Platform Reporter: Richard Su <rwsu>
Component: InstallerAssignee: Pawan Pinjarkar <ppinjark>
Installer sub component: Agent based installation QA Contact: Manoj Hans <mhans>
Status: CLOSED WONTFIX Docs Contact:
Severity: high    
Priority: high CC: asegurap, mhans, ppinjark, zbitter
Version: 4.11   
Target Milestone: ---   
Target Release: 4.12.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: 2024-04-30 18:04:53 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:
Attachments:
Description Flags
journalctl log from node0 none

Description Richard Su 2022-08-05 12:32:01 UTC
Created attachment 1903905 [details]
journalctl log from node0

Description:

I was testing the DHCP scenario where only rendezvousIP is specified in the agent-config.yaml and no NMStateConfig is embedded. create-cluster-and-infraenv.service fails on node0 when networkConfig is missing from agent-config.yaml. /etc/assisted/manifests/nmstateconfig.yaml is an empty file.

agent-config.yaml used:

metadata:
  name: ostest
  namespace: cluster0
spec:
  rendezvousIP: 192.168.122.2

Steps to reproduce:

1. Create agent.iso using install-config.yaml and agent-config.yaml
2. Deploy cluster using agent.iso
3. Log into node0 and create-cluster-and-infraenv.service will be displayed as a failed unit.

Expected:

create-cluster-and-infraenv.service in success state

Actual:

create-cluster-and-infraenv.service in failed state

Aug 05 08:27:59 control1 podman[2681]: time="2022-08-05T08:27:59Z" level=info msg="releaseImage version 4.11.0-0.okd-2022-08-04-074610 cpuarch x86_64"
Aug 05 08:27:59 control1 create-cluster-and-infraenv[2693]: time="2022-08-05T08:27:59Z" level=info msg="Registered cluster with id: 1cc3ea1a-5bbc-4c4d-ad66-6e052800fb0c"
Aug 05 08:27:59 control1 create-cluster-and-infraenv[2693]: time="2022-08-05T08:27:59Z" level=info msg="Registering infraenv"
Aug 05 08:27:59 control1 podman[2681]: time="2022-08-05T08:27:59Z" level=info msg="Registered cluster with id: 1cc3ea1a-5bbc-4c4d-ad66-6e052800fb0c"
Aug 05 08:27:59 control1 podman[2681]: time="2022-08-05T08:27:59Z" level=info msg="Registering infraenv"
Aug 05 08:27:59 control1 create-cluster-and-infraenv[2693]: time="2022-08-05T08:27:59Z" level=fatal msg="Failed to register infraenv with assisted-service: nmstateconfig should have at least one label set matching the infra-env label selector"
Aug 05 08:27:59 control1 podman[2681]: time="2022-08-05T08:27:59Z" level=fatal msg="Failed to register infraenv with assisted-service: nmstateconfig should have at least one label set matching the infra-env label selector"
Aug 05 08:27:59 control1 systemd[1]: create-cluster-and-infraenv.service: Main process exited, code=exited, status=1/FAILURE
Aug 05 08:27:59 control1 systemd[1]: create-cluster-and-infraenv.service: Failed with result 'exit-code'.
Aug 05 08:27:59 control1 systemd[1]: Failed to start Service that creates initial cluster and infraenv.

/etc/assisted/manifests/nmstateconfig.yaml is an empty file.

[core@control1 ~]$ sudo cat /etc/assisted/manifests/nmstateconfig.yaml 
[core@control1 ~]$

Comment 2 Zane Bitter 2022-08-17 02:37:44 UTC
Since the create-cluster-and-infraenv code is in the release payload, it's effectively not fixable for installing the 4.11 payload.

We'll need to either create a dummy NMStateConfig to keep it happy, or maintain the restriction that at least 1 network config must be supplied (even if the rendezvousIP is also set).

Comment 5 Manoj Hans 2022-09-28 11:05:36 UTC
Bug has been verified with 4.12.0-0.nightly-2022-09-26-111919 release. create-cluster-and-infraenv service started without any issue when only provided rendezvousIP in the agent-config.

Comment 7 Rory Thrasher 2024-04-30 18:04:53 UTC
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary