Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1153974

Summary:	guestfish prints '\n' in error message
Product:	Red Hat Enterprise Linux 6	Reporter:	Lingfei Kong <lkong>
Component:	libguestfs	Assignee:	Pino Toscano <ptoscano>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.6	CC:	huzhan, jherrman, leiwang, mbooth, ptoscano, rjones, wshi
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libguestfs-1.20.11-12.el6	Doc Type:	Enhancement
Doc Text:	Minor fixes and improvements have been done to the help message of the "set-append" command, an error message of the "guestfish umount" command, and to the guestfish(1) and virt-edit(1) man pages.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-22 05:56:09 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:	923355
Bug Blocks:

Description Lingfei Kong 2014-10-17 08:29:07 UTC

Description of problem:
guestfish do not escape the'\n' in the error message


Version-Release number of selected component (if applicable):
libguestfs-tools-c-1.20.11-11.el6.x86_64


How reproducible:
100%


Steps to Reproduce:
#guestfish umount /
libguestfs: error: umount: call launch before using this function\n(in guestfish, don't forget to use the 'run' command)


Actual results:
guestfish do not escape the'\n' in the error message


Expected results:
#guestfish umount /
libguestfs: error: umount: call launch before using this function
(in guestfish, don't forget to use the 'run' command)


Additional info:

Comment 1 Pino Toscano 2014-10-17 08:38:00 UTC

(In reply to Lingfei Kong from comment #0)
> Description of problem:
> guestfish do not escape the'\n' in the error message

No, it has nothing to do with escaping, it is just a typo in the error message; see bug #923355 which was the upstream version of this.

Comment 3 Chao Zhang 2014-12-11 01:49:16 UTC

Verify with libguestfs-tools-c-1.20.11-12.el6.x86_64

Steps to verify:

#guestfish umount /
libguestfs: error: umount: call launch before using this function
(in guestfish, don't forget to use the 'run' command)

Comment 6 errata-xmlrpc 2015-07-22 05:56:09 UTC

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://rhn.redhat.com/errata/RHBA-2015-1444.html