[Bug 1109] New: fuzzy container hex-id naming leads to nondeterminism

[bugzilla-daemon@xxxxxxxxxxx]

Bug ID	1109
Summary	fuzzy container hex-id naming leads to nondeterminism
Product	pcp
Version	unspecified
Hardware	All
OS	Linux
Status	NEW
Severity	major
Priority	P5
Component	pcp
Assignee	pcp@oss.sgi.com
Reporter	fche@redhat.com
CC	pcp@oss.sgi.com
Classification	Unclassified

Consider 

% pmval pmcd.hostname --container 0

relying on src/pmdas/root/docker.c docker_name_matching's fuzzy code.
With that running, now start some docker jobbies, enough to get some
with a hex 0DEADBEEF instance-id:

% for i in `seq 30`
do
docker run --rm busybox sleep 200 </dev/null &
done

Wait a while and do it again.

Observe how pmval's output will change periodically, depending on
which container it happens to match; what containers and other copies
of pmval happened to be running at the moment when it first connected;
how containers die and get born.

In short, it is a non-identifying identifier, even within the lifetime
of a single pcp client.

---

      You are receiving this mail because:

• You are on the CC list for the bug.
• You are the assignee for the bug.