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-951: [release-4.18] Fixed an indentation issue in 'prometheus-ocs-rules.yaml' file #2929

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2921

/assign aruniiird

Signed-off-by: Arun Kumar Mohan <amohan@redhat.com>
Copy link
Contributor

openshift-ci bot commented Dec 6, 2024

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

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

/assign aruniiird

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.

@agarwal-mudit agarwal-mudit added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 10, 2024
Copy link
Contributor

openshift-ci bot commented Dec 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: 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

@agarwal-mudit agarwal-mudit changed the title [release-4.18] Fixed an indentation issue in 'prometheus-ocs-rules.yaml' file DFBUGS-951: [release-4.18] Fixed an indentation issue in 'prometheus-ocs-rules.yaml' file Dec 10, 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/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Dec 10, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 10, 2024

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

Requesting review from QA contact:
/cc @vkathole

In response to this:

This is an automated cherry-pick of #2921

/assign aruniiird

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 Dec 10, 2024

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

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:

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

Requesting review from QA contact:
/cc @vkathole

In response to this:

This is an automated cherry-pick of #2921

/assign aruniiird

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.

@openshift-merge-bot openshift-merge-bot bot merged commit a4fcd14 into red-hat-storage:release-4.18 Dec 10, 2024
11 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 10, 2024

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

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

In response to this:

This is an automated cherry-pick of #2921

/assign aruniiird

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 Indicates a PR has been approved by an approver from all required OWNERS files. 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 Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants