Bug 1851473

Summary: Include the RPM package NVR in the binaries.
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Flavio Leitner <fleitner>
Component: openvswitch2.13Assignee: Timothy Redaelli <tredaelli>
Status: ASSIGNED --- QA Contact: Jiying Qiu <jiqiu>
Severity: high Docs Contact:
Priority: unspecified    
Version: FDP 20.ECC: ctrautma, ggrimaux, jhsiao, ralongi, tredaelli
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://patchwork.ozlabs.org/project/openvswitch/patch/f5ab5f00f8bdcb9ec4bf5715861774519920a544.1668006310.git.tredaelli@redhat.com/
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Flavio Leitner 2020-06-26 16:33:42 UTC
Description of problem:

When a core is generated, it is impossible to tell from which package it came from.

The packaging NVR is critical support information.

One idea is to change ovs_version at build time to be RPM version-release, but it may cause scripting issues, so not sure.

Perhaps it could include package_version along with ovs_version, so that ovs-vsctl command shows like below:

# ovs-vsctl show | grep version
    ovs_version: "2.13.0"
    ovs_package: <packaging ID/NVR>

And we could easily get that from core since it would be global variable.

Version-Release number of selected component (if applicable):
2.9.0 but it should be the same in upstream branch master

How reproducible:
Always

Steps to Reproduce:
1. Start OVS service
2. kill -ABRT ovs-vswitchd/ovsdb-server to generate a core
3. Try to find the OVS package NVR from the core.

Actual results:
That critical support information is missing.

Expected results:
Easy to find identify which package NVR was being used.