Description of problem: We needed to re-run fusor-installer at one point. After fusor-installer returned us to a command prompt, we ran 'launch-fusor-installer' again, but apparently it wasn't done running, because we saw the message - "Please allow several minutes for fusor-installer to complete running." There's no progress indicator or spinner or anything that keeps moving to help give you confidence that it's doing things in the background. We ended up staring at that string for about 7 minutes before it finally continued and ran fusor-installer. Not sure why it took so long for things to settle before it could continue. Would that have been shorter if we hadn't used the launch-fusor-installer variant? Version-Release number of selected component (if applicable): Tech Preview Additional info:
That message is echoed to the terminal any time you run launch-fusor-installer. I believe it is meant to indicate that the fusor-installer task about to be kicked off is going to take several minutes. If there is better wording we can use we can change it. Maybe something on the lines of, "fusor-installer is being launched. Please allow several minutes for it to complete running", or something along those lines..
Jason, when I saw that message, I thought it was basically saying that we were waiting for the previous run to finish up, before it would launch again. Once fusor-installer finally kicks off, you get output that it's doing stuff, but my issue is with the fact that all we had for the 7 minutes or so before it started was that string in the terminal, saying that we had to wait for it to finish running. A spinner or some progress indicator would help reinforce that things are working and haven't gotten stuck. Do you know what it's doing at that point, when we output that string?
Matt in reply to comment #2, the launch-fusor-installer script doesn't do much besides invoking fusor-installer with a known password parameter. There is no work being done to add a spinner or anything. I suspect that the 7 minute delay you saw is related to the VM/console not refreshing, it's not related to any processing being done by the script. launch-fusor-installer is just a wrapper around fusor-installer. To be clear, when fusor-installer finishes it's 100% done, it can be immediately invokved if desired, there is no logic anywhere to detect it was running and wait for something to happen. https://gitlab.sat.lab.tlv.redhat.com/rhci/bootiso/blob/master/experiments/InitialSetup/bin/launch-fusor-installer Moving to CLOSED, please re-open if you would like us to change the wording or do something else.