-
Notifications
You must be signed in to change notification settings - Fork 117
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
Enable serial console by default for pxe #160
Conversation
/assign @derekhiggins |
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stbenjam The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold Based on @juliakreger's comment above |
If a problem happens in IPA, it can help to use the serial console to debug. We can also use the serial console to log the output in CI systems. We specify 2 console options, one for the serial console, and one for the graphical display. According to the kernel docs, the last devices will be used for /dev/console, but output will appear on all of them[1]. `tty0` is last so if there's an emegency prompt needed it'll be put on the graphical console by default. [1] https://www.kernel.org/doc/html/v5.5-rc2/admin-guide/serial-console.html
New changes are detected. LGTM label has been removed. |
/test-integration |
I tested this and while it does output some of the console content seen on the VGA console, it doesn't contain the IPA log output AFAICS - are we missing something to add that? The kernel CLI looks like this in
However in inspector.ipxe I see |
The ironic images can be used to do inspection in two ways, the one we are using is managed by ironic, in this case ironic is I've tried a few different configurations trying to get IPA to output to both the VGA console and ttyS0 (so it could be logged), here is my understanding Multiple console= entries on the command line result in the kernel messages being logged to multiple devices but the last one on the line is also known as /dev/console systemd.journald.forward_to_console=yes causes journal messages to be output to /dev/console So if we have console=ttyS0 console=tty0 systemd.journald.forward_to_console=yes then journal logs will only be logged to tty0 while kernel messages will be logged to both ttyS0 and tty0 The only way I have managed to get IPA logs to output to both tty0 and ttyS0 is to set systemd.journald.forward_to_kmsg=True in this case journal message are sent to kmsg but for some reason tty0 get all of the log entries but ttyS0 get some IPA log entries and not others ( I've yet to figure this out) .... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues close after 30d of inactivity. Reopen the issue with /close |
@metal3-io-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
If a problem happens in IPA, it can help to use the serial console to
debug. We can also use the serial console to log the output in CI
systems.
We specify 2 console options, one for the serial console, and one for
the graphical display. According to the kernel docs, the last devices
will be used for /dev/console, but output will appear on all of them[1].
tty0
is last so if there's an emegency prompt needed it'll be puton the graphical console by default.
[1] kernel.org/doc/html/v5.5-rc2/admin-guide/serial-console.html