Tempest failing on max_meta_* fields when testing RGW
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Francesco Pantano |
Bug Description
After deploying an overcloud, Tempest is reporting 3 failed tests that are related to Swift, after some Swift tests have passed before these 3.
The failures suggest variable value errors, such as:
"/usr/lib/
max_count = self.constraint
KeyError: 'max_meta_count'
"/usr/lib/
max_length = self.constraint
KeyError: 'max_meta_
"/usr/lib/
max_length = self.constraint
KeyError: 'max_meta_
Changed in tripleo: | |
assignee: | nobody → Francesco Pantano (fmount) |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Undecided → Medium |
milestone: | none → xena-rc1 |
milestone: | xena-rc1 → yoga-1 |
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/817395 /opendev. org/openstack/ tripleo- heat-templates/ commit/ 632afe18c061061 fb1f69d8fe522bf dcc2724d4d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 632afe18c061061 fb1f69d8fe522bf dcc2724d4d
Author: Francesco Pantano <email address hidden>
Date: Wed Nov 10 13:21:55 2021 +0100
Add rgw max attributes constraints
When the swift /info endpoint is queried, Tempest fails checking the
following missing keys:
1. max_meta_count name_length value_length
2. max_meta_
3. max_meta_
Those keys are not present because the related rgw settings are missing,
and as per [1], nothing is generated if the rgw_max_* are not set.
This patch is a workaround, on the TripleO side, to provide the missing
keys to the cluster.
[1] https:/ /github. com/ceph/ ceph/blob/ master/ src/rgw/ rgw_rest_ swift.cc# L1883-L1900
Closes-Bug: #1950486 72490110105f6a4 ff94f90934d
Change-Id: I0b199e47cce9dc