services doesn't restart on stopped status

[brgnepal]

Hi,

It seems that services could not be restarted on 'stopped' status.

[vagrant@centos7-adb ~]$ sudo sccli docker status
[vagrant@centos7-adb ~]$ echo $?
0
[vagrant@centos7-adb ~]$ sudo sccli docker stop
[vagrant@centos7-adb ~]$ echo $?
0
[vagrant@centos7-adb ~]$ sudo sccli docker restart
Start docker first

Any particular reason?

However, systemctl restart docker running fine on 'stopped' mode.

[vagrant@centos7-adb ~]$ sudo systemctl restart docker
[vagrant@centos7-adb ~]$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/docker.service.d
           └─flannel.conf
   Active: active (running) since Mon 2016-07-11 02:55:15 EDT; 9s ago
..............

[praveenkumar]

@budhrg we implemented this due to behaviour of kubernetes and openshift service both are contradict each other so if openshift service is running then user try to restart kubernetes without stopping openshift it will fail. That was the case this behavior we implemented in sccli.

[brgnepal]

Closing as it is fair enough to implement that way due to above reason.

[navidshaikh]

Current state:
docker - running
kubernetes -stopped
openshift - stopped

A user performs
vagrant service-manager restart kubernetes

acutal scenario: vsm won't allow it, since sccli doesn't allow it.

expected scenario: If no contradiction with openshift service, sccli should allow it.

[praveenkumar]

expected scenario: If no contradiction with openshift service, sccli should allow it.

That is the way it is currently because k8s and openshift contradict so you only want docker to be do restart ?