Problem updating endorsingpeers/peerorgs variables
Dudu3710 opened this issue · comments
When commit or instantiate are called, they use endorsingpeers/peerorgs variables in a for loop, to get all the necessary information about the peers. But in the commit command for example it only recognize the orgs and peers that are in the network that called the function. In my case i have a channel with two different networks connected and i cant reach majority using this functions because the command don`t use the other network orgs/peers in the for loop.
Where this variables are? How can i change them?
@Dudu3710 I believe that you should use -o to specify an org for the commit command.
Thanks for your answer.
I used -o but the problem is still going on.
Thanks for your answer.
I used -o but the problem is still going on.
I followed the docs/ExpandYourNetwork.md file to run an example. and when i tried to run the commit function using mysite1 i received the error that i can`t reach majority, i think is because the endorsingpeers/peerorgs variables are not being updated.
Is normal that only mysite0 can commit?
I do not think that is the case. It depends how many approve the action. Probably your site1 has less number of orgs?
…
Sent from my iPhone On Nov 4, 2022, at 12:43 PM, Dudu3710 @.> wrote: Thanks for your answer. I used -o but the problem is still going on. I followed the docs/ExpandYourNetwork. md file to run an example. and when i tried to run the commit function using mysite1 i received the error that i cant reach majority, ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Thanks for your answer. I used -o but the problem is still going on. I followed the docs/ExpandYourNetwork.md file to run an example. and when i tried to run the commit function using mysite1 i received the error that i cant reach majority, i think is because the endorsingpeers/peerorgs variables are not being updated. Is normal that only mysite0 can commit? — Reply to this email directly, view it on GitHub<#361 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAO2NSZTGBSD2PIXEQLQNUTWGU4KRANCNFSM6AAAAAARTM5TJI. You are receiving this because you commented.Message ID: @.>
Yes, site1 have only 1 org, but they all approved so in this case anyone that approve can commit right?
Using the site1:
checking the cccommit.sh script, site1 only have 1 org so it will only use 1 org on commit function. Generating an endorsment policy failure (i am using majority).
.
This problem got worse when i executed an example with 2 sites with 2 orgs each, neither has majority so i can`t commit.
I checked that all orgs have approved the definition.
Thank you!