[next-devel] platforms: add secondary serial console on OpenStack, VirtualBox, VMware #2038
Conversation
This file contains 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
This was referenced Oct 28, 2022
travier
previously approved these changes
Oct 28, 2022
|
Hmm I'm a little confused honestly, it seems like we're getting to a point where we're enabling the console on pretty much every platform except metal? If that's getting to be the case I wonder if we should change things to go back to more having a default console setup that can be overridden per-platform - in particular, we have the same kernel arguments across aws/azure/gcp for example. Anyways, seems OK to me! |
dustymabe
previously approved these changes
Oct 28, 2022
Previously, `openstack console log <server>` was useful for collecting console logs from OpenStack VMs, but we disabled serial console output on OpenStack. Re-enable it as a secondary console so it gets as much information as possible without interfering with the graphical console. Fixes https://issues.redhat.com/browse/OCPBUGS-2926.
The FCOS platform docs for VMware/VirtualBox include instructions on
connecting to the serial console to get a console log, and some users
make use of this functionality:
coreos/fedora-coreos-tracker#567 (comment)
Re-enable secondary serial consoles on those platforms, so the serial
console gets as much information as possible without interfering with the
graphical console.
jlebon
approved these changes
Oct 28, 2022
|
@cgwalters Some platforms want serial console only, some want graphical console only, and some want both with serial console either primary or secondary. Since enabling serial console requires us to be thoughtful about how we configure it, I think the current default is useful to ensure we do that. @dustymabe I've added a link for OpenStack. VirtualBox and VMware both just emulate standard PCs, and how we use the serial ports is up to us, so the links to our docs are in some sense the authoritative ones. |
dustymabe
approved these changes
Oct 28, 2022
4 tasks
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/os
that referenced
this pull request
Nov 2, 2022
Previously, `openstack console log <server>` was useful for collecting console logs from OpenStack VMs, and the serial console was similarly useful in VMware, but we disabled serial console output on both platforms. Re-enable it as a secondary console so it gets as much information as possible without interfering with the graphical console. Do the same on VirtualBox to stay in sync with FCOS. Fixes: https://issues.redhat.com/browse/OCPBUGS-2926 xref: coreos/fedora-coreos-config#2038
bgilbert
added a commit
to openshift-cherrypick-robot/os
that referenced
this pull request
Nov 3, 2022
Previously, `openstack console log <server>` was useful for collecting console logs from OpenStack VMs, and the serial console was similarly useful in VMware, but we disabled serial console output on both platforms. Re-enable it as a secondary console so it gets as much information as possible without interfering with the graphical console. Do the same on VirtualBox to stay in sync with FCOS. Fixes: https://issues.redhat.com/browse/OCPBUGS-2926 xref: coreos/fedora-coreos-config#2038
bgilbert
added a commit
to openshift-cherrypick-robot/os
that referenced
this pull request
Nov 3, 2022
Previously, `openstack console log <server>` was useful for collecting console logs from OpenStack VMs, and the serial console was similarly useful in VMware, but we disabled serial console output on both platforms. Re-enable it as a secondary console so it gets as much information as possible without interfering with the graphical console. Do the same on VirtualBox to stay in sync with FCOS. Fixes: https://issues.redhat.com/browse/OCPBUGS-2926 xref: coreos/fedora-coreos-config#2038
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously,
openstack console log <server>was useful for collecting console logs from OpenStack VMs, and FCOS docs included instructions on connecting to the VirtualBox/VMware serial console to get a console log. However, we've disabled the serial console on all three platforms. Re-enable it as a secondary console so those techniques continue to work while avoiding interfering with the primary graphical console.The OpenStack change is untested.
Fixes: OCPBUGS-2926
Fixes: coreos/fedora-coreos-tracker#567 (comment)