Bug 954301
| Summary: | [TEXT] Event "rhevm failed to elect SPM for a DC" is misleading | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ilanit Stein <istein> | ||||||||
| Component: | ovirt-engine | Assignee: | Mooli Tayer <mtayer> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.2.0 | CC: | abaron, acathrow, amureini, bazulay, iheim, istein, jkt, lpeer, mtayer, pstehlik, Rhev-m-bugs, yeylon, yzaslavs | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.3.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | infra | ||||||||||
| Fixed In Version: | is7 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 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
Ilanit Stein
2013-04-22 08:18:55 UTC
Ilanit, I'm not sure what we want to solve here, can you please elaborate? From what it seems to be, that AuditLog is being shown only on a very specific case (and possibly - we should edit the it's text regardless). In case of problem, the engine will try to select an spm indefinitely, so i guess that we don't want to flood the log with that event or on what phase do we need to log it, it seems to me like it would just be annoying to the user and will flood the event log. The main point in this bug is that there is no consistency on when "rhevm failed to elect SPM for a DC" event is sent: For network exception, that prevents the connection to vdsm, we send it, On the other hand for the 2 cases, described in the bug description, we don't. Why should it differ? If, for example, this event is reported in event notification, for some cases of SPM election failure, the user will be notified, and for others not. What is scenario to generate this message please? "Fencing failed on Storage Pool Manager for
Data Center ${StoragePoolName}. Setting status to Non-Operational"
how to reproduce the scenario that generates the above error ?
David - where do you see this? Do you see ${StoragePoolName} in the UI ?
If so , this is a different bug.
Hi, The message I should see and now I can see is-> Fencing failed on Storage Pool Manager south-01.xx.xx.xx.com for Data Center DC33-is12-Tabs. Setting status to Non-Operational. But what scenario should I use ? 3.3/is12 & is13
----------------------
The main problem I see disregarding the Text issue,
Is the recovering process - it fails
With two hosts ,1 DC
I removed all iptables rules
I tried "Select SPM" - failed
"Host south-01.lab.bos.redhat.com was force selected by admin@internal"
Only the first host that was SPM succeeds eventualy
- Even after I recover host1 to SPM
I try to "Select SPM" for the second, and it fails
"Host south-01.lab.bos.redhat.com was force selected by admin@internal"
- after couple of tries it succeeds to become SPM
with 1 host 1 DC
I removed all iptables rules
I tried "Select SPM" - failed
host is active but -
"Failed to connect Host south-05.lab.bos.redhat.com to Storage Servers"
"Failed to Reconstruct Master Domain for Data Center DC33-is13-BOS."
Created attachment 796301 [details]
south05
Created attachment 796302 [details]
south01
Created attachment 796303 [details]
south07
Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |