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.
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
Verified on 3.6.0-20
Since oVirt 3.6.0 has been released, moving from verified to closed current release.