search

EC-Release / oci

A series of EC helm charts used for k8s deployment.
https://hub.docker.com/repository/docker/enterpriseconnect/agent
Other
3 stars 5 forks source link

TLS EC is failing on EKS #100

Closed simran3695 closed 4 years ago

simran3695 commented 4 years ago

@ayasuda2OO3 We are currently seeing the TLS EC app is not getting sync on Argocd with below error. As suggested yesterday I have rollback the changes to last successful code but still the error remains the same.

Deployment in version "v1" cannot be handled as a Deployment: v1.Deployment.Spec: v1.DeploymentSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Containers: []v1.Container: v1.Container.Env: []v1.EnvVar: v1.EnvVar.Value: ReadString: expects " or n, but found t, error found in #10 byte of ...|,"value":true}],"ima|..., bigger context ...|.lpt","value":"7980"},{"name":"conf.rpt","value":true}],"image":"enterprisecon

Please check.

simran3695 commented 4 years ago

After looking on the error i got https://stackoverflow.com/questions/59354115/helm-upgrade-fails-with-error-expects-or-n-but-found-t and I tried to add quotes to rpt, plugin.port and plg in quotes and now the app is atleast getting sync.

The pod is failing now with different error.

[EC Server] 2020/10/09 10:31:18 [cleaned up logging file(s). connectivity.log plugin.log] [EC Server] 2020/10/09 10:31:18 [Rev: v1.hokkaido.212] [EC Agent] main pacakge exception: interface conversion: interface {} is string, not bo ol

ayasuda2OO3 commented 4 years ago

@simran3695 please confirm the fix and close.

ayasuda2OO3 commented 4 years ago

113 #112 #110 #109 #108 #106 #105 #104 #103

simran3695 commented 4 years ago

TLS EC is now fixed. Hence closing this issue. Thankyou for the the help and guidance to fix this as always.