There are cases when opensafd startup is still ongoing and SMF will send out a reboot command for a node. Because opensafd has taken a lock the reboot command will not be able to call opensafd stop. It is suggested that SMF tries to wait for the release of the lock with "opensafd status". The waiting time is short and SMF continues with reboot even if the lock is not released.
ticket [#2459] allows SMF to query the status of opensafd.
Diff:
Related
Tickets:
#2459This ticket should be invalidated because of new solution of ticket [#2459]?
Related
Tickets:
#2459solved in base opensaf
commit a051496719a3c862594af17d88b082031dd53b33 (ticket-2459)
Seen again as protecting with mutexes and try again loops in opensafd nid script does not solve for when triggering node reboot as other services will be shutting down and causing unexpected errors.
commit f3ef8eebf44f0eab4dcc65f83fe3119a77ef5067 (HEAD -> develop, origin/develop)
Author: Rafael Odzakow rafael.odzakow@ericsson.com
Date: Mon Sep 25 13:52:03 2017 +0200