Error while joining 2nd org into the same channel

[y0zg]

hi @sstone1 !

We use IBM Blockchain platform SAAS and ansible scripts

It works fine when we create orderer and org1 and joined org2 organization into the channel

But when I try joining 3rd organization into the same channel I receive below error, please advise what might be the issue

Do you know about any limitation or so on?

TASK [Update the channel writers policy] *************************************************************************************************************************************************
changed: [localhost]

TASK [Compute the channel configuration update] ******************************************************************************************************************************************
changed: [localhost]

TASK [Sign the channel configuration update] *********************************************************************************************************************************************
changed: [localhost]

TASK [Apply the channel configuration update] ********************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not update channel on any ordering service node: Failed to update channel on ordering service node: \u001b[34m2020-09-01 17:11:13.606 EEST [channelCmd] InitCmdFactory -> INFO 001\u001b[0m Endorser and orderer connections initialized\nError: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'commonstage': error authorizing update: error validating DeltaSet: policy for [Policy] /Channel/Application/Readers not satisfied: signature set did not satisfy policy\n"}

PLAY RECAP *******************************************************************************************************************************************************************************
localhost                  : ok=10   changed=8    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0 

[y0zg]

This is possible to fix manually by updating each organization and channel policy but I wonder whether this is possible to do with ansible scripts