Cause: When there are no NMStateConfigs defined, the pre-network-manager-config.service attempts to process non-existing NMStateConfigs.
Consequence: The pre-network-manager-config.service fails because it cannot find NMStateConfigs to process.
Fix: When there are no NMStateConfigs defined, the pre-network-manager-config.service is disabled.
Result: The pre-network-manager-config.service is not enabled when no NMStateConfigs are defined.
Created attachment 1903893[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. pre-network-manager-config.service fails on node0 when networkConfig is missing from agent-config.yaml. /usr/local/bin/pre-network-manager-config.sh is not found on node0.
If NMStateConfig is not provided, then perhaps the service should not be included and activated in the ignition.
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 pre-network-manager-config.service will be displayed as a failed unit.
Expected:
pre-network-manager-config.service in success state
Actual:
pre-network-manager-config.service in failed state
Aug 05 08:27:18 localhost systemd[1]: Starting Prepare network manager config content...
Aug 05 08:27:18 localhost systemd[1]: pre-network-manager-config.service: Main process exited, code=exited, status=203/EXEC
Aug 05 08:27:18 localhost systemd[1]: pre-network-manager-config.service: Failed with result 'exit-code'.
Aug 05 08:27:18 localhost systemd[1]: Failed to start Prepare network manager config content.
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
Created attachment 1903893 [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. pre-network-manager-config.service fails on node0 when networkConfig is missing from agent-config.yaml. /usr/local/bin/pre-network-manager-config.sh is not found on node0. If NMStateConfig is not provided, then perhaps the service should not be included and activated in the ignition. 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 pre-network-manager-config.service will be displayed as a failed unit. Expected: pre-network-manager-config.service in success state Actual: pre-network-manager-config.service in failed state Aug 05 08:27:18 localhost systemd[1]: Starting Prepare network manager config content... Aug 05 08:27:18 localhost systemd[1]: pre-network-manager-config.service: Main process exited, code=exited, status=203/EXEC Aug 05 08:27:18 localhost systemd[1]: pre-network-manager-config.service: Failed with result 'exit-code'. Aug 05 08:27:18 localhost systemd[1]: Failed to start Prepare network manager config content.