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

livemedia-creator waits for enter to continue on complete #1448

Open
siepkes opened this issue Jan 23, 2025 · 1 comment
Open

livemedia-creator waits for enter to continue on complete #1448

siepkes opened this issue Jan 23, 2025 · 1 comment

Comments

@siepkes
Copy link

siepkes commented Jan 23, 2025

When I invoke livemedia-creator from a script (in a VM) with the following flags:

# livemedia-creator \
        --make-iso \
        --no-virt \
        --ks=clientplatform.ks \
        --compression=xz \
        --fs-label=foo-client \
        --resultdir "/root/livemedia"

livemedia-creator will hang after the Complete! message and wait for an enter before continuing (other keys don't make it continue). In the console this looks like this:

2025-01-23 10:10:15,121: Storing configuration files and kickstarts
2025-01-23 10:10:15,121: .
2025-01-23 10:10:15,121: Running post-installation scripts
2025-01-23 10:10:23,623: ...
2025-01-23 10:10:23,623: Complete!

2025-01-23 10:10:53,224: Shutting down log processing
2025-01-23 10:10:53,925: Disk Image install successful
2025-01-23 10:10:53,925: working dir is /var/tmp/lmc-work-9o818qiz
2025-01-23 10:10:53,947: Using disk size of 3074MiB

I've tried searching the documentation and cursory looked at the source but I can't find any leads on how I can make livemedia-creator not wait for an enter on complete.

@bcl
Copy link
Contributor

bcl commented Jan 23, 2025

What version of Fedora, Lorax, and Anaconda are you using? Lorax calls Anaconda with the --cmdline argument which is supposed to keep it from doing things like waiting for input. Also take a look at the anaconda logs to see what it shows. This is likely a problem in Anaconda, not Lorax since lorax never waits for input.
I have seen the shutdown take some time when Anaconda crashes, it has some embedded timing loops that make it pause before it continues. But that should be associated with an error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants