Bug 621685

Summary: TypeError: sequence item 0: expected string, NoneType found
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: adirusf, anaconda-maint-list, awilliam, bcl, benedictus, cpanceac, cramer, david250, dtimms, filcole, flokip, gjansen, goldlyron, jonathan, jturner, lgraves, mblankenfeld, mniu, mockusmeister, mschmidt, norrist, rhe, schaiba, seandarcy, stephent98, tgutwin, twoerner, vanmeeuwen+fedora
Target Milestone: ---Keywords: CommonBugs
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:dd5d9121b3d09d62c51159d6dde2a7400f97d3cefe16fbc6f506624182844a89 https://fedoraproject.org/wiki/Common_F14_bugs#incomplete-previous-install
Fixed In Version: anaconda-14.16-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-01 16:43:36 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:
Bug Depends On:    
Bug Blocks: 538277    
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description James Laska 2010-08-05 19:52:03 UTC
The following was filed automatically by anaconda:
anaconda 14.14 exception report
Traceback (most recent call first):
  File "/tmp/updates/pyanaconda/upgrade.py", line 86, in findRootParts
    oldInstalls += " on ".join(info)
  File "/tmp/updates/pyanaconda/dispatch.py", line 212, in moveStep
    rc = stepFunc(self.anaconda)
  File "/tmp/updates/pyanaconda/dispatch.py", line 131, in gotoNext
    self.moveStep()
  File "/tmp/updates/pyanaconda/gui.py", line 1262, in setScreen
    self.anaconda.dispatch.gotoNext()
  File "/tmp/updates/pyanaconda/gui.py", line 1175, in nextClicked
    self.setScreen ()
TypeError: sequence item 0: expected string, NoneType found

Comment 1 James Laska 2010-08-05 19:52:09 UTC
Created attachment 436963 [details]
Attached traceback automatically from anaconda.

Comment 2 James Laska 2010-08-05 20:24:23 UTC
Testing F-14-Alpha TC#2 with an updates.img that pulls in all recent anaconda changes, hits the above traceback.  This appears to be the result of installing to system on top of a previously incomplete install.  Talking to clumens, we agreed this likely won't impact a significant number of F14Alpha users considering the exceptional conditions around the issue.  An updates.img will be available for those users.

Comment 3 Radek Vykydal 2010-08-06 10:45:46 UTC
*** Bug 621119 has been marked as a duplicate of this bug. ***

Comment 4 AdiRusF 2010-08-06 13:02:45 UTC
Created attachment 437140 [details]
Attached traceback automatically from anaconda.

Comment 5 Brian Lane 2010-08-06 17:06:28 UTC
*** Bug 621100 has been marked as a duplicate of this bug. ***

Comment 6 He Rui 2010-08-11 07:34:39 UTC
Created attachment 438098 [details]
Attached traceback automatically from anaconda.

Comment 7 He Rui 2010-08-11 07:36:51 UTC
After the system encountered bug#590640 with unfinished install, this issue can be reproduced on it.

Comment 8 Michal Schmidt 2010-08-11 12:48:21 UTC
Created attachment 438178 [details]
Attached traceback automatically from anaconda.

Comment 9 James Laska 2010-08-11 18:07:12 UTC
When documenting this issue for F-14-Alpha CommonBugs, one can create a updates.img that includes the change referenced at http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=1cf0ab74176b8203ffb590c47c508716fb4a5727

Comment 10 Flóki Pálsson 2010-08-14 13:35:41 UTC
Created an attachment (id=438794)
Attached traceback automatically from anaconda.

Comment 11 David Timms 2010-08-15 03:40:49 UTC
Created an attachment (id=438809)
Attached traceback automatically from anaconda.

Comment 12 David Timms 2010-08-15 03:53:46 UTC
(In reply to comment #11)
> Created an attachment (id=438809)
> Attached traceback automatically from anaconda.
The QEMU storage in this case was screwed up by problem in F14alphaRC2 (which I forgot about). It seems such a situation could be more nicely explained to user.

Comment 13 Radek Vykydal 2010-08-16 09:57:02 UTC
*** Bug 624318 has been marked as a duplicate of this bug. ***

Comment 14 cornel panceac 2010-08-19 12:31:12 UTC
Created an attachment (id=439666)
Attached traceback automatically from anaconda.

Comment 15 cornel panceac 2010-08-19 12:38:58 UTC
Created an attachment (id=439670)
Attached traceback automatically from anaconda.

Comment 16 James Laska 2010-08-19 12:52:47 UTC
A workaround is to manually remove the incomplete disk configuration using parted or 'dd'.  Alternatively, an updates image is available for test at http://jlaska.fedorapeople.org/updates/621685.img

Comment 17 cornel panceac 2010-08-20 06:00:29 UTC
Created an attachment (id=439867)
Attached traceback automatically from anaconda.

Comment 18 cornel panceac 2010-08-20 06:04:59 UTC
Created an attachment (id=439868)
Attached traceback automatically from anaconda.

Comment 19 cornel panceac 2010-08-20 06:18:14 UTC
i get over it by removing the existing lvm. (while leaving alone the /boot partition). affects both rc3 and rc4.

Comment 20 Geert Jansen 2010-08-23 08:49:39 UTC
Created an attachment (id=440323)
Attached traceback automatically from anaconda.

Comment 21 Mike Chambers 2010-08-23 09:19:02 UTC
Created an attachment (id=440340)
Attached traceback automatically from anaconda.

Comment 22 Mike Chambers 2010-08-23 22:34:12 UTC
Created an attachment (id=440515)
Attached traceback automatically from anaconda.

Comment 23 Lawrence Graves 2010-08-24 13:15:16 UTC
Created an attachment (id=440651)
Attached traceback automatically from anaconda.

Comment 24 Chris Lumens 2010-08-24 20:07:52 UTC
*** Bug 626993 has been marked as a duplicate of this bug. ***

Comment 25 Sigitas Mockus 2010-08-25 14:10:15 UTC
Created an attachment (id=440952)
Attached traceback automatically from anaconda.

Comment 26 Aioanei Rares 2010-08-25 16:54:43 UTC
Created an attachment (id=440995)
Attached traceback automatically from anaconda.

Comment 27 Bill Pemberton 2010-08-26 18:39:43 UTC
Created an attachment (id=441298)
Attached traceback automatically from anaconda.

Comment 28 Adam Williamson 2010-08-27 16:24:47 UTC
Discussed at today's blocker review meeting. We don't have an exact criterion to cover it, but 'The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above'  (final) is close enough. This should be fixed now anyway so we aren't too worried. We may propose a new criterion to cover handling existing disk contents.

Comment 29 Todd 2010-08-29 13:49:24 UTC
Created an attachment (id=441790)
Attached traceback automatically from anaconda.

Comment 30 Lawrence Graves 2010-08-31 20:32:22 UTC
Created an attachment (id=442272)
Attached traceback automatically from anaconda.

Comment 31 Ben Lambrechts 2010-09-03 06:12:17 UTC
Created an attachment (id=442800)
Attached traceback automatically from anaconda.

Comment 32 Ben Lambrechts 2010-09-03 06:15:18 UTC
Created an attachment (id=442801)
Attached traceback automatically from anaconda.

Comment 33 Phil Cole 2010-09-04 16:11:12 UTC
*** Bug 630254 has been marked as a duplicate of this bug. ***

Comment 34 Lawrence Graves 2010-09-04 16:23:20 UTC
Created an attachment (id=443067)
Attached traceback automatically from anaconda.

Comment 35 Chris Lumens 2010-09-04 21:22:01 UTC
*** Bug 630291 has been marked as a duplicate of this bug. ***

Comment 36 Jan Cramer 2010-09-09 04:49:09 UTC
Created an attachment (id=446135)
Attached traceback automatically from anaconda.

Comment 37 Thomas Woerner 2010-09-09 19:23:35 UTC
Created an attachment (id=446353)
Attached traceback automatically from anaconda.

Comment 38 Steve Tyler 2010-09-10 12:46:41 UTC
Created an attachment (id=446505)
Attached traceback automatically from anaconda.

Comment 39 Thomas Woerner 2010-09-10 12:59:22 UTC
Clearing the some 100 MB from the start of the partition I used for an aborted installation before solved this for me.

Comment 40 Steve Tyler 2010-09-10 13:22:32 UTC
(In reply to comment #38)
> Created an attachment (id=446505)
> Attached traceback automatically from anaconda.

This occurred when I restarted an install after aborting the previous one
shortly after packages were being downloaded. IIRC, I aborted with
ctrl-alt-del. Partitioning was done with custom layout and had one ext4 and one
swap.

After booting in rescue mode:
blkid can recognize both partitions and reports their UUIDs.
e2fsck does not report any problems with the ext4 partition.
The partition can be mounted and there are directories and files in it.

I recovered by deleting all partitions with fdisk while in rescue mode.

$ qemu-kvm -cdrom Fedora-14-Alpha-x86_64-netinst.iso -m 512m -hda foobar.img
-boot menu=on

$ qemu-img info foobar.img 
image: foobar.img
file format: raw
virtual size: 3.0G (3221225472 bytes)
disk size: 357M

Comment 41 David Bernier 2010-09-17 09:11:19 UTC
Created attachment 447950 [details]
Attached traceback automatically from anaconda.

Comment 42 David Bernier 2010-09-17 09:13:17 UTC
Created attachment 447952 [details]
Attached traceback automatically from anaconda.

Comment 43 James Laska 2010-09-27 19:13:47 UTC
This issue was not encountered while testing F-14-Beta.  Marking as VERIFIED.

Comment 44 Tom Gutwin 2010-09-30 01:16:41 UTC
Created attachment 450633 [details]
Attached traceback automatically from anaconda.

Comment 45 Tom Gutwin 2010-09-30 01:24:47 UTC
Fedora 14 beta i386 version still exists.

I had a 2nd primary partition with F9 on it that I was going to blow away anyway.
I will try to fdisk it away and try again.

Comment 46 Brian Lane 2010-09-30 04:25:58 UTC
That isn't F14 Beta. your report says anaconda 14.15 and Beta has 14.17 in it.

Comment 47 Adam Williamson 2010-10-01 16:43:36 UTC
we can close this, 14.17 has been pushed stable.

Comment 48 goldlyron 2010-12-20 01:20:47 UTC
Created attachment 469653 [details]
Attached traceback automatically from anaconda.

Comment 49 goldlyron 2010-12-20 01:21:35 UTC
Created attachment 469654 [details]
Attached traceback automatically from anaconda.

Comment 50 goldlyron 2010-12-20 01:26:23 UTC
Created attachment 469655 [details]
Attached traceback automatically from anaconda.

Comment 51 Manfred Blankenfeld 2013-06-17 04:40:25 UTC
Creating of livecds FC19 with spin-kickstarts ends with this output:

[code]
Traceback (most recent call last):
File "/bin/livecd-creator", line 237, in <module>
sys.exit(main())
File "/bin/livecd-creator", lin 218, in main
creator.install()
File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 655 in install
ayum.runInstall()
File "/usr/lib/python2.7/site-packages/imgcreate/yuminst.py", line 220, in runInstall
raise CreateError("Dependency check failed : %s" % "\n".join(deps))
TypeError: sequence item 0: expected string, tuple found
[/code]

2013-06-17

Manfred Blankenfeld

Comment 52 Brian Lane 2013-06-17 17:01:17 UTC
(In reply to Manfred Blankenfeld from comment #51)
> Creating of livecds FC19 with spin-kickstarts ends with this output:
> 
> [code]
> Traceback (most recent call last):
> File "/bin/livecd-creator", line 237, in <module>
> sys.exit(main())
> File "/bin/livecd-creator", lin 218, in main
> creator.install()
> File "/usr/lib/python2.7/site-packages/imgcreate/creator.py", line 655 in
> install
> ayum.runInstall()
> File "/usr/lib/python2.7/site-packages/imgcreate/yuminst.py", line 220, in
> runInstall
> raise CreateError("Dependency check failed : %s" % "\n".join(deps))
> TypeError: sequence item 0: expected string, tuple found
> [/code]
> 
> 2013-06-17
> 
> Manfred Blankenfeld

Please open a new bug for this against f19, also include the version of livecd-creator and yum that you have installed.