search

canonical / s3-integrator

An integrator charm for handling s3 credentials
https://charmhub.io/s3-integrator
Apache License 2.0
1 stars 1 forks source link

Unit moves into blocked state some time after deployment with no missing parameters #8

Closed shayancanonical closed 1 year ago

shayancanonical commented 1 year ago

Issue

Some time after the deployment and configuration of S3 integrator, the unit goes into blocked status with no missing parameters.

Output of juju status --storage -- relations:

Model  Controller   Cloud/Region        Version  SLA          Timestamp
dev    uk8s-2-9-38  microk8s/localhost  2.9.38   unsupported  17:21:19-05:00

App            Version                  Status   Scale  Charm          Channel  Rev  Address         Exposed  Message
mysql-k8s      8.0.31-0ubuntu0.22.04.1  active       2  mysql-k8s                 0  10.152.183.223  no       
s3-integrator                           waiting      1  s3-integrator             0  10.152.183.31   no       installing agent

Unit              Workload  Agent  Address      Ports  Message
mysql-k8s/0       active    idle   10.1.94.252         Unit is ready: Mode: RO
mysql-k8s/1*      active    idle   10.1.94.249         Unit is ready: Mode: RW
s3-integrator/0*  blocked   idle   10.1.94.251         Missing parameters: []

Relation provider                  Requirer                           Interface            Type     Message
mysql-k8s:database-backups         mysql-k8s:database-backups         database-backups     peer     
mysql-k8s:database-peers           mysql-k8s:database-peers           mysql-peers          peer     
mysql-k8s:restart                  mysql-k8s:restart                  rolling_op           peer     
s3-integrator:s3-credentials       mysql-k8s:s3-credentials           s3-credentials       regular  
s3-integrator:s3-integrator-peers  s3-integrator:s3-integrator-peers  s3-integrator-peers  peer     

Storage Unit  Storage ID  Type        Pool        Mountpoint                        Size    Status    Message
mysql-k8s/0   database/0  filesystem  kubernetes  /var/lib/juju/storage/database/0  1.0GiB  attached  Successfully provisioned volume pvc-4a66fca2-c476-48ce-88a8-7a97335b868a
mysql-k8s/1   database/1  filesystem  kubernetes  /var/lib/juju/storage/database/0  1.0GiB  attached  Successfully provisioned volume pvc-8b9b1d1d-e0ad-46db-87ce-99bf5f278230

Upon closer inspection, the message appears when a pod is killed and restarted by k8s.

Environment

juju version = 2.9.38-ubuntu-amd64 microk8s version = MicroK8s v1.26.0 revision 4390 juju agent version for k8s 2.9.38