临时解决kube-controller-manager 无法创建rbd image 问题

注:以下情况参考http://www.jianshu.com/p/8ce11f947410 基础上进行测试

环境

centos7.2
kubeadm 1.6.1

问题现象

[root@cloud4ourself-kube1 manifests]# kubectl get pvc
NAME           STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS     AGE
datadir-zk-0   Pending                                                                       slow             16h
gluster1       Bound     pvc-45c39fbe-2a57-11e7-bdbe-fa163e72ab1f   5Gi        RWO           gluster-heketi   18h

[root@cloud4ourself-kube1 manifests]# kubectl describe  pvc datadir-zk-0
Name:       datadir-zk-0
Namespace:  default
StorageClass:   slow
Status:     Pending
Volume:
Labels:     app=zk
Annotations:    volume.beta.kubernetes.io/storage-class=slow
        volume.beta.kubernetes.io/storage-provisioner=kubernetes.io/rbd
Capacity:
Access Modes:
Events:
  FirstSeen LastSeen    Count   From                SubObjectPath   Type        Reason          Message
  --------- --------    -----   ----                -------------   --------    ------          -------
  16h       36m     3850    persistentvolume-controller         Warning     ProvisioningFailed  Failed to provision volume with StorageClass "slow": failed to create rbd image: executable file not found in $PATH, command output:

问题原因

由于kube-controller-manager使用容器方式运行,gcr.io/google_containers/kube-controller-manager-amd64:v1.6.0而该容器不包含rbd,
因此kube-controller-manager在创建pv时,无法调用rbd,解决办法就是将kube-controller-manager运行在有rbd的环境中,
本次临时将kube-controller-manager从容器提取出来,在master节点服务器上用命令方式运行

复制kube-controller-manager

[root@cloud4ourself-kube1 kubernetes]# kubectl exec -it kube-controller-manager-cloud4ourself-kube1.novalocal -n kube-system --
/ #
/ #
/ #
/ # cd /usr/local/bin/
/usr/local/bin # ls
kube-controller-manager
/usr/local/bin # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/docker-253:1-201327648-973d5c7c4aa6e982d0b5eef5e301dd7261b7470d8de8a508f85942441c39237c
                      10474496    163204  10311292   2% /
tmpfs                  1941100         0   1941100   0% /dev
tmpfs                  1941100         0   1941100   0% /sys/fs/cgroup
/dev/vda1             41930056   4704356  37225700  11% /etc/pki
/dev/vda1             41930056   4704356  37225700  11% /dev/termination-log
/dev/vda1             41930056   4704356  37225700  11% /etc/kubernetes
/dev/vda1             41930056   4704356  37225700  11% /etc/resolv.conf
/dev/vda1             41930056   4704356  37225700  11% /etc/hostname
/dev/vda1             41930056   4704356  37225700  11% /etc/hosts
shm                      65536         0     65536   0% /dev/shm
/dev/vda1             41930056   4704356  37225700  11% /etc/ssl/certs
tmpfs                  1941100         0   1941100   0% /proc/kcore
tmpfs                  1941100         0   1941100   0% /proc/timer_list
tmpfs                  1941100         0   1941100   0% /proc/timer_stats
tmpfs                  1941100         0   1941100   0% /proc/sched_debug
/usr/local/bin # cp kube-controller-manager /etc/kubernetes/
cp: can't create '/etc/kubernetes/kube-controller-manager': Read-only file system
/usr/local/bin # cp kube-controller-manager /etc/pki/
/usr/local/bin # cd /etc/pki/
/etc/pki # ls
CA                       java                     nssdb                    rsyslog
ca-trust                 kube-controller-manager  rpm-gpg                  tls
/etc/pki # ps
PID   USER     TIME   COMMAND
    1 root       0:02 kube-controller-manager --controllers=*,bootstrapsigner,tokencleaner --kubeconfig=/etc/kubernetes/controller-manager.conf --service-account-private-key-file=/etc/kubernetes/pki/sa.key --a
   13 root       0:00 sh
   23 root       0:00 ps


/etc/pki # cat /proc/1/cmdline
kube-controller-manager--controllers=*,bootstrapsigner,tokencleaner--kubeconfig=/etc/kubernetes/controller-manager.conf--service-account-private-key-file=/etc/kubernetes/pki/sa.key--address=127.0.0.1--leader-elect=true--insecure-experimental-approve-all-kubelet-csrs-for-group=system:bootstrappers--cluster-signing-key-file=/etc/kubernetes/pki/ca.key--use-service-account-credentials=true--root-ca-file=/etc/kubernetes/pki/ca.crt--cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt/etc/pki #

移动kube-controller-manager.yaml

cd /etc/kubernetes
[root@cloud4ourself-kube1 kubernetes]# kubectl get pod -n kube-system
NAME                                                    READY     STATUS    RESTARTS   AGE
calico-etcd-vbc6x                                       1/1       Running   1          1d
calico-node-0hbw2                                       2/2       Running   0          1d
calico-node-7x2jv                                       2/2       Running   4          1d
calico-node-cr8dc                                       2/2       Running   1          1d
calico-node-z928t                                       2/2       Running   2          1d
calico-policy-controller-2561685917-13j12               1/1       Running   1          1d
etcd-cloud4ourself-kube1.novalocal                      1/1       Running   1          1d
kube-apiserver-cloud4ourself-kube1.novalocal            1/1       Running   1          1d
kube-controller-manager-cloud4ourself-kube1.novalocal   1/1       Running   0          51m
kube-dns-3913472980-zfpkg                               3/3       Running   622        1d
kube-proxy-4h57v                                        1/1       Running   1          1d
kube-proxy-r5wqj                                        1/1       Running   0          1d
kube-proxy-r8b5p                                        1/1       Running   1          1d
kube-proxy-wfmrd                                        1/1       Running   0          1d
kube-scheduler-cloud4ourself-kube1.novalocal            1/1       Running   1          1d
[root@cloud4ourself-kube1 kubernetes]# mv manifests/kube-controller-manager.yaml .
[root@cloud4ourself-kube1 kubernetes]# kubectl get pod -n kube-system
NAME                                           READY     STATUS    RESTARTS   AGE
calico-etcd-vbc6x                              1/1       Running   1          1d
calico-node-0hbw2                              2/2       Running   0          1d
calico-node-7x2jv                              2/2       Running   4          1d
calico-node-cr8dc                              2/2       Running   1          1d
calico-node-z928t                              2/2       Running   2          1d
calico-policy-controller-2561685917-13j12      1/1       Running   1          1d
etcd-cloud4ourself-kube1.novalocal             1/1       Running   1          1d
kube-apiserver-cloud4ourself-kube1.novalocal   1/1       Running   1          1d
kube-dns-3913472980-zfpkg                      3/3       Running   622        1d
kube-proxy-4h57v                               1/1       Running   1          1d
kube-proxy-r5wqj                               1/1       Running   0          1d
kube-proxy-r8b5p                               1/1       Running   1          1d
kube-proxy-wfmrd                               1/1       Running   0          1d
kube-scheduler-cloud4ourself-kube1.novalocal   1/1       Running   1          1d

在服务器里启动(非容器方式)

/etc/pki/kube-controller-manager --controllers=*,bootstrapsigner,tokencleaner --kubeconfig=/etc/kubernetes/controller-manager.conf --service-account-private-key-file=/etc/kubernetes/pki/sa.key --address=127.0.0.1 --leader-elect=true --insecure-experimental-approve-all-kubelet-csrs-for-group=system:bootstrappers --cluster-signing-key-file=/etc/kubernetes/pki/ca.key --use-service-account-credentials=true --root-ca-file=/etc/kubernetes/pki/ca.crt --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt/etc/pki/ca.crt

在此确认pvc

[root@cloud4ourself-kube1 manifests]# kubectl get pvc
NAME           STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS     AGE
datadir-zk-0   Bound     pvc-7f1a0c7e-2a67-11e7-bdbe-fa163e72ab1f   1Gi        RWO           slow             17h
gluster1       Bound     pvc-45c39fbe-2a57-11e7-bdbe-fa163e72ab1f   5Gi        RWO           gluster-heketi   19h
[root@cloud4ourself-kube1 manifests]# kubectl get pv
NAME                                       CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS    CLAIM                  STORAGECLASS     REASON    AGE
pvc-45c39fbe-2a57-11e7-bdbe-fa163e72ab1f   5Gi        RWO           Delete          Bound     default/gluster1       gluster-heketi             19h
pvc-7f1a0c7e-2a67-11e7-bdbe-fa163e72ab1f   1Gi        RWO           Delete          Bound     default/datadir-zk-0   slow                       16s

待pv全部创建完毕

[root@cloud4ourself-kube1 pki]# kubectl get pod
NAME                      READY     STATUS    RESTARTS   AGE
glusterfs-66gn0           1/1       Running   1          20h
glusterfs-srhh8           1/1       Running   0          20h
glusterfs-z55q5           1/1       Running   0          20h
heketi-1125625054-pl9qc   1/1       Running   0          20h
zk-0                      1/1       Running   0          17h
zk-1                      1/1       Running   0          9m
zk-2                      1/1       Running   0          7m
[root@cloud4ourself-kube1 pki]# kubectl get pvc
NAME           STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS     AGE
datadir-zk-0   Bound     pvc-7f1a0c7e-2a67-11e7-bdbe-fa163e72ab1f   1Gi        RWO           slow             17h
datadir-zk-1   Bound     pvc-c58c0a6e-2afc-11e7-bdbe-fa163e72ab1f   1Gi        RWO           slow             9m
datadir-zk-2   Bound     pvc-19b76842-2afd-11e7-bdbe-fa163e72ab1f   1Gi        RWO           slow             7m
gluster1       Bound     pvc-45c39fbe-2a57-11e7-bdbe-fa163e72ab1f   5Gi        RWO           gluster-heketi   19h
[root@cloud4ourself-kube1 pki]# kubectl get pv
NAME                                       CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS    CLAIM                  STORAGECLASS    REASON    AGE
pvc-19b76842-2afd-11e7-bdbe-fa163e72ab1f   1Gi        RWO           Delete          Bound     default/datadir-zk-2   slow              7m
pvc-45c39fbe-2a57-11e7-bdbe-fa163e72ab1f   5Gi        RWO           Delete          Bound     default/gluster1       gluster-heketi             19h
pvc-7f1a0c7e-2a67-11e7-bdbe-fa163e72ab1f   1Gi        RWO           Delete          Bound     default/datadir-zk-0   slow              12m
pvc-c58c0a6e-2afc-11e7-bdbe-fa163e72ab1f   1Gi        RWO           Delete          Bound     default/datadir-zk-1   slow              9m

重新恢复容器方式

# 停止kube-controller-manager
# 移动配置文件
[root@cloud4ourself-kube1 kubernetes]# mv kube-controller-manager.yaml manifests/
[root@cloud4ourself-kube1 kubernetes]# kubectl get pod -n kube-system
NAME                                                    READY     STATUS    RESTARTS   AGE
calico-etcd-vbc6x                                       1/1       Running   1          1d
calico-node-0hbw2                                       2/2       Running   0          1d
calico-node-7x2jv                                       2/2       Running   4          1d
calico-node-cr8dc                                       2/2       Running   1          1d
calico-node-z928t                                       2/2       Running   2          1d
calico-policy-controller-2561685917-13j12               1/1       Running   1          1d
etcd-cloud4ourself-kube1.novalocal                      1/1       Running   1          1d
kube-apiserver-cloud4ourself-kube1.novalocal            1/1       Running   1          1d
kube-controller-manager-cloud4ourself-kube1.novalocal   1/1       Running   0          7s
kube-dns-3913472980-zfpkg                               3/3       Running   622        1d
kube-proxy-4h57v                                        1/1       Running   1          1d
kube-proxy-r5wqj                                        1/1       Running   0          1d
kube-proxy-r8b5p                                        1/1       Running   1          1d
kube-proxy-wfmrd                                        1/1       Running   0          1d
kube-scheduler-cloud4ourself-kube1.novalocal            1/1       Running   1          1d
最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 204,445评论 6 478
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 85,889评论 2 381
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 151,047评论 0 337
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 54,760评论 1 276
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 63,745评论 5 367
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 48,638评论 1 281
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 38,011评论 3 398
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 36,669评论 0 258
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 40,923评论 1 299
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 35,655评论 2 321
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 37,740评论 1 330
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 33,406评论 4 320
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 38,995评论 3 307
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 29,961评论 0 19
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 31,197评论 1 260
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 45,023评论 2 350
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 42,483评论 2 342

推荐阅读更多精彩内容