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

DFBUGS-1145: Update externalsnapshotter volumegroupsnapshot container arg #65

Merged

Conversation

Madhu-1
Copy link
Member

@Madhu-1 Madhu-1 commented Dec 11, 2024

This is a backport of ceph#179.

Note:- Keeping it on hold until the downstream main is synced with upstream main

/hold

In external-snapshotter the groupsnapshot
feature flag is moved to a new container
argument and the old enable-volumegroup-snapshot
flag is removed, This PR updates the flag
to use external-snapshotter latest version,

Note:- As the flag is removed with Rook the
user cannot test/use the older version of
external-snapshotter for groupsnapshot
feature, but all other features will be still
supported with older releases.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 6f4dc24)
updating the external-snapshotter image
to the latest release.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 810accd)
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Dec 11, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 11, 2024

@Madhu-1: This pull request references [Jira Issue DFBUGS-1145](https://issues.redhat.com//browse/DFBUGS-1145), which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @nehaberry

In response to this:

This is a backport of ceph#179.

Note:- Keeping it on hold until the downstream main is synced with upstream main

/hold

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.

Copy link

openshift-ci bot commented Dec 11, 2024

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: nehaberry.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@Madhu-1: This pull request references [Jira Issue DFBUGS-1145](https://issues.redhat.com//browse/DFBUGS-1145), which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @nehaberry

In response to this:

This is a backport of ceph#179.

Note:- Keeping it on hold until the downstream main is synced with upstream main

/hold

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.

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.

@leelavg
Copy link

leelavg commented Dec 11, 2024

previously @Nikhil-Ladha mentioned that d/s automation will sync main daily and then we should raise a backport.

@Nikhil-Ladha
Copy link
Member

previously @Nikhil-Ladha mentioned that d/s automation will sync main daily and then we should raise a backport.

Yes, I have triggered a sync job, will update here once complete.
Though, seems like there is some outage in jenkins and a lot of jobs are in queue, so it might take some time

@Nikhil-Ladha
Copy link
Member

Sync PR is created #66 , I think we are good to close this PR now.

@Madhu-1
Copy link
Member Author

Madhu-1 commented Dec 12, 2024

This is a backport PR for 4.18 branch

/hold cancel

@Madhu-1
Copy link
Member Author

Madhu-1 commented Dec 12, 2024

/assign @nb-ohad

@nb-ohad
Copy link
Collaborator

nb-ohad commented Dec 12, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Dec 12, 2024
Copy link

openshift-ci bot commented Dec 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Madhu-1, nb-ohad

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

@openshift-merge-bot openshift-merge-bot bot merged commit 8032744 into red-hat-storage:release-4.18 Dec 12, 2024
13 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 12, 2024

@Madhu-1: [Jira Issue DFBUGS-1145](https://issues.redhat.com//browse/DFBUGS-1145): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-1145](https://issues.redhat.com//browse/DFBUGS-1145) has been moved to the MODIFIED state.

In response to this:

This is a backport of ceph#179.

Note:- Keeping it on hold until the downstream main is synced with upstream main

/hold

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/valid-bug Indicates that the 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants