Back to bug 1312431

Who When What Removed Added
Adrian Likins 2016-02-26 16:54:10 UTC Priority unspecified high
Target Release --- 6.8
Xianghua Chen 2016-07-29 09:25:00 UTC Blocks 1359965
Amnon Ilan 2016-08-08 12:29:34 UTC Blocks 1364808
Xianghua Chen 2016-08-16 09:38:03 UTC CC xchen
Amnon Ilan 2016-08-16 09:54:53 UTC CC ailan
Chris Williams 2016-09-07 21:54:09 UTC Blocks 1269194
Bin Han 2016-10-18 05:37:43 UTC CC bihan
Jim Wildman 2016-10-25 03:03:30 UTC CC jwildman
Richard W.M. Jones 2016-10-31 11:17:54 UTC Status NEW MODIFIED
Fixed In Version virt-what-1.11-1.3.el6
errata-xmlrpc 2016-10-31 11:39:31 UTC Status MODIFIED ON_QA
Bin Han 2016-11-02 01:45:09 UTC Status ON_QA VERIFIED
John Skeoch 2016-11-21 00:20:57 UTC CC bihan leiwang
Lenka Špačková 2016-12-07 09:41:36 UTC Docs Contact jherrman
Jiri Herrmann 2016-12-07 15:15:46 UTC Flags needinfo?(rjones)
Richard W.M. Jones 2016-12-07 17:35:28 UTC Doc Text Cause: The "virt-what" tool is used to detect if the current system is running under virtualization, and what sort of virtualization. This tool did not recognize IBM POWER s/390 LPARs (https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zmainframe/zconc_mfhwlpar.htm)

Consequence: We use virt-what in subscription-manager, so s-m would give misleading licensing information.

Fix: virt-what was fixed to detect running inside an LPAR

Result: s-m and other tools that use virt-what will now be able to determine that they are being run in virtualization.
Flags needinfo?(rjones)
Yehuda Zimmerman 2016-12-27 12:44:47 UTC Doc Text Cause: The "virt-what" tool is used to detect if the current system is running under virtualization, and what sort of virtualization. This tool did not recognize IBM POWER s/390 LPARs (https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zmainframe/zconc_mfhwlpar.htm)

Consequence: We use virt-what in subscription-manager, so s-m would give misleading licensing information.

Fix: virt-what was fixed to detect running inside an LPAR

Result: s-m and other tools that use virt-what will now be able to determine that they are being run in virtualization.
"virt_what" now detects IBM POWER s/390 LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER s/390 LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machines is running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* now provides correct subscription information.
Flags needinfo?(rjones)
Yehuda Zimmerman 2016-12-28 08:45:04 UTC Doc Text "virt_what" now detects IBM POWER s/390 LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER s/390 LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machines is running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* now provides correct subscription information.
"virt-what" now detects IBM POWER s/390 LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER s/390 LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* now provides correct subscription information.
Yehuda Zimmerman 2017-01-02 10:00:50 UTC Docs Contact jherrman yzimmerm
Jaroslav Suchanek 2017-01-09 13:31:54 UTC CC jsuchane, ptoscano
Flags needinfo?(ptoscano)
Pino Toscano 2017-01-10 14:05:14 UTC Doc Text "virt-what" now detects IBM POWER s/390 LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER s/390 LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER s/390 LPAR. As a result, *subscription-manager* now provides correct subscription information.
"virt-what" now detects IBM POWER LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER LPAR. As a result, *subscription-manager* now provides correct subscription information.
Flags needinfo?(ptoscano)
Jiri Herrmann 2017-01-18 19:18:59 UTC CC jherrman
Doc Text "virt-what" now detects IBM POWER LPARs

Previously, the "virt-what" tool did not recognize if the current system was running in an IBM POWER LPAR. As a result, *subscription-manager* would give misleading licensing information for guest virtual machines running in an IBM POWER LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER LPAR. As a result, *subscription-manager* now provides correct subscription information.
"virt-what" now detects IBM POWER LPARs

Previously, the "virt-what" utility did not recognize if the current system was running in an IBM POWER logical partition (LPAR). As a result, the *subscription-manager* utility displayed misleading licensing information for guest virtual machines running in an IBM POWER LPAR. With this update, "virt-what" was fixed and can now detect when the guest virtual machine is running in an IBM POWER LPAR. As a result, *subscription-manager* now provides correct subscription information in this scenario.
errata-xmlrpc 2017-03-21 01:28:18 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-03-21 11:28:43 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-03-21 07:28:43 UTC
Richard W.M. Jones 2018-07-16 12:13:19 UTC Flags needinfo?(rjones)

Back to bug 1312431