Bug 972002

Summary: sfcbd process SEGV on openlmi lmiip request
Product: [Fedora] Fedora Reporter: Frank Ch. Eigler <fche>
Component: openlmi-networkingAssignee: Radek Novacek <rnovacek>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jsafrane, jsynacek, miminar, ovasik, pschiffe, rnovacek, rrakus, tbzatek, tsmetana, vcrhonek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openlmi-networking-0.0.9-2.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-19 08:20:45 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:
Attachments:
Description Flags
ABRT data dump about crash none

Description Frank Ch. Eigler 2013-06-07 18:37:37 UTC 
Created attachment 758273 [details]
ABRT data dump about crash

yum-installed unmodified openlmi* and prereqs
started sblim-sfcb service
ran lmiip from the openlmi-tools/cli-tools git

% lmiip -h vm-rawhide-64.local -u root -p PASSWORD addr show

SEGV reported in sfcbd

ABRT directory attached, including backtrace & core dump.
Automated reporting failed due to bug #958933.
Comment 1 Radek Novacek 2013-06-10 07:08:35 UTC 
The crash is somewhere in openlmi-networking but the backtrace doesn't show where exactly. Could you attach result of this command executed on the managed (vm-rawhide-64.local) system:

nmcli dev list
Comment 2 Frank Ch. Eigler 2013-06-10 13:53:07 UTC 
% nmcli dev list no workie, but
% nmcli dev status shows
eth0 ethernet connected
lo   loopback unmanaged

(By the way, do you support non-NM setups?)
Comment 3 Radek Novacek 2013-06-11 07:56:33 UTC 
ah, nmcli arguments are different in rawhide, the command I meant is:

nmcli dev show


non-NM setups are not supported, NM is required for openlmi-networking.
Comment 4 Roman Rakus 2013-06-17 15:49:18 UTC 
Seems to be same problem as in bug #973233.
Comment 5 Radek Novacek 2013-06-19 08:20:45 UTC 
I think 973233 is different issue.

This bug should be fixed in openlmi-networking-0.0.9-2.fc20.