Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Fleet refuses to stop a dependent process #1384

Open
normelton opened this issue Oct 28, 2015 · 0 comments
Open

Fleet refuses to stop a dependent process #1384

normelton opened this issue Oct 28, 2015 · 0 comments

Comments

@normelton
Copy link

I've got two unit files loaded into fleet:

auth-radius-1.service

[Unit]
Wants=auth-cache-1.service
After=auth-cache-1.service

[Service]
ExecStart=/usr/bin/docker run --name auth-radius-1 -p=1812:1812/udp --link auth-cache-1:cache auth-radius radiusd -X
ExecStop=/usr/bin/docker stop auth-radius-1

[X-Fleet]
MachineMetadata=role=master

auth-cache-1.service

[Unit]

[Service]
ExecStart=/usr/bin/docker run --name auth-cache-1 redis
ExecStop=/usr/bin/docker stop auth-cache-1

[X-Fleet]
MachineMetadata=role=master

When I fleetctl start auth-radius-1, both units start. When I fleet stop auth-radius-1, the cache process continues running. This is all expected.

When I then fleetctl stop auth-cache-1, fleet refuses to cooperate. Here's what I see:

$ fleetctl --debug stop auth-cache-1
2015/10/28 08:00:00 DEBUG http.go:28: HTTP GET http://domain-sock/fleet/v1/units?alt=json
2015/10/28 08:00:00 DEBUG http.go:31: HTTP GET http://domain-sock/fleet/v1/units?alt=json 200 OK
2015/10/28 08:00:00 DEBUG stop.go:68: Unit(auth-cache-1.service) already loaded, skipping.

The stop command seems to think that auth-cache-1.service is already in loaded state. But running fleetctl list-units confirms the container is still running:

$ fleetctl list-units
UNIT        MACHINE     ACTIVE  SUB
auth-cache-1.service    ef72cebf.../172.16.4.10 active  running
auth-radius-1.service   ef72cebf.../172.16.4.10 failed  failed

This is on CoreOS 845.0.0, Fleet 0.11.5

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants