rhevm network persistence issue

Today I observed a strange issue due to host non operational

>Tried service vdsmd restart but there was another issue with rhevm network which went down and was not coming up:

I had to recreate /etc/sysconfig/network-scripts/ifcfg-rhevm (it was trying dhcp for ip addressing) from another host.

Also I had to re create  bond0 at /var/lib/vdsm/persistence/netconf/bond and rhevm at /var/lib/vdsm/persistence/netconf/nets

--=====

[root@dedrhosp4 bin]# cd /var/lib/vdsm/persistence/netconf
[root@dedrhosp4 netconf]# pwd
/var/lib/vdsm/persistence/netconf
[root@dedrhosp4 netconf]# ll
total 8
drwxr-xr-x. 2 root root 4096 Jul 30 22:07 bonds
drwxr-xr-x. 2 root root 4096 Jul 30 22:07 nets
[root@dedrhosp4 netconf]# ll -R
.:
total 8
drwxr-xr-x. 2 root root 4096 Jul 30 22:07 bonds
drwxr-xr-x. 2 root root 4096 Jul 30 22:07 nets

./bonds:
total 24
-rw-r--r--. 1 root root 58 Jul 30 22:07 bond0
-rw-r--r--. 1 root root 58 Jun 10 15:17 bond1
-rw-r--r--. 1 root root 58 Jun 10 15:17 bond2
-rw-r--r--. 1 root root 58 Jun 10 15:17 bond3
-rw-r--r--. 1 root root 58 Jun 10 15:17 bond4
-rw-r--r--. 1 root root 60 Jun 10 15:17 bond5

./nets:
total 68
-rw-r--r--. 1 root root 121 Jun 10 15:17 intnet_655
-rw-r--r--. 1 root root 106 Jun 10 15:17 neutron
-rw-r--r--. 1 root root 224 Jul 30 22:07 rhevm
-rw-r--r--. 1 root root 120 Jun 10 15:17 vlan_25
-rw-r--r--. 1 root root 203 Jun 10 15:17 vlan_651
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_656
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_657
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_700
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_701
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_712
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_714
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_715
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_800
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_801
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_802
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_803
-rw-r--r--. 1 root root 121 Jun 10 15:17 vlan_804

Host Non-operational issue - Storage domain monitoring thread slows down

Implemented following change to resolve/avoid this issue:

1)      Check the current configuration on RHEV Manager using after switching to root:

engine-config -g MaxStorageVdsTimeoutCheckSec

2)      Change the current configuration (change value to 75):

rhevm-config -s MaxStorageVdsTimeoutCheckSec=75

Now 2^nd parameter  “vdsHeartbeatInSeconds”

3)      Check the current configuration:

engine-config -g vdsHeartbeatInSeconds

4)      Change the current configuration (change value to 20) if it’s not set to 20 already:

rhevm-config -s vdsHeartbeatInSeconds=20

5)      Restart the ovirt-engine service after this.

               /etc/init.d/ovirt-engine restart

Check the changed configurations:

engine-config -g MaxStorageVdsTimeoutCheckSec

engine-config -g vdsHeartbeatInSeconds

Data storage domain (FC storage) has some issue. it is getting unavailable to different RHEV hosts randomly.

We can fix this issue by setting following steps on RHEV manager:
---

#grep vdsHeartbeatInSeconds.type /etc/ovirt-engine/engine-config/engine-config.properties

#cp /etc/ovirt-engine/engine-config/engine-config.properties /etc/ovirt-engine/engine-config/engine-config.properties.backup

#echo vdsHeartbeatInSeconds.type=Integer >> /etc/ovirt-engine/engine-config/engine-config.properties

#engine-config -s vdsHeartbeatInSeconds=20

#service ovirt-engine restart

#service jbossas restart

#engine-config  -l vdsHeartbeatInSeconds

#engine-config  --help

#engine-config -g vdsHeartbeatInSeconds

IPA user unable to login - rare issue

/tmp permission could be an issue, check and change!

error deadlock detected in postgresql - RHEVM down

/tmp permissions can result in "error deadlock detected in postgresql"

make sure that /tmp has appropriate permissions.

Update RHEVM!