Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Invoke tar from same location in source and target mode (#297) When cloning we were invoking tar at the container root in the source mode and within the volume mount in target mode. The result was the disk.img file appearing in a tmp/clone/image subdirectory in the target pvc instead of being copied exactly. Signed-off-by: Adam Litke <alitke@redhat.com> * Having the cloning label in the target pod, make the pod affinity fails. (#280) The target pod looks for a pod with a specific label (specified in the pod affinity) that matches the source pod label. In my case the target pod included this label as well, so we can see that the target pod found matching pod, but it is the WRONG pod. It's itself!! The target was running without finding the source pod first. If we remove this label from the target pod, it will find the source pod and then will be scheduled on the same node. If it does not find the source pod (because the scheduler tried to schedule it before the source pod), it will be in 'Pending' state until the source pod is scheduled, and then will be running on the same node. #279
- Loading branch information