Bug 2237699

Summary: Tests 702 and 707 of the pcp-testuite are failing
Product: [Fedora] Fedora Reporter: Jan Kurik <jkurik>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 39CC: agerstmayr, jkurik, lchilton, mgoodwin, nathans, sfeifer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-06 22:41:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Kurik 2023-09-06 12:31:37 UTC
With the currently latest pcp build pcp-6.1.0-1.fc39, tests 702 and 707 are failing, throwing a python exception.

Reproducible: Always

Steps to Reproduce:
1. Configure a Fedora39 system to run PCP testsuite
2. Run tests 702 and/or 707 of the PCP testsuite
3. Check the output
Actual Results:  
Both tests are failing with the following output:

# su -l -s /bin/bash -c 'cd /var/lib/pcp/testsuite && ./check 702' pcpqa
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sample.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sampledso.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f simple.numfetch
Primary pmlogger not running ...
chkconfig pmlogger on, and restart PMCD
702 [failed, exit status 1] - output mismatch (see 702.out.bad)
2c2,9
< live - OK
---
> live -   File "/var/lib/pcp/testsuite/src/test_pcp.py", line 533, in test_context
>     test_pcp(self)
>   File "/var/lib/pcp/testsuite/src/test_pcp.py", line 126, in test_pcp
>     descs[0].contents.type,
>     ^^^^^^^^^^^^^^^^^^^^^^
> AttributeError: 'dict' object has no attribute 'type'
> 
> ----------------------------------------------------------------------
Check local PMCD is still alive ...
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sample.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sampledso.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f simple.numfetch
Failures: 702
Failed 1 of 1 tests



# su -l -s /bin/bash -c 'cd /var/lib/pcp/testsuite && ./check 707' pcpqa
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sample.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sampledso.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f simple.numfetch
707 [failed, exit status 1] - output mismatch (see 707.out.bad)
2c2,9
< archive - OK
---
> archive -   File "/var/lib/pcp/testsuite/src/test_pcp.py", line 533, in test_context
>     test_pcp(self)
>   File "/var/lib/pcp/testsuite/src/test_pcp.py", line 126, in test_pcp
>     descs[0].contents.type,
>     ^^^^^^^^^^^^^^^^^^^^^^
> AttributeError: 'dict' object has no attribute 'type'
> 
> ----------------------------------------------------------------------
Check local PMCD is still alive ...
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sample.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f sampledso.milliseconds
PMDA probe: pminfo -h vm-10-0-184-105.hosted.upshift.rdu2.redhat.com -f simple.numfetch
Failures: 707
Failed 1 of 1 tests


Expected Results:  
Both tests should pass.

This seems to be an issue in the pcp-testsuite, not in the PCP it self. As such, setting the severity to a low value.

Comment 1 Nathan Scott 2023-09-06 22:41:24 UTC
This is a python-3.12 issue, being tackled over in BZ 2231751.

*** This bug has been marked as a duplicate of bug 2231751 ***