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

OCPBUGS-48403: Bring groupsnapshot beta feature to 4.18 #2169

Conversation

jsafrane
Copy link

@jsafrane jsafrane commented Jan 13, 2025

Backport volume group snapshot tests to OCP 4.18. There is one <carry> patch that enables volume group feature gate in a test manifest by default, because that's our goal in 4.18 - have the feature enabled by default. The carry patch has been removed, it breaks other tests. So this just brings a new test + marks it as [Disabled:Alpha]. We will solve it differently.

Corresponding 4.19 PR: #2155

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Jan 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 13, 2025

@jsafrane: This pull request references STOR-2135 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 the "4.18.0" version, but no target version was set.

In response to this:

Backport volume group snapshot tests to OCP 4.18. There is one <carry> patch that enables volume group feature gate in a test manifest by default, because that's our goal in 4.18 - have the feature enabled by default.

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

@jsafrane: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 13, 2025

@jsafrane: This pull request references STOR-2135 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 the "4.18.0" version, but no target version was set.

In response to this:

Backport volume group snapshot tests to OCP 4.18. There is one <carry> patch that enables volume group feature gate in a test manifest by default, because that's our goal in 4.18 - have the feature enabled by default.

Corresponding 4.19 PR: #2155

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 deads2k and jerpeter1 January 13, 2025 17:05
@jsafrane jsafrane changed the title STOR-2135: Bring groupsnapshot beta feature to 4.18 OCPBUGS-48403: Bring groupsnapshot beta feature to 4.18 Jan 15, 2025
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-48403, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-48402 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48402 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Backport volume group snapshot tests to OCP 4.18. There is one <carry> patch that enables volume group feature gate in a test manifest by default, because that's our goal in 4.18 - have the feature enabled by default.

Corresponding 4.19 PR: #2155

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 openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 15, 2025
@jsafrane
Copy link
Author

/retest

@jsafrane
Copy link
Author

/test help

Copy link

openshift-ci bot commented Jan 20, 2025

@jsafrane: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test artifacts
/test configmap-scale
/test e2e-aws-crun-wasm
/test e2e-aws-jenkins
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-downgrade
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-runc
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-upgrade
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-ovn-upgrade
/test images
/test integration
/test k8s-e2e-conformance-aws
/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/test okd-scos-images
/test perfscale-control-plane-6nodes
/test unit
/test verify
/test verify-commits

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-ovn
/test e2e-aws-single-node
/test e2e-azure
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-openstack
/test e2e-openstack-csi-cinder
/test e2e-openstack-csi-manila
/test e2e-vsphere
/test k8s-e2e-aws
/test k8s-e2e-aws-ovn-serial
/test k8s-e2e-gcp-five-control-plane-replicas
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-kubernetes-release-4.18-artifacts
pull-ci-openshift-kubernetes-release-4.18-e2e-agnostic-ovn-cmd
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-crun-wasm
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-csi
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-fips
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-runc
pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-release-4.18-e2e-gcp
pull-ci-openshift-kubernetes-release-4.18-e2e-gcp-ovn-upgrade
pull-ci-openshift-kubernetes-release-4.18-images
pull-ci-openshift-kubernetes-release-4.18-integration
pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-conformance-aws
pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-gcp-ovn
pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-gcp-serial
pull-ci-openshift-kubernetes-release-4.18-okd-scos-e2e-aws-ovn
pull-ci-openshift-kubernetes-release-4.18-okd-scos-images
pull-ci-openshift-kubernetes-release-4.18-unit
pull-ci-openshift-kubernetes-release-4.18-verify
pull-ci-openshift-kubernetes-release-4.18-verify-commits

In response to this:

/test help

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.

jsafrane added a commit to jsafrane/origin that referenced this pull request Jan 21, 2025
Copy link

openshift-ci bot commented Jan 21, 2025

@jsafrane: This PR was included in a payload test run from openshift/origin#29455
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/14c69e80-d7dd-11ef-81a4-277ec891544d-0

@jsafrane
Copy link
Author

/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
Run this without openshift/origin#29455 to see how it fails to pull images

Copy link

openshift-ci bot commented Jan 21, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3a789520-d7dd-11ef-8f7d-a0d037a5b880-0

@jsafrane
Copy link
Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm openshift/origin#29455
And run it again with the origin PR to see the images are mirrored now

Copy link

openshift-ci bot commented Jan 21, 2025

@jsafrane: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. unable to get additional pr info from string: run: string: run doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

@jsafrane
Copy link
Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm openshift/origin#29455

And run it again with the origin PR to see the images are mirrored now

Copy link

openshift-ci bot commented Jan 21, 2025

@jsafrane: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. unable to get additional pr info from string: And: string: And doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

@bertinatto
Copy link
Member

/retest

jsafrane added a commit to jsafrane/origin that referenced this pull request Jan 21, 2025
Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed this with the Storage Team and the plan is to merge this in 4.18 and, once the k8s 1.32 bump lands, merge it in 4.19.

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2025
@bertinatto
Copy link
Member

/hold

We need openshift/origin#29455 before merging this, otherwise metal jobs will get broken.

@jsafrane
Copy link
Author

/retest-required

@jsafrane
Copy link
Author

I can see a baremetal job that mirrors its images succeeded: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-kubernetes-2169-nightly-4.18-e2e-metal-ipi-ovn-bm/1882350627531526144 (e2e script logs with mirroring here)

So when it comes to image mirroring, this is ready for merge.

@jsafrane
Copy link
Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 23, 2025
@duanwei33
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 23, 2025
Copy link

openshift-ci bot commented Jan 23, 2025

@jsafrane: 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-agnostic-ovn-cmd b8e6734 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-csi b8e6734 link false /test e2e-aws-csi
ci/prow/okd-scos-e2e-aws-ovn b8e6734 link false /test okd-scos-e2e-aws-ovn
ci/prow/k8s-e2e-aws-ovn-serial b8e6734 link false /test k8s-e2e-aws-ovn-serial

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.

@jsafrane
Copy link
Author

/retest-required

@gnufied
Copy link
Member

gnufied commented Jan 23, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2025
Copy link

openshift-ci bot commented Jan 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, gnufied, jsafrane

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

@jsafrane
Copy link
Author

/validate-backports

@openshift-ci-robot
Copy link

@jsafrane: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@p0lyn0mial
Copy link

/remove-label backports/unvalidated-commits

@openshift-ci openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 24, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7665f4b into openshift:release-4.18 Jan 24, 2025
18 of 22 checks passed
@openshift-ci-robot
Copy link

@jsafrane: Jira Issue OCPBUGS-48403: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-48403 has not been moved to the MODIFIED state.

In response to this:

Backport volume group snapshot tests to OCP 4.18. There is one <carry> patch that enables volume group feature gate in a test manifest by default, because that's our goal in 4.18 - have the feature enabled by default. The carry patch has been removed, it breaks other tests. So this just brings a new test + marks it as [Disabled:Alpha]. We will solve it differently.

Corresponding 4.19 PR: #2155

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.

jsafrane added a commit to jsafrane/origin that referenced this pull request Jan 24, 2025
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.18.0-202501241032.p0.g7665f4b.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.18.0-202501241032.p0.g7665f4b.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.18.0-202501241032.p0.g7665f4b.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.18.0-202501241032.p0.g7665f4b.assembly.stream.el9.
All builds following this will include this PR.

jsafrane added a commit to jsafrane/origin that referenced this pull request Jan 30, 2025
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.