Bug 1246440

Summary: (Fencing) on Cluster <UNKNOWN>
Product: [oVirt] ovirt-engine Reporter: Netbulae <info>
Component: GeneralAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, ecohen, gklein, lsurette, oourfali, pmatyas, rbalakri, 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: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: 3.6.0-4_alpha3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-27 07:50:34 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:

Description Netbulae 2015-07-24 10:29:46 UTC 
Description of problem:
On 3.5.3.1-1.el7.centos, we see the following message when activating a host that has been in maintenance (upgrade) and activated before it's booted up properly. The fencing works fine.

"Stopping Host test2.netbulae.test (Fencing) on Cluster <UNKNOWN>"
and
"Starting Host test2.netbulae.test (Fencing) on Cluster <UNKNOWN>"

It looks the same as in:
Same as in https://bugzilla.redhat.com/show_bug.cgi?id=967446

But it's consistent in our environment. All hosts are set to "cluster" fencing, not "dc" and this is a 3 host cluster for virtualization plus a 3 node cluster for glusterfs. The glusterfs cluster is the first cluster and the virtualization hosts cluster the second one.

It's not a big problem but strange that it can't find the cluster name.
Comment 1 Eli Mesika 2015-07-26 07:19:29 UTC 
Problem is in ExecutionHandler::resolveJobMessage
This actually call AuditLogDirector::resolveMessage and the value for the "VdsGroups" custom variable in the log message is not found in the maps created by AuditlogDirector::getAvailableValues 

The code therefor returns an UNKNOWN value for such case 

The variable is not set probably correctly in the caller command
Comment 2 Petr Matyáš 2015-11-19 11:48:24 UTC 
Verified on 3.6.0-20
Comment 3 Sandro Bonazzola 2015-11-27 07:50:34 UTC 
Since oVirt 3.6.0 has been released, moving from verified to closed current release.