You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I upgraded from 3.3.0 to 3.5.0, I had issues with litmusportal-server pod which was logging the following error:
│ {"file":"/gql-server/pkg/database/mongodb/init.go:109","func":"github.com/litmuschaos/litmus/chaoscenter/graphql/server/pkg/database/mongodb.MongoConnection","level":"info","msg":" ││ connected to mongo","time":"2024-03-19T14:59:39Z"} ││ {"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. P ││ lease refer to our documentation. Requested index: { v: 2, unique: true, key: { environment_id: 1 }, name: "environment_id_1", partialFilterExpression: { is_removed: false } }, e ││ xisting 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":"2024-0 ││ 3-19T14:59:39Z"}
What you expected to happen:
Upgrade successfull and no issues.
Where can this issue be corrected? (optional)
How to reproduce it (as minimally and precisely as possible):
Upgrade from 3.3.0 to 3.4.0 or to 3.5.0
Anything else we need to know?:
Issue already present in previous release.
The text was updated successfully, but these errors were encountered:
What happened:
When I upgraded from 3.3.0 to 3.5.0, I had issues with litmusportal-server pod which was logging the following error:
│ {"file":"/gql-server/pkg/database/mongodb/init.go:109","func":"github.com/litmuschaos/litmus/chaoscenter/graphql/server/pkg/database/mongodb.MongoConnection","level":"info","msg":" ││ connected to mongo","time":"2024-03-19T14:59:39Z"} ││ {"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. P ││ lease refer to our documentation. Requested index: { v: 2, unique: true, key: { environment_id: 1 }, name: "environment_id_1", partialFilterExpression: { is_removed: false } }, e ││ xisting 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":"2024-0 ││ 3-19T14:59:39Z"}
What you expected to happen:
Upgrade successfull and no issues.
Where can this issue be corrected? (optional)
How to reproduce it (as minimally and precisely as possible):
Upgrade from 3.3.0 to 3.4.0 or to 3.5.0
Anything else we need to know?:
Issue already present in previous release.
The text was updated successfully, but these errors were encountered: