origin icon indicating copy to clipboard operation
origin copied to clipboard

Conformance test suite for OpenShift

Results 577 origin issues
Sort by recently updated
recently updated
newest added

Reapply the changes from PR #29074 that were previously reverted, and mark both certificate tests as informing so failures don't block CI jobs. ## Changes ### Commit 1: Reapply PR...

jira/invalid-bug
jira/valid-reference

This case is about checking the Kubelet log level is 2. Here is the test case link : https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-55033 It is duplicate of PR: https://github.com/openshift/origin/pull/30460 PR: 30460 got closed because...

Test Coverage for Bug: https://issues.redhat.com/browse/OCPBUGS-63348 Test steps : 1. Check the node capacity ``` Annotations: cloud.network.openshift.io/egress-ipconfig: [{"interface":"eni-018a493be1e8adf3f","ifaddr":{"ipv4":"10.0.0.0/18"},"capacity":{"ipv4":14,"ipv6":15}}] csi.volume.kubernetes.io/nodeid: {"ebs.csi.aws.com":"i-061369b27ea9661fc"} ``` 2. Label it as egress node 3. Configure multiple EIPs...

Add three new test cases to validate etcd cluster recovery from cold boot scenarios reached through different graceful/ungraceful shutdown combinations: - Cold boot from double GNS: both nodes gracefully shut...

approved
jira/valid-reference

Both testUpgradeOperatorStateTransitions and testStableSystemOperatorStateTransitions calls testOperatorStateTransitions to check ClusterOperator's condition to validate CO's SLOs. The former is exectuted in a upgrade test and the latter is in a non-upgrade test....

The new reasons are ImageConfigControllerError and Unavailable. It would help jobs such as [1, 2]. [1]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-vsphere-ovn-upgrade/1997799449451040768 [2]. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips/1997883437565874176

If a cluster upgrade is blocked before co/machine-config starts to update (`Progressing=True`), then `machineConfigProgressingStart` is zero. In that case, the rule "each CO should stay `Progressing=False` while MCO is `Progressing=True`"...

See #30262 for reference. In response to #30557 .

lgtm
jira/valid-reference
verified

Register the OTE binary cluster-kube-descheduler-operator as part of JIRA [ticket](https://issues.redhat.com/browse/CNTRLPLANE-2185) (first [PR](https://github.com/openshift/cluster-kube-descheduler-operator/pull/1071) already merged).

lgtm
do-not-merge/hold
jira/valid-reference