Bug 1317574

Summary: When no SPM can be chosen, AuditLog should display notification.
Product: [oVirt] ovirt-engine Reporter: Natalie Gavrielov <ngavrilo>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED DEFERRED QA Contact: Raz Tamir <ratamir>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.3.3CC: bugs, ngavrilo, tnisan, ylavi
Target Milestone: ---Flags: amureini: ovirt-4.1?
ngavrilo: planning_ack?
ngavrilo: devel_ack?
ngavrilo: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-12 10:16:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
engine.log none

Description Natalie Gavrielov 2016-03-14 15:16:31 UTC 
Description of problem:
When no SPM can be chosen, AuditLog should display notification.

Version-Release number of selected component (if applicable):
rhevm-3.6.3.3-0.1.el6.noarch
vdsm-4.17.23-0.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Move hosts to maintenance. 
2. Change their spm priority to -1.
3. Activate hosts.

Actual results:
No AuditLog notification regarding spm.

Expected results:
AuditLog notification that no host can be chosen as SPM.
Comment 1 Natalie Gavrielov 2016-03-14 15:17:20 UTC 
Created attachment 1136191 [details]
engine.log
Comment 2 Yaniv Lavi 2017-02-06 12:43:11 UTC 
There is a column on SPM next to each host. You can know that no host is SPM from there. You will also get error every time a host is contending and fails.
I think this is enough and that notification that none can be elected will flood the event log. Can we close this?
Comment 3 Natalie Gavrielov 2017-02-07 10:07:10 UTC 
(In reply to Yaniv Dary from comment #2)
> There is a column on SPM next to each host. You can know that no host is SPM
> from there. You will also get error every time a host is contending and
> fails.

Yea, you can see all hosts have "Normal" status in the SPM column and one of them is contending for SPM role (has "Contending" status), but there is no way of telling from the UI that none of these hosts can potentially be an SPM (the priority is not shown). 
and I don't think a user can guess that..
Maybe if it was displayed with the priority it would be clear that this host can't act as SPM.

> I think this is enough and that notification that none can be elected will
> flood the event log.
Just saw that the RFE for flooding mechanism is still in status "New", so I won't mention anything about it. 

>Can we close this?
Emmm... it's your call.
Comment 4 Yaniv Kaul 2017-02-12 10:16:11 UTC 
I don't think it's an important enough scenario - and I do hope in most cases it's a transient state. Closing for the time being.