The most recent copy of a container can be removed in the following scenario:
- the container is migrated in the interface of PVA MN from one node to another without deleting the private area from the source node or using the command line tool
vzmigratewith the option
- some time later, the original container is manually restored on the source node by renaming the configuration file and the directory with the private area:
- on Windows:
%vzroot%\conf\CTID.conf.migratedis renamed to
%vzroot%\private\CTID.migratedis renamed to
- on Linux:
/etc/vz/conf/CTID.conf.migratedis renamed to
/etc/vz/conf/CTID.confwith changing the target of the symbolic link if needed, and
/vz/private/CTID.migratedis renamed to
/vz/private/CTID(the actual path may be different); (Replace
CTIDwith the appropriate container's ID value.)
- on Windows:
- the recovered container is started on the source node while the target node still has the copy of this container with the same CTID and EID;
- in the interface of PVA MN, the container is deleted, being expected to be deleted from the destination node.
The actual result is: the container from the source node is actually deleted.
The container's EID (Environment ID) value is not changed during migration. Any environment is represented with an unique EID value in PVA and all operations for environments are performed using the corresponding EID values.
In case two containers with the same EID exist in the infrastructure on different nodes, PVA MN displays only one of them and detects the parent (the node where the container resides currently) of the container by the last operation that was performed on the container.
For the scenario described in the Symptoms section:
- if before deleting the copy of the container on the destination server something is done with the copy of the container on the source node (for example, it is stopped/started), PVA MN considers the source node as the parent server for this container, and even if explicitly pointing to the destination node in the web interface of PVA MN, the container will be deleted from the source node.
Manual restore on the source node of the already migrated container (and thus creating 2 copies of the same container with the same EID value) is not supported by PVA MN and should be avoided.