Created attachment 1600590 [details] issue picture Description of problem: 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-20190801.2-RHVH-x86_64-dvd1.iso cockpit-195-1.el7.x86_64 cockpit-bridge-195-1.el7.x86_64 cockpit-storaged-195-1.el7.noarch cockpit-system-195-1.el7.noarch cockpit-ws-195-1.el7.x86_64 cockpit-machines-ovirt-195-1.el7.noarch cockpit-ovirt-dashboard-0.13.5-1.el7ev.noarch cockpit-dashboard-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 rhvm-appliance-4.3-20190801.0.el7.rpm How reproducible: 100% Steps to Reproduce: 1. Clean install RHVH-4.3-20190801.2-RHVH-x86_64-dvd1.iso 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: The issue is not detected with RHVH 4.3.5
Created attachment 1600604 [details] Log files
Test Version RHVH-4.3-20190822.2-RHVH-x86_64-dvd1.iso cockpit-195-1.el7.x86_64 cockpit-bridge-195-1.el7.x86_64 cockpit-storaged-195-1.el7.noarch cockpit-dashboard-195-1.el7.x86_64 cockpit-system-195-1.el7.noarch cockpit-ws-195-1.el7.x86_64 cockpit-machines-ovirt-195-1.el7.noarch cockpit-ovirt-dashboard-0.13.6-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.5-1.el7ev.noarch ovirt-hosted-engine-setup-2.3.12-1.el7ev.noarch Test Steps: According to comment 0 Test Result: he-invalid-engine-fqdn-err "Unable to resolve address" displays under the engine fqdn text-box. Bug is fixed, move it to "VERIFIED"
*** Bug 1753921 has been marked as a duplicate of this bug. ***
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.