Bug 493523
| Summary: | Traceback on "write changes" when creating encrypted disk during install - install fails. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Wolf <mikewolf53> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | anaconda-maint-list, bcl, benedictus, cochranb, conlinpg, dan, eric, flokip, frankly3d, jdmulloy, jeff, pjones, rmaximo, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | anaconda_trace_hash:d41a6aea73372d473b5833a114a52b8cff6d3b108958ff919f41e16f3a46a1b9 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
=======
During install, select "Encrypt System", then press "Next".
Consequence:
============
Anaconda indicates file system is being created, then crashes, and install fails.
Fix:
====
Result:
=======
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-04-06 17:01:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 337718 [details]
Attached traceback automatically from anaconda.
Created attachment 337728 [details]
Attached traceback automatically from anaconda.
Created attachment 337916 [details]
Attached traceback automatically from anaconda.
Created attachment 338107 [details]
Attached traceback automatically from anaconda.
Created attachment 338240 [details]
Attached traceback automatically from anaconda.
The automatic addition in Comment #5 is actually for an x86_64 installation attempt. I attempted the install twice, first as a "replace existing system" installation using the medialess installation method listed in the Fedora 11 Installation Guide. With the first attempt, I had edited the volume group and logical volume names so they are unique, and I specified encryption for every volume. The blue bar indicating the filesystem is being created went back and forth wildly for a long time, then an exception window opened. My second attempt at installing was a DVD-based install. Again this is for x86_64 and I wanted to encrypt the partitions. For this second installation I accepted the default volume group and logical volume names that were offered. The same behavior as before occured. The system I'm using is a Dell Latitude E6400 notebook with 4 Gb of RAM. I use Fedora 10 on it most of the time. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: ======= During install, select "Encrypt System", then press "Next". Consequence: ============ Anaconda indicates file system is being created, then crashes, and install fails. Fix: ==== Result: ======= Traceback from comment #1 was i386 install from DVD on Dell Dimension 4700 w/512MB RAM. I changed the platform indicator above to "ALL" since we have i386 and x86_64. I should also note that the encryption step does appear to succeed, at least on some level. On subsequent attempts to install I was prompted to entry my passphrase before Anaconda would edit the filesystem. I agree with Brian in his Comment #9, the encryption step does appear to succeed, in my case with x86_64 install attempts. The existing Linux system I was replacing was also encrypted. It was a Fedora 10 x86_64 system with virtualization features installed and the filesystem was formatted as ext3. I had used the same passphrase for the Fedora 11 system as was on the old system. Created attachment 338275 [details]
Attached traceback automatically from anaconda.
Created attachment 338277 [details]
Attached traceback automatically from anaconda.
*** This bug has been marked as a duplicate of bug 492354 *** Created attachment 338890 [details]
Attached traceback automatically from anaconda.
Created attachment 339117 [details]
Attached traceback automatically from anaconda.
For anyone who ends up on this bug and sees that it is closed, there is a workaround located in the comments of Bug 493575. This bug was (indirectly) marked as a duplicate of that bug. Created attachment 339795 [details]
Attached traceback automatically from anaconda.
Created attachment 339954 [details]
Attached traceback automatically from anaconda.
Created attachment 340234 [details]
Attached traceback automatically from anaconda.
Created attachment 341048 [details]
Attached traceback automatically from anaconda.
Created attachment 341468 [details]
Attached traceback automatically from anaconda.
|
The following was filed automatically by anaconda: anaconda 11.5.0.38 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 371, in lvcreate raise LVMError("lvcreate failed for %s/%s" % (vg_name, lv_name)) File "/usr/lib/anaconda/storage/devices.py", line 1959, in create lvm.lvcreate(self.vg.name, self._name, self.size) File "/usr/lib/anaconda/storage/deviceaction.py", line 206, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 659, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 210, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 115, in turnOnFilesystems anaconda.id.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() LVMError: lvcreate failed for VolGroup/lv_swap