When running this test, this is the first modify request that we receive:
gribi::ModifyRequest params {
}
Note the lack of an election_id inside the modify request. And no further modify request is received by the server with an election_id. So, there is no reason for the server to send an error back to the client because it never receives an election_id from the client that requested all primary mode.
I am not too familiar with the code but I think it may be due the switch on the redundancy mode in GRIBIClient Start function in fluent.go. In that switch, if we are in all primary mode, then the election id is ignored. Only when in the single primary mode is the election id even considered. I wonder if the test infrastructure is preventing this invalid request from being made in the first place.
When running this test, this is the first modify request that we receive:
Note the lack of an election_id inside the modify request. And no further modify request is received by the server with an election_id. So, there is no reason for the server to send an error back to the client because it never receives an election_id from the client that requested all primary mode.
I am not too familiar with the code but I think it may be due the switch on the redundancy mode in GRIBIClient Start function in fluent.go. In that switch, if we are in all primary mode, then the election id is ignored. Only when in the single primary mode is the election id even considered. I wonder if the test infrastructure is preventing this invalid request from being made in the first place.