openshift-ci-robot
commented
2 weeks ago @djoshy: This pull request explicitly references no jira issue.
In response to [this](https://github.com/openshift/origin/pull/29262):
>The [last set of timeout failures are isolated to SNO](https://sippy.dptools.openshift.org/sippy-ng/tests/4.18/analysis?test=%5Bsig-mco%5D%5BOCPFeatureGate%3AManagedBootImagesAWS%5D%5BSerial%5D%20Should%20update%20boot%20images%20on%20all%20MachineSets%20when%20configured%20%5Bapigroup%3Amachineconfiguration.openshift.io%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fserial%5D&filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22%5Bsig-mco%5D%5BOCPFeatureGate%3AManagedBootImagesAWS%5D%5BSerial%5D%20Should%20update%20boot%20images%20on%20all%20MachineSets%20when%20configured%20%5Bapigroup%3Amachineconfiguration.openshift.io%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fserial%5D%22%7D%2C%7B%22columnField%22%3A%22variants%22%2C%22not%22%3Atrue%2C%22operatorValue%22%3A%22contains%22%2C%22value%22%3A%22never-stable%22%7D%2C%7B%22columnField%22%3A%22variants%22%2C%22not%22%3Atrue%2C%22operatorValue%22%3A%22contains%22%2C%22value%22%3A%22aggregated%22%7D%5D%2C%22linkOperator%22%3A%22and%22%7D), I suspect this is because the controller waits for "one" control plane node to be up-to date. This can take an unpredicatable amount of time, depending on other cluster variables. Increasing [the timeout helped a bit](https://github.com/openshift/origin/pull/29210), but whenever SNO goes through a "slow" patch, these failures will creep up again. Further, boot images updates are not applicable for SNO, as they are never scaled up after installation - so updating the machineset in such a case is moot. Let's skip these tests for the SNO cases.
Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). 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.
djoshy
yuqi-zhang
openshift-ci[bot]
openshift-bot
The last set of timeout failures are isolated to SNO, I suspect this is because the controller waits for "one" control plane node to be up-to date. This can take an unpredicatable amount of time, depending on other cluster variables. Increasing the timeout helped a bit, but whenever SNO goes through a "slow" patch, these failures will creep up again. Further, boot images updates are not applicable for SNO, as they are never scaled up after installation - so updating the machineset in such a case is moot. Let's skip these tests for the SNO cases.