1. Messages
  2. Error Removing Orgs from Fabric Network

Re: Error Removing Orgs from Fabric Network

Brett Tiller
 

Thanks Chandramohan, I’ve got the example working by setting the policies in configtx.yaml from MAJORITY to ANY.  I have the following questions.

 

  1. The peer channel commands to fetch and update the block requires that an orderer and channel be specified.  Does this requirement then mean that all orderers and any channels to which the organization subscribes must be operated upon as well to remove the organization from the network?

 

  1. After removing the organization from the network, when I run the command ‘peer channel list’, the response shows that the organization still belongs to the channel ‘mychannel’.  When an organization is removed from a network shouldn’t it also be removed from all channels?

 

  1. How does organization once removed from the network rejoin the network?

 

Thanks,

 

Brett Tiller

Sr. Software Engineer

984-349-4239 (mobile)

btiller@...

 

https://www.linkedin.com/company/securboration

 

From: Chandramohan Jagtap <cmjagtap1@...>
Sent: Wednesday, August 3, 2022 9:43 PM
To: Brett Tiller <btiller@...>
Cc: fabric@...
Subject: Re: [Hyperledger Fabric] Error Removing Orgs from Fabric Network

 

Hi Brett,

 

I am the author of above article. In article I am using a ANY policy, that's why I only require single organization signature. If you are trying it on test-network then you will have take signature from majority of organization then only you will be able to submit the transaction. It means you will have to execute step 10 from majority of organization to take signatures.

 

Let me know if you need any assistance.

 

Thanks & Regards,

Chandramohan Jagtap 

 

On Wed, Aug 3, 2022, 11:51 PM Brett Tiller <btiller@...> wrote:

I’m testing that an organization can be removed from a network and am following the steps specified in the fairly recent article https://medium.com/geekculture/remove-org-from-running-hypeledger-fabric-blockchain-744bdd05511b, as it is relevant to HLF fabric 2.3.  I’m using the fabric-sample test-network,

which as you know has two organizations and one orderer, for my test case. After Step 8 I stopped the Org2MSP docker container because in my view it is in process of being removed from the network so should be not endorsing transactions.  The error I’m encountering is in the final step, step 11 which is to

submit the channel update to the blockchain, when I run the command below.

 

peer channel update -f config_update_in_envelope.pb -c mychannel -o localhost:7050 --tls --cafile $ORDERER_CA

  1. Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'mychannel': error authorizing update: error validating DeltaSet: policy for [Group]  /Channel/Application not satisfied: implicit policy evaluation failed - 1 sub-policies were satisfied, but this policy requires 2 of the 'Admins' sub-policies to be satisfied

 

My question is where and how do I make the policy change to resolve the error above?

 

Thanks,

 

Brett Tiller

Sr. Software Engineer

984-349-4239 (mobile)

btiller@...

 

https://www.linkedin.com/company/securboration

 

Message Sender is EXTERNAL to Securboration. Carefully examine this message before you open any links or attachments.

Join {fabric@lists.hyperledger.org to automatically receive all group messages.