Bug 1379777
| Summary: | docker-novolume-plugin does not start when docker service restarted | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Chris Evich <cevich> |
| Component: | docker | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED NOTABUG | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | amurdaca, lsm5 |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-28 13:29:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Evich
2016-09-27 16:03:44 UTC
Shouldn't you just enable docker-novolume-plugin. It should not stop when the docker service stops. Enabling the service works fine, however the service does not start on boot, nor does it start when the docker service is started/restarted. Ok if the service does not start on boot then you have a bug. Is there a failure in the logs stating why it did not start? TBH, I didn't check, was focused on verifying the bug 1376953. I can manually start it w/o a problem: systemctl start docker-novolume-plugin. It's just the automatic start dependency from docker service that doesn't work. I'll make sure it's enabled, reboot, and check the logs.... Hrmmm, okay, after rebooting, it did come up this time. So maybe it was my goof. Double-checking to see if I can make it break the same as before... Okay, so it doesn't appear it starts w/o rebooting: # systemctl status docker-novolume-plugin ● docker-novolume-plugin.service - Docker No volumes authZ Plugin Loaded: loaded (/usr/lib/systemd/system/docker-novolume-plugin.service; enabled; vendor preset: disabled)...cut... # systemctl stop docker-novolume-plugin # systemctl stop docker-novolume-plugin.socket # systemctl disable docker-novolume-plugin # systemctl disable docker-novolume-plugin.socket # systemctl status docker-novolume-plugin ● docker-novolume-plugin.service - Docker No volumes authZ Plugin Loaded: loaded (/usr/lib/systemd/system/docker-novolume-plugin.service; disabled; vendor preset: disabled)...cut... # systemctl stop docker # vi /etc/sysconfig/docker (plugin is still listed in OPTIONS) # systemctl enable docker-novolume-plugin Created symlink from /etc/systemd/system/multi-user.target.wants/docker-novolume-plugin.service to /usr/lib/systemd/system/docker-novolume-plugin.service. # systemctl status docker-novolume-plugin ● docker-novolume-plugin.service - Docker No volumes authZ Plugin Loaded: loaded (/usr/lib/systemd/system/docker-novolume-plugin.service; enabled; vendor preset: disabled) Active: inactive (dead) since Tue 2016-09-27 15:17:09 EDT; 4min 5s ago ...cut... # systemctl start docker (waited a few seconds) # systemctl status docker-novolume-plugin ● docker-novolume-plugin.service - Docker No volumes authZ Plugin Loaded: loaded (/usr/lib/systemd/system/docker-novolume-plugin.service; enabled; vendor preset: disabled) Active: inactive (dead) since Tue 2016-09-27 15:17:09 EDT; 4min 19s ago ...cut... So it's def. not starting with just the docker service. But... # reboot Connection to 1.2.3.4 closed by remote host. # ssh 1.2.3.4... # systemctl status docker-novolume-plugin ● docker-novolume-plugin.service - Docker No volumes authZ Plugin Loaded: loaded (/usr/lib/systemd/system/docker-novolume-plugin.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-09-27 15:25:28 EDT; 39s ago So it's fine after rebooting. Maybe this is expected behavior then? Chris could you check if you experience similar behavior with rhel-push-plugin? I see this as not a bug. There is no relationship between docker and docker-novolume-plugin, IE We don't state that one needs to run for the other. Although I think there is or was a link that say docker-novolume-plugin needs to start before docker starts. To make this work you would need to do systemctl enable docker-novolume-plugin systemctl start docker-novolume-plugin systemctl enable docker systemctl start docker And you should be all set. (In reply to Lokesh Mandvekar from comment #8) > Chris could you check if you experience similar behavior with > rhel-push-plugin? I did not. The rhel-push-plugin was already up and running on first-boot. I didn't even need to enable it. (In reply to Daniel Walsh from comment #9) > I see this as not a bug. There is no relationship between docker and > docker-novolume-plugin, IE We don't state that one needs to run for the > other. Although I think there is or was a link that say > docker-novolume-plugin needs to start before docker starts. > > To make this work you would need to do > > systemctl enable docker-novolume-plugin > systemctl start docker-novolume-plugin > systemctl enable docker > systemctl start docker > > And you should be all set. Yep, this seems to be the case. The incorrect / missing text is here: https://github.com/projectatomic/docker-novolume-plugin#installing So, I guess we can call this a docs bug :D |