Bug 1373378
Summary: | Applying errata RHBA-2016:1645 causing different behaviour of applying custom values on systems | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Steffen Froemer <sfroemer> |
Component: | Client | Assignee: | Tomáš Kašpárek <tkasparek> |
Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 570 | CC: | rdrazny, tlestach |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spacecmd-2.5.0-15-sat | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 07:58:38 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1450111, 1450940 |
Description
Steffen Froemer
2016-09-06 07:00:46 UTC
Actually every call which uses quotes in order to pass multi-word parameters into spacecmd is broken, e.g. system_addnote. spacewalk.git(master): 4d71d82eaa4b15bdae8e9718d169de832fabd84e Reproduced on spacecmd-2.5.0-14.el6sat using the reproducer from the initial report. The bug is valid only for the "spacecmd command" call directly from system shell. Running a command from spacecmd shell works as expected. On spacecmd-2.5.0-16.el6sat: $ spacecmd system_updatecustomvalue SAMPLE_VALUE "four five six seven eight" clien7.testing.mylocal $ spacecmd system_listcustomvalues clien7.testing.mylocal INFO: Connected to https://satellite.server.com/rpc/api as admin SAMPLE_VALUE = four five six seven eight Beside spaces, I have tested inserting tabs (Ctrl+V Ctrl+I) and newlines (Ctrl-V Ctrl+J). All were correctly inserted into custom value field. VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3445 |