openshift-ci-robot
commented
2 months ago @neisw: This pull request references OCPNODE-2357 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.18." or "openshift-4.18.", but it targets "openshift-4.17" instead.
In response to [this](https://github.com/openshift/machine-config-operator/pull/4523):
>Reverts openshift/machine-config-operator#4437 - Opening to just to run payload tests currently
>
>Seeing failures in 4.8 & 4.17 nightly payloads afther 4437 && https://github.com/openshift/machine-config-operator/pull/4518 landed for [e2e-aws-ovn-serial](https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial/1822233611227631616)
>
>```
>[sig-storage] [Serial] Volume metrics Ephemeral should create volume metrics with the correct BlockMode PVC ref [Suite:openshift/conformance/serial] [Suite:k8s] expand_less 5m0s
>{ schedulerName: default-scheduler
> securityContext: {}
> serviceAccount: default
> serviceAccountName: default
> terminationGracePeriodSeconds: 30
> tolerations:
> - effect: NoExecute
> key: node.kubernetes.io/not-ready
> operator: Exists
> tolerationSeconds: 300
> - effect: NoExecute
> key: node.kubernetes.io/unreachable
> operator: Exists
> tolerationSeconds: 300
> volumes:
> - ephemeral:
> volumeClaimTemplate:
> metadata:
> creationTimestamp: null
> spec:
> accessModes:
> - ReadWriteOnce
> resources:
> requests:
> storage: 2Gi
> volumeMode: Block
> name: volume1
> - name: kube-api-access-gzst8
> projected:
> defaultMode: 420
> sources:
> - serviceAccountToken:
> expirationSeconds: 3607
> path: token
> - configMap:
> items:
> - key: ca.crt
> path: ca.crt
> name: kube-root-ca.crt
> - downwardAPI:
> items:
> - fieldRef:
> apiVersion: v1
> fieldPath: metadata.namespace
> path: namespace
> - configMap:
> items:
> - key: service-ca.crt
> path: service-ca.crt
> name: openshift-service-ca.crt
> status:
> conditions:
> - lastProbeTime: null
> lastTransitionTime: "2024-08-10T13:06:04Z"
> status: "True"
> type: PodReadyToStartContainers
> - lastProbeTime: null
> lastTransitionTime: "2024-08-10T13:05:54Z"
> status: "True"
> type: Initialized
> - lastProbeTime: null
> lastTransitionTime: "2024-08-10T13:05:54Z"
> message: 'containers with unready status: [write-pod]'
> reason: ContainersNotReady
> status: "False"
> type: Ready
> - lastProbeTime: null
> lastTransitionTime: "2024-08-10T13:05:54Z"
> message: 'containers with unready status: [write-pod]'
> reason: ContainersNotReady
> status: "False"
> type: ContainersReady
> - lastProbeTime: null
> lastTransitionTime: "2024-08-10T13:05:54Z"
> status: "True"
> type: PodScheduled
> containerStatuses:
> - image: quay.io/openshift/community-e2e-images:e2e-7-registry-k8s-io-e2e-test-images-busybox-1-36-1-1-n3BezCOfxp98l84K
> imageID: ""
> lastState: {}
> name: write-pod
> ready: false
> restartCount: 0
> started: false
> state:
> waiting:
> message: |
> container create failed: mknod `/mnt/`: No such file or directory
> reason: CreateContainerError
> hostIP: 10.0.109.141
> hostIPs:
> - ip: 10.0.109.141
> phase: Pending
> podIP: 10.128.3.3
> podIPs:
> - ip: 10.128.3.3
> qosClass: BestEffort
> startTime: "2024-08-10T13:05:54Z"
>Error: exit with code 1
>Ginkgo exit error 1: exit with code 1}
>```
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.
openshift-ci[bot]
neisw
sohankunkerkar
xueqzhan
deads2k
openshift-bot
Reverts openshift/machine-config-operator#4437; tracked by https://issues.redhat.com/browse/OCPBUGS-38320
Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.
4.18/4.17 Disruption failures
To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:
CC: @sohankunkerkar