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