OCPBUGS-35300: Azure: add Azure specific dnsmasq ordering

[yuqi-zhang]

In 4.14 we slightly tweaked the services such that mcd-pull no longer depends on network-online.target. This broke some ARO disconnected environments that needed dnsmasq to be ready before the MCD-pull runs on firstboot.

Add in a new Azure template for MCD-pull with an additional After=dnsmasq.service so the strict ordering of:

1. ovs-configuration
2. dnsmasq
3. mcd-pull
4. mcd-firstboot

is adhered to.

- What I did

- How to verify it

- Description for the changelog

[openshift-ci-robot]

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-35300, which is invalid:

• expected the bug to target the "4.17.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:

In 4.14 we slightly tweaked the services such that mcd-pull no longer depends on network-online.target. This broke some ARO disconnected environments that needed dnsmasq to be ready before the MCD-pull runs on firstboot.

Add in a new Azure template for MCD-pull with an additional After=dnsmasq.service so the strict ordering of:

1. ovs-configuration
2. dnsmasq
3. mcd-pull
4. mcd-firstboot

is adhered to.

- What I did

- How to verify it

- Description for the changelog

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.

[yuqi-zhang]

/jira refresh

[openshift-ci-robot]

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-35300, 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.17.0) matches configured target version for branch (4.17.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

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.

[sinnykumari]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sinnykumari, yuqi-zhang

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sinnykumari,yuqi-zhang]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 0278c48 and 2 for PR HEAD a5dcc6f in total

[openshift-ci]

@yuqi-zhang: The following test 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/e2e-gcp-op-techpreview	a5dcc6f	link	false	/test e2e-gcp-op-techpreview

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.

[openshift-ci-robot]

@yuqi-zhang: Jira Issue OCPBUGS-35300: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#4404

Jira Issue OCPBUGS-35300 has been moved to the MODIFIED state.

In response to this:

In 4.14 we slightly tweaked the services such that mcd-pull no longer depends on network-online.target. This broke some ARO disconnected environments that needed dnsmasq to be ready before the MCD-pull runs on firstboot.

Add in a new Azure template for MCD-pull with an additional After=dnsmasq.service so the strict ordering of:

1. ovs-configuration
2. dnsmasq
3. mcd-pull
4. mcd-firstboot

is adhered to.

- What I did

- How to verify it

- Description for the changelog

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.

[yuqi-zhang]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@yuqi-zhang: new pull request created: #4406

In response to this:

/cherry-pick release-4.16

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-config-operator-container-v4.17.0-202406121741.p0.gfc878b8.assembly.stream.el9 for distgit ose-machine-config-operator.
All builds following this will include this PR.

[wking]

#4411 is up suggesting we revert this change.