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-1296: [release-4.18] Include networkfence and networkfenceclasses in must-gather #217

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #216

/assign black-dragon74

Signed-off-by: Niraj Yadav <niryadav@redhat.com>
@black-dragon74
Copy link
Member

/retitle [DFBUGS-1296] [release-4.18] Include networkfence and networkfenceclasses in must-gather

@openshift-ci openshift-ci bot changed the title [release-4.18] Include networkfence and networkfenceclasses in must-gather [DFBUGS-1296] [release-4.18] Include networkfence and networkfenceclasses in must-gather Jan 7, 2025
@black-dragon74
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

@black-dragon74: 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:

/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.

@black-dragon74
Copy link
Member

black-dragon74 commented Jan 7, 2025

/retitle DFBUGS-1296: [release-4.18] Include networkfence and networkfenceclasses in must-gather

@openshift-ci openshift-ci bot changed the title [DFBUGS-1296] [release-4.18] Include networkfence and networkfenceclasses in must-gather DFBUGS-1296: [release-4.18] Include networkfence and networkfenceclasses in must-gather Jan 7, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 7, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1296](https://issues.redhat.com//browse/DFBUGS-1296), 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)

No GitHub users were found matching the public email listed for the QA contact in Jira (oviner@redhat.com), skipping review request.

In response to this:

This is an automated cherry-pick of #216

/assign black-dragon74

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.

@black-dragon74
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 7, 2025

@black-dragon74: This pull request references [Jira Issue DFBUGS-1296](https://issues.redhat.com//browse/DFBUGS-1296), 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)

No GitHub users were found matching the public email listed for the QA contact in Jira (oviner@redhat.com), skipping review request.

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.

@black-dragon74
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm label Jan 8, 2025
Copy link
Contributor

openshift-ci bot commented Jan 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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-ci openshift-ci bot added the approved label Jan 8, 2025
@black-dragon74
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2025

@black-dragon74: This pull request references [Jira Issue DFBUGS-1296](https://issues.redhat.com//browse/DFBUGS-1296), 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)

No GitHub users were found matching the public email listed for the QA contact in Jira (oviner@redhat.com), skipping review request.

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.

@Nikhil-Ladha
Copy link
Member

/jira refresh

@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 Jan 8, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2025

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-1296](https://issues.redhat.com//browse/DFBUGS-1296), 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)

No GitHub users were found matching the public email listed for the QA contact in Jira (oviner@redhat.com), skipping review request.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit bc0549d into red-hat-storage:release-4.18 Jan 8, 2025
3 checks passed
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 8, 2025

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

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

In response to this:

This is an automated cherry-pick of #216

/assign black-dragon74

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.

4 participants