Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Setting password with a special character for system user breaks the cluster

Description

Version 1.9.0

Using default cr.yaml

Steps to reproduce:

1. Apply the following secret with users:

$ cat deploy/secrets.yaml apiVersion: v1 kind: Secret metadata: name: my-cluster-name-secrets type: Opaque stringData: MONGODB_BACKUP_USER: backup MONGODB_BACKUP_PASSWORD: backup123456! MONGODB_CLUSTER_ADMIN_USER: clusterAdmin MONGODB_CLUSTER_ADMIN_PASSWORD: clusterAdmin123456#! MONGODB_CLUSTER_MONITOR_USER: clusterMonitor MONGODB_CLUSTER_MONITOR_PASSWORD: clusterMonitor123!456 MONGODB_USER_ADMIN_USER: userAdmin MONGODB_USER_ADMIN_PASSWORD: userAdmin123!456 PMM_SERVER_USER: admin PMM_SERVER_PASSWORD: admin

2. apply cr.yaml

 

Result: 

Log is full of 

{"level":"error","ts":1628067113.4603548,"logger":"controller_psmdb","msg":"failed to reconcile cluster","Request.Namespace":"default","Request.Name":"my-cluster-name","replset":"rs0","error":"dial:: failed to ping mongo: connection() : auth error: sasl conversation error: unable to authenticate using mechanism \"SCRAM-SHA-256\": (AuthenticationFailed) Authentication failed.","errorVerbose":"failed to ping mongo: connection() : auth error: sasl conversation error: unable to authenticate using mechanism \"SCRAM-SHA-256\": (AuthenticationFailed) Authentication failed.

Also I cannot connect to MongoDB using any user with a password with a special character.

 

We were fixing liveness probe issue here: https://jira.percona.com/browse/K8SPSMDB-364

But seems it is still an issue in other places.

Environment

None

Smart Checklist

Activity

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Smart Checklist

Created August 4, 2021 at 8:58 AM
Updated October 2, 2024 at 6:19 PM
Resolved April 14, 2022 at 9:05 PM

Flag notifications