Bug 1224045
| Summary: | DeviceCreateError: ('Process reported exit code 1280: A volume group called fedora already exists.\n', 'fedora') | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Ruckman <mruckman> | ||||||||||||||||||||||||||
| Component: | python-blivet | Assignee: | Vratislav Podzimek <vpodzime> | ||||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 22 | CC: | anaconda-maint-list, bcl, dlehman, g.kaviyarasu, jfilak, jonathan, kparal, mruckman, pschindl, robatino, satellitgo, vanmeeuwen+fedora, vpodzime | ||||||||||||||||||||||||||
| Target Milestone: | --- | Keywords: | CommonBugs | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | i686 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:c6136a18f7ce8cb09de7009272109b4672437949528850ff0092d735e4530d83 RejectedBlocker https://fedoraproject.org/wiki/Common_F22_bugs#firmware-raid-problems-with-leftovers | ||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2016-07-19 14:11:58 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 1028536 [details]
File: anaconda-tb
Created attachment 1028537 [details]
File: anaconda.log
Created attachment 1028538 [details]
File: dnf.log
Created attachment 1028539 [details]
File: environ
Created attachment 1028540 [details]
File: lsblk_output
Created attachment 1028541 [details]
File: nmcli_dev_list
Created attachment 1028542 [details]
File: os_info
Created attachment 1028543 [details]
File: program.log
Created attachment 1028544 [details]
File: storage.log
Created attachment 1028545 [details]
File: syslog
Created attachment 1028546 [details]
File: ifcfg.log
Created attachment 1028547 [details]
File: packaging.log
Tested this with both the i386 netinst and live image. Mike reproduced this by installing on raid. Then he deleted raid and installed again and then created raid again and it failed on next installation. I tried to reproduce it, but I got crash on the beginning of the second installation (after I deleted RAID volume: bug 1208212). I think that these two bugs are related to how firmware raid handle creating and deleting of raid volumes. There are probably some leftovers from previous installations (or some flags are set which shouldn't). Proposed as a Blocker for 22-final by Fedora user roshi using the blocker tracking app because: Violates the following criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices." Discussed at today's go/no-go meeting [1]. This bug was rejected as F22 Final Blocker - This bug is a corner case, and while it does violate the criteria it's not severe enough to block the release for Fedora 22. [1] http://meetbot.fedoraproject.org/fedora-meeting-2/2015-05-22/f22_final_gono-go_meeting_-_2.2015-05-22-17.01.log.txt Another user experienced a similar problem:
I added /boot as a standard partion, then I accidentaly removed it (hit -) so I had to add it again. Finaly I renamed the vg to 'vgmain', the vg had fixed size, and I created LVs for /, /home, /var and swap. LVs were encrypted.
addons: com_redhat_kdump
cmdline: /usr/bin/python2 /sbin/anaconda
cmdline_file: inst.repo=nfs:nfs.englab.brq.redhat.com:/pub/fedora/linux/development/22/x86_64/os/ initrd=F22/latest/x86_64/initrd.img BOOT_IMAGE=F22/latest/x86_64/vmlinuz
dnf.rpm.log: May 27 04:23:31 INFO --- logging initialized ---
hashmarkername: anaconda
kernel: 4.0.4-301.fc22.x86_64
package: anaconda-22.20.13-1
product: Fedora
reason: DeviceCreateError: ('Process reported exit code 1280: Logical volume "00" already exists in volume group "vgmain"\n', 'vgmain-00')
release: Cannot get release name.
version: 22
I got the same backtrace but in my case logical volume "00" already existed in volume group 'vgmain'. The GUI created both /var and / LVs with Name "00" and it seems to me that the GUI does that because I renamed the vg. Patch for the issue hit by Jakub posted as a PR: https://github.com/rhinstaller/anaconda/pull/123 This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: Set up RAID0 array. Start anaconda. Select array in storage spoke. Begin installation. Crash. Version-Release number of selected component: anaconda-22.20.13-1 The following was filed automatically by anaconda: anaconda 22.20.13-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 501, in create raise errors.DeviceCreateError(str(e), self.name) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 303, in execute self.device.create() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 362, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 162, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1057, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib/python2.7/site-packages/pyanaconda/install.py", line 196, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, *args, **kwargs) DeviceCreateError: ('Process reported exit code 1280: A volume group called fedora already exists.\n', 'fedora') Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-i386 quiet dnf.rpm.log: May 22 05:42:45 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.4-301.fc22.i686 product: Fedora release: Cannot get release name. type: anaconda version: 22