specify authentication error #193
Merged
Conversation
This file contains hidden or 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
Signed-off-by: evloev.sayfuddin <[email protected]>
FrenkenFlores
force-pushed
the
authentication_error
branch
from
d493e29 to
ed29e0a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The
Error: Unable to establish IPMI v1.5 / RMCP sessionerror message is too ambiguous. It makes it hard to find the the source of problem. We had servers that used for BMC and Redfish API different credentials and it was hard to detect the issue because of the error message, it didn't tell if IPMI was disabled, inactive or if the credentials are invalid. By adding the-vflag we can get more info about the source of problem. TheRAKP 2 HMAC is invalidis mostly and almost for every vendor means that the provided password is invalid (IBM, Intel, etc).