Hide Forgot
Description of problem: Anaconda installation throw error message. 19:38:19,117 CRIT anaconda: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 184, in storageInitialize storage.reset() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 489, in reset self.devicetree.populate(cleanupOnly=cleanupOnly) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2228, in populate self._populate() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2295, in _populate self.addUdevDevice(dev) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1285, in addUdevDevice self.handleUdevDeviceFormat(info, device) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1981, in handleUdevDeviceFormat self.handleUdevLVMPVFormat(info, device) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1629, in handleUdevLVMPVFormat self.handleVgLvs(vg_device) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1566, in handleVgLvs addLV(lv) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1513, in addLV addRequiredLV(origin_device_name, "failed to locate origin lv") File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1426, in addRequiredLV File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1540, in addLV exists=True, **lv_kwargs) File "/usr/lib/python2.7/site-packages/blivet/devices/lvm.py", line 517, in __init__ exists=exists) File "/usr/lib/python2.7/site-packages/blivet/devices/dm.py", line 73, in __init__ parents=parents, sysfsPath=sysfsPath) File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 130, in __init__ Device.__init__(self, name, parents=parents) File "/usr/lib/python2.7/site-packages/blivet/devices/device.py", line 84, in __init__ raise ValueError("%s is not a valid name for this device" % name) ValueError: ovirt-node-ng-4.0.0-0.3.master.20160325135421.git02e2f29.el7 is not a valid name for this device 19:38:19,121 DEBUG anaconda: Gtk running, queuing exception handler to the main loop 19:38:19,121 INFO anaconda: Thread Done: AnaPayloadThread (139908968818432) 19:38:19,919 DEBUG anaconda: network standalone spoke (init): completed: ['eth0'] Version-Release number of selected component (if applicable): master branch in ovirt-node-ng tree How reproducible: make installed-squashfs make debug-installed The debug operation stuck, open the virtual machine via virt-manager and will see the message.
Created attachment 1141326 [details] anaconda logs
We might be using a LVM name which is not suitable for blivet.
(In reply to Fabian Deutsch from comment #2) > We might be using a LVM name which is not suitable for blivet. Others references with similar problem: ValueError: /data is not a valid name for this device https://bugzilla.redhat.com/show_bug.cgi?id=1219749 ValueError: cciss/c0d0 is not a valid name for this device https://bugzilla.redhat.com/show_bug.cgi?id=1103751
According to the blivet code, LVM devices should be at max 55 chars. $ echo -n ovirt-node-ng-4.0.0-0.3.master.20160325135421.git02e2f29.el7 | wc -c 60 The name of the LV is to long.
One patch no verifies the LVM name The other patch reduces the default NVR of the image
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Should be fixed in ovirt-node-ng-installer-master-20160406.iso
Test with the latest master branch in ovirt-node-ng, the bug cannot reproduced. Steps: 1. dnf install lorax libvirt libvirt-daemon-kvm virt-install libguestfs-tools 2. git clone git://gerrit.ovirt.org/ovirt-node-ng.git 3. ./autogen.sh 4. make squashfs 5. make installed-squashfs 6. make debug-installed Result: Install successfully. The bug is verified, so I change the status to VERIFIED.
oVirt 4.0.0 has been released, closing current release.