OCPBUGS-46072: create /run/nodeip-configuration before use

[rbbratta]

With nmstate br-ex creation using static IP, it looks like the systemd boot ordering can change and we can attempt to run 30-resolv-prepender before nodeip-configuration.service.

When 30-resolv-prepender runs it tries to touch a file in /run/nodeip-configuration when it does not exist.

nm-dispatcher[2409]: touch: cannot touch '/run/nodeip-configuration/br-ex-up': No such file or directory

The quick fix is to always mkdir before touching, then we don't have to track the global state of /run/nodeip-configuration

[openshift-ci-robot]

@rbbratta: This pull request references Jira Issue OCPBUGS-46072, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

With nmstate br-ex creation using static IP, it looks like the systemd boot ordering can change and we can attempt to run 30-resolv-prepender before nodeip-configuration.service.

When 30-resolv-prepender runs it tries to touch a file in /run/nodeip-configuration when it does not exist.

nm-dispatcher[2409]: touch: cannot touch '/run/nodeip-configuration/br-ex-up': No such file or directory

The quick fix is to always mkdir before touching, then we don't have to track the global state of /run/nodeip-configuration

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[cybertron]

/lgtm
/jira refresh
/label acknowledge-critical-fixes-only

[openshift-ci-robot]

@cybertron: This pull request references Jira Issue OCPBUGS-46072, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rbbratta

In response to this:

/lgtm
/jira refresh
/label acknowledge-critical-fixes-only

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: rbbratta.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@cybertron: This pull request references Jira Issue OCPBUGS-46072, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rbbratta

In response to this:

/lgtm
/jira refresh
/label acknowledge-critical-fixes-only

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cybertron, rbbratta
Once this PR has been reviewed and has the lgtm label, please assign cheesesashimi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cybertron]

/retest-required

[openshift-ci]

@rbbratta: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	010efe3	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-vsphere-ovn-upi-zones	010efe3	link	false	/test e2e-vsphere-ovn-upi-zones
ci/prow/e2e-azure-ovn-upgrade-out-of-change	010efe3	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-gcp-op-ocl	010efe3	link	false	/test e2e-gcp-op-ocl

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[pierreprinetti]

/uncc pierreprinetti