hyperledger/fabric · error
could not get MSPs
Error message
could not get MSPs
What it means
Returned by validateCollectionConfigMemberOrgsPolicy when the mspMgr cannot supply MSPs while compiling the collection's member-org policy. The policy envelope was structurally present but the MSP context needed to validate it is unavailable at validation time.
Source
Thrown at core/chaincode/lifecycle/scc.go:853
}
if coll.MemberOrgsPolicy.GetSignaturePolicy() == nil {
return errors.Errorf("collection member org policy is empty for collection '%s'", coll.Name)
}
// calling this constructor ensures extra semantic validation for the policy
pp := &cauthdsl.EnvelopeBasedPolicyProvider{Deserializer: mspMgr}
if _, err := pp.NewPolicy(coll.MemberOrgsPolicy.GetSignaturePolicy()); err != nil {
return errors.WithMessagef(err, "invalid member org policy for collection '%s'", coll.Name)
}
// make sure that the signature policy is meaningful (only consists of ORs)
if err := validateSpOrConcat(coll.MemberOrgsPolicy.GetSignaturePolicy().Rule); err != nil {
return errors.WithMessagef(err, "collection-name: %s -- error in member org policy", coll.Name)
}
msps, err := mspMgr.GetMSPs()
if err != nil {
return errors.Wrapf(err, "could not get MSPs")
}
// make sure that the orgs listed are actually part of the channel
// check all principals in the signature policy
for _, principal := range coll.MemberOrgsPolicy.GetSignaturePolicy().Identities {
var orgID string
// the member org policy only supports certain principal types
switch principal.PrincipalClassification {
case mspprotos.MSPPrincipal_ROLE:
msprole := &mspprotos.MSPRole{}
err := proto.Unmarshal(principal.Principal, msprole)
if err != nil {
return errors.Wrapf(err, "collection-name: %s -- cannot unmarshal identity bytes into MSPRole", coll.GetName())
}
orgID = msprole.MspIdentifier
// the msp map is indexed using msp IDs - this behavior is implementation specific, making the following check a bit of a hack
_, ok := msps[orgID]View on GitHub (pinned to 2736b63f8f)
Solutions
- Check the wrapped error and the channel's MSP configuration
- Retry after the channel config/MSP setup is healthy
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at core/chaincode/lifecycle/scc.go:853 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04).
Data as JSON: /api/errors/1927aef58f56fc00.
Report an issue: GitHub.