I've been trying out containers in PVE 2.0. I had some issues migrating that has left me in a weird state. Here's what I did:
- 2-node PVE 2.0 cluster
- Created a new CT (104) on node A
- Using ubuntu 10.04 x86_64 template, with bridge networking
- Started it up, confirmed networking correct, etc.
- Ran vzmigrate --online <node b ip> 104
Didn't work. Got this:
Had a look around. The 104.conf file is actually located at /etc/pve/openvz/104.conf
- Decided to just make a symlink , point /etc/vz/conf/104.conf -> /etc/pve/openvz/104.conf
- Do the vzmigrate again. Works! Hmm, wait, it didn't. The 104.conf file now exists on node b, but is empty. My network switch confirms the container is still on node A.
- I scp the 104.conf file from node A to node B, and also symlink it similarly on node B.
- vzmigrate again. It works! The container stayed up, the container was removed from node A, my network switch sees it on the new port, etc.
But it doesn't show up under Node B in the web GUI. In fact, it's missing completely (not on node A either). The container is still running though; I'm SSH'd into it, and I can enter it using vzctl on node B, vzlist on node B shows it. It's just gone from the GUI. It seems like PVE just doesn't know about it anymore.
So, questions:
- What might I have done wrong to start with, when it couldn't find the config files?
- What did my symlinking and scp'ing of the config file shenanigans do?
- How can I get the container to show up in the GUI again??
- 2-node PVE 2.0 cluster
- Created a new CT (104) on node A
- Using ubuntu 10.04 x86_64 template, with bridge networking
- Started it up, confirmed networking correct, etc.
- Ran vzmigrate --online <node b ip> 104
Didn't work. Got this:
Code:
.: 372: Can't open /etc/vz/conf/104.conf- Decided to just make a symlink , point /etc/vz/conf/104.conf -> /etc/pve/openvz/104.conf
- Do the vzmigrate again. Works! Hmm, wait, it didn't. The 104.conf file now exists on node b, but is empty. My network switch confirms the container is still on node A.
- I scp the 104.conf file from node A to node B, and also symlink it similarly on node B.
- vzmigrate again. It works! The container stayed up, the container was removed from node A, my network switch sees it on the new port, etc.
But it doesn't show up under Node B in the web GUI. In fact, it's missing completely (not on node A either). The container is still running though; I'm SSH'd into it, and I can enter it using vzctl on node B, vzlist on node B shows it. It's just gone from the GUI. It seems like PVE just doesn't know about it anymore.
So, questions:
- What might I have done wrong to start with, when it couldn't find the config files?
- What did my symlinking and scp'ing of the config file shenanigans do?
- How can I get the container to show up in the GUI again??
