kolla

CONFIG_STRATEGY should read KOLLA_CONFIG_STRATEGY

Bug #1471326 reported by Harm Weites
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Critical
Harm Weites
kolla liberty-2 "liberty-2"

Bug Description

CONFIG_STRATEGY is seen both with and without a KOLLA_ prefix. The former is prefered.

Revision history for this message
Harm Weites (harmw) wrote :

pbourke noticed the following:

$ grep -r CONFIG_STRATEGY . | grep -v spec
./tools/genenv:CONFIG_STRATEGY=CONFIG_INTERNAL
./docker/common/base/kolla-common.sh: case $KOLLA_CONFIG_STRATEGY in
./docker/common/base/kolla-common.sh: echo '$CONFIG_STRATEGY is not set properly'
./ansible/roles/keystone/tasks/start.yml: CONFIG_STRATEGY: "{{ config_strategy }}"
./ansible/roles/keystone/tasks/bootstrap.yml: CONFIG_STRATEGY: "{{ config_strategy }}"

Sam Yaple (s8m)
Changed in kolla:
importance: Undecided → Critical
status: New → Triaged
Steven Dake (sdake)
Changed in kolla:
assignee: nobody → Harm Weites (harmw)
milestone: none → liberty-2
status: Triaged → Confirmed
Sam Yaple (s8m)
Changed in kolla:
status: Confirmed → Fix Committed
Sam Yaple (s8m)
Changed in kolla:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.