Images and flavours are hard-coded in tempest.conf
Bug #1838174 reported by
James Hebden
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-openstack-service-checks |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
Per usual tempest usage, the IDs of the Both images and flavours used in testing are configured in the temptest.conf. For fcbtest, this lives inside the snap filesystem.
This becomes problematic when cloud admins who are not familiar with these images and flavours delete or change them, resulting the ID changing.
Ideally these images and flavours should be protected, private and created and removed during testing. As a quicker fix however, the IDs should be exposed as Juju configuration items so they can easily be changed to new IDs, which will also improve awareness of the fact that these IDs are hard-coded.
Related branches
~aluria/charm-openstack-service-checks/+git/charm-openstack-service-checks:bug/1835433-part2
- Peter Sabaini (community): Approve
- BootStack Reviewers: Pending requested
-
Diff: 1781 lines (+1184/-267)14 files modifiedactions.yaml (+2/-0)
actions/create-flavor-rally (+15/-0)
config.yaml (+20/-7)
files/plugins/check_rally.py (+53/-79)
files/run_rally.py (+74/-39)
layer.yaml (+0/-7)
lib/lib_openstack_service_checks.py (+217/-100)
reactive/openstack_service_checks.py (+24/-25)
requirements.txt (+1/-0)
templates/extra_config.conf.j2 (+12/-0)
templates/rally.conf.j2 (+756/-0)
tests/unit/conftest.py (+3/-6)
tests/unit/test_lib.py (+6/-4)
wheelhouse.txt (+1/-0)
| Changed in charm-openstack-service-checks: | |
| status: | New → In Progress |
| assignee: | nobody → Alvaro Uria (aluria) |
Revision history for this message
| Alvaro Uria (aluria) wrote | #1 |
| Changed in charm-openstack-service-checks: | |
| importance: | High → Wishlist |
| status: | In Progress → Confirmed |
| assignee: | Alvaro Uria (aluria) → nobody |
Revision history for this message
| Eric Chen (eric-chen) wrote | #2 |
| Changed in charm-openstack-service-checks: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Tempest/Rally support in charm-openstack
The bug is confirmed, but I have lowered the priority as "check-rally" can't be enabled most of the time (when OpenStack API endpoints run over TLS and a custom CA is used).
1. https:/