Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mas update fails in the update-mongodb task for SNO #924

Closed
mudspringhiker opened this issue Apr 29, 2024 · 4 comments
Closed

mas update fails in the update-mongodb task for SNO #924

mudspringhiker opened this issue Apr 29, 2024 · 4 comments
Assignees
Labels
Bug Fix High Priority High priority issue to be addressed asap Triage Issue was triaged and acknowledged

Comments

@mudspringhiker
Copy link
Contributor

When running mas update for MAS in SNO, it fails in the update-mongodb task, waiting for mas-mongo-ce stateful set to be ready. MongoDBCommunity CR status is "Pending".

status:
  currentMongoDBMembers: 1
  currentStatefulSetReplicas: 1
  message: ReplicaSet is not yet ready, retrying in 10 seconds
  mongoUri: mongodb://mas-mongo-ce-0.mas-mongo-ce-svc.mongoce.svc.cluster.local:27017/?replicaSet=mas-mongo-ce
  phase: Pending
  version: 5.0.23

It appears that MongoDBCommunity CR spec.members is 3. Comparing this to a different, newly installed MAS on SNO, its MongoDBCommunity CR spec.members is 1. Changing the spec.members in the instance being updated above to 1 fixed the issue.

@terenceq
Copy link
Contributor

By default the mongo role will set the number of replicas to three. To override this behavior the environment variable MONGODB_REPLICAS can be set to one.

https://ibm-mas.github.io/ansible-devops/roles/mongodb/#mongodb_replicas

@terenceq terenceq reopened this May 1, 2024
@terenceq
Copy link
Contributor

terenceq commented May 1, 2024

I've reopened this issue as @mudspringhiker has reproduced it. I appears that mas update is not passing the env var MONGODB_REPLICAS to the mongodb role.

@istrate istrate added Bug Fix High Priority High priority issue to be addressed asap Triage Issue was triaged and acknowledged labels May 10, 2024
@istrate
Copy link
Contributor

istrate commented May 10, 2024

Worked tracked in: #941

@durera
Copy link
Contributor

durera commented May 15, 2024

Delivered in #941, new release pending

@durera durera closed this as completed May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Fix High Priority High priority issue to be addressed asap Triage Issue was triaged and acknowledged
Projects
None yet
Development

No branches or pull requests

4 participants