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

On satellite 6.14.2 + satellite virt-who config shows No report yet on WEB UI though hypervisors are reporting to satellite cli.

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Phoenix - Content
    • Yes

      Description of problem:

      On satellite 6.14.2, 6.14.3, 6.14.4, on satellite WEB UI virt-who config shows 'No report yet' though the hypervisors are being reported on the satellite cli.

      Satellite cli shows these hypervisors are guests are being reported from 'virt-who-config-1' config.

      1. virt-who -o -d

      2024-06-24 17:45:23,077 [rhsm.connection DEBUG] MainProcess(818927):Thread-4 @connection.py:_request:861 - Response: status=200, request="PUT /rhsm/hypervisors/RedHat/heartbeat?reporter_id=satellite.example.com-7e8080739ff0496cbb6ec6d60a410509"
      2024-06-24 17:45:23,077 [virtwho.destination_-4255702752784201995 INFO] MainProcess(818927):Thread-4 @virt.py:_send_data:651 - Hosts-to-guests mapping for config "virt-who-config-1": 7 hypervisors and 5 guests found       <<---------------------------------------------------
      2024-06-24 17:45:23,078 [rhsm.connection DEBUG] MainProcess(818927):Thread-4 @connection.py:{}init{}:211 - Environment variable NO_PROXY= will be used
      2024-06-24 17:45:23,079 [rhsm.connection DEBUG] MainProcess(818927):Thread-4 @connection.py:{}init{}:310 - Connection built: host=sussen-rhsat.syslab.pnq2.redhat.com port=443 handler=/rhsm auth=basic username=virt_who_reporter_1
      2024-06-24 17:45:23,078 [virtwho.destination_-4255702752784201995 INFO] MainProcess(818927):Thread-4 @virt.py:_send_data:687 - Sending updated Host-to-guest mapping to "RedHat" including 7 hypervisors and 5 guests   <<-------------------------------------------------

      =====================================

      But Hammer command shows the below output

      ======================================      

      1. date
        Mon Jun 24 17:48:16 IST 2024
      1. hammer virt-who list
        -{}|{}----------------{}|{}-----------{}|{}-----------{}|{}-------------
        ID | NAME               | INTERVAL      | STATUS        | LAST REPORT AT
        -{}|{}----------------{}|{}-----------{}|{}-----------{}|{}-------------
        1  | virt-who-Testathon | every 2 hours | No Report Yet |              <<-------------------------------------------------- 
        2  | virt-who           | every 4 hours | No Report Yet |               
        -{}|{}----------------{}|{}-----------{}|{}-----------{}|{}-------------

       

      How reproducible:

      Steps to Reproduce:

      1. On you satellite WEB UI -> Infrastructure -> virt-who Config -> Create virt-who config -> Select 'Hypervisor Type' - Vmware  -> put username and password -> save

      Copy the hammer command to config virt-who config on satellite cli.

      1. hammer virt-who-config deploy --id 1 --organization-id 1

      2. Once that is configured on the satellite server. Need to run the below command on the satellite cli to report the hypervisors.

      1. systemctl stop virt-who
      1. virt-who -o -d
      1. systemctl start virt-who

      3. All the hypervisors will show on the cli which are being reported but on the WEB UI it'll show 'No report yet'. On the content-hosts as well it'll show all hypervisors are being reported on WEB UI.

      4. It is working fine for RHEVM.

      Actual behavior:

      virt-who config is not showing the reported time.

      Expected behavior:

      Hypervisors immediately show report time on the satellite WEB UI while being reported on the cli. **

      Business Impact / Additional info:

       It is working fine for RHEVM. Vmware is working fine for satellite 6.13 as well.

              Unassigned Unassigned
              rhn-support-sussen Susmita Sen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: