microk8s inspect incorrectly logs the 'ip addr' and 'ip route' system commands. #4694
Conversation
…h being written to the file 'ip-addr'. The 'ip route' command was run second so the result was A) a misleading output in the ip-addr file actually being from 'ip-route' and missing the output from 'ip-addr'.
|
hey @countravioli do you have Launchpad account? What is its handler? |
|
@maci3jka - same as github "countravioli". I did go through the docs on that, thought it was linked up. Sorry if I missed something. |
@countravioli could you provide URL to your Launchpad account? You can find it by clicking on your name in the top right corner |
|
@maci3jka - hmm, maybe I didn't complete part of the process. I had a login at "login.launchpad.net" but hadn't been to launchpad.net yet. |
@countravioli is your mail in launchpad set to |
@countravioli have you managed to check the mail? |
In the inspect report, the commands 'ip addr' and 'ip route' were both being written to the file 'ip-addr' file.
The 'ip route' command was run second so the result was
Summary
'ip addr' command will generate the 'ip-addr' file for output Corrected
'ip route' command will generate the 'ip-route' file New
Changes
One liner, redirect the output of 'ip route' to 'ip-route' file.
Testing
no testing, seemed very straight forward.
Possible Regressions
Anyone programmatically running a microk8s inspect report on failure and parsing the output of this file would need to change their system to use the "ip-route" file.
Checklist
Notes
n/a