duplicated definition for Keystone_user[swift]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Medium
|
Unassigned |
Bug Description
Hello,
While doing a migration test (pike BM -> pike Containers), with ceph+rados, I encounter the following error:
"Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Duplicate declaration: Keystone_
Pretty clear to read - now the question is: why? :).
I include the following env files in my upgrade process:
ENVIRONMENTS=" \
-e ./openstack-
-e ./upgrade-pike.yaml
-e ./openstack-
-e ./openstack-
-e ./openstack-
-e ./openstack-
-e ./openstack-
-e ./${1}-
-e ./openstack-
-e ./openstack-
-e ./docker_
-e ./environment.yaml \
"
The upgrade-pike.yaml contains only a yum command, while the ${1}-specifics.yaml contains only network-related things, as I have two envs (lab and prod) using the same environment/
For the records: my goal is to move from a Pike Baremetal deploy to a Pike Containerized deploy, and I was told to start with common services before doing ceph (have to move from puppet-ceph to ceph-ansible, in containers).
Feel free to ask for more details, I'll check on my side in order to see if I can avoid such a duplicate definition.
Thank you for your concerne, time and inputs :).
Cheers,
C.
Apparently it's a value override issue:
I include docker at the end of my env listing, and there's a small conflict:
openstack- tripleo- heat-templates/ environments/ docker. yaml: OS::TripleO: :Services: :SwiftProxy: ../docker/ services/ swift-proxy. yaml tripleo- heat-templates/ environments/ docker. yaml: OS::TripleO: :Services: :SwiftStorage: ../docker/ services/ swift-storage. yaml tripleo- heat-templates/ environments/ docker. yaml: OS::TripleO: :Services: :SwiftRingBuild er: ../docker/ services/ swift-ringbuild er.yaml tripleo- heat-templates/ environments/ docker. yaml: OS::TripleO: :Services: :SwiftDispersio n: OS::Heat::None
openstack-
openstack-
openstack-
while, in ceph parts: tripleo- heat-templates/ environments/ ceph-radosgw. yaml: OS::TripleO: :Services: :SwiftProxy: OS::Heat::None tripleo- heat-templates/ environments/ ceph-radosgw. yaml: OS::TripleO: :Services: :SwiftStorage: OS::Heat::None tripleo- heat-templates/ environments/ ceph-radosgw. yaml: OS::TripleO: :Services: :SwiftRingBuild er: OS::Heat::None
openstack-
openstack-
openstack-
Guess I'd rather push ceph-rgw *after* docker? Any cons?