kolla-toolbox container failed and stick on create stage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Critical
|
Sam Yaple |
Bug Description
[root@localhost kolla]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eebe54757c12 hub.xcodest.
21eb292ed9e7 hub.xcodest.
[root@localhost kolla]# docker logs rsyslog
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__
INFO:__
INFO:__
INFO:__
INFO:__
INFO:__
INFO:__
Running command: '/usr/sbin/rsyslogd -n'
rsyslogd: cannot create '/run/kolla/log': Address already in use
[root@localhost kolla]# docker logs kolla_toolbox
Timestamp: 2016-02-11 07:31:16.11548407 -0500 EST
Code: System error
Message: not a directory
Frames:
---
0: setupRootfs
Package: github.
File: rootfs_linux.go@40
---
1: Init
Package: github.
File: standard_
---
2: StartInitialization
Package: github.
File: factory_
---
3: initializer
Package: github.
File: init.go@35
---
4: Init
Package: github.
File: reexec.go@26
---
5: main
Package: main
File: docker.go@18
---
6: main
Package: runtime
File: proc.go@111
---
7: goexit
Package: runtime
File: asm_amd64.s@1721
I am using SSD + brfs filesystem. So I suppose the root cause is that after the rsyslog container start but before the rsyslog service finished initialization( i.e. /run/kolla/log is not created ), the kolla_toolbox started and create the /run/kolla/log as folder.
The solution is: wait for a moment and ensure the /run/kolla/log is created before starting the kolla_toolbox container.
Changed in kolla: | |
assignee: | nobody → Jeffrey Zhang (jeffrey4l) |
Changed in kolla: | |
assignee: | Jeffrey Zhang (jeffrey4l) → Sam Yaple (s8m) |
importance: | Undecided → Critical |
Changed in kolla: | |
milestone: | none → mitaka-3 |
Fix proposed to branch: master /review. openstack. org/279064
Review: https:/