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

Bug 1251971

Summary: Host PM failure message is not descriptive enough
Product: [oVirt] ovirt-engine Reporter: Pavel Stehlik <pstehlik>
Component: Frontend.WebAdminAssignee: Ori Liel <oliel>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: brunowcs, bugs, creatmbox, ecohen, gklein, lsurette, lsvaty, mgoldboi, oourfali, pstehlik, rbalakri, volga629, yeylon
Target Milestone: ovirt-3.6.0-rcFlags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: 3.6.0-12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:27:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
PM-host.png none

Description Pavel Stehlik 2015-08-10 12:37:14 UTC
Created attachment 1061025 [details]
PM-host.png

Description of problem:
 The message on PM Tab of Host is not descriptive enough.
Current message:
Test failed: Failed to run fence action on host '<FQDN-of-my-host>', no proxy was found.

 Which proxy? I already set WebSocket Proxy during installation; our company WEB proxy is also set ;) I know, but can you imagine ppl who are using it? Which proxy should I set? 
Aha, how should I know this is term for an available host in same Cluster/DC (based on setting)?
Please either provide link for documentation or (even better) rephrase error message - I could imagine: "No other host available in current realm for acting as fence proxy". There is plenty space on the window (see att scrnshot).


Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.6.0-0.0.master.20150804111407.git122a3a0.el6

How reproducible:


Steps to Reproduce:
1. Try to add 1st host into RHEVM & set PM for it.
2. Hit Test button on PM tab of host.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Oved Ourfali 2015-08-11 08:50:56 UTC
What about:
Test failed: Failed to run fence action on host '<FQDN-of-my-host>', no available proxy host to run the operation.

Comment 2 Pavel Stehlik 2015-08-11 09:08:02 UTC
(In reply to Oved Ourfali from comment #1)
> What about:
> Test failed: Failed to run fence action on host '<FQDN-of-my-host>', no
> available proxy host to run the operation.

What if we'll change the sentence: "Test failed: Failed to run fence action on host '<FQDN-of-my-host>', no available proxy host to run the operation. You need at leas one available host for the successful test."

Comment 3 Oved Ourfali 2015-08-11 09:13:15 UTC
(In reply to Pavel Stehlik from comment #2)
> (In reply to Oved Ourfali from comment #1)
> > What about:
> > Test failed: Failed to run fence action on host '<FQDN-of-my-host>', no
> > available proxy host to run the operation.
> 
> What if we'll change the sentence: "Test failed: Failed to run fence action
> on host '<FQDN-of-my-host>', no available proxy host to run the operation.
> You need at leas one available host for the successful test."

There are different rules for the proxy selection, so I wouldn't go into adding the last sentence.

Comment 4 Pavel Stehlik 2015-08-11 09:23:16 UTC
Well - we need some decision here, please help us, thank you.

I think, we either should add this TEXT change or not to fail test when adding first host - due to workflow. Is confusing. User did nothing wrong, but get Fail message.

Comment 5 Oved Ourfali 2015-08-11 09:29:59 UTC
(In reply to Pavel Stehlik from comment #4)
> Well - we need some decision here, please help us, thank you.
> 
> I think, we either should add this TEXT change or not to fail test when
> adding first host - due to workflow. Is confusing. User did nothing wrong,
> but get Fail message.

Not to fail means misleading the user.
Moran - please choose TEXT from the proposals above, or suggest your own so that we'll discuss.

Comment 6 Moran Goldboim 2015-08-16 16:30:43 UTC
(In reply to Oved Ourfali from comment #5)
> (In reply to Pavel Stehlik from comment #4)
> > Well - we need some decision here, please help us, thank you.
> > 
> > I think, we either should add this TEXT change or not to fail test when
> > adding first host - due to workflow. Is confusing. User did nothing wrong,
> > but get Fail message.
> 
> Not to fail means misleading the user.
> Moran - please choose TEXT from the proposals above, or suggest your own so
> that we'll discuss.

Is there an option to disable/grey out the test button on first host in the cluster?

Comment 7 Pavel Stehlik 2015-08-17 06:24:47 UTC
> Is there an option to disable/grey out the test button on first host in the
> cluster?

I can cope with that. Currently we don't have such setting. Would it be possible to add such functionality?

Comment 8 Oved Ourfali 2015-08-17 08:35:24 UTC
But you have other cases like fee hosts, but none is reachable. I'd suggest to either change the error, or add an information icon near the test, that says it might fail in case of not finding a host to run on.

Comment 9 Moran Goldboim 2015-08-17 09:03:11 UTC
(In reply to Oved Ourfali from comment #8)
> But you have other cases like fee hosts, but none is reachable. I'd suggest
> to either change the error, or add an information icon near the test, that
> says it might fail in case of not finding a host to run on.

sounds good enough.

Comment 10 Ori Liel 2015-08-18 14:11:37 UTC
I'll change to:

"Test failed: Failed to run fence status-check on host xxx. No other host is available to serve as proxy for the operation". 

OK?

Comment 11 Pavel Stehlik 2015-08-25 08:15:05 UTC
(In reply to Ori Liel from comment #10)
> I'll change to:
> 
> "Test failed: Failed to run fence status-check on host xxx. No other host is
> available to serve as proxy for the operation". 
> 
> OK?

I like it. Moran?

Comment 12 Moran Goldboim 2015-08-25 09:55:13 UTC
(In reply to Pavel Stehlik from comment #11)
> (In reply to Ori Liel from comment #10)
> > I'll change to:
> > 
> > "Test failed: Failed to run fence status-check on host xxx. No other host is
> > available to serve as proxy for the operation". 
> > 
> > OK?
> 
> I like it. Moran?

works for me, thanks.

Comment 13 Lukas Svaty 2015-10-05 10:41:36 UTC
verified in rhevm-3.6.0-0.18.el6.noarch

current message:
Test failed: Failed to run fence status-check on host '$HOST'. No other host was available to serve as proxy for the operation.

Comment 14 Sandro Bonazzola 2015-11-04 11:27:28 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.

Comment 15 lifeman 2016-09-30 08:37:38 UTC
oVirt 4.0 has same massage with apc settings set.

Comment 16 lifeman 2016-09-30 08:44:58 UTC
Ovirt engine log: Can not run fence action on host no suitable proxy host was found.

Comment 17 lifeman 2016-10-03 09:08:24 UTC
*** Bug 1380647 has been marked as a duplicate of this bug. ***

Comment 18 Bruno Carvalho 2016-11-23 13:29:33 UTC
I am with same problem used Ovirt 4.0 with ipmilan

Comment 19 Slava 2017-01-08 04:20:10 UTC
Ovirt 4.05 same error with ilo2 card. From cli all works fine.

Can not run fence action on host 'hosted_engine_1', no suitable proxy host was found