Hide Forgot
Description of problem: While verifying bug 1376953, step 1 "enable docker-novolume-plugin", following the steps listed at https://github.com/projectatomic/docker-novolume-plugin#installing the plugin process did not start automatically when restarting, or stop + start, of docker service. Version-Release number of selected component (if applicable): rhel-atomic-host/7/x86_64/standard Version: 7.3 (2016-09-26 16:13:07) docker-novolume-plugin-1.10.3-55.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. # vi /etc/sysconfig/docker OPTIONS='... --authorization-plugin=docker-novolume-plugin" 2. # systemctl stop docker 3. # systemctl enable docker-novolume-plugin 4. # systemctl start docker Actual results: # ps waux | grep -v grep | grep plugin root 12269 0.0 0.1 44428 6820 ? Ssl 10:53 0:00 /usr/libexec/docker/rhel-push-plugin root 13766 0.2 0.6 352936 24712 ? Ssl 11:39 0:00 /usr/bin/docker-current... Expected results: # ps waux | grep -v grep | grep plugin root 728 0.0 0.1 40592 4068 ? Ssl 11:59 0:00 /usr/libexec/docker/docker-novolume-plugin root 6113 0.2 0.6 297968 26152 ? Ssl 11:59 0:00 /usr/bin/docker-current... root 12222 0.0 0.1 43372 5876 ? Ssl 12:00 0:00 /usr/libexec/docker/rhel-push-plugin Additional info: I can manually start the service with 'systemctl start docker-novolume-plugin' and then everything works as expected.
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
Doc. Fix: https://github.com/projectatomic/docker-novolume-plugin/pull/12