chore: Stabilize Valkey and Mongodb tests

[skourta]

Valkey

The test deployed valkey from 9/edge without a base. The channel holds one revision per base: rev 88 for ubuntu@24.04 and rev 99 for ubuntu@26.04. Juju 3.6 uses its default base when none is given, so the test got rev 88, an old 24.04 build. The Valkey charm has moved to ubuntu@26.04.

The test now passes --base=ubuntu@26.04 and gets rev 99. It deploys Valkey with ops_test.juju("deploy", ...) because python-libjuju cannot do this:

• model.deploy(..., base="ubuntu@26.04") resolves the revision before it applies the base. It picks rev 88 and fails with base "ubuntu@26.04/stable" is not supported, supported bases are: ubuntu@24.04.
• Pinning revision=99 fails with Unknown series: resolute, because libjuju's series table stops at 24.04.
• 3.6.1.3 is the latest libjuju release, so an upgrade does not help.

I checked each case against a local Juju 3.6.28 controller, the same version CI uses.

A valkey bug is being fixed where storage-attached crashes when the workload container's Pebble socket does not exist yet. The fix is in canonical/valkey-operator.

MongoDB

mongodb-k8s reports active before its mongod container is up. The test waited for that status, related data-integrator, and asserted active after a 15s idle window. MongoDB skips client requests until it initialises the database, so data-integrator stayed blocked on "Please relate the data-integrator with the desired product".

This test used to pass because workload containers started faster in CI. In the last green run, pebble-ready fired about 20s after the unit started. In the failing runs it took about 60s, and in the MongoDB job it never fired before the assert.

MongoDB creates users for existing relations once it initialises the database. The test now waits up to 1000s for both apps to reach active, the same way test_valkey.py waits.

Changes

• tests/integration/constants.py: add VALKEY_BASE = "ubuntu@26.04".
• tests/integration/test_valkey.py: deploy Valkey through the Juju CLI with --base.
• tests/integration/test_mongodb.py: after relating, wait for status="active" in place of the immediate assert.

[imanenami]

Thanks Smail 🙂