Unable to use v1.1 agent

[ramaraosrikakulapu]

This is for a customer use case. Planning to run EC gateway under Corp Azure subscription and trying to launch gateway, but giving following error -

 [EC Gateway x0] 2020/06/29 20:07:38 [cleaned up logging file(s). connectivity.log plugin.log]
 [EC Gateway x0] 2020/06/29 20:07:38 [Rev: v1.1.edo.0]
 [EC Gateway x0] 2020/06/29 20:07:38 [Agent websocket compression is being negotiated at level 0]
 [EC Gateway x0] 2020/06/29 20:07:38 [Id: xxxxx]
 [EC Gateway x0] 2020/06/29 20:07:38 [instantiate usage..]
 [EC Gateway x0] 2020/06/29 20:07:39 []
 [EC Gateway x0] 2020/06/29 20:07:39 [github.build.ge.com/212359746/wzconf.(*Config).GetPublicKey.func1.1 get cert call failed.]
 [EC Gateway x0] 2020/06/29 20:07:39 [github.build.ge.com/212359746/wzconf.(*Config).GetEncryptedKey.func1.1 received empty cert from the service.]
 [EC Gateway x0] 2020/06/29 20:07:39 [github.build.ge.com/212359746/wzconf.(*Config).UsageReporting.func1.1 getting encrypted key errors.]
 [EC Agent] main pacakge exception: EC Service is invalid. Contact your EC Service administrator for more detail.

Verified the cert expiry and valid until Sep 2020.

Not Before: Oct  1 05:07:36 2019 GMT
Not After : Sep 30 05:07:36 2020 GMT

This is not happening with 212 agent version

[ayasuda2OO3]

Acknowledged. In investigating.

[ayasuda2OO3]

Can you share the -sst setting in your test? @ramaraosrikakulapu

[Gayatri212]

@ramaraosrikakulapu did you add /v1 at the end of sst. For new version /v1 in case of v1.1 agent and /v1beta in case of v1.1beta agent version is required

[ramaraosrikakulapu]

Good catch. Yes, I have to add /v1 at the end of sst flag. Thank you @ayasuda2003 @Gayatri212