Bug 588207 - Logical volume name is invalid
Logical volume name is invalid
Status: CLOSED DUPLICATE of bug 600639
Product: Fedora
Classification: Fedora
Component: schroot (Show other bugs)
12
All Linux
low Severity medium
: ---
: ---
Assigned To: Zach Carter
Fedora Extras Quality Assurance
:
Depends On: 588200
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-03 03:01 EDT by Oron Peled
Modified: 2010-06-09 12:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-09 12:37:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Oron Peled 2010-05-03 03:01:38 EDT
Description of problem:
Using schroot with type=lvm-snapshot fails because the snapshot
logical volume name chosen by schroot is illegal.

Version-Release number of selected component (if applicable):
schroot-1.2.3-3.fc12.i686

How reproducible:
Create an lvm-snapshot schroot (for example, like in bug #588200).
Trying to enter this schroot fails.

Actual results:
Running:
 [root@argon schroot]# schroot -c lenny-i386
 Logical volume name "lenny-i386-2010-05-03T06:33:59Z-31230" is invalid
 Run `lvcreate --help' for more information.
 E: lenny-i386-2010-05-03T06:33:59Z-31230: Chroot setup failed: stage=setup-start

Expected results:
A snapshot logical volume of the chroot should have been created and that
schroot should enter into the chroot environment.

Additional info:
Entering the source (not snapshot) of the same schroot works:
 [root@argon ~]# schroot -c lenny-i386-source
 I: [lenny-i386-source chroot] Running login shell: ‘/bin/bash’

Searching for the limitation, I bumped across this relevant bug report:
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg476634.html
Comment 1 Zach Carter 2010-06-09 12:37:43 EDT

*** This bug has been marked as a duplicate of bug 600639 ***

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