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

[release-4.13] api: update ocs-operator pkg version #421

Conversation

Nikhil-Ladha
Copy link
Member

@Nikhil-Ladha Nikhil-Ladha commented Jun 6, 2024

Update ocs-operator pkg version to include new api changes
Ref BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2276694

update ocs-operator pkg version to
include new api changes

Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
Copy link
Contributor

openshift-ci bot commented Jun 6, 2024

@Nikhil-Ladha: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

api: update ocs-operator pkg version

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.

@Nikhil-Ladha Nikhil-Ladha changed the title api: update ocs-operator pkg version [release-4.13] api: update ocs-operator pkg version Jun 6, 2024
Copy link
Contributor

openshift-ci bot commented Jun 6, 2024

@Nikhil-Ladha: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.13] api: update ocs-operator pkg version

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.

1 similar comment
Copy link
Contributor

openshift-ci bot commented Jun 6, 2024

@Nikhil-Ladha: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.13] api: update ocs-operator pkg version

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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2024
Copy link
Contributor

openshift-ci bot commented Jun 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, Nikhil-Ladha

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 6, 2024
@Nikhil-Ladha
Copy link
Member Author

/retest

@iamniting
Copy link
Member

/override ci/prow/odf-operator-e2e-aws

Copy link
Contributor

openshift-ci bot commented Jun 18, 2024

@iamniting: Overrode contexts on behalf of iamniting: ci/prow/odf-operator-e2e-aws

In response to this:

/override ci/prow/odf-operator-e2e-aws

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.

@iamniting iamniting changed the title [release-4.13] api: update ocs-operator pkg version DFBUGS-1248:[release-4.13] api: update ocs-operator pkg version Jan 17, 2025
@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 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 17, 2025

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-1248](https://issues.redhat.com//browse/DFBUGS-1248), 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.13.z) matches configured target version for branch (odf-4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

Update ocs-operator pkg version to include new api changes
Ref BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2276694

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.

@iamniting
Copy link
Member

/hold

@Nikhil-Ladha
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 17, 2025

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.13.z) matches configured target version for branch (odf-4.13.z)
  • 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.

@Nikhil-Ladha
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 17, 2025

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.13.z) matches configured target version for branch (odf-4.13.z)
  • 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.

@Nikhil-Ladha
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 17, 2025

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.13.z) matches configured target version for branch (odf-4.13.z)
  • 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.

@Nikhil-Ladha
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 24, 2025

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.13.z) matches configured target version for branch (odf-4.13.z)
  • 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.

@iamniting
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot removed the jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting label Jan 27, 2025
@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 Jan 27, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 27, 2025

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

  • expected the bug to target either version "odf-4.13.12." or "openshift-odf-4.13.12.", but it targets "odf-4.13.z" 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:

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

@iamniting iamniting changed the title DFBUGS-1248:[release-4.13] api: update ocs-operator pkg version [release-4.13] api: update ocs-operator pkg version Jan 27, 2025
@openshift-ci-robot openshift-ci-robot removed 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 Jan 27, 2025
@openshift-ci-robot
Copy link

@Nikhil-Ladha: 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:

Update ocs-operator pkg version to include new api changes
Ref BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2276694

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.

@iamniting
Copy link
Member

EOL

@iamniting iamniting closed this Jan 29, 2025
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. do-not-merge/hold lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants