Containers incorrectly attributed to host

[2opremio]

This is kubernetes and note how a single host is attributed 3 (all) the scope probes whilst there is a one-to-one mapping between probes (DaemonSet) and hosts .

Report: report_wrongly_attributed_containers.json.gz

[2opremio]

Once a while it very briefly (1 second) shows the correct table:

Possibly related: #1064

[tomwilkie]

I don't get this on gke:

report.json.zip

[tomwilkie]

I suspect this is a dupe of #1081, although I don't see why fons is hitting it (it was fixed)

[2opremio]

@paulbellamy can reproduce

[paulbellamy]

I do get this on gke..

report.zip

Edit: k8s 1.2.4

[tomwilkie]

Hmmm, weird. Will investigate tomorrow. Feel free to fix it before me if you want...

[paulbellamy]

It's not intermittent, it just assigns a bunch of "extra" containers to one of the hosts at any given time (which moves around).

[paulbellamy]

It's to do with having the ContainerImageRenderer and PodRenderer rolled up into the HostRenderer. Not sure quite how, yet...

[paulbellamy]

Also, existed in 0.14.0

[paulbellamy]

Ah ha. In previous versions of docker the container image id was different on each host. Now, they are the same. This means the container images have a random host_node_id based on whichever probe reported latest. Then because the children are propagated in NewDerivedNode all the containerImage's children (probes on other hosts) get set as children of the host.

Edit: the bit about docker behaviour changing is an "I believe"

[tomwilkie]

Also, existed in 0.14.0

I thought this was because every probe produced nodes for every container in the k8s reporter.