1
69%
main: 49%

Ran 01 Aug 2018 01:50AM UTC

Files 9

Run time 1s

Badge

Embed ▾

Committed 01 Aug 2018 01:42AM UTC coverage: 68.658% (+0.06%) from 68.594%

Job # 866.1

Build Type

push

travis-ci

Committed by

jeffvance

Commit Message

Backports of Cloning PRs #280 and #297 to 1.1 branch (#301)

* 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.
https://github.com/kubevirt/containerized-data-importer/issues/279

Run Details

1023 of 1490 relevant lines covered (68.66%)

0.75 hits per line

kubevirt / containerized-data-importer / 866 / 1
69%
main: 49%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 866.1

kubevirt / containerized-data-importer / 866 / 1 69% main: 49%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 866.1

kubevirt / containerized-data-importer / 866 / 1
69%
main: 49%

README BADGES
x