Charm fails hook "update-status" due to bad gateway

Bug #2003799 reported by Bas de Bruijne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charm AWS Kubernetes Storage
New
Undecided
Unassigned

Bug Description

In testrun https://solutions.qa.canonical.com/v2/testruns/c4d7b9a6-aa8d-4581-af0c-12687e55d884, aws-k8s-storage fails to install. In the logs we see:

```
unit-aws-k8s-storage-0: 09:43:37 DEBUG unit.aws-k8s-storage/0.juju-log HTTP Request: GET https://54.82.142.89/api/v1/namespaces/kube-system/secrets/aws-secret "HTTP/1.1 502 Bad Gateway"
unit-aws-k8s-storage-0: 09:43:37 ERROR unit.aws-k8s-storage/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "./src/charm.py", line 183, in <module>
    main(AwsK8sStorageCharm)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/main.py", line 438, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/main.py", line 150, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/framework.py", line 355, in emit
    framework._emit(event) # noqa
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/framework.py", line 856, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/framework.py", line 931, in _reemit
    custom_handler(event)
  File "./src/charm.py", line 87, in _update_status
    unready = self.collector.unready
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/manifests/collector.py", line 90, in unready
    return sorted(
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/manifests/collector.py", line 93, in <genexpr>
    for obj in manifest.status()
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/manifests/manifest.py", line 192, in status
    return frozenset(_ for _ in self.installed_resources() if _.status_conditions)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/ops/manifests/manifest.py", line 199, in installed_resources
    next_rsc = self.client.get(
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/lightkube/core/client.py", line 108, in get
    return self._client.request("get", res=res, name=name, namespace=namespace)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/lightkube/core/generic_client.py", line 245, in request
    return self.handle_response(method, resp, br)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/lightkube/core/generic_client.py", line 196, in handle_response
    self.raise_for_status(resp)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/lightkube/core/generic_client.py", line 190, in raise_for_status
    raise transform_exception(e)
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/lightkube/core/generic_client.py", line 188, in raise_for_status
    resp.raise_for_status()
  File "/var/lib/juju/agents/unit-aws-k8s-storage-0/charm/venv/httpx/_models.py", line 745, in raise_for_status
    raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Server error '502 Bad Gateway' for url 'https://54.82.142.89/api/v1/namespaces/kube-system/secrets/aws-secret'
For more information check: https://httpstatuses.com/502
```

There are a bunch of other requests to that IP that do succeed, maybe the URL has changed?

Crashdumps and log can be found here:
https://oil-jenkins.canonical.com/artifacts/c4d7b9a6-aa8d-4581-af0c-12687e55d884/index.html

Revision history for this message
Bas de Bruijne (basdbruijne) wrote :

Test run https://solutions.qa.canonical.com/v2/testruns/474d3998-ce76-435b-bcc2-6e4758cb6ade shows the same symptoms during the update-status hook after it has been installed successfully.

Revision history for this message
Adam Dyess (addyess) wrote :

This is a duplicate of LP#1999427 which has been resolved in the 1.26/stable channel of the charm.

Let's update this bug to indicate that the latest/stable channels haven't been updated since the 1.26+ck1 release

Revision history for this message
Adam Dyess (addyess) wrote :

Just as an update -- during the 1.26+ck1 release we missed promoting 1.26/stable charms to latest/stable charms. This has been resolved

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.