[Bug 1105] New: pmie doesn't follow -h HOSTSPEC vs. "fqdn" hostname distinction

[bugzilla-daemon@xxxxxxxxxxx]

Bug ID	1105
Summary	pmie doesn't follow -h HOSTSPEC vs. "fqdn" hostname distinction
Product	pcp
Version	unspecified
Hardware	All
OS	Linux
Status	NEW
Severity	major
Priority	P5
Component	pcp
Assignee	pcp@kenj.com.au
Reporter	fche@redhat.com
CC	pcp@oss.sgi.com
Classification	Unclassified

Consider any pcp server configuration where the pmcd.hostname results in a
string that's not resolvable as a tcp/ip-connectable name.  For example a
docker container, where $hostname is a hex magic string that is not reachable
as is.  The same thing applies if the the hostspec contains some sort of proxy
or tunneling instruction, and the destination 

Now consider a pmie being attached to that container thusly:

% pmie -f -h 'pcp://localhost?container=508fdd55187f'
/etc/pcp/pmie/config.default
[Mon Mar 30 15:38:31] pmie(18988) Info: Cannot connect to pmcd on host
508fdd55187f
pmie: warning - host 508fdd55187f is unreachable
^C

This is an old problem in pmie; it never learned to separate target hostname
and connection-specification, like pmlogger did.  The old pcpfans.git
fche/pmie-fqdn branch contains some work in this direction.

---

      You are receiving this mail because:

• You are on the CC list for the bug.