Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-27293

`foreman-pcp` package is not available in the Satellite capsule repo

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Moderate
    • No

      Description of problem:

      foreman-pcp package is not available in the Satellite capsule repo. This blocks the setup of PCP on a capsule server.

       

      How reproducible:

      Always.

       

      Is this issue a regression from an earlier version:

      No.

       

      Steps to Reproduce:

      1. Try to install foreman-pcp package in a capsule server.

       

      Actual behavior:
      The package is not available:

      No package foreman-pcp available
      

       

      Expected behavior:
      The package (and its dependencies, which are all on the baseos or appstream repos) are installed.

       

      Business Impact / Additional info:

      Without it is not possible to monitor Satellite capsules using the PCP stack.

       

      I've been able to configure monitoring on a Satellite capsule using the metrics role by installing the foreman-pcp package from the Satellite server repo:

       

      [root@capsule-a-1 ~]# pcp
      Performance Co-Pilot configuration on capsule-a-1.$DOMAIN:
      
       platform: Linux capsule-a-1.$DOMAIN 4.18.0-513.24.1.el8_9.x86_64 #1 SMP Thu Mar 14 14:20:09 EDT 2024 x86_64
       hardware: 4 cpus, 2 disks, 1 node, 11973MB RAM
       timezone: UTC
       services: pmcd pmproxy
           pmcd: Version 5.3.7-20, 13 agents, 4 clients
           pmda: root pmcd proc pmproxy xfs redis linux apache mmv kvm
                 postgresql jbd2 openmetrics
       pmlogger: primary logger: /var/log/pcp/pmlogger/capsule-a-1.$DOMAIN/20240605.00.10
           pmie: primary engine: /var/log/pcp/pmie/capsule-a-1.$DOMAIN/pmie.log
      [root@capsule-a-1 ~]# ps auxw | grep pmda
      root 185453 0.0 0.0 106432 7056 ? S Jun04 0:00 /var/lib/pcp/pmdas/root/pmdaroot
      root 185454 0.2 0.0 101288 8600 ? S Jun04 1:51 /var/lib/pcp/pmdas/proc/pmdaproc -d 3
      root 185455 0.0 0.0 96920 4808 ? S Jun04 0:00 /var/lib/pcp/pmdas/xfs/pmdaxfs -d 11
      pcp 185456 0.0 0.1 128956 15852 ? Ss Jun04 0:04 pmdaredis
      root 185457 0.0 0.0 99876 8140 ? S Jun04 0:04 /var/lib/pcp/pmdas/linux/pmdalinux
      pcp 185458 0.0 0.0 108504 7188 ? S Jun04 0:00 /var/lib/pcp/pmdas/apache/pmdaapache -d 68
      root 185459 0.0 0.0 96972 6836 ? S Jun04 0:00 /var/lib/pcp/pmdas/kvm/pmdakvm -d 95
      postgres 185460 1.2 0.1 182884 23692 ? S Jun04 11:22 python3 /var/lib/pcp/pmdas/postgresql/pmdapostgresql.python
      root 185464 0.0 0.2 331672 31176 ? S Jun04 0:27 python3 /var/lib/pcp/pmdas/openmetrics/pmdaopenmetrics.python
      root 211076 0.0 0.0 11812 1208 pts/0 S+ 07:53 0:00 grep --color=auto pmda
      [root@capsule-a-1 ~]# pmval -f 1 redis.used_memory_human
      metric: redis.used_memory_human
      host: capsule-a-1.green.ddns.perf.redhat.com
      semantics: instantaneous value
      units: count
      samples: all
      localhost:6379 
      "179.21M" 
      "179.21M" 
      "179.21M" 
      "179.21M" 
      ^C
      

       

            egolov@redhat.com Evgeni Golov
            rhn-engineering-pablomh Pablo Méndez Hernández
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: