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-961: [release-4.18] Fix the length of generated OBC bucket name #252

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #251

/assign vbnrh

@vbnrh
Copy link
Member

vbnrh commented Dec 19, 2024

/lgtm
/approve

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

openshift-ci bot commented Dec 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, vbnrh

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

@vbnrh
Copy link
Member

vbnrh commented Dec 19, 2024

/retitle DFBUGS-461: [release-4.18] Fix the length of generated OBC bucket name

@openshift-ci openshift-ci bot changed the title [release-4.18] Fix the length of generated OBC bucket name DFBUGS-461: [release-4.18] Fix the length of generated OBC bucket name Dec 19, 2024
@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 19, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-461](https://issues.redhat.com//browse/DFBUGS-461), which is invalid:

  • expected the bug to target either version "odf-4.18." or "openshift-odf-4.18.", but it targets "odf-4.16.5" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

This is an automated cherry-pick of #251

/assign vbnrh

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/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Dec 19, 2024
@vbnrh
Copy link
Member

vbnrh commented Dec 19, 2024

/retitle DFBUGS-961: [release-4.18] Fix the length of generated OBC bucket name

@openshift-ci openshift-ci bot changed the title DFBUGS-461: [release-4.18] Fix the length of generated OBC bucket name DFBUGS-961: [release-4.18] Fix the length of generated OBC bucket name Dec 19, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Dec 19, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-961](https://issues.redhat.com//browse/DFBUGS-961), 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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

This is an automated cherry-pick of #251

/assign vbnrh

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 removed the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Dec 19, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 6c85be5 into red-hat-storage:release-4.18 Dec 19, 2024
11 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024

@openshift-cherrypick-robot: [Jira Issue DFBUGS-961](https://issues.redhat.com//browse/DFBUGS-961): All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #251

/assign vbnrh

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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.

3 participants