+++ This bug was initially created as a clone of Bug #618207 +++
Description of problem:
When I try to create new LV and check "mount when rebooted" option and fill in mount point text field, I get this traceback:
Traceback (most recent call last):
File "/usr/share/system-config-lvm/InputController.py", line 656, in on_new_lv
if dlg.run() == False:
File "/usr/share/system-config-lvm/InputController.py", line 1351, in run
if self.apply() == True:
File "/usr/share/system-config-lvm/InputController.py", line 2041, in apply
Fstab.add(None, lv_path, mountpoint_new, filesys_new.fsname)
File "/usr/share/system-config-lvm/Fstab.py", line 27, in add
fstab = __remove_and_replace(dev_path_old, line)
File "/usr/share/system-config-lvm/Fstab.py", line 43, in __remove_and_replace
paths = get_all_paths(mnt_device)
File "/usr/share/system-config-lvm/Fstab.py", line 114, in get_all_paths
follow_links_to_target(dev_path, paths)
File "/usr/share/system-config-lvm/utilities.py", line 6, in follow_links_to_target
o, s = execWithCaptureStatus('/bin/readlink', ['/bin/readlink', '-e', path])
File "/usr/share/system-config-lvm/execute.py", line 15, in execWithCaptureStatus
res = execWithCaptureErrorStatus(bin, args)
File "/usr/share/system-config-lvm/execute.py", line 22, in execWithCaptureErrorStatus
command = command + ' ' + arg
TypeError: cannot concatenate 'str' and 'NoneType' objects
The dialog then stays stuck and must be closed with titlebar close button. The LV is created, filesystem is created, but /etc/fstab is not modified and filesystem is not mounted.
Version-Release number of selected component (if applicable):
system-config-lvm-1.1.14-2.fc13.noarch
How reproducible:
always
Steps to Reproduce:
1. Hit Create new LV
2. Select name, size, filesystem, select "mount when rebooted", fill in mount point
3. Hit OK
*** Bug 621139 has been marked as a duplicate of this bug. ***
Comment 7releng-rhel@redhat.com
2010-11-10 21:42:54 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.