- **Milestone**: future --> never
---
** [tickets:#879] amfnd: CSI remove not working correctly when num of CSIs is
different between SIs**
**Status:** duplicate
**Milestone:** never
**Created:** Tue Apr 29, 2014 06:47 PM UTC by Alex Jones
**Last Updated:** Wed Apr 30, 2014 05:15 PM UTC
**Owner:** Alex Jones
The "CSI Remove All" logic does not remove all CSIs for a component when the
CSIs are not evenly distributed across all SIs to which this component is
assigned.
The configuration in which this bug shows up is the following:
N+M (2+1) SG,
3 SUs for this SG,
2 SIs for this SG,
3 Components one for each SU,
1 CSI for the Component assigned to one of the SIs
The problem occurs on the node hosting the 2 STANDBY SIs for the SG.
1) Perform an "admin shutdown" on the SG.
2) This will silently fail, and you can see the CSIs assigned to the STANDBY
have not been removed. They are still in amf, and in IMM.
3) Subsequent admin operations on the SG (admin lock-instantiate) will fail,
and log messages will be printed such as: "localmessages:Mar 5 20:33:37 linux
osafamfd[31613]: WA SG state is not stable"
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
