Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1359122 +++
Description of problem:
Anaconda installation to existing volume group with thinPool and thinLV on this thinPool, is failing.
Steps to reproduce:
1) Create partitioning with vg, thinPool and thinLV
2) Create kickstart which is installing to this existing thinLV with --useexisting parameter (on vg and thiPool too)
Actual results:
Crash in Summary hub
Expected results:
Should install when using existing partitioning
Aditional info:
--useexisting is working fine with "part" kickstart command
Version-Release number of selected component:
anaconda-25.19-1
The following was filed automatically by anaconda:
anaconda 25.19-1 exception report
Traceback (most recent call first):
File "/usr/lib/python3.5/site-packages/blivet/deviceaction.py", line 551, in __init__
raise ValueError("resource to create this format %s is unavailable" % fmt)
File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock
return m(*args, **kwargs)
File "/usr/lib64/python3.5/site-packages/pyanaconda/kickstart.py", line 961, in execute
devicetree.actions.add(ActionCreateFormat(device, fmt))
File "/usr/lib64/python3.5/site-packages/pyanaconda/kickstart.py", line 799, in execute
l.execute(storage, ksdata, instClass)
File "/usr/lib64/python3.5/site-packages/pyanaconda/kickstart.py", line 2220, in doKickstartStorage
ksdata.logvol.execute(storage, ksdata, instClass)
File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 379, in _doExecute
doKickstartStorage(self.storage, self.data, self.instclass)
File "/usr/lib64/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run
threading.Thread.run(self, *args, **kwargs)
ValueError: resource to create this format non-existent None is unavailable
Additional info:
addons: com_redhat_kdump, com_redhat_docker
cmdline: /usr/bin/python3 /sbin/anaconda
cmdline_file: initrd=/test/rawhide/initrd.img nokill resolution=1024x768 inst.repo=ftp://cobra02/rawhide/ ks=http://cobra02/ks/jk/testing.ks BOOT_IMAGE=/test/rawhide/vmlinuz
executable: /sbin/anaconda
hashmarkername: anaconda
kernel: 4.7.0-0.rc5.git1.1.fc25.x86_64
product: Fedora
release: Cannot get release name.
reproducible: Not sure how to reproduce the problem
type: anaconda
version: rawhide
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:09 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:11 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:12 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:14 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:16 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:17 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:18 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:47 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:48 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:47:50 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:48:03 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:48:07 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:48:09 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:48:10 EDT ---
--- Additional comment from Jiri Konecny on 2016-07-22 06:48:13 EDT ---
--- Additional comment from Jan Kurik on 2016-07-26 00:06:57 EDT ---
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
--- Additional comment from David Lehman on 2016-07-27 17:06:56 EDT ---
I think you missed --noformat. See if that helps. I don't see a blivet bug here by any stretch of the imagination.
--- Additional comment from Jiri Konecny on 2016-07-28 03:47:45 EDT ---
I have tested it with --noformat and I'm getting "not enough space for LVM requests" which is error too because I don't need any more space then before.
I tested it with --noformat on thinLV and also without --noformat parameter, result is the still the same.
I'm attaching new kickstart file.
--- Additional comment from Jiri Konecny on 2016-07-28 03:49 EDT ---
--- Additional comment from David Lehman on 2016-08-31 10:51:45 EDT ---
This is almost certainly happening in pyanaconda.kickstart.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2207