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 688062 - fish: add luks-open mapped device to tab completion list
Summary: fish: add luks-open mapped device to tab completion list
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libguestfs
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 07:46 UTC by Jinxin Zheng
Modified: 2011-12-06 10:31 UTC (History)
2 users (show)

Fixed In Version: libguestfs-1.7.17-24.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:31:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1512 0 normal SHIPPED_LIVE libguestfs bug fix update 2011-12-06 00:39:11 UTC

Description Jinxin Zheng 2011-03-16 07:46:56 UTC
Description of problem:
Currently no one tells where the mapped device created by luks-open is. It's completely the user's job to read the manual and take '/dev/mapper/mapname'. Guestfish should help to remember this name.

Version-Release number of selected component (if applicable):
libguestfs-1.7.17-15.el6

How reproducible:
always

Steps to Reproduce:
1.
...
><fs> luks-open /dev/sda1 map1
Enter key or passphrase ("key"): 
><fs> list-devices 
/dev/vda
><fs> list-filesystems 
><fs> mount /dev/[TAB]
/dev/vda   /dev/vda1  

  
Actual results:
We wanted to get the mapped device name from the tab completion, but failed.
We can't either see it from list-devices or list-filesystems.
However, `mount /dev/mapper/map1 / ` works fine.

Comment 1 Richard W.M. Jones 2011-06-10 09:59:33 UTC
Let's try to fix this for 6.2.  Should be very simple.

Comment 2 Richard W.M. Jones 2011-07-12 12:41:41 UTC
Patch posted upstream:

https://www.redhat.com/archives/libguestfs/2011-July/msg00020.html

Comment 4 Richard W.M. Jones 2011-08-10 16:01:00 UTC
https://brewweb.devel.redhat.com/taskinfo?taskID=3546057

Comment 6 Jinxin Zheng 2011-08-23 09:21:24 UTC
Reproduced in -1.7.17-19 and verified in -1.7.17-26.

$ guestfish
><fs> sparse test.img 100M
><fs> run
><fs> part-disk /dev/sda mbr
><fs> luks-format /dev/sda1 1
Enter key or passphrase ("key"): 
><fs> luks-open /dev/sda1 luks1
Enter key or passphrase ("key"): 
><fs> mount /dev/[TAB]
/dev/mapper/luks1  /dev/vda           /dev/vda1

(-19 does not have the /dev/mapper/luks1 entry, -26 does.)

Comment 7 errata-xmlrpc 2011-12-06 10:31:30 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.

http://rhn.redhat.com/errata/RHBA-2011-1512.html


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