Rally check does not support juju-<proto>-proxy settings
Bug #1841092 reported by
Paul Goins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-openstack-service-checks |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
At present, if proxy settings need to be defined for the rally check, they must be passed via the legacy <proto>-proxy settings. The charm doesn't do anything to convert the JUJU_CHARM_
Based on memory, I think this is most relevant at time of doing rally initialization.
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)
~aluria/charm-openstack-service-checks/+git/charm-openstack-service-checks:bug/1841092
Merged
into
~canonical-bootstack/charm-openstack-service-checks:master
at
revision 18499343cbc194f31b7f795e50bee7e00b99247e
- Legacy - Canonical WTFB: Pending requested
-
Diff: 68 lines (+11/-11)3 files modifiedfiles/plugins/check_rally.py (+1/-2)
files/run_rally.py (+1/-7)
lib/lib_openstack_service_checks.py (+9/-2)
| Changed in charm-openstack-service-checks: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Alvaro Uria (aluria) |
| status: | Confirmed → In Progress |
Revision history for this message
| Alvaro Uria (aluria) wrote | #1 |
| Changed in charm-openstack-service-checks: | |
| status: | In Progress → Triaged |
| assignee: | Alvaro Uria (aluria) → nobody |
To post a comment you must log in.
Change was approved but a bug in snaps does not allow TLS certificate verification by bsrally snap. That has to be fixed or a python-virtualenv alternative needs to be used to run rally.