fleetctl queues job for scheduling

a.service

[Unit]
Description=a

[Service]
TimeoutStartSec=20m
ExecStart=/bin/bash -c "while true; do echo 'a...' && sleep 10; done" 

[Install]
WantedBy=multi-user.target

b.service

[Unit]
Description=b
Requires=a.service
After=a.service

[Service]
TimeoutStartSec=20m
ExecStart=/bin/bash -c "while true; do echo 'b...' && sleep 10; done"

[Install]
WantedBy=multi-user.target

[X-Fleet]
X-ConditionMachineOf=a.service

output

$ fleetctl submit a.service b.service
$ fleetctl list-units
UNIT		LOAD	ACTIVE	SUB	DESC	MACHINE
a.service	-	-	-	a	-
b.service	-	-	-	b	-
$ fleetctl start b.service
Job b.service still queued for scheduling
$ fleetctl list-units
UNIT		LOAD	ACTIVE	SUB	DESC	MACHINE
a.service	-	-	-	a	-
b.service	-	-	-	b	-

This is all a bit in flux at the moment - the next release of fleet should definitely make it clearer what's going on here (one of our goals is to better report status for units that aren't scheduling, for example).

As to the behaviour you're hoping for, would it be something like the X-Requires/X-Wants mentioned in #287?

Do feel free to file issues against the fleet project for anything like this - sometimes we can be a little more responsive there than IRC :-)

@jonboulle X-Requires/X-Wants is great for coordinating dependencies across the cluster, which is what's desired here. However, not sure why even when scheduling these two jobs on the same machine (this test scenario only had one machine in the cluster), the jobs are not starting properly.

PS I opened the issue as coreos/fleet#363