Bug 2115798 - pre-network-manager-config.service fails when agent-config.yaml does not include nmstateconfig
Summary: pre-network-manager-config.service fails when agent-config.yaml does not incl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.12.0
Assignee: Richard Su
QA Contact: Manoj Hans
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-05 12:20 UTC by Richard Su
Modified: 2024-04-30 18:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2024-04-30 18:04:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
journalctl log from node0 (44.37 KB, application/gzip)
2022-08-05 12:20 UTC, Richard Su
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 6323 0 None open OCPBUGSM-47737: Do not enable pre-network-manager-config.service 2022-09-09 12:24:01 UTC

Description Richard Su 2022-08-05 12:20:14 UTC
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.

Comment 3 Manoj Hans 2022-09-28 12:10:02 UTC
Bug has been verified with 4.12.0-0.nightly-2022-09-26-111919 release. It's working fine when only provided rendezvousIP in the agent-config.

Comment 5 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


Note You need to log in before you can comment on or make changes to this bug.