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

external: fix client.healthchecker user keyring return #13001

Merged
merged 2 commits into from
Oct 5, 2023

Conversation

parth-gr
Copy link
Member

@parth-gr parth-gr commented Oct 5, 2023

Description of your changes:
if the client.health checker already exited it was returning extra information,
It was making the structure and return JSON non idempotent output , So fixed that problem by returning a single value

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Reviewed the developer guide on Submitting a Pull Request
  • Pending release notes updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

@parth-gr parth-gr changed the title external: fix client.healthchecker user keying return external: fix client.healthchecker user keyring return Oct 5, 2023
if the client.health checker already exited it was
returning extra information, It was making the structure and
return JSON non idempotent output, So fixed
that problem by returning a single value

Signed-off-by: parth-gr <paarora@redhat.com>
@parth-gr parth-gr force-pushed the external-healtchker branch 5 times, most recently from f140562 to 467b3f7 Compare October 5, 2023 13:53
Signed-off-by: parth-gr <paarora@redhat.com>
@@ -1162,7 +1162,7 @@ def create_checkerKey(self, user):
# check if user already exist
user_key = self.check_user_exist(entity)
if user_key != "":
return user_key, f"{entity.split('.', 1)[1]}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this was a regression from #12941? The second return value was just not needed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct

@travisn travisn merged commit 38c4bd2 into rook:master Oct 5, 2023
49 of 50 checks passed
travisn added a commit that referenced this pull request Oct 5, 2023
external: fix client.healthchecker user keyring return (backport #13001)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants