Open marccampbell opened 8 years ago
can reproduce. also, other commands work, including swarmctl network inspect
on the problem network. also, removing the problem network restores normal functionality of swarmctl network ls
. i'll take a look.
the crash is in swarmctl. swarmd shows but does not go down.
ERRO[2903] Failed allocation for network 8o9gxgs5fq4xgv7e3y6fdv91i: failed during network allocation for network 8o9gxgs5fq4xgv7e3y6fdv91i: failed during network allocation for 8o9gxgs5fq4xgv7e3y6fdv91i: could not resolve network driver asfd
on removal, swarmd shows error
ERRO[3065] Failed during network free for network 8o9gxgs5fq4xgv7e3y6fdv91i: could not get networker state for network 8o9gxgs5fq4xgv7e3y6fdv91i
/cc @mrjana
Thanks @marccampbell
/cc @mavenugo
Will take a look @ it later today.
/cc @mrjana @mavenugo
bin/swarmctl network create --name test --driver does_not_exists Error: plugin does_not_exists not supported
not reproducible
Output is below. There doesn't appear to be validation that the driver exists when adding a network. Once a network is added using
swarmctl
and it's invalid or not found, requests toswarmctl network ls
crashes.