Systemd commands for kubernetes resources have invalid exec commands
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
Medium
|
janonymous |
Bug Description
On using systemctl commands for kubernetes-* what we actually do is use command from ExecStart below:
---
cat /<email address hidden>
`
[Unit]
Description = Devstack <email address hidden>
[Service]
ExecStart = /usr/bin/docker logs -f kubernetes-api
User = vagrant
[Install]
WantedBy = multi-user.target
------
<Code>
https:/
On using run container at the time of installation it correctly follows the steps in run_container, however once the entries are placed in ExecStart above, commands to restart and stop would not actually starts/stops docker processes.
`
Devstack do not have parameter like ExecStartPre , which might support multiple commands but currently start/stop should work..
Changed in kuryr-kubernetes: | |
importance: | Undecided → Medium |
status: | New → Triaged |
assignee: | nobody → janonymous (janonymous) |
Reviewed: https:/ /review. openstack. org/484754 /git.openstack. org/cgit/ openstack/ kuryr-kubernete s/commit/ ?id=bf60bb44ef5 ae5ed4a0c628744 b6b9d3897568fe
Committed: https:/
Submitter: Jenkins
Branch: master
commit bf60bb44ef5ae5e d4a0c628744b6b9 d3897568fe
Author: Janonymous <email address hidden>
Date: Tue Jul 18 12:58:04 2017 +0000
Systemd usage of kubernetes startup
Change-Id: Id791189f94a02d 0cc60766f8cf20d 9cf854aeb93
Closes-bug: #1705028