kollakube res create configmap: maximum recursion depth exceeded

Bug #1735286 reported by Alvaro Aleman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-kubernetes
New
Undecided
Unassigned

Bug Description

When trying to install kolla-kubernetes as described in the guide at [0] version "UPDATED: 2017-11-20 17:38", the command

kollakube res create configmap \
    mariadb keystone horizon rabbitmq memcached nova-api nova-conductor \
    nova-scheduler glance-api-haproxy glance-registry-haproxy glance-api \
    glance-registry neutron-server neutron-dhcp-agent neutron-l3-agent \
    neutron-metadata-agent neutron-openvswitch-agent openvswitch-db-server \
    openvswitch-vswitchd nova-libvirt nova-compute nova-consoleauth \
    nova-novncproxy nova-novncproxy-haproxy neutron-server-haproxy \
    nova-api-haproxy cinder-api cinder-api-haproxy cinder-backup \
    cinder-scheduler cinder-volume iscsid tgtd keepalived \
    placement-api placement-api-haproxy

exits with rc1 but without an error message. When adding '--print-jinja-vars' to the command the error 'maximum recursion depth exceeded' gets printed.

Attached is a repro for centos 7.4.

[0]https://docs.openstack.org/kolla-kubernetes/latest/deployment-guide.html

Revision history for this message
Alvaro Aleman (alvaroaleman) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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