Bug 2224518
| Summary: | VNC installation with reverse connection ends up in local GUI installation. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Ruzicka <lruzicka> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 39 | CC: | anaconda-maint-list, awilliam, vponcova, vslavik, w | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2143444 | ||||||
| Attachments: |
|
||||||
|
Description
Lukas Ruzicka
2023-07-21 10:05:32 UTC
Created attachment 1976870 [details]
Video of the procedure
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 Uh, it's `inst.vncconnect=`. Not `install.vncconnect=`. You also have to pass `inst.vnc`. Again, if you're investigating the openQA failures, I already did that, and the cause is https://bugzilla.redhat.com/show_bug.cgi?id=2223795 . Yeah, mea culpa. I used inst.vncconnect= but ommited the inst.vnc. Now, I am using it correctly, but I am still unable to establish the connection: On my host machine, I am using `vncviwere -listen 5500` On the VM, I am using the `inst.vnc inst.vncconnect=192.168.122.1:5500`, but Anaconda reports trying the connection but does not succeed. The 5500 port is opened in Firewall (as is the default). A ping to 192.168.122.1 works just fine inside the VM and the host machine can also be SSHed into. Just the VNC does not catch up. I was not trying to report the openQA failures. I was trying to fill in the holes in the matrices and ran into VNC installation problems. Please, the typos I have produced in the above comment are not the reason it is not working for me. well, vncconnect can be a bit tricky to figure out, but it's not broken, it is working in openQA. the test is only failing on the systemd issue, the VNC connection works fine. In the openQA test we actually take down the firewall entirely, I don't recall why, but maybe try that? Ok, when I switch off firewall entirely, this reverse vnc installation works ok. However, this should not be needed. Please, could someone from Anaconda tell me, which ports should be accessible and opened on the host machine, so that this would work with Firewall still on? Because we will need to update our test description to adapt to the reality. This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39. |