Open jonathangold opened 5 years ago
I might have a go at this one in a bit.
I think the issue's on my end. Closing for now.
Fixed my issue. Still panics.
It should never panic unless something is really wrong (eg: hardware error)
Maybe something changed with go-systemd package?
I'd try with an older version of that for fun (one where I made a commit perhaps) and then we write tests and fix bugs :/
But we (I?) have to fix that engine bug panic to make sure none of these are related to that.
This is NOT happening on my fedora box. It must be something with debian and/or google cloud. I'll post the fix here if and when I find it.
So the issue was on my end (the unit was failing to start,) but that should result in an error, not a panic.
Versions:
mgmt version (eg:
mgmt --version
):0.0.15-65-g7cf1e4b
operating system/distribution (eg:
uname -a
):Linux vps 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
golang version (eg:
go version
):go version go1.11.2 linux/amd64
Description:
The svc resource works fine unless
session => true
, in which case it panics (close of closed channel.)