mariadb can not start in pod with error: Operation not permitted

Bug #1748351 reported by LYJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-kubernetes
Invalid
Undecided
Unassigned

Bug Description

i'm deploying kolla in openshift with the version of kubernetes 1.6.
follow this tutorial : https://docs.openstack.org/kolla-kubernetes/latest/deployment-guide.html#
but i connot start the mariadb service when running "helm install --debug kolla-kubernetes/helm/service/mariadb --namespace kolla --name mariadb --values ./cloud.yaml"

# oc get pod
NAME READY STATUS RESTARTS AGE
mariadb-0 0/1 Init:0/1 0 17h
mariadb-init-element-8p4zd 0/1 CrashLoopBackOff 13 44m

#oc describe pod mariadb-init-element-8p4zd
Events:
  FirstSeen LastSeen Count From SubObjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  1h 1h 1 default-scheduler Normal Scheduled Successfully assigned mariadb-init-element-8p4zd to node2
  1h 1h 4 kubelet, node2 spec.containers{main} Normal Pulled Container image "docker.io/kolla/centos-source-mariadb:4.0.0" already present on machine
  1h 1h 4 kubelet, node2 spec.containers{main} Normal Created Created container
  1h 1h 4 kubelet, node2 spec.containers{main} Normal Started Started container
  1h 33m 184 kubelet, node2 spec.containers{main} Warning BackOff Back-off restarting failed container
  1h 3m 320 kubelet, node2 Warning FailedSync Error syncing pod

#oc logs mariadb-init-element-8p4zd
sudo: unable to change to sudoers gid: Operation not permitted

how can i run mariadb service?

LYJ (lyj498639133)
Changed in kolla-kubernetes:
status: New → Invalid
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.