Fixed noobaa CLI api calls to object_api #1203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…_objects() Call failed: failed to WebSocket dial" Signed-off-by: Aayush Chouhan <[email protected]>
achouhan09
force-pushed
the
bugfix_list_objects
branch
from
c8b5e96
to
0f3dd04
Compare
dannyzaken
approved these changes
Aug 21, 2023
dannyzaken
changed the title
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…_objects() Call failed: failed to WebSocket dial"
Explain the changes
md-httpsas port name for object_api and func_api, which is causing the failure asmd-httpswas not present in noobaa-mgmt service. So we modified the code and returningmgmt-httpsas port for both api calls now.Issues
https://bugzilla.redhat.com/show_bug.cgi?id=2227835
[MCG] RPC method "list_objects" fails with "RPC: object.list_objects() Call failed: failed to WebSocket dial"