Skip to content

[release-4.16] DFBUGS-713: Block creation of external mode when Provider mode is already present #1641

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
Open
wants to merge 1 commit into
base: release-4.16
Choose a base branch
from
Open

[release-4.16] DFBUGS-713: Block creation of external mode when Provider mode is already present #1641

wants to merge 1 commit into from

Conversation

bipuladh
Copy link
Contributor

Reset radio button when Provider mode is selected from dropdown

@bipuladh
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 16, 2024

@bipuladh: This pull request references Bugzilla bug 2317793, which is invalid:

  • expected the bug to target the "ODF 4.16.3" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.16] Bug 2317793: Block creation of external mode when Provider mode is already present

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

openshift-ci bot commented Oct 16, 2024

@bipuladh: This pull request references Bugzilla bug 2317793, which is invalid:

  • expected the bug to target the "ODF 4.16.3" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla 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 kubernetes-sigs/prow repository.

@bipuladh bipuladh changed the title [release-4.16] Bug 2317793: Block creation of external mode when Provider mode is already present [release-4.16] DFBUGS-713: Block creation of external mode when Provider mode is already present Nov 25, 2024
@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 Nov 25, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 25, 2024 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.4" 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:

Reset radio button when Provider mode is selected from dropdown

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.

@bipuladh
Copy link
Contributor Author

/bugzilla refresh

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2024 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.4" 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.

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.4" 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.

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.5" 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.

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting label Dec 19, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2024 •
edited by openshift-ci bot
Loading

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.16.5) matches configured target version for branch (odf-4.16.5)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @PrasadDesala

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-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 Dec 19, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 19, 2024 •
edited
Loading

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

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:

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.16.5) matches configured target version for branch (odf-4.16.5)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @PrasadDesala

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.

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.

@SanjalKatiyar
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Dec 19, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bipuladh, SanjalKatiyar

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

@bipuladh
Block creation of external mode when Provider mode is already present
c63746b 
Reset radio button when Provider mode is selected from dropdown

Signed-off-by: Bipul Adhikari <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm label Dec 19, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 19, 2024

New changes are detected. LGTM label has been removed.

@SanjalKatiyar
Copy link
Collaborator

/jira refresh

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

openshift-ci-robot commented Dec 19, 2024 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.5" 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.

@SanjalKatiyar
Copy link
Collaborator

/cherry-pick release-4.16-compatibility

@openshift-cherrypick-robot
Copy link

@SanjalKatiyar: once the present PR merges, I will cherry-pick it on top of release-4.16-compatibility in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16-compatibility

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.

@bipuladh
Copy link
Contributor Author

bipuladh commented Jan 8, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 8, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.5" 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.

@bipuladh
Copy link
Contributor Author

bipuladh commented Jan 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 9, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.5" 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.

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 13, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.6" 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.

@bipuladh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.16.6" 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@SanjalKatiyar SanjalKatiyar

Labels
approved bugzilla/invalid-bug bugzilla/severity-urgent 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.
4 participants
@bipuladh @openshift-ci-robot @SanjalKatiyar @openshift-cherrypick-robot