Skip to content
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

Fix reboot_gnome vnc lost connection issue #12617

Conversation

lemon-suse
Copy link
Contributor

Keep console after reboot is not suitable for s390x, on s390x it will reconnect console and reconnect vnc after reboot, to make the vnc re-connect more stable, we'd better don't keep console on s390x.

@lemon-suse lemon-suse force-pushed the Fix_reboot_gnome_vnc_lost_connection branch 2 times, most recently from c11b431 to 005f06a Compare May 28, 2021 03:51
lib/services/users.pm Outdated Show resolved Hide resolved
@lemon-suse lemon-suse force-pushed the Fix_reboot_gnome_vnc_lost_connection branch from 005f06a to babd420 Compare May 28, 2021 06:37
lib/services/users.pm Outdated Show resolved Hide resolved
@lemon-suse lemon-suse force-pushed the Fix_reboot_gnome_vnc_lost_connection branch 3 times, most recently from 37daec5 to d7fbedc Compare June 1, 2021 05:58
Keep console after reboot is not suitable for s390x, on s390x it will reconnect
console and reconnect vnc after reboot, to make the vnc re-connect more stable,
we'd better to not to keep console on s390x.
@lemon-suse lemon-suse force-pushed the Fix_reboot_gnome_vnc_lost_connection branch from d7fbedc to 46fd513 Compare June 1, 2021 06:22
Copy link
Contributor

@rfan1 rfan1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lemon-suse lemon-suse merged commit 0e717e6 into os-autoinst:master Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants