Bug 2193010 - Kickstart in graphical mode runs chvt to the wrong terminal and Graphical kickstart hangs forever in Satellite 6.13 [NEEDINFO]
Summary: Kickstart in graphical mode runs chvt to the wrong terminal and Graphical kic...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-04 00:57 UTC by Jayant Bhatia
Modified: 2023-07-22 10:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
mhulan: needinfo? (mkolman)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36134 0 Normal New kickstart in graphical mode runs chvt to the wrong terminal 2023-06-12 10:31:36 UTC
Red Hat Issue Tracker SAT-18095 0 None None None 2023-06-04 16:14:07 UTC

Description Jayant Bhatia 2023-05-04 00:57:12 UTC
Description of problem:

When the use_graphical_installer boolean is set to `true` for kickstart the %post snippet will run `chvt 1` which is not the right VTTY for the installer to complete.

This is upstream in https://projects.theforeman.org/issues/36134. 


Version-Release number of selected component (if applicable): Satellite-6.13


How reproducible: Always


Steps to Reproduce:

When %post completes it tries to change to the incorrect terminal.  Anaconda detects a process is still running in %post (namely the new terminal open) and the installation doesn't complete until someone presses CTRL+ALT+F6


Actual results: Graphical kickstart hangs forever


Expected results: If there was a way to just store the current vtty, that would be great.

Comment 2 Sam Lindberg 2023-06-04 16:13:19 UTC
Hello Team,

I see this has been marked as triaged and workaround. Forgive me, but I am not seeing the workaround. Could you please advise?

Very Respectfully,

Sam


Note You need to log in before you can comment on or make changes to this bug.