openshift-ci-robot
commented
2 months ago @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](https://github.com/openshift/machine-config-operator/pull/4404):
>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](https://prow.ci.openshift.org/command-help?repo=openshift%2Fmachine-config-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
yuqi-zhang
sinnykumari
openshift-ci[bot]
openshift-cherrypick-robot
openshift-bot
wking
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:
is adhered to.
- What I did
- How to verify it
- Description for the changelog