Bug 1851473 - Include the RPM package NVR in the binaries.
Summary: Include the RPM package NVR in the binaries.
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch2.13
Version: FDP 20.E
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Timothy Redaelli
QA Contact: Jiying Qiu
URL: https://patchwork.ozlabs.org/project/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-26 16:33 UTC by Flavio Leitner
Modified: 2023-07-13 07:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FD-740 0 None None None 2022-11-09 15:16:52 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.