touch-packages team mailing list archive

[Tim Penhey <tim.penhey@xxxxxxxxxxxxx>]

Tested on a precise lxc container I have:

it seems we could try with -L (or even better --console-log) and fall
back to -c (or --console) if that fails with exit code 1 (we could even
check the output for "invalid option".

---- 
ubuntu@clean-precise:~$ lxc-start -n foo -L omg
lxc-start: invalid option -- 'L'
Usage: lxc-start --name=NAME -- COMMAND

lxc-start start COMMAND in specified container NAME

Options :
  -n, --name=NAME      NAME for name of the container
  -d, --daemon         daemonize the container
  -f, --rcfile=FILE    Load configuration file FILE
  -c, --console=FILE   Set the file output for the container console
  -C, --close-all-fds  If any fds are inherited, close them
                       If not specified, exit with failure instead
		       Note: --daemon implies --close-all-fds
  -s, --define KEY=VAL Assign VAL to configuration variable KEY

Common options :
  -o, --logfile=FILE               Output log to FILE instead of stderr
  -l, --logpriority=LEVEL          Set log priority to LEVEL
  -q, --quiet                      Don't produce any output
  -?, --help                       Give this help list
      --usage                      Give a short usage message

Mandatory or optional arguments to long options are also mandatory or optional
for any corresponding short options.

See the lxc-start man page for further information.

ubuntu@clean-precise:~$ echo $?
1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1348386

Title:
  lxc template fails to stop

Status in juju-core:
  Triaged
Status in juju-core 1.20 series:
  Triaged
Status in “lxc” package in Ubuntu:
  New

Bug description:
  The clone template determines when to stop by watching the console.log
  in the container directory. This used to contain the output from
  cloud-init.

  It seems that sometime recently, this has changed, and we are now no
  longer seeing any output in the console.log file.

  This means that we hit the 5 minute wait timeout for the machine to
  stop after the last bit of output we saw (which was nothing ever).

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1348386/+subscriptions