Bug 1427888 - spacecmd system_runscript does not take system ID as argument
Summary: spacecmd system_runscript does not take system ID as argument
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks: sat580-low
TreeView+ depends on / blocked
 
Reported: 2017-03-01 13:08 UTC by Lukáš Hellebrandt
Modified: 2017-06-21 12:17 UTC (History)
2 users (show)

Fixed In Version: spacecmd-2.5.0-9-sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-21 12:17:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukáš Hellebrandt 2017-03-01 13:08:27 UTC
Description of problem:
Rather than identifying system with a non-unique name, one might want to use it's ID. In other commands, you just use it in place of name. In system_runscript command, however, when you do this, you get an error:

ERROR: sequence item 0: expected string, int found

How reproducible:
Deterministic

Steps to Reproduce:
system_runscript <ID> -uroot -groot -t600 -snow -lLABEL -f/root/script.sh

Actual results:
Error shown above

Expected results:
Behavior consistent with other commands when identifying a system with it's ID

Comment 1 Lukáš Hellebrandt 2017-03-02 15:18:16 UTC
Same bug for

system_reboot

Comment 2 Tomáš Kašpárek 2017-03-02 15:34:44 UTC
spacewalk.git(master): 445e102a8deef48a0f188a28de1bb3a5943c5383

Comment 3 Tomáš Kašpárek 2017-03-02 15:36:53 UTC
ignore comment#2 please, will fix this systematically...

Comment 4 Tomáš Kašpárek 2017-03-02 15:40:49 UTC
spacewalk.git(master): fb7a9fe8517219a6fc1dbd2c848f929da9b1e642

Comment 7 Lukáš Hellebrandt 2017-03-07 10:27:30 UTC
Verified with spacecmd-2.5.0-9.

It is now possible to use system ID in both system_reboot and system_runscript.


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