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-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception #242

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #241

/assign GowthamShanmugam

Copy link
Contributor

openshift-ci bot commented Nov 28, 2024

@openshift-cherrypick-robot: GitHub didn't allow me to assign the following users: GowthamShanmugam.

Note that only red-hat-storage members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

This is an automated cherry-pick of #241

/assign GowthamShanmugam

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.

@GowthamShanmugam
Copy link
Contributor

GowthamShanmugam commented Nov 28, 2024

/retitle: DFBUGS-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception

@openshift-ci openshift-ci bot changed the title [release-4.18] Initialize Mirroring spec to avoid nil pointer exception : DFBUGS-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception Nov 28, 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-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Nov 28, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2024

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

  • expected the bug to target the "odf-4.18" version, but no target version was set

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 #241

/assign GowthamShanmugam

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.

@GowthamShanmugam
Copy link
Contributor

GowthamShanmugam commented Nov 28, 2024

/retitle DFBUGS-939](https://issues.redhat.com//browse/DFBUGS-939): [release-4.18] Initialize Mirroring spec to avoid nil pointer exception

@openshift-ci openshift-ci bot changed the title : DFBUGS-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception DFBUGS-939](https://issues.redhat.com//browse/DFBUGS-939): [release-4.18] Initialize Mirroring spec to avoid nil pointer exception Nov 28, 2024
@openshift-ci-robot openshift-ci-robot removed jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type labels Nov 28, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #241

/assign GowthamShanmugam

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 Nov 28, 2024
@GowthamShanmugam
Copy link
Contributor

GowthamShanmugam commented Nov 28, 2024

/retitle DFBUGS-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception

@openshift-ci openshift-ci bot changed the title DFBUGS-939](https://issues.redhat.com//browse/DFBUGS-939): [release-4.18] Initialize Mirroring spec to avoid nil pointer exception DFBUGS-939: [release-4.18] Initialize Mirroring spec to avoid nil pointer exception Nov 28, 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-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Nov 28, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2024

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

  • expected the bug to target the "odf-4.18" version, but no target version was set

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 #241

/assign GowthamShanmugam

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.

@GowthamShanmugam
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2024

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

  • expected the bug to target the "odf-4.18" version, but no target version was set

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:

/jira refresh

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.

@GowthamShanmugam
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Nov 28, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2024

@GowthamShanmugam: This pull request references [Jira Issue DFBUGS-939](https://issues.redhat.com//browse/DFBUGS-939), which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

/jira refresh

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
Contributor

openshift-ci bot commented Nov 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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 f334667 into red-hat-storage:release-4.18 Nov 28, 2024
11 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2024

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

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

In response to this:

This is an automated cherry-pick of #241

/assign GowthamShanmugam

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.

4 participants