Skip to content
This repository was archived by the owner on May 25, 2026. It is now read-only.

rev38

  • rev38
  • 618fe32

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
rev38: Check osm-zookeeper status in a special way (#149)
  • rev38
  • 618fe32

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    GPG key ID: 4AEE18F83AFDEB23
    Expired
    Verified
    Learn about vigilant mode
@taurus-forever taurus-forever tagged this 20 Feb 09:24 
* Check osm-zookeeper status in a special way

The osm-zookeeper unit is constantly switching his status
between `active` and `maintenance`:

>> juju show-status-log osm-zookeeper/0
> Time                        Type       Status       Message
> ...
> 16 Feb 2023 11:30:18+01:00  workload   active       ready
> 16 Feb 2023 11:30:22+01:00  workload   maintenance  Sending Zookeeper configuration
> 16 Feb 2023 11:30:22+01:00  workload   active       ready
> 16 Feb 2023 11:30:30+01:00  workload   maintenance  Sending Zookeeper configuration
> 16 Feb 2023 11:30:31+01:00  workload   active       ready
> 16 Feb 2023 11:30:39+01:00  workload   maintenance  Sending Zookeeper configuration
> 16 Feb 2023 11:30:39+01:00  workload   active       ready
> 16 Feb 2023 11:30:49+01:00  workload   maintenance  Sending Zookeeper configuration
> 16 Feb 2023 11:30:49+01:00  workload   active       ready

As a result GH CI test might be unlucky to wait until timeouts:
https://github.com/canonical/mysql-k8s-operator/actions/runs/4189712435/jobs/7262386481

> ...
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] maintenance: Sending Zookeeper configuration
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] active: ready
> INFO     juju.model:model.py:2530 Waiting for model:
>   osm-zookeeper/0 [idle] maintenance: Sending Zookeeper configuration
> ...

We cannot blindly wait for osm-zookeeper active status.
As a proposal, let's check the component status separately and
decreate idle_period from default 15 seconds to 1 second.

P.S. No need to re-check kafka/mongodb status after relation mysql-k8s and keystone.

* Improve the test as suggested in PR
Assets 2
Loading