| Summary: | spacecmd adds weird [?1034h escape sequence in output | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Amit Upadhye <aupadhye> |
| Component: | spacecmd | Assignee: | Miroslav Suchý <msuchy> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | el6 | CC: | marcel.wysocki, msuchy |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-30 15:33:48 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: | |
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: # spacecmd -u ${SATELLITEUSER} -p ${SATELLITEPASSWORD} -- configchannel_list | grep "_tue-aim-vm" |hexdump -C INFO: Spacewalk Username: satadmin INFO: Connected to https://localhost/rpc/api as satadmin 00000000 1b 5b 3f 31 30 33 34 68 5f 74 75 65 2d 61 69 6d |.[?1034h_tue-aim| 00000010 2d 76 6d 0a |-vm.| 00000014 Version-Release number of selected component (if applicable): spacecmd-1.7.7-1.el6.noarch How reproducible: Every time Steps to Reproduce: Running spacecmd command with above options. Actual results: It adds escape characters at the beginning. Expected results: It should not add escape characters at beginning of configuration channel name. Additional info: