-
Notifications
You must be signed in to change notification settings - Fork 30
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
Better error message on ServiceAccountJSON decode failure #67
Conversation
@AhmedMozaly Thank you for your contribution. |
Thank you @AhmedMozaly for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
thanks for your changes
@himanshu-kun I've a side question, posting here as I can't find other place But it's always in "Pending" status when I run Is there an example for what I should set in the k8s secret to allow the machine status to move from "Pending" to "Running"? |
hello @AhmedMozaly |
tracking issue -> gardener/machine-controller-manager#768 |
@himanshu-kun Thanks for the response, I've added a comment on the issue let's kindly continue discussion there |
c38527c
to
b112139
Compare
What this PR does / why we need it:
I spent more than an hour trying to troubleshoot
invalid character '\n' in string literal
when creating new VMs, At the end it was extra\n
in the secret valueThought it's better to guide the developer to the root cause of the error by enhancing the error message
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: