Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CNTRLPLANE-1: Update etcd test data for 1.32 release #29376

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bertinatto
Copy link
Member

@bertinatto bertinatto commented Dec 13, 2024

This is intended to fix:

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2147-ci-4.19-e2e-aws-ovn-techpreview-serial/1867506662982553600

[sig-api-machinery] API data in etcd should be stored at the correct location and version for all resources [Serial] [Suite:openshift/conformance/serial] expand_less 	15s
{  fail [github.com/openshift/origin/test/extended/etcd/etcd_storage_path.go:482]: test failed:
no test data for resource.k8s.io/v1beta1, Kind=DeviceClass.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceClaim.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceClaimTemplate.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceSlice.  Please add a test for your new type to etcdStorageData.
GVK for resource.k8s.io/v1alpha3, Kind=DeviceClass does not match, expected resource.k8s.io/v1alpha3, Kind=DeviceClass got resource.k8s.io/v1beta1, Kind=DeviceClass
GVK for resource.k8s.io/v1alpha3, Kind=ResourceClaim does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceClaim got resource.k8s.io/v1beta1, Kind=ResourceClaim
GVK for resource.k8s.io/v1alpha3, Kind=ResourceClaimTemplate does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceClaimTemplate got resource.k8s.io/v1beta1, Kind=ResourceClaimTemplate
GVK for resource.k8s.io/v1alpha3, Kind=ResourceSlice does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceSlice got resource.k8s.io/v1beta1, Kind=ResourceSlice
etcd data does not match the types we saw:
seen but not in etcd data:
[
	resource.k8s.io/v1beta1, Resource=resourceslices 
	resource.k8s.io/v1beta1, Resource=resourceclaims 
	resource.k8s.io/v1beta1, Resource=resourceclaimtemplates 
	resource.k8s.io/v1beta1, Resource=deviceclasses]
Ginkgo exit error 1: exit with code 1}

/assign @dusk125

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 13, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2024

@bertinatto: This pull request references CNTRLPLANE-1 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 epic to target the "4.19.0" version, but no target version was set.

In response to this:

/assign @dusk125

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2024

@bertinatto: This pull request references CNTRLPLANE-1 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 epic to target the "4.19.0" version, but no target version was set.

In response to this:

This is intended to fix:

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2147-ci-4.19-e2e-aws-ovn-techpreview-serial/1867506662982553600

[sig-api-machinery] API data in etcd should be stored at the correct location and version for all resources [Serial] [Suite:openshift/conformance/serial] expand_less 	15s
{  fail [github.com/openshift/origin/test/extended/etcd/etcd_storage_path.go:482]: test failed:
no test data for resource.k8s.io/v1beta1, Kind=DeviceClass.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceClaim.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceClaimTemplate.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1beta1, Kind=ResourceSlice.  Please add a test for your new type to etcdStorageData.
GVK for resource.k8s.io/v1alpha3, Kind=DeviceClass does not match, expected resource.k8s.io/v1alpha3, Kind=DeviceClass got resource.k8s.io/v1beta1, Kind=DeviceClass
GVK for resource.k8s.io/v1alpha3, Kind=ResourceClaim does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceClaim got resource.k8s.io/v1beta1, Kind=ResourceClaim
GVK for resource.k8s.io/v1alpha3, Kind=ResourceClaimTemplate does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceClaimTemplate got resource.k8s.io/v1beta1, Kind=ResourceClaimTemplate
GVK for resource.k8s.io/v1alpha3, Kind=ResourceSlice does not match, expected resource.k8s.io/v1alpha3, Kind=ResourceSlice got resource.k8s.io/v1beta1, Kind=ResourceSlice
etcd data does not match the types we saw:
seen but not in etcd data:
[
  resource.k8s.io/v1beta1, Resource=resourceslices 
  resource.k8s.io/v1beta1, Resource=resourceclaims 
  resource.k8s.io/v1beta1, Resource=resourceclaimtemplates 
  resource.k8s.io/v1beta1, Resource=deviceclasses]
Ginkgo exit error 1: exit with code 1}

/assign @dusk125

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.

@openshift-ci openshift-ci bot requested review from dusk125 and Elbehery December 13, 2024 18:53
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 13, 2024
@dusk125
Copy link
Contributor

dusk125 commented Dec 13, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 13, 2024
Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, dusk125

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:

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

@bertinatto
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial openshift/kubernetes#2147

Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c3bbbbd0-b999-11ef-8485-4df525008c08-0

@bertinatto
Copy link
Member Author

/retest-required

Copy link

openshift-trt bot commented Dec 13, 2024

Job Failure Risk Analysis for sha: b74a53b

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones High
[sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
This test has passed 99.24% of 132 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b7c61a7 and 2 for PR HEAD b74a53b in total

@bertinatto bertinatto force-pushed the fix-tp-serial-etcd-data branch from b74a53b to 48ebd00 Compare December 14, 2024 01:31
Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 14, 2024
@bertinatto
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial openshift/kubernetes#2147

Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/487cdc20-b9bb-11ef-8f3b-2dffa7abea46-0

Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

@bertinatto: The following tests 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-openstack-ovn 48ebd00 link false /test e2e-openstack-ovn
ci/prow/okd-scos-e2e-aws-ovn 48ebd00 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-csi 48ebd00 link false /test e2e-aws-csi
ci/prow/e2e-agnostic-ovn-cmd 48ebd00 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 48ebd00 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node 48ebd00 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial 48ebd00 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade 48ebd00 link false /test e2e-aws-ovn-single-node-upgrade

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants