This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2227011 - dstat fails to run when account has anaconda/conda python environment setup: ModuleNotFoundError: No module named 'pcp'
Summary: dstat fails to run when account has anaconda/conda python environment setup: ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcp
Version: CentOS Stream
Hardware: All
OS: All
low
low
Target Milestone: rc
: 9.4
Assignee: Nathan Scott
QA Contact: Jan Kurik
Jacob Taylor Valdez
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-27 12:43 UTC by daryl herzmann
Modified: 2023-09-22 17:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 17:41:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7509 0 None Migrated None 2023-09-22 17:41:50 UTC
Red Hat Issue Tracker RHELPLAN-163682 0 None None None 2023-07-27 12:46:07 UTC
Red Hat Issue Tracker RHELPLAN-163683 0 None None None 2023-07-27 12:46:11 UTC

Description daryl herzmann 2023-07-27 12:43:06 UTC 
Description of problem:

A user can not run `dstat` when configured to use its own python installation, for example, from anaconda.  The error received is:

$ dstat
Traceback (most recent call last):
  File "/usr/bin/dstat", line 30, in <module>
    from pcp import pmapi, pmconfig
ModuleNotFoundError: No module named 'pcp'

for some reason pmpython is not using platform python, but the user's local python

$ which pmpython
/usr/bin/pmpython
$ pmpython
Python 3.11.4 | packaged by conda-forge | (main, Jun 10 2023, 18:08:17) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.


Version-Release number of selected component (if applicable):

pcp-system-tools-6.0.4-2.el9.x86_64

How reproducible: 100%


Steps to Reproduce:
1. install anaconda python
2. conda activate env
3. dstat
Comment 1 Nathan Scott 2023-07-27 22:43:00 UTC 
Thanks for reporting the issue.  What does this command report?

grep PCP_PYTHON_PROG /etc/pcp.conf
rpm -qa | grep pcp | grep python


The first should be indicating the system python, and this is what pmpython uses.

cheers.
Comment 2 daryl herzmann 2023-07-28 02:06:17 UTC 
Thank you for the response.

$ grep PCP_PYTHON_PROG /etc/pcp.conf
PCP_PYTHON_PROG=python3
$ rpm -qa | grep pcp | grep python
python3-pcp-6.0.5-1.el9.x86_64
$ which python3
/opt/miniconda3/envs/prod/bin/python3

I thought there was a mechanism to specify "platform python", but am not seeing it now.  It seems like dstat should be hardcoding to /usr/bin/python3 as python3-pcp installs into /usr/lib64/python3.9/site-packages
Comment 3 Nathan Scott 2023-07-30 23:44:05 UTC 
Thanks Daryl.

For PCP, you can specify the python version to be used across all PCP tools in /etc/pcp.conf - so quickest workaround for you here is to just do that for now.

Longer term though I agree a fixed-path specification would be for the best, I'll get that change made in an upcoming release.

cheers.
Comment 5 RHEL Program Management 2023-09-22 17:40:19 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6 RHEL Program Management 2023-09-22 17:41:54 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.