The VNC installation cannot be started as Anaconda fails with a bunch of critical messages on the machine being installed, see the screenshot. Reproducible: Always Steps to Reproduce: 1. Download the Everything nightly ISO (20230719) 2. Boot it and add `inst.vnc` to the kernel line. 3. Wait until the installation starts -> it shows the info that the VNC server has started. 4. Almost immediatly, that message is replaced with a bunch of critical error messages and there is no way how the installation could proceed. 4. Actual Results: Installation via VNC is not possible. Expected Results: Installation via VNC should be flawless.
Created attachment 1976853 [details] Error messages provided by Anaconda.
Created attachment 1976857 [details] Start of the VNC captured.
Situation is the same with Server netinst ISO.
I propose this as a beta blockers based on the following criterion: When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces. https://fedoraproject.org/wiki/Basic_Release_Criteria#Installation_interfaces
Regarding the critical messages, the issue seems to be tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=2224009.
I'm a bit confused what you're reporting here. The 'critical' errors are annoying, but I don't think they actually break anything. I suppose one issue is that they make the information about how to connect scroll off the top of the screen, so unless you know what you need to do already, it's a bit harder to figure out. Is that what you're reporting? The reason the openQA VNC tests currently fail is https://bugzilla.redhat.com/show_bug.cgi?id=2223795 , if that's where you got here from. it's not actually a VNC problem at all. It should be resolved in tomorrow's compose. I did link the bug from openQA comments already.
Yeah, I am reporting that you cannot use VNC installation, unless you can guess the exact way to invoke it, which not "just confusing", it is more than that as there is no way how you could scroll these messages away to find out about the correct way to invoke the vnc connection. I have tried to establish the connection via 192.168.122.99 (the IP of the VM) and got connection refused. Then I tried the default VNC port 192.168.122.99::5900 and got connection refused again. Then, after you have claimed it to be working, I tried with other combinations and finally succeeded with 192.168.122.99:1. I am fine with closing this bug in favour of 2224009 as mentioned in comment 5.
*** This bug has been marked as a duplicate of bug 2224009 ***