- **status**: review --> fixed
- **Comment**:
changeset: 5624:d6bded84da41
branch: opensaf-4.3.x
parent: 5622:91cc3199615f
user: Nagendra Kumar<[email protected]>
date: Wed Aug 20 16:27:34 2014 +0530
summary: amfd: allow lock on su after issue of shutdown [#582]
changeset: 5625:acd24a430677
branch: opensaf-4.4.x
tag: tip
parent: 5623:b0fd1a2c4b8a
user: Nagendra Kumar<[email protected]>
date: Wed Aug 20 16:28:10 2014 +0530
summary: amfd: allow lock on su after issue of shutdown [#582]
[staging:d6bded]
[staging:acd24a]
---
** [tickets:#582] AMF: SU cannot be locked in shutting-down admin state**
**Status:** fixed
**Milestone:** 4.3.3
**Created:** Thu Oct 03, 2013 07:27 AM UTC by Hans Feldt
**Last Updated:** Tue Aug 12, 2014 03:30 PM UTC
**Owner:** Nagendra Kumar
There is logic to handle the case where an SU gets locked while it is
shutting-down state. However a recently () added check in su_admin_op_cb()
makes this code unreachable. The change in question was:
changeset: 4251:3ea7a5ddde48
parent: 4248:a3cb80b7e1b9
user: Nagendra Kumar<[email protected]>
date: Mon May 06 15:18:55 2013 +0530
summary: Amf: Add validation during Sg and Su admin operation (#3117)
So it seemed to have worked before this change. Locking as SI works while in
shutting-down state.
I think the changeset above should be corrected to exclude the current SU under
operation.
---
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.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
