Bug 1810021 - [UI] Refresh LUN cause 2 UI errors to pop up on the web admin
Summary: [UI] Refresh LUN cause 2 UI errors to pop up on the web admin
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.3
: ---
Assignee: Ahmad Khiet
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-04 12:27 UTC by Daniel
Modified: 2020-11-11 06:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 06:39:44 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)
ui_print_screen (26.86 KB, image/png)
2020-03-04 12:27 UTC, Daniel
no flags Details
engine&vdsm logs (1.66 MB, application/gzip)
2020-03-24 06:17 UTC, Daniel
no flags Details
new_screenshot (291.33 KB, image/png)
2020-08-30 20:56 UTC, Shir Fishbain
no flags Details

Description Daniel 2020-03-04 12:27:30 UTC
Created attachment 1667479 [details]
ui_print_screen

Description of problem:
When pressing "Refresh LUN" button, it cause 2 errors to pop up in the UI.
The functionality works as it should (it really refresh it) and none errors\warns shown in logs.

Version-Release number of selected component (if applicable):
4.4.0-0.24.master.el8ev

How reproducible:
100%

Steps to Reproduce:
1. Create / Pick direct LUN disk
2. Press on "Refresh LUN" button

Actual results:
Seems that the functionality of the button works as expected and it really refresh the LUN. However, 2 UI errors popped up one on each other via webadmin (Print screens attached).

Expected results:
Button should cause the refresh and not errors should shown up.

Additional info:
Print screens attached.
#1 details: "Operation Canceled Error while executing action: Cannot sync Virtual Disk. Operation can be performed only when Host status is Up.
#2 details: "Operation Canceled Error while executing action: Cannot sync Virtual Disk. Related operation is currently in progress. Please try again later."


All logs are clear and none errors or warns occurred.

Comment 1 Ahmad Khiet 2020-03-23 11:52:10 UTC
Tried to reproduce and also checked other related patches that have been done to Refresh Luns 
https://gerrit.ovirt.org/c/100871/
https://gerrit.ovirt.org/c/101283/

I see that it works in my environment.

I see other warning messages from the web browser JS console. which I tried to follow and see if they're related.

what I see from the messages from the screenshots that the host is down. ( which I saw when I turned off the host)

can you provide more logs? from the engine and UI logs? 
and if you can send me the environment (email) to reproduce on it.

Comment 2 Daniel 2020-03-24 06:16:42 UTC
(In reply to Ahmad Khiet from comment #1)
> Tried to reproduce and also checked other related patches that have been
> done to Refresh Luns 
> https://gerrit.ovirt.org/c/100871/
> https://gerrit.ovirt.org/c/101283/
> 
> I see that it works in my environment.

still occurs in 4.4.0-0.26.master.el8ev

> 
> I see other warning messages from the web browser JS console. which I tried
> to follow and see if they're related.
> 
> what I see from the messages from the screenshots that the host is down. (
> which I saw when I turned off the host)
> 
> can you provide more logs? from the engine and UI logs? 

Attaching both vdsm and engine logs.
Can't provide you ui.log because the log is complete empty.

> and if you can send me the environment (email) to reproduce on it.

I've sent to Avichai mail about it and notice you once I have one to give you.

Comment 3 Daniel 2020-03-24 06:17:40 UTC
Created attachment 1672917 [details]
engine&vdsm logs

Comment 4 Ahmad Khiet 2020-03-31 10:16:35 UTC
from logs I see that there is a networking error and in vdsm 'libvirt.libvirtError: Requested operation is not valid: cgroup CPU controller is not mounted'
if the host is not connected (network failure, or deactivated) these two errors will be shown.

can you re-check from a stable environment?

Comment 5 Daniel 2020-03-31 13:24:46 UTC
(In reply to Ahmad Khiet from comment #4)
> from logs I see that there is a networking error and in vdsm
> 'libvirt.libvirtError: Requested operation is not valid: cgroup CPU
> controller is not mounted'
> if the host is not connected (network failure, or deactivated) these two
> errors will be shown.
> 
> can you re-check from a stable environment?

Hey Ahmad,
Not sure... what do you mean when you're saying stable environment?
If it helps, the issue keep reproducing over 3 different environments and on the latest ovirt-engine as well.

Comment 6 Ahmad Khiet 2020-03-31 13:27:20 UTC
Hi Daniel,

I mean without the network issues and the cpu groups issues. 
see the logs

Comment 7 Avihai 2020-03-31 14:16:08 UTC
(In reply to Ahmad Khiet from comment #6)
> Hi Daniel,
> 
> I mean without the network issues and the cpu groups issues. 
> see the logs

The storage and storage domains are available so this is not an ENV issue.
cpu groups issue seen in VDSM looks like a libvirt issue so maybe we need someone from libvirt team to check this out.

Comment 9 Ahmad Khiet 2020-08-26 09:12:18 UTC
is this bug still reproducing? 
does this bug fix https://bugzilla.redhat.com/show_bug.cgi?id=1838051 solved this issue? can you verify it?

Comment 11 Shir Fishbain 2020-08-30 20:56:39 UTC
Created attachment 1713089 [details]
new_screenshot

Comment 15 Bella Khizgiyaev 2020-10-14 14:06:04 UTC
As Ahmad mention the original issue was solved in https://bugzilla.redhat.com/show_bug.cgi?id=1838051 

Regarding the other issue that Shir posted in the last command a new bug was opened since its diffrent from the original bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1888278

Comment 17 Sandro Bonazzola 2020-11-11 06:39:44 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.


Note You need to log in before you can comment on or make changes to this bug.