Juju client periodically loses proxy config for k8s controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Hi,
I have noticed an oddity on a juju client. This client is running on a Bastion host and is connected to 2 controllers, one is a machine controller and another is a k8s controller. Connecting and using both controllers was working fine until a few weeks ago when connecting to the k8s controller stopped working and it was found that within the controllers.yaml file, the proxy-config section (for the k8s controller) had gone missing. I had chalked this up to someone manually editing the file and fortunately we had a backup of the original file (specifically because we were trying to register users to k8s controller unsuccessfully due to this bug - https:/
Original Controllers.yaml file (only the section for the k8s controller):
controllers:
comsys-
uuid: d381ade1-
dns-cache: {localhost: [127.0.0.1]}
ca-cert: |
cloud: ps5-staging
type: kubernetes
config:
type: kubernetes-
current-controller: comsys-ps5-staging
Logs from today to illustrate the problem:
stg-canonical-
Mon Dec 5 08:39:54 UTC 2022
stg-canonical-
controllers:
comsys-
uuid: d381ade1-
api-endpoints: ['<Removed>']
dns-cache: {localhost: [127.0.0.1]}
ca-cert: |
<Removed>
cloud: ps5-staging
type: kubernetes
agent-version: 2.9.34
controller-
active-
machine-count: 0
prodstack-
uuid: ccf3a6e2-
api-endpoints: ['<Removed>']
ca-cert: |
<Removed>
cloud: ""
agent-version: 2.9.32
controller-
active-
current-controller: prodstack-is-beta
stg-canonical-
2.9.37-ubuntu-amd64
In Summary:
- The proxy-config option in controllers.yaml is periodically being deleted.
- I initially thought the deletion was due to a user editing the file, but it has occurred twice now.
- Unfortunately I'm not sure how to replicate this but I'll keep a close eye on it and try to see if I can trigger the behavior.
- And as a final aside, this could still be user error, perhaps there's a command or some flag that is causing this proxy-config to be removed?
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |