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

Charm in blocked status with `Missing parameters: []` message #30

Open mthaddon opened 4 months ago

mthaddon commented 4 months ago

Steps to reproduce

I'm not sure how to reproduce this, or how it's even possible from looking at the code.

Expected behavior

Charm isn't in blocked status if you set access-key and secret-key or is if you don't.

Actual behavior

Charm is in blocked status even though access-key and secret-key are set.

Versions

Operating system: 22.04

Juju CLI: 2.9.44

Juju agent: 2.9.44

Charm revision: 13 (latest/stable)

Log output

Juju debug log: 

2024-03-01 15:43:26 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:49:08 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:49:08 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:49:09 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:54:21 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:54:21 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:54:22 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:59:27 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:59:27 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:59:27 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:02:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:02:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event sync_s3_credentials_action.
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'access-key': 'REDACTED'}
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'secret-key': 'REDACTED'}
2024-03-01 16:04:14 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:04:14 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:04:14 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:08:28 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:08:28 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:08:28 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:13:26 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:13:26 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:13:27 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:18:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:18:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:18:31 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:22:48 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:22:48 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
github-actions[bot] commented 4 months ago

https://warthogs.atlassian.net/browse/DPE-3697

mthaddon commented 4 months ago

Worth mentioning that this application was deployed a while ago, possibly before https://github.com/canonical/s3-integrator/issues/8 was solved, so it's possible it got into this state, but now can't get out of it unless a peer-relation-changed or start event fires.

taurus-forever commented 2 weeks ago

@delgod I think you have addressed this already in https://github.com/canonical/s3-integrator/commit/16d8b7eedd1b13310551523f89166facf8c66ebb

Resolved?