Hello,
I had a cluster with two nodes with proxmox 4.0. Recently I added a third node with proxmox 4.4 because I want to update all the nodes to the latest version with the smallest downtime possible.
To try it out, I moved some containers to the new node (pve 4.4) but they don't boot and now I can not migrate them back to the pve 4.0 nodes either.
Trying to start a container in pve 4.4:
root@pve2:~# lxc-start -n 123 -F --logfile=lxc.log --logpriority=debug
got unexpected ostype (debian != ubuntu)
lxc-start: conf.c: run_buffer: 347 Script exited with status 2
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "123".
lxc-start: start.c: __lxc_start: 1313 Failed to initialize container "123".
lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained by setting the --logfile and --logpriority options.
root@pve2:~# tail lxc.log
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:402 - processing: .delete_module errno 1.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:567 - Adding native rule for delete_module action 327681.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:570 - Adding compat rule for delete_module action 327681.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:580 - Merging in the compat Seccomp ctx into the main one.
lxc-start 20170215213835.682 INFO lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '123', config section 'lxc'
lxc-start 20170215213836.895 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 2
lxc-start 20170215213836.895 ERROR lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "123".
lxc-start 20170215213836.895 ERROR lxc_start - start.c:__lxc_start:1313 - Failed to initialize container "123".
lxc-start 20170215213836.895 ERROR lxc_start_ui - tools/lxc_start.c:main:365 - The container failed to start.
lxc-start 20170215213836.895 ERROR lxc_start_ui - tools/lxc_start.c:main:369 - Additional information can be obtained by setting the --logfile and --logpriority options.
Trying to migrate a container from pve 4.4 to pve 4.0:
ERROR: unknown command 'mtunnel'
USAGE: pvecm <COMMAND> [ARGS] [OPTIONS]
pvecm add <hostname> [OPTIONS]
pvecm addnode <node> [OPTIONS]
pvecm create <clustername> [OPTIONS]
pvecm delnode <node>
pvecm expected <expected>
pvecm keygen <filename>
pvecm nodes
pvecm status
pvecm updatecerts [OPTIONS]
pvecm help [<cmd>] [OPTIONS]
Feb 15 21:43:35 ERROR: migration aborted (duration 00:00:01): command '/usr/bin/ssh -o 'BatchMode=yes' root@x.x.x.x pvecm mtunnel --get_migration_ip' failed: exit code 255
TASK ERROR: migration aborted
I had a cluster with two nodes with proxmox 4.0. Recently I added a third node with proxmox 4.4 because I want to update all the nodes to the latest version with the smallest downtime possible.
To try it out, I moved some containers to the new node (pve 4.4) but they don't boot and now I can not migrate them back to the pve 4.0 nodes either.
Trying to start a container in pve 4.4:
root@pve2:~# lxc-start -n 123 -F --logfile=lxc.log --logpriority=debug
got unexpected ostype (debian != ubuntu)
lxc-start: conf.c: run_buffer: 347 Script exited with status 2
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "123".
lxc-start: start.c: __lxc_start: 1313 Failed to initialize container "123".
lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained by setting the --logfile and --logpriority options.
root@pve2:~# tail lxc.log
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:402 - processing: .delete_module errno 1.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:567 - Adding native rule for delete_module action 327681.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:570 - Adding compat rule for delete_module action 327681.
lxc-start 20170215213835.682 INFO lxc_seccomp - seccomp.c: parse_config_v2:580 - Merging in the compat Seccomp ctx into the main one.
lxc-start 20170215213835.682 INFO lxc_conf - conf.c:run_script_argv:367 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '123', config section 'lxc'
lxc-start 20170215213836.895 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 2
lxc-start 20170215213836.895 ERROR lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "123".
lxc-start 20170215213836.895 ERROR lxc_start - start.c:__lxc_start:1313 - Failed to initialize container "123".
lxc-start 20170215213836.895 ERROR lxc_start_ui - tools/lxc_start.c:main:365 - The container failed to start.
lxc-start 20170215213836.895 ERROR lxc_start_ui - tools/lxc_start.c:main:369 - Additional information can be obtained by setting the --logfile and --logpriority options.
Trying to migrate a container from pve 4.4 to pve 4.0:
ERROR: unknown command 'mtunnel'
USAGE: pvecm <COMMAND> [ARGS] [OPTIONS]
pvecm add <hostname> [OPTIONS]
pvecm addnode <node> [OPTIONS]
pvecm create <clustername> [OPTIONS]
pvecm delnode <node>
pvecm expected <expected>
pvecm keygen <filename>
pvecm nodes
pvecm status
pvecm updatecerts [OPTIONS]
pvecm help [<cmd>] [OPTIONS]
Feb 15 21:43:35 ERROR: migration aborted (duration 00:00:01): command '/usr/bin/ssh -o 'BatchMode=yes' root@x.x.x.x pvecm mtunnel --get_migration_ip' failed: exit code 255
TASK ERROR: migration aborted