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

Virt-who ignores the bad http(s) proxy when run with hyperv, libvirt-remote and kubevirt

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • None
    • None
    • subs-client-tools-2
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • 57,005

      Description of problem:
      When configure bad http(s) proxy in /etc/virt-who.conf, virt-who can still get and send the hyperv, remote libvirt and kubevirt to entitlement server successfully.

      For esx, virt-who is failed to get esx mapping with bad http(s), which works as expected.

      For nutanix/ahv, there is known bz1992619.

      And because of bz1989354, we cannot make sure if the http(s) take effect when set with available value, we can just make sure virt-who can get and send mapping for all hypervisors normally with available http(s).

      Version-Release number of selected component (if applicable):
      virt-who-1.31.26-1.el9.noarch

      How reproducible:
      always

      Expected results:
      Virt-who should be failed to get mapping from each hypervisor with bad http(s).

              csi-client-tools-bugs CSI Client Tools Bugs Bot
              rhn-support-yuefliu Yuefen Liu
              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:
                Resolved: