Skip to content

DFBUGS-3664:[release-4.19] indicate connected client about server ability to serve requests #3388

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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #3386

/assign leelavg

1. explicitly sets a key on client-op configmap for client to take
decisions on co-location with hub
2. explicity send a failed precondition when server not able to serve
the connected client

Signed-off-by: Leela Venkaiah G <[email protected]>
@leelavg
Copy link
Contributor

leelavg commented Jul 24, 2025

/retitle DFBUGS-3664:[release-4.19] indicate connected client about server ability to serve requests

@openshift-ci openshift-ci bot changed the title [release-4.19] indicate connected client about server ability to serve requests DFBUGS-3664:[release-4.19] indicate connected client about server ability to serve requests Jul 24, 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 Jul 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 24, 2025

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.19) matches configured target version for branch (odf-4.19)
  • 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 ([email protected]), skipping review request.

In response to this:

This is an automated cherry-pick of #3386

/assign leelavg

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.

@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 Jul 24, 2025
Copy link
Contributor

openshift-ci bot commented Jul 24, 2025

[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

@openshift-merge-bot openshift-merge-bot bot merged commit 541d5d8 into red-hat-storage:release-4.19 Jul 24, 2025
11 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 24, 2025

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

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

In response to this:

This is an automated cherry-pick of #3386

/assign leelavg

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