Bug 1264066

Summary:	cryptsetup is not printing error message when device exists
Product:	[Fedora] Fedora	Reporter:	Zdenek Kabelac <zkabelac>
Component:	cryptsetup	Assignee:	Milan Broz <gmazyland>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	agk, gmazyland, okozina
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-04 07:08:41 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:

Description Zdenek Kabelac 2015-09-17 12:24:09 UTC

Description of problem:

When I open crypt device - and I replace its table line with 'error' target,
and I run  luksOpen second time -  I get 'no error'message telling me
what's wrong - just return code is 1 - so something is wrong, but
normally I'm not exploring return code - so I'd prefer some error message.

Version-Release number of selected component (if applicable):
cryptsetup-1.6.8-2.fc24.x86_64

How reproducible:


Steps to Reproduce:
1. cryptsetup luksOpen /dev/vg/lvol0 mydev
2. mount /dev/mapper/mydev  /mnt/test
3. dmsetup remove --force  mydev
4. cryptsetup luksOpen /dev/vg/lvol0 mydev


Actual results:
return code is 1
no error is printed
/me being confused ;)

Expected results:
telling me, there is something wrong

Additional info:

Comment 1 Jan Kurik 2016-02-24 13:45:42 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 2 Fedora End Of Life 2017-07-25 19:17:14 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's 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 Fedora  'version'
of '24'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Jan Kurik 2017-08-15 06:52:00 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 4 Milan Broz 2018-04-04 07:08:41 UTC

# With recent cryptsetup, this happens

# cryptsetup luksOpen /dev/sdb x
Enter passphrase for /dev/sdb: 
Cannot use device x, name is invalid or still in use.

Closing as fixed in rawhide.