QA failures - holding the release

I've not yet been able to resolve the following QA failures on F24/x86_64.
Some just need some QA work (e.g. the nfsv4 related), others need better
filtering. But some are not understood (by me anyway). I'm concentrating on
the pmrep segfaults before tackling any others for now.

Failures: 042 216 232 366 651 732 755 766 782 798 895 1069

042 no values available for proc.memory.rss in busybox container
    (other metrics are OK)

216 network metrics out of range (0..0). Issue with version of netstat on
F24?
> network.icmp.inerrors = 152 out of range 0..0
> network.icmp.outechos = 612 out of range 0..0
> network.tcp.outsegs = 6703507 out of range 0..0
> network.tcp.retranssegs = 77259 out of range 0..0
> network.tcp.inerrs = 7440 out of range 0..0
> network.udp.noports = 226 out of range 0..0


232 torture indom, fetch != pmGetInDom for nfs4.client.reqs
nfs4.client.reqs:
number of instances from unprofiled fetch (0) != that for pmGetInDom (56)


366 logconf for jbd2
$ rpm -qf $(pwd)/jbd2
file /var/lib/pcp/config/pmlogconf/filesystem/jbd2 is not owned by any
package
... hmm so how did it get there? Left over from a previous install?

651 sample PMDA IPC protocol failure

732 nfs4.server.reqs has 11 additional entries on fc24 (allocate, copy,
copy-notify, etc)

755 no apache agent?

766 >   pcp://10.64.152.4:44321
    >   pcp://10.64.152.4:44321

782 pmwebd not terminating in a timely manner .. forced to terminate)

798 nfs value filtering?

895 oops, 100 archive records not between the expected range of 300 and 1500

1069 python, pmrep segfaults
$ pmrep -s 1 --archive archives/20130706 -z -O 30m
disk.dev.read,,"'sda','sdb'",,,16
          d.d.read          d.d.read
               sda               sdb
           count/s           count/s
               N/A               N/A
Segmentation fault (core dumped)
must be segfaulting somewhere in the C libraries?