Skip to content

[release-4.19] DFBUGS-2295: ensure OBC spec is not reset unexpectedly #318

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

[release-4.19] DFBUGS-2295: ensure OBC spec is not reset unexpectedly #318

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #316

/assign umangachapagain

@umangachapagain
ensure OBC spec is not reset unexpectedly
05c5791 
When creating or updating an OBC, we only manage certain fields.
There are other fields managed by other agents. We should not reset
those fields whhen we update the resource.

Signed-off-by: Umanga Chapagain <[email protected]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 21, 2025
Merged
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign umangachapagain for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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-robot
Copy link

openshift-ci-robot commented Apr 21, 2025 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: [Jira Issue DFBUGS-2276](https://issues.redhat.com//browse/DFBUGS-2276) has been cloned as [Jira Issue DFBUGS-2295](https://issues.redhat.com//browse/DFBUGS-2295). Will retitle bug to link to clone.
/retitle [release-4.19] DFBUGS-2295: ensure OBC spec is not reset unexpectedly

In response to this:

This is an automated cherry-pick of #316

/assign umangachapagain

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 openshift-ci bot changed the title [release-4.19] DFBUGS-2276: ensure OBC spec is not reset unexpectedly [release-4.19] DFBUGS-2295: ensure OBC spec is not reset unexpectedly Apr 21, 2025
@openshift-ci-robot openshift-ci-robot added 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 Apr 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 21, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.19" 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 #316

/assign umangachapagain

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
Copy link

openshift-ci-robot commented Apr 21, 2025 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-2295](https://issues.redhat.com//browse/DFBUGS-2295). The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

This is an automated cherry-pick of #316

/assign umangachapagain

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
Reviewers
No reviews
Assignees

@umangachapagain umangachapagain

Labels
jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@openshift-cherrypick-robot @openshift-ci-robot @umangachapagain