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.
Description of problem:
In beaker job xml I have the following partition specified
<partitions>
<partition fs="btrfs" name="/mnt/testarea" size="10" type="part"/>
</partitions>
And the installation aborted
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
threading.Thread.run(self, *args, **kwargs)
File "/usr/lib64/python2.7/threading.py", line 504, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall
turnOnFilesystems(storage)
File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 193, in turnOnFilesystems
skipRoot=False)
File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1655, in mountFilesystems
readOnly=readOnly, skipRoot=skipRoot)
File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2881, in mountFilesystems
chroot=rootPath)
File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 1140, in setup
return self.mount(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 594, in mount
raise FSError("filesystem has not been created")
pyanaconda.storage.errors.FSError:
filesystem has not been created
If I changed the fstype to other fs rather than btrfs the installation process goes fine
Version-Release number of selected component (if applicable):
anaconda 18.37.11
How reproducible:
always
Steps to Reproduce:
1. put the partition layout from description in beaker job xml and submit the job
or just clone my job https://beaker.engineering.redhat.com/recipes/808965
Additional info:
I'm not sure if it's really an anaconda bug, it might be a beaker bug.
I have a file system test case needs btrfs partition created at installation time, so it's kind of test blocker.
Sorry, I don't know how to gather that log. When the beaker job hangs, the ssh service is disabled so that I can not connect to the host. console gives me no shell. Can you give me some guidances? Thanks.
Comment 14Alexander Todorov
2013-06-12 09:51:10 UTC
David,
looking at the generated ks.cfg it seems that it's just wrong wrt btrfs special handling. That said this is a Beaker issue at the moment.
Is anaconda going to allow the part --fstype=btrfs syntax or Beaker needs to be adjusted?
I'm going to clone this bug against Beaker and leave it open for tracking. Let us know if you decide to modify anaconda behavior.
See the link in comment #13 for information on the kickstart 'btrfs' command. This should be explained in the Migration Planning Guide as well as the Installation Guide.
Agreed, comment #21 looks fine to me. When I reassign to the installation guide, I am assuming that docs will reassign to a more appropriate guide if necessary. In this case, the migration guide does make sense.
Description of problem: In beaker job xml I have the following partition specified <partitions> <partition fs="btrfs" name="/mnt/testarea" size="10" type="part"/> </partitions> And the installation aborted Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall turnOnFilesystems(storage) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 193, in turnOnFilesystems skipRoot=False) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1655, in mountFilesystems readOnly=readOnly, skipRoot=skipRoot) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2881, in mountFilesystems chroot=rootPath) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 1140, in setup return self.mount(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 594, in mount raise FSError("filesystem has not been created") pyanaconda.storage.errors.FSError: filesystem has not been created If I changed the fstype to other fs rather than btrfs the installation process goes fine Version-Release number of selected component (if applicable): anaconda 18.37.11 How reproducible: always Steps to Reproduce: 1. put the partition layout from description in beaker job xml and submit the job or just clone my job https://beaker.engineering.redhat.com/recipes/808965 Additional info: I'm not sure if it's really an anaconda bug, it might be a beaker bug. I have a file system test case needs btrfs partition created at installation time, so it's kind of test blocker.