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
Created attachment 1049252 [details] File: backtrace
Created attachment 1049253 [details] File: cgroup
Created attachment 1049254 [details] File: core_backtrace
Created attachment 1049255 [details] File: dso_list
Created attachment 1049256 [details] File: environ
Created attachment 1049257 [details] File: limits
Created attachment 1049258 [details] File: maps
Created attachment 1049259 [details] File: mountinfo
Created attachment 1049260 [details] File: namespaces
Created attachment 1049261 [details] File: open_fds
Created attachment 1049262 [details] File: proc_pid_status
Created attachment 1049263 [details] File: var_log_messages
This also happens for the WSMAN interface on an Intel NUC and happens 100% of the time.
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.
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
Thanks for investigation, updated package will be in testing soon.
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).
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.