Bug 1240638

Summary: [abrt] wsmancli: wsmc_action_invoke(): wsman killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Julian Stecklina <js>
Component: wsmancliAssignee: srinivas gowda <srinivas_g_gowda>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: praveen_paladugu, srinivas_g_gowda, vcrhonek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3ad5845bfa9c6e13d27a883a874da4563e2c4451
Whiteboard: abrt_hash:4178ba678ae874f0c80555fd5d9c860dd5c1dc17
Fixed In Version: wsmancli-2.3.2-1.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-07 13:04:49 UTC Type: ---
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
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Julian Stecklina 2015-07-07 12:07:12 UTC 
Description of problem:
I am trying to reset a Thinkpad X250 via wsman using the command below.

 wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService --port 16992 -h 192.168.1.94 --username admin -p 'xxx' -V -v -J -  <<EOF
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:PowerState>10</p:PowerState>
  <p:ManagedElement xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
                    xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
    <wsa:ReferenceParameters>
      <wsman:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</wsman:ResourceURI>
      <wsman:SelectorSet>
        <wsman:Selector Name="CreationClassName">CIM_ComputerSystem</wsman:Selector>
        <wsman:Selector Name="Name">ManagedSystem</wsman:Selector>
      </wsman:SelectorSet>
    </wsa:ReferenceParameters>
  </p:ManagedElement>
</p:RequestPowerStateChange_INPUT>
EOF
~ 

Version-Release number of selected component:
wsmancli-2.3.1-3.fc22

Additional info:
reporter:       libreport-2.6.0
backtrace_rating: 4
cmdline:        wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService --port 16992 -h 192.168.1.94 --username admin -p xxx -V -v -J -
crash_function: wsmc_action_invoke
executable:     /usr/bin/wsman
global_pid:     10522
kernel:         4.0.6-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 wsmc_action_invoke at /usr/src/debug/openwsman-2.4.15/src/lib/wsman-client.c:1435
Comment 1 Julian Stecklina 2015-07-07 12:07:16 UTC 
Created attachment 1049252 [details]
File: backtrace
Comment 2 Julian Stecklina 2015-07-07 12:07:17 UTC 
Created attachment 1049253 [details]
File: cgroup
Comment 3 Julian Stecklina 2015-07-07 12:07:18 UTC 
Created attachment 1049254 [details]
File: core_backtrace
Comment 4 Julian Stecklina 2015-07-07 12:07:19 UTC 
Created attachment 1049255 [details]
File: dso_list
Comment 5 Julian Stecklina 2015-07-07 12:07:20 UTC 
Created attachment 1049256 [details]
File: environ
Comment 6 Julian Stecklina 2015-07-07 12:07:21 UTC 
Created attachment 1049257 [details]
File: limits
Comment 7 Julian Stecklina 2015-07-07 12:07:23 UTC 
Created attachment 1049258 [details]
File: maps
Comment 8 Julian Stecklina 2015-07-07 12:07:24 UTC 
Created attachment 1049259 [details]
File: mountinfo
Comment 9 Julian Stecklina 2015-07-07 12:07:25 UTC 
Created attachment 1049260 [details]
File: namespaces
Comment 10 Julian Stecklina 2015-07-07 12:07:26 UTC 
Created attachment 1049261 [details]
File: open_fds
Comment 11 Julian Stecklina 2015-07-07 12:07:27 UTC 
Created attachment 1049262 [details]
File: proc_pid_status
Comment 12 Julian Stecklina 2015-07-07 12:07:29 UTC 
Created attachment 1049263 [details]
File: var_log_messages
Comment 13 Julian Stecklina 2015-07-28 11:41:38 UTC 
This also happens for the WSMAN interface on an Intel NUC and happens 100% of the time.
Comment 14 Julian Stecklina 2015-07-28 11:49:45 UTC 
I tested with upstream git version 01a5e2151d5b660dace60843973a97a7d968c1e0 (the last which works with the openwsman version we have as a fedora 22 package) and this works fine.
Comment 15 Fedora Update System 2015-07-28 13:06:35 UTC 
wsmancli-2.3.2-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/wsmancli-2.3.2-1.fc22
Comment 16 Vitezslav Crhonek 2015-07-28 13:08:13 UTC 
Thanks for investigation, updated package will be in testing soon.
Comment 17 Fedora Update System 2015-07-30 00:48:47 UTC 
Package wsmancli-2.3.2-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing wsmancli-2.3.2-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-12106/wsmancli-2.3.2-1.fc22
then log in and leave karma (feedback).
Comment 18 Fedora Update System 2015-08-07 13:04:49 UTC 
wsmancli-2.3.2-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.