Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-19963

[2106188] 4 SVVP cases failed in CNV4.11 SVVP test

XMLWordPrintable

    • Critical
    • None

      +++ This bug was initially created as a clone of Bug #2105905 +++

      Description of problem:

      CNV4.11 SVVP Testing added 5 USB related cases,and 4 cases can not pass.

      new case list:
      USB Exposed port system test
      USB xHCI Transfer Speed Test
      USB3 Termination
      Boot from USB
      Bitlocker Drive Encryption USB Bios Log Test – PASS

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

      CNV4.11
      Win2019

      How reproducible:

      100%

      Steps to Reproduce:

      1.Prepare CNV4.11 Environment
      2.Boot up Win2019 guest and doing SVVP testing

      Actual results:
      Case list added 5 new cases,and 4 cases can not pass

      Expected results:

      All cases passed.
      Additional info:

      — Additional comment from RHEL Program Management on 2022-07-11 15:06:37 CST —

      This bug report has Keyword TestBlocker.

      Since test blockers have high impact on release verification, it is also being [proposed|marked] as a blocker for this release.

      Please resolve ASAP.

      — Additional comment from RHEL Program Management on 2022-07-11 15:06:37 CST —

      A request has been made to block the RHEL release until this bug has been addressed. If you only meant to get a check-in exception please set "exception?" instead. For blocker requests please follow the instructions in this comment to verify BZ accuracy and provide answers to 3 blocker review questions. You can fill out this form by clicking the [reply] link on this comment, and then reply in-line to this message. Please do this even if you believe the case is obvious, or already covered in the BZ, as a way to make it easier for reviewers to approve this request.

      Verify the following information is set in the BZ:

      • Confirm the Internal Target Release field reflects which release to block

      Answer the following 3 questions:
      1. What is the scope of harm if this BZ is not resolved in this release? Reviewers want to know which RHEL features or customers are affected and if it will impact any Layered Product or Hardware partner plans.
      2. What are the risks associated with resolving this BZ? Reviewers want to know the scope of retesting, potential regressions
      3. Provide any other details that meet blocker criteria or should be weighed in making a decision (Other releases affected, upstream status, business impacts, etc).

      — Additional comment from Qianqian Zhu on 2022-07-12 09:38:30 CST —

      Hi Marek,

      This is mainly for asking for errata, if CNV can not fix it very soon.
      If it possible for you to help evaluate how long it will take to get an errata for it?

      Regards,
      Qianqian

              acardace@redhat.com Antonio Cardace
              qizhu@redhat.com Qianqian Zhu
              Leidong Wang Leidong Wang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: