Quantcast

Invoke commands not working with 2.4 or newer wsmancli

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

 

With wsmancli 2.4 or newer, invoke commands no longer work and fail for invalid selectors. I read this post (https://sourceforge.net/p/openwsman/mailman/message/34184703/) and it states to now use “&” instead of “,” for separator but still same failure.

 

Has this issue been escalated to be fixed?

Thanks

Tex

 

 

 

 


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
Tex,

* [hidden email] <[hidden email]> [Mar 09. 2016 16:51]:
> Dell - Internal Use - Confidential
>
> With wsmancli 2.4 or newer,

there is no version 2.4 of wsmancli. Which exact version are you using ?

You're probably running version 2.5 or later and wsmancli and
openwsman have different versions.

See https://github.com/Openwsman/wsmancli/releases/tag/v2.5.0,
https://github.com/Openwsman/openwsman/releases/tag/v2.5.0, and
https://sourceforge.net/p/openwsman/mailman/message/34907685 for
details.

If you're using matching versions, please state the exact wsmancli command
and the failure to help you further.


Regards,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

Sorry about that, was looking at the version of openwsman. So for wsmancli I tried 2.3.1 and 2.6.0, both failed with same issue. I tried 2.3.0 and this version works using comma separator.

 

 

Version that works (on RHEL 7):

 

RHEL 7

 

[root@localhost ~]# rpm -qa | grep -i wsman

libwsman1-2.3.6-13.el7.x86_64

wsmancli-2.3.0-4.el7.x86_64

[root@localhost ~]#

 

Version that fails on SLES 12:

 

linux-1rq9:~ # rpm -qa | grep -i wsman

libwsman_clientpp1-2.4.11-9.2.x86_64

wsmancli-2.3.1-3.17.x86_64

libwsman1-2.4.11-9.2.x86_64

linux-1rq9:~ #

 

Here’s 2.6 on Fedora 32 which shows the command failing. I tried “,” and “&” separator, both fail:

 

[root@localhost openwsman_scripts]# cat export_config_xml.sh

#! /bin/bash

 

wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem",CreationClassName="DCIM_LCService",SystemName="DCIM:ComputerSystem",Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

 

[root@localhost openwsman_scripts]# ./export_config_xml.sh 192.168.0.121

Maybe wrong use of ',' separator in URI, should be '&'

<?xml version="1.0" encoding="UTF-8"?>

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">

  <s:Header>

    <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

    <wsa:Action>http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</wsa:Action>

    <wsa:RelatesTo>uuid:b9d6145e-2db3-1db3-8002-083d105d1500</wsa:RelatesTo>

    <wsa:MessageID>uuid:0c9298bf-2db2-1db2-a3cd-d6f0fb722ab8</wsa:MessageID>

  </s:Header>

  <s:Body>

    <s:Fault>

      <s:Code>

        <s:Value>s:Sender</s:Value>

        <s:Subcode>

          <s:Value>wsman:InvalidSelectors</s:Value>

        </s:Subcode>

      </s:Code>

      <s:Reason>

        <s:Text xml:lang="en">The Selectors for the resource are not valid.</s:Text>

      </s:Reason>

      <s:Detail>

        <wsman:FaultDetail>http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InsufficientSelectors</wsman:FaultDetail>

      </s:Detail>

    </s:Fault>

  </s:Body>

</s:Envelope>

 

[root@localhost openwsman_scripts]# cat export_config_xml.sh

#! /bin/bash

 

wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName="DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

[root@localhost openwsman_scripts]# ./export_config_xml.sh 192.168.0.121

<?xml version="1.0" encoding="UTF-8"?>

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">

  <s:Header>

    <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

    <wsa:Action>http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</wsa:Action>

    <wsa:RelatesTo>uuid:bd9a4ca7-2db3-1db3-8002-083d105d1500</wsa:RelatesTo>

    <wsa:MessageID>uuid:10581f1a-2db2-1db2-a3d2-d6f0fb722ab8</wsa:MessageID>

  </s:Header>

  <s:Body>

    <s:Fault>

      <s:Code>

        <s:Value>s:Sender</s:Value>

        <s:Subcode>

          <s:Value>wsman:InvalidSelectors</s:Value>

        </s:Subcode>

      </s:Code>

      <s:Reason>

        <s:Text xml:lang="en">The Selectors for the resource are not valid.</s:Text>

      </s:Reason>

    </s:Fault>

  </s:Body>

</s:Envelope>

[root@localhost openwsman_scripts]#

 

 

Thanks

Tex

 

 

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Thursday, March 10, 2016 12:56 AM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

Tex,

* [hidden email] [Mar 09. 2016 16:51]:
> Dell - Internal Use - Confidential
>
> With wsmancli 2.4 or newer,

there is no version 2.4 of wsmancli. Which exact version are you using ?

You're probably running version 2.5 or later and wsmancli and openwsman have different versions.

See https://github.com/Openwsman/wsmancli/releases/tag/v2.5.0,
https://github.com/Openwsman/openwsman/releases/tag/v2.5.0, and
https://sourceforge.net/p/openwsman/mailman/message/34907685 for details.

If you're using matching versions, please state the exact wsmancli command and the failure to help you further.


Regards,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* [hidden email] <[hidden email]> [Mar 10. 2016 17:12]:
>
> wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem",CreationClassName="DCIM_LCService",SystemName="DCIM:ComputerSystem",Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

This one is wrong and ...

>
> [root@localhost openwsman_scripts]# ./export_config_xml.sh 192.168.0.121
> Maybe wrong use of ',' separator in URI, should be '&'

... wsmancli tells you this.
So not all selectors are reconized and the server responds with

> [...]
>       <s:Detail>
>         <wsman:FaultDetail>http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InsufficientSelectors</wsman:FaultDetail>
>       </s:Detail>

InsufficientSelectors

>     </s:Fault>
>   </s:Body>
> </s:Envelope>
>
> [root@localhost openwsman_scripts]# cat export_config_xml.sh
> #! /bin/bash
>
> wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName="DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

Looks like the " is wrongly placed for Name=DCIM:"LCService"

Too bad Dell does not publish MOF definitions for DCIM_ classes. With
a MOF, I could check the key definitions for DCIM_LCService.

Hth,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

I corrected the placement of  “ and still same failure.

 

All MOFs and Profiles are posted on Dell Tech Center site. Here’s the link to LC Management profile:

 

http://en.community.dell.com/techcenter/extras/m/white_papers/20441094

 

 

Thanks

Tex

 

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Friday, March 11, 2016 7:01 AM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

* [hidden email] [Mar 10. 2016 17:12]:
>
> wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem",CreationClassName="DCIM_LCService",SystemName="DCIM:ComputerSystem",Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

This one is wrong and ...

>
> [root@localhost openwsman_scripts]# ./export_config_xml.sh
> 192.168.0.121 Maybe wrong use of ',' separator in URI, should be '&'

... wsmancli tells you this.
So not all selectors are reconized and the server responds with

> [...]
>
> http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InsufficientSelectors
>

InsufficientSelectors

>
>
>
>
> [root@localhost openwsman_scripts]# cat export_config_xml.sh #!
> /bin/bash
>
> wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName="DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name=DCIM:"LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "ShareType=0" -k "FileName=config.xml" -k "Target=BIOS,NIC"

Looks like the " is wrongly placed for Name=DCIM:"LCService"

Too bad Dell does not publish MOF definitions for DCIM_ classes. With a MOF, I could check the key definitions for DCIM_LCService.

Hth,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* [hidden email] <[hidden email]> [Mar 11. 2016 17:15]:
> Dell - Internal Use - Confidential
> I corrected the placement of  " and still same failure.

Hmm. Then please add "-R" (--dump-request) to the wsman command and
send me the output.

Thanks,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* Klaus Kaempf <[hidden email]> [Mar 11. 2016 20:10]:
> * [hidden email] <[hidden email]> [Mar 11. 2016 17:15]:
> > Dell - Internal Use - Confidential
> > I corrected the placement of  " and still same failure.
>
> Hmm. Then please add "-R" (--dump-request) to the wsman command and
> send me the output.

Also please change the order of the -k parameters and place "FileName" before
"ShareType".

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

 [root@localhost openwsman_scripts]# cat export_config_xml.sh

#! /bin/bash

 

wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName="DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name="DCIM:LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "FileName=config.xml" -k "ShareType=0" -k "Target=BIOS,NIC" -R

 

[root@localhost openwsman_scripts]# ./export_config_xml.sh 192.168.0.121

<?xml version="1.0"?>

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:n1="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService">

  <s:Header>

    <wsa:Action s:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService/ExportSystemConfiguration</wsa:Action>

    <wsa:To s:mustUnderstand="true">https://192.168.0.121:443/wsman</wsa:To>

    <wsman:ResourceURI s:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService</wsman:ResourceURI>

    <wsa:MessageID s:mustUnderstand="true">uuid:d493c283-2dca-1dca-8002-083d105d1500</wsa:MessageID>

    <wsa:ReplyTo>

      <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>

    </wsa:ReplyTo>

    <wsman:SelectorSet>

      <wsman:Selector Name="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName">DCIM_ComputerSystem</wsman:Selector>

      <wsman:Selector Name="Name">DCIM:LCService</wsman:Selector>

      <wsman:Selector Name="SystemName">DCIM:ComputerSystem</wsman:Selector>

      <wsman:Selector Name="CreationClassName">DCIM_LCService</wsman:Selector>

    </wsman:SelectorSet>

  </s:Header>

  <s:Body>

    <n1:ExportSystemConfiguration_INPUT>

      <n1:IPAddress>192.168.0.120</n1:IPAddress>

      <n1:ShareName>/nfs</n1:ShareName>

      <n1:FileName>config.xml</n1:FileName>

      <n1:ShareType>0</n1:ShareType>

      <n1:Target>BIOS,NIC</n1:Target>

    </n1:ExportSystemConfiguration_INPUT>

  </s:Body>

</s:Envelope>

<?xml version="1.0" encoding="UTF-8"?>

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">

  <s:Header>

    <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

    <wsa:Action>http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</wsa:Action>

    <wsa:RelatesTo>uuid:d493c283-2dca-1dca-8002-083d105d1500</wsa:RelatesTo>

    <wsa:MessageID>uuid:2767a488-2dc9-1dc9-9665-d6f0fb722ab8</wsa:MessageID>

  </s:Header>

  <s:Body>

    <s:Fault>

      <s:Code>

        <s:Value>s:Sender</s:Value>

        <s:Subcode>

          <s:Value>wsman:InvalidSelectors</s:Value>

        </s:Subcode>

      </s:Code>

      <s:Reason>

        <s:Text xml:lang="en">The Selectors for the resource are not valid.</s:Text>

      </s:Reason>

    </s:Fault>

  </s:Body>

</s:Envelope>

[root@localhost openwsman_scripts]#

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Friday, March 11, 2016 1:18 PM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

* Klaus Kaempf [Mar 11. 2016 20:10]:
> * [hidden email] [Mar 11. 2016 17:15]:
> > Dell - Internal Use - Confidential
> > I corrected the placement of " and still same failure.
>
> Hmm. Then please add "-R" (--dump-request) to the wsman command and
> send me the output.

Also please change the order of the -k parameters and place "FileName" before "ShareType".

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* [hidden email] <[hidden email]> [Mar 11. 2016 20:26]:
> Dell - Internal Use - Confidential
>  [root@localhost openwsman_scripts]# cat export_config_xml.sh
> #! /bin/bash
>
> wsman invoke 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName="DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name="DCIM:LCService"' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k "ShareName=/nfs" -k "FileName=config.xml" -k "ShareType=0" -k "Target=BIOS,NIC" -R
[...]
>     <wsman:SelectorSet>
>       <wsman:Selector Name="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName">DCIM_ComputerSystem</wsman:Selector>

Hmm, it is the URI parsing indeed.

What does "wsman --version" report ?

Can you update openwsman and wsmancli to a later version ?

My local system (running 2.6.0) does not show this behaviour.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

My system is currently at 2.6.0 version which is the system I’ve been using to execute invoke commands.

 

[root@localhost openwsman_scripts]# wsman --version

wsmancli 2.6.0 (201506160922)

 

[root@localhost openwsman_scripts]# rpm -qa | grep -i wsman

wsmancli-2.6.0-1.fc23.x86_64

openwsman-client-2.6.1-1.fc24.x86_64

libwsman1-2.6.0-2.fc23.x86_64

[root@localhost openwsman_scripts]#

 

 

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Friday, March 11, 2016 1:45 PM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

* [hidden email] [Mar 11. 2016 20:26]:


> Dell - Internal Use - Confidential
> [root@localhost openwsman_scripts]# cat export_config_xml.sh #!
> /bin/bash
>
> wsman invoke
> 'http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCSe
> rvice?SystemCreationClassName="DCIM_ComputerSystem"&CreationClassName=
> "DCIM_LCService"&SystemName="DCIM:ComputerSystem"&Name="DCIM:LCService
> "' -h $1 -V -v -c dummy.cert -P 443 -u root -p calvin -a
> ExportSystemConfiguration -k "IPAddress=192.168.0.120" -k
> "ShareName=/nfs" -k "FileName=config.xml" -k "ShareType=0" -k
> "Target=BIOS,NIC" -R
[...]
>
> <wsman:Selector
> Name="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM
> _LCService?SystemCreationClassName">DCIM_ComputerSystem</wsman:Selecto
> r>

Hmm, it is the URI parsing indeed.

What does "wsman --version" report ?

Can you update openwsman and wsmancli to a later version ?

My local system (running 2.6.0) does not show this behaviour.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* [hidden email] <[hidden email]> [Mar 11. 2016 21:56]:

> Dell - Internal Use - Confidential
> My system is currently at 2.6.0 version which is the system I've been using to execute invoke commands.
>
> [root@localhost openwsman_scripts]# wsman --version
> wsmancli 2.6.0 (201506160922)
>
> [root@localhost openwsman_scripts]# rpm -qa | grep -i wsman
> wsmancli-2.6.0-1.fc23.x86_64
> openwsman-client-2.6.1-1.fc24.x86_64
> libwsman1-2.6.0-2.fc23.x86_64

wsmancli and libwsman1 seem to be correct. What is openwsman-client
and from where did you get it ?

Can you try the official builds from
https://build.opensuse.org/package/show/Openwsman/openwsman ?

Thanks,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

With same wsmancli, I updated only libwsman to the version in the link you sent and “&” separator works now. Here’s my system versions now:

 

[root@localhost openwsman_scripts]# rpm -qa | grep -i wsman

wsmancli-2.6.0-1.fc23.x86_64

libwsman3-2.6.2-170.3.x86_64

 

So for backwards compatibility with using “,” separator, this will not be supported correct? If users decide to update to latest wsmancli, they will have to use “&” and change all their scripts.

 

Thanks

Tex

 

 

 

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Monday, March 14, 2016 2:47 AM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

* [hidden email] [Mar 11. 2016 21:56]:


> Dell - Internal Use - Confidential
> My system is currently at 2.6.0 version which is the system I've been using to execute invoke commands.
>
> [root@localhost openwsman_scripts]# wsman --version wsmancli 2.6.0
> (201506160922)
>
> [root@localhost openwsman_scripts]# rpm -qa | grep -i wsman
> wsmancli-2.6.0-1.fc23.x86_64
> openwsman-client-2.6.1-1.fc24.x86_64
> libwsman1-2.6.0-2.fc23.x86_64

wsmancli and libwsman1 seem to be correct. What is openwsman-client and from where did you get it ?

Can you try the official builds from
https://build.opensuse.org/package/show/Openwsman/openwsman ?

Thanks,

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Klaus Kaempf
* [hidden email] <[hidden email]> [Mar 14. 2016 18:33]:
> Dell - Internal Use - Confidential
> With same wsmancli, I updated only libwsman to the version in the link you sent and "&" separator works now.

Great ! From where did you get the old libwsman package ? Is it from
an official Fedora release ?


>
> So for backwards compatibility with using "," separator, this will not be supported correct?

Correct. It esp. conflicts with WINRM, which uses "," insided values.
Supporting "," was wrong from the beginning. Use "&" or ";", these
separators are standards-conforming.

> If users decide to update to latest wsmancli, they will have to use "&"
> and change all their scripts.

Yes, sorry. There's no simple way to make this change
backwards-compatible.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Invoke commands not working with 2.4 or newer wsmancli

Texas_Roemer

Dell - Internal Use - Confidential

It didn’t come with the ISO like RHEL and SLES which comes with the rpms needed to support wsman in linux, I downloaded it from rpmfind site:

 

https://www.rpmfind.net/linux/rpm2html/search.php?query=libwsman&submit=Search+...&system=&arch=

 

Thanks

Tex

 

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Tuesday, March 15, 2016 2:55 AM
To: Roemer, Texas
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Invoke commands not working with 2.4 or newer wsmancli

* [hidden email] [Mar 14. 2016 18:33]:
> Dell - Internal Use - Confidential
> With same wsmancli, I updated only libwsman to the version in the link you sent and "&" separator works now.

Great ! From where did you get the old libwsman package ? Is it from an official Fedora release ?


>
> So for backwards compatibility with using "," separator, this will not be supported correct?

Correct. It esp. conflicts with WINRM, which uses "," insided values.
Supporting "," was wrong from the beginning. Use "&" or ";", these separators are standards-conforming.

> If users decide to update to latest wsmancli, they will have to use "&"
> and change all their scripts.

Yes, sorry. There's no simple way to make this change backwards-compatible.

Klaus
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Loading...