Updating PVA Agent on PVCfL 4.7 active node triggers relocation
Cluster is verifying node state by querying three service -
pvapp. Relocation occurs because cluster considers node to be down when PVA Agent is getting interrupted during update installation.
Prior to updating PVA Agent clustered service should be frozen with a following command:
# clusvcadm -Z <cluster_service_name>
Note, after PVA Agent update installation
pvaagentd services will be enabled for autostart again, so it will be necessary to disable their automatic startup once again:
# chkconfig pvapp off # chkconfig pvaagentd off
Once PVA Agent update is finished, verify that services are running using following command:
# pvaagent status;pvapp status pvaagentd (pid 28063) is running... pvappd (pid 28118) is running...
If one of the services is not running, start it manually. If both services are running you may unfreeze the clustered service now:
# clusvcadm -U <cluster_service_name>
NOTE: Do not unfreeze the clustered service until you make sure all monitored services are running, otherwise it will trigger relocation.