Unable to start escaped unit files

[oxtopus]

Or maybe it started, but I can't get status?

$ fleetctl load f-\\xc3\\xb6-o.service 
Unit f-\xc3\xb6-o.service loaded on 2970b762.../172.17.8.101
$ fleetctl start f-\\xc3\\xb6-o.service 
Unit f-\xc3\xb6-o.service launched on 2970b762.../172.17.8.101
$ fleetctl status f-\\xc3\\xb6-o.service 
● f-xc3xb6-o.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
...

It shows up in fleetctl list-unit-files as f-\xc3\xb6-o.service 4038b32 launched launched 2970b762.../172.17.8.101

I'm using systemd-escape[1] to generate escaped filenames:

$ systemd-escape -- f/ö/o.service
f-\xc3\xb6-o.service
$ systemd-escape -u -- f-\\xc3\\xb6-o.service
f/ö/o.service

See http://www.freedesktop.org/software/systemd/man/systemd-escape.html and search for "escape" in http://www.freedesktop.org/software/systemd/man/systemd.unit.html

For now, I'm having to resort to base32-encoding the filenames instead, which works for my purposes, but doesn't produce an easily readable fleetctl output.

[oxtopus]

As far as I can tell, it's only a problem when tunneling. For example, I can fleetctl ssh into a node and do this:

$ fleetctl status f-\\xc3\\xb6-o.service 
● f-\xc3\xb6-o.service
   Loaded: loaded (/run/fleet/units/f-\xc3\xb6-o.service; linked-runtime; vendor preset: disabled)
   Active: inactive (dead)

[crawford]

Fixed in #1253.

Old:

$ fleetctl status crazy-name.service
● \x22crazy-name.service\x22.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

New:

$ fleetctl status crazy-name.service
● crazy-name.service
   Loaded: loaded (/run/fleet/units/crazy-name.service; linked-runtime; vendor preset: disabled)
   Active: active (running) since Thu 2015-06-18 00:04:24 ; 58s ago
 Main PID: 2301 (sleep)
   Memory: 120.0K
   CGroup: /system.slice/crazy-name.service
           └─2301 /usr/bin/sleep 1000000

Jun 18 00:04:24 crawford-test-3 systemd[1]: Started crazy-name.service.
Jun 18 00:04:24 crawford-test-3 systemd[1]: Starting crazy-name.service...