- **status**: assigned -- duplicate
- **assigned_to**: Anders Bjornerstedt -- nobody
- **Milestone**: 4.4.0 -- never
---
** [tickets:#709] saImmRepositoryInit attrib modification returns TRY_AGAIN in
2PBE scenario**
**Status:** duplicate
**Created:** Tue Jan 07, 2014 10:23 AM UTC by
---
** [tickets:#709] saImmRepositoryInit attrib modification returns TRY_AGAIN in
2PBE scenario**
**Status:** unassigned
**Created:** Tue Jan 07, 2014 10:23 AM UTC by surender khetavath
**Last Updated:** Tue Jan 07, 2014 10:23 AM UTC
**Owner:** nobody
changeset : 4733
setup: 5nodes
Test:
- **status**: unassigned -- assigned
- **assigned_to**: Anders Bjornerstedt
- **Milestone**: future -- 4.4.0
---
** [tickets:#709] saImmRepositoryInit attrib modification returns TRY_AGAIN in
2PBE scenario**
**Status:** assigned
**Created:** Tue Jan 07, 2014 10:23 AM UTC by surender
If I understand correctly, you have a cluster configured for 2PBE where
only one SC is available. That means the cluster is by default not persistent
writable (in the twoSafe2PBE state that requires both PBEs to be available).
Ccb operations will be rejected with TRY_AGAIN in this state.
It is
