Bug 1768037

Summary: RFE: Backport nova [libvirt] option sysinfo_serial value "unique" into OSP 13
Product: Red Hat OpenStack Reporter: Ben Roose <broose>
Component: openstack-novaAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: amodi, broose, dasmith, egallen, eglynn, jhakimra, kchamart, lyarwood, sbauza, sgordon, smooney, vromanso
Target Milestone: z11Keywords: FeatureBackport, Patch, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-17.0.12-12.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-10 11:27:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Roose 2019-11-01 23:20:36 UTC
Request For Enhancement:
Customer is asking for the code changes for the nova [libvirt] "sysinfo_serial" option from upstream Stein release to be backported down into OSP 13.

Description of problem:
Customer is finding that Service Now does not correctly identify a virtual instance in OpenStack Platform 13 environments. Service Now uses dmidcode command for instance discovery and assumes the "system_serial" entry garnered from the instance's SMBIOS/DMI table is a unique identification number for that instance. In OSP 13 environments, this value is not unique, since all instances running on a compute node will gain the same "system_serial" value as that underlying compute host's UUID value.

How reproducible:
Always

Background:
Prior to the upstream OpenStack Stein release, the "system_serial" parameter could only be set to the UUID of the underlying compute host via the nova configuration [libvirt] option "sysinfo_serial" [1].

In upstream Stein (OSP 15) and Train releases, a new valid value of "unique" was added to the nova configuration [libvirt] option "sysinfo_serial" and defined as a "per-instance sysinfo serial number" [2]. When the sysinfo_serial option is set to "unique" the "system_serial" SMBIOS/DMI table parameter of an instance will be set to equal the unique "system_uuid" value of the instance [3].

Additional info:
Upstream OpenStack Compute (nova) blueprint information for "libvirt: per-instance sysinfo serial number" [2]
Upstream OpenStack Stein implemented specs for "Per instance serial number" [4]
Upstream OpenStack Stein code change commits by Kevin Zheng related to adding the "unique" feature into sysinfo_serial option [5]
Upstream OpenStack Stein additional code change commits by Matt Riedemann [6]

References:
[1] https://docs.openstack.org/nova/queens/configuration/config.html#libvirt.sysinfo_serial
[2] https://blueprints.launchpad.net/nova/+spec/per-instance-libvirt-sysinfo-serial
[3] https://docs.openstack.org/nova/train/configuration/config.html#libvirt.sysinfo_serial
[4] https://specs.openstack.org/openstack/nova-specs/specs/stein/implemented/per-instance-libvirt-sysinfo-serial.html
[5] https://opendev.org/openstack/nova/commit/dec5dd9286e0d218d3f7658879369b5d4a529a65
[6] https://opendev.org/openstack/nova/commit/b29158149d802cfc81541f13255394da559d0c48

Comment 9 errata-xmlrpc 2020-03-10 11:27:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0759