| 2017-12-16 05:49:47 |
Yushiro FURUKAWA |
description |
I ran following command with k8s v1.9 environment. Then, it occurred an error:
[commands]
kollakube --debug 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
helm install --debug kolla-kubernetes/helm/service/mariadb --namespace kolla --name mariadb --values ./cloud.yaml
[Error in journalctl]
12-16 14:43:15 kolla kubelet[6277]: E1216 14:43:15.258421 6277 configmap.go:202] Couldn't get configMap kolla/mariadb-logging: configmaps "mariadb-logging" not found
[Check configmap]
$ kubectl get configmap -n kolla
NAME DATA AGE
cinder-api 2 1h
cinder-api-haproxy 2 1h
cinder-backup 2 1h
cinder-scheduler 2 1h
cinder-volume 2 1h
glance-api 2 1h
glance-api-haproxy 2 1h
...(snip)...
mariadb 2 1h
...(snip)...
So, I think it is necessary to develop for handling k8s v1.9 configmap. |
I ran following command with k8s v1.9 environment. Then, it occurred an error:
[commands]
kollakube --debug 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
helm install --debug kolla-kubernetes/helm/service/mariadb --namespace kolla --name mariadb --values ./cloud.yaml
[Error in journalctl]
12-16 14:43:15 kolla kubelet[6277]: E1216 14:43:15.258421 6277 configmap.go:202] Couldn't get configMap kolla/mariadb-logging: configmaps "mariadb-logging" not found
[Check configmap]
$ kubectl get configmap -n kolla
NAME DATA AGE
cinder-api 2 1h
cinder-api-haproxy 2 1h
cinder-backup 2 1h
cinder-scheduler 2 1h
cinder-volume 2 1h
glance-api 2 1h
glance-api-haproxy 2 1h
...(snip)...
mariadb 2 1h
...(snip)...
$ kollakube map | grep mariadb
service[mariadb]
ResourceTemplate name[mariadb] template[auto] vars[]
ResourceTemplate name[mariadb-logging] template[services/common/logging-configmap.yml.j2] vars[{u'log_format': u'mariadb', u'configmap_name': u'mariadb-logging'}]
Am I missing something? kollakube has already generated 'mariadb-logging' as ResourceTemplate. |
|
