Fix for set-name bug in networkd renderer#1100
Conversation
|
Thank you! |
Hi @pradipd, I hope you do not think me rude to steal your patch and turn it into a PR. I credited you up above, and hopefully they can just set you as the author on the commit. I also knew we needed some unit testing around this. Since I'd fixed the previous |
|
Not at all. I definitely appreciate you cleaning it up, adding unit tests, and pushing it through. |
holmanb
left a comment
There was a problem hiding this comment.
Thanks for the PR. I left a couple of nitpick style comments. Generally this looks good.
|
Hi @holmanb, Thanks for the review. I've addressed your feedback and pushed the updates. Thanks! |
|
Thanks as ever for the speedy turnaround. |
1d5b608 to
1a96f0c
Compare
blackboxsw
left a comment
There was a problem hiding this comment.
I think minimally the unit test needs to be a bit tighter, but I think we can "fix" the rendering in networkd, but not sure I have all the context here.
Thanks @blackboxsw, I will see if I can fix it. |
This patch address launch pad bug 1949407 where the use of a "set-name" directive caused the networkd renderer to fail.
blackboxsw
left a comment
There was a problem hiding this comment.
LGTM! thanks for the work on this @akutz
Proposed Commit Message
Additional Context
Please note this was root caused by @pradipd at pradipd@756742a, and this PR is merely an optimization on their existing fix as well as the addition of a unit test to validate the fix.
Fixes Kubernetes image builder bug described in this comment - kubernetes-sigs/image-builder#712 (comment)
CC @MaxRink @zawachte-msft @kkeshavamurthy @randomvariable @codenrhoden
Test Steps
The following command and output demonstrates the patch works as intended:
However, if the patch to the file is removed and the test is executed again, the original error occurs:
Checklist: