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

[bitnami/mongodb-sharded] systemLogVerbosity is ignored #31057

Open
Nickmman opened this issue Dec 16, 2024 · 1 comment
Open

[bitnami/mongodb-sharded] systemLogVerbosity is ignored #31057

Nickmman opened this issue Dec 16, 2024 · 1 comment
Assignees
Labels
tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@Nickmman
Copy link
Contributor

Name and Version

bitnami/mongodb-sharded 7.8.0

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Deploy with ArgoCD
  2. Add custom value to set verbosity
  3. Watch as setting is ignored

Are you using any custom parameters or values?

common:
  systemLogVerbosity: 3
systemLogVerbosity: 3

What is the expected behavior?

MONGODB_SYSTEM_LOG_VERBOSITY is set to 3

What do you see instead?

MONGODB_SYSTEM_LOG_VERBOSITY is set to 0

kubectl get application -n argocd mongodb-sharded -o yaml | grep -B1 systemLogVerbosity
        common:
          systemLogVerbosity: 3
        systemLogVerbosity: 3
--
              storageClass: ceph-block
          systemLogVerbosity: 3
--
          common:
            systemLogVerbosity: 3
--
          common:
            systemLogVerbosity: 3
          systemLogVerbosity: 3
--
            common:
              systemLogVerbosity: 3
            systemLogVerbosity: 3
--
            common:
              systemLogVerbosity: 3
            systemLogVerbosity: 3

From mongodb:

kubectl get all -o yaml | grep -A1 MONGODB_SYSTEM_LOG_VERBOSITY
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
      - name: MONGODB_SYSTEM_LOG_VERBOSITY
        value: "0"
--
          - name: MONGODB_SYSTEM_LOG_VERBOSITY
            value: "0"
--
          - name: MONGODB_SYSTEM_LOG_VERBOSITY
            value: "0"
--
          - name: MONGODB_SYSTEM_LOG_VERBOSITY
            value: "0"
--
          - name: MONGODB_SYSTEM_LOG_VERBOSITY
            value: "0"
--
          - name: MONGODB_SYSTEM_LOG_VERBOSITY
            value: "0"

Additional information

Var is handled via https://github.com/bitnami/charts/blob/mongodb-sharded/7.8.0/bitnami/mongodb/templates/replicaset/statefulset.yaml#L288-L289

@Nickmman Nickmman added the tech-issues The user has a technical issue about an application label Dec 16, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 16, 2024
@carrodher
Copy link
Member

The parameter is common.mongodbSystemLogVerbosity, see https://github.com/bitnami/charts/tree/mongodb-sharded/7.8.0/bitnami/mongodb-sharded#mongodb-sharded-parameters, it seems you're missing the mongodb prefix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants