-
-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
btrfs doesn't report transfer progress on both sides of the migration #676
Comments
Can you try your copy again but with |
When you run The fact that the target connects to the source is why you often will have no problem interacting with both servers yourself but a copy may fail due to network issues going the other way.
You also have the option of using |
Hi @stgraber and thanks for replying so quickly. With lxc copy av j:av --mode=relay I'm getting
During the copy, I do observe a with lxc copy av j:av --mode=push I'm getting this message:
The "transferring instance" is not shown when I specify However, it unfortunately also errors out. With all three modes, this happens after around 1m30s. time lxc copy av j:av --mode=push
Error: Failed instance migration: Failed migration on source: migration dump failed
(00.011761) Error (criu/namespaces.c:460): Can't dump nested uts namespace for 4738
(00.011764) Error (criu/namespaces.c:721): Can't make utsns id
(00.018309) Error (criu/util.c:642): exited, status=1
(00.021460) Error (criu/util.c:642): exited, status=1
(00.022562) Error (criu/cr-dump.c:2098): Dumping FAILED.
incus copy av j:av --mode=push 0.09s user 0.02s system 0% cpu 1:24.65 total |
Ah, please stop the container first or pass --stateless as live migrations of containers are very unlikely to succeed. |
Alright, I'm running this now. Will update you when it completes. time lxc copy av j:av --mode=push --stateless |
I tried the commands. lxc copy av j:av --mode=push --stateless Works. lxc copy av j:av --mode=relay --stateless lxc copy av j:av --stateless Work as well but don't show progress. Also, about the |
Hmm, I've been unable to reproduce the migration error issue here:
Then with stateless:
All of those showed transfer progress information as expected. In my case, this was with Incus 0.7 on source and target server, CLI is Incus 0.7 too and storage on both source and target is basic |
Moving the issue back to Incomplete and un-milestone until I can reproduce an issue with either the error handling or transfer progress. |
I was running both machines with incus 0.7, but with the btrfs storage backend on both. |
Can I be of any help by e.g. retrying with debugging flags or something like that? |
I'll retry with btrfs see if that makes it behave differently here. |
Errors still propagate correctly but the progress information is indeed missing, so that's a btrfs driver issue then. |
Alright, great. I'm happy to hear I was able to report a bug which helps to improve the project and I wasn't wasting your time. Thank you for all your efforts and good night :) |
I don't think it's specific to the btrfs driver only. This affects also the zfs driver: using I also get the error mentioned in the issue description on some containers when copying over WAN network thru a tunnel:
rerunning the command later may be successfull. full command used:
on source target server runs: incus 6.0.0 |
Required information
Incus info of local machine
Incus info of remote
Issue description
(I'm using
alias lxc = incus
)Adding a remote and then executing
lxc list
orlxc exec
from local to the remote works properly.lxc remote add j 10.0.0.45 lxc list j: lxc exec j:summary-mole bash
This also does seem to execute, but at the end returns
Steps to reproduce
Information to attach
I think the error might either be related to the differing processor architectures, or are related to the fact that the machines, which are run on Oracle cloud free tier, are doing something strange with the network interface MAC.
On both machines,
br0
provides networking for the containers.Network config local machine
enp0s6
is the primary network interface with DHCP IP10.0.0.136
Network config remote
ens3
is the primary network interface with DHCP IP10.0.0.45
The text was updated successfully, but these errors were encountered: