Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1440582

Summary: "404" error message displays when login to engine on cockpit UI
Product: [oVirt] ovirt-node Reporter: Wei Wang <weiwang>
Component: UIAssignee: Marek Libra <mlibra>
Status: CLOSED UPSTREAM QA Contact: Wei Wang <weiwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1CC: bugs, cshao, huzhao, leiwang, qiyuan, rbarry, tjelinek, weiwang, yaniwang, ycui
Target Milestone: ---Flags: cshao: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-25 13:14:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
picture
none
log files
none
picture none

Description Wei Wang 2017-04-10 03:07:28 UTC
Created attachment 1270357 [details]
picture

Description of problem:
"404" error message displays when login to engine on cockpit UI

Version-Release number of selected component (if applicable):
host1:
update rhvh: rhev-hypervisor6-6.8-20160707.3.el6ev -->redhat-virtualization-host-3.6-20170404.0 --> redhat-virtualization-host-4.1-20170403.0
cockpit-ws-126-1.el7.x86_64
cockpit-ovirt-dashboard-0.10.7-0.0.16.el7ev.noarch
imgbased-0.9.20-0.1.el7ev.noarch

host2:
update rhvh: redhat-virtualization-host-3.6-20170404.0 --> redhat-virtualization-host-4.1-20170403.0
cockpit-ws-126-1.el7.x86_64
cockpit-ovirt-dashboard-0.10.7-0.0.16.el7ev.noarch
imgbased-0.9.20-0.1.el7ev.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install and update host1 or host2 according to bug 1421098 comment #15
2. Login host1 or host2 cockpit with root account
3. Go to Virtualization --> Virtual Machines
4. Add engine IP/FQDN to /etc/hosts file
5. Login to engine



Actual results:
"404" error message displays when login to engine on cockpit UI

Expected results:
No error messages displays, and login to engine successful.


Additional info:

Comment 1 Wei Wang 2017-04-10 03:08:27 UTC
Created attachment 1270359 [details]
log files

Comment 2 Marek Libra 2017-04-10 07:01:48 UTC
@weiwang, in step 4: On which machine do you modify the /etc/hosts file, please?

Is the entered engine URL correct?

Comment 3 Wei Wang 2017-04-10 07:29:12 UTC
(In reply to Marek Libra from comment #2)
> @weiwang, in step 4: On which machine do you modify the /etc/hosts file,
> please?
Modify the /etc/hosts file on the host which login to with root account.
> 
> Is the entered engine URL correct?
I remember it is correct.

Comment 4 Tomas Jelinek 2017-04-19 07:38:28 UTC
can you please look at the browser developer console what endpoint returned the 404? In firefox it is "ctrl+shift+k" and than the "network" tab. You will see the communication and also the failed one.

Comment 5 Wei Wang 2017-04-20 05:49:09 UTC
(In reply to Tomas Jelinek from comment #4)
> can you please look at the browser developer console what endpoint returned
> the 404? In firefox it is "ctrl+shift+k" and than the "network" tab. You
> will see the communication and also the failed one.

The test environment is being prepared, I will give the result later.

Comment 6 Tomas Jelinek 2017-04-20 13:34:49 UTC
ok, so putting the needinfo back

Comment 7 Wei Wang 2017-04-24 06:57:59 UTC
(In reply to Tomas Jelinek from comment #6)
> ok, so putting the needinfo back

Retest with new build, the bug still occurs. Take a picture for the browser developer console according to "In firefox, it is 'ctrl+shift+k' and then the "network" tab.", but I cannot find the endpoint returned the 404.

I will send you the email about my testing environment. If you need do further check.

Comment 8 Wei Wang 2017-04-24 06:58:27 UTC
Created attachment 1273521 [details]
picture

Comment 9 Tomas Jelinek 2017-04-25 07:37:24 UTC
The engine is of version 3.6 - the cocpit-ovirt can only talk to engine 4.0+
Can you please re-check with a 4.0 engine?

thank you

Comment 10 Wei Wang 2017-04-25 07:53:05 UTC
(In reply to Tomas Jelinek from comment #9)
> The engine is of version 3.6 - the cocpit-ovirt can only talk to engine 4.0+
> Can you please re-check with a 4.0 engine?
> 
> thank you

According to the steps in bug 1421098 comment #15, before the host updated to rhvh 4.1, the host with rhevh-3.6-ngn has been added to engine 3.6. So we don't use 4.0+ engine in this case.

Comment 11 Ying Cui 2017-04-25 08:20:20 UTC
(In reply to Wei Wang from comment #10)
> According to the steps in bug 1421098 comment #15, before the host updated
> to rhvh 4.1, the host with rhevh-3.6-ngn has been added to engine 3.6. So we
> don't use 4.0+ engine in this case.

Wei, in your case, you have to do the additional step to update the engine to 4.0+ version to try according to comment 9? Otherwise, it should be considered it is not a bug.

Comment 12 Tomas Jelinek 2017-04-25 13:14:49 UTC
Actually the issue here is that you can add 4.1 ngn into 3.6 engine (which is correct) while the cocpit-ovirt expects to work only with 4.0+ without actually checking if the engine is of version 4.0+.

Since this cockpit-ovirt is a tech preview which is being replaced by [1], I have opened a bug on the new provider [2] to track this fix.

Thus, closing this BZ and continue tracking it on the other component.

[1]: https://github.com/oVirt/cockpit-machines-ovirt-provider/ 
[2]: https://github.com/oVirt/cockpit-machines-ovirt-provider/issues/23