Repository navigation
Commit 2bc2d55
committed
ceph: adapt the configuration past squid
The next lane moves to Tentacle, and two things in the testbed
configuration assume a Ceph release ceph-ansible can deploy.
The manager starts a ceph-ansible container whose tag on the latest
track follows ceph_version, so a Tentacle testbed asks for
ceph-ansible:tentacle, which does not exist: ceph-ansible has no branch
past squid. This lane is a nutshell lane, where python-osism selects the
Ceph backend and CEPH_STACK stays unset, so the cephadm switch on
CEPH_STACK does not reach it.
The Ceph configuration sets "rgw keystone api version". Tentacle removed
that option together with Keystone v2.0 support, and writing a removed
option is not ignored: ceph config set answers EINVAL and the cephadm
configuration play fails. Reef and squid still default it to 2, so it
cannot simply be dropped.
set-ceph-version.sh is where the Ceph release enters a latest testbed's
configuration, so decide both there: for any release other than
quincy, reef and squid, disable the ceph-ansible container and remove
the option from the Ceph environments. This matches cfg-cookiecutter,
which makes the same two decisions on the same release list. Running
the script again changes nothing further.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Roger Luethi <luethi@osism.tech>1 parent b6365d5 commit 2bc2d55
1 file changed
Lines changed: 19 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
0 commit comments