Replies: 1 comment 4 replies
-
|
Hi @abdnah , |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @ispeakc0de, will try this and update here. |
Beta Was this translation helpful? Give feedback.
-
|
@ispeakc0de , unfortunately I don't have account in kubernetes.slack and I'm not able to create one :( |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
@ispeakc0de, would you please help with the mongodb issue ? |
Beta Was this translation helpful? Give feedback.
-
Hello, I've launched the upgrade using litmus-cluser-scope-3.4.0.yaml file after modifying the DB_SERVER only but I'm getting the following errors in litmusportalserver pod:
{"error":"(IndexKeySpecsConflict) An existing index has the same name as the requested index. When index names are not specified, they are auto generated and can cause conflicts. Please refer to our documentation. Requested index: { v: 2, ││ unique: true, key: { environment_id: 1 }, name: \"environment_id_1\", partialFilterExpression: { is_removed: false } }, existing index: { v: 2, unique: true, key: { environment_id: 1 }, name: \"environment_id_1\" }","file":"/gql-server/pkg ││ /database/mongodb/init.go:270","func":"github.com/litmuschaos/litmus/chaoscenter/graphql/server/pkg/database/mongodb.(*MongoClient).initAllCollection","level":"fatal","msg":"failed to create indexes for environments collection","time":"202 ││ 4-03-01T15:02:22Z"}Can someone help with this issue please ?
Beta Was this translation helpful? Give feedback.
All reactions