Created attachment 1617115 [details] picture he-invalid-engine-fqdn-err "Unable to resolve address" is missing in cockpit UI. When inputting invalid engine fqdn in vm setting, there should be a he-invalid-engine-fqdn-err "Unable to resolve address" prompted. But now a long unreadable sentence is displayed under the engine fqdn text-box. (Refer to the picture in attachment) Version-Release number of selected component (if applicable): rhvh-4.3.5.4-0.20190918.0 cockpit-bridge-195-1.el7.x86_64 cockpit-ws-195-1.el7.x86_64 cockpit-dashboard-195-1.el7.x86_64 cockpit-machines-ovirt-195-1.el7.noarch cockpit-ovirt-dashboard-0.13.5-1.el7ev.noarch cockpit-storaged-195-1.el7.noarch cockpit-system-195-1.el7.noarch cockpit-195-1.el7.x86_64 ovirt-hosted-engine-ha-2.3.3-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.11-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install rhvh-4.3.5.4-0.20190918.0 2. Login to "http://localhost:9090" 3. Input "invalid" fqdn of vm in vm setting 4. Next Actual results: A long unreadable sentence is displayed under the engine fqdn text-box instead of the he-invalid-engine-fqdn-err "Unable to resolve address". Expected results: he-invalid-engine-fqdn-err "Unable to resolve address" should be displayed under the engine fqdn text-box Additional info:
Created attachment 1617116 [details] log files
This was already reported and fixed in 4.3.6 witgh bug #1737353. This test has been done on 4.3.5 async which is known to include this bug. *** This bug has been marked as a duplicate of bug 1737353 ***
Hi Sandro, This issue is detected with the latest 4.3.5 build rhvh-4.3.5.4-0.20190918.0