857
74%
main: 50%

Ran 31 Jul 2018 04:43PM UTC

Jobs 1

Files 10

Run time 25s

Badge

Embed ▾

pending completion

Build # 857

Build Type

push

travis-ci

Committed by

jeffvance

Commit Message

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

Coverage Stats

1046 of 1579 relevant lines covered (66.24%)

0.72 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	857.1	31 Jul 2018 04:43PM UTC	0	66.24	Travis Job 857.1

Source Files on build 857

Detailed source file information is not available for this build.

kubevirt / containerized-data-importer / 857
74%
main: 50%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 857

kubevirt / containerized-data-importer / 857 74% main: 50%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 857

kubevirt / containerized-data-importer / 857
74%
main: 50%

README BADGES
x