Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-21652

[RFE] Have virt-who send off name of config in report

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-8.9.0
    • virt-who
    • None
    • sst_csi_client_tools
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • None
    • None
    • x86_64
    • None

      What were you trying to do that didn't work?

       

      We redesigned virt-who configure in Satellite to use 1 user for all configs as instructed per Will, but then we have an issue of us marking the config updated if there are multiple configs being sent in, since now it is all one report being sent in. For the mean time if we see a report coming in we are marking all configs updated in the UI, but this is not accurate for the customer if there was an issue with a config. We are requesting the name of the config/s be passed in with the report so we can parse the JSON and update accordingly. 

      Please provide the package NVR for which bug is seen:

      virt-who-1.30.16-1.el8.noarch

      How reproducible:

      Steps to reproduce

      1. Install Satellite and setup a few configs in the virt-who configure plugin
      2.  Run the script or hammer command to install virt-who and deploy the configs
      3.  Watch the report come in and look at the JSON, we have no way to see which config was used in the report so we can mark the UI updated accordingly. Since some configs can be on different time intervals etc.

      Expected results

       

      In the virt-who report JSON have the name of the config being used in the /etc/virt-who.d directory.

      Actual results

      Only hypervisors and guests are listed in the JSON

            jhnidek@redhat.com Jiri Hnidek
            rhn-support-chrobert Chris Roberts
            CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
            CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: