- **status**: wontfix --> review
- **Comment**:
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.
---
** [tickets:#2464] smf: try to wait for opensafd status before executing reboot
**
**Status:** review
**Milestone:** 5.17.10
**Created:** Fri May 19, 2017 10:55 AM UTC by Rafael Odzakow
**Last Updated:** Mon Aug 14, 2017 11:22 AM UTC
**Owner:** Rafael Odzakow
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.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
