Bug 923459

Summary:	F19 pre-Alpha TC1 network installs stop at "Starting package installation process" (anaconda is stuck in a loop between writev and recvfrom)
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
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:	unspecified
Version:	19	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, jreznik, mkolman, robatino, satellitgo, sbueno, shawn.starr, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:	AcceptedBlocker
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-20 19:50:13 UTC	Type:	Bug
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:	834084

Description Adam Williamson 2013-03-19 22:00:06 UTC

Using this test image bcl built on 2013-03-18:

https://alt.fedoraproject.org/pub/alt/anaconda/anaconda-19.11-1.boot.iso

both bcl and I are seeing that, once install hits yum - UI displays "Starting package installation process" - it proceeds extremely slowly. Mine's been sitting at "Starting package installation process" for about five minutes now. Looking behind the scenes indicates nothing has crashed or gone wrong, everything appears to be running as expected, just very very slow. We are both running in VMs (him via virt-install, me via virt-manager).

bcl writes:

<bcl> yep. yum seems extremely slow. stracing the anaconda process shows it stuck in a loop between writev and recvfrom, so something related to networking.
<bcl> I can just wget just fine though.

Proposing as an Alpha blocker, criterion https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria#Remote_package_sources :

"When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources. The network install image must default to a valid publicly-accessible package source."

Practically speaking, the slowness is such that this is effectively not possible. It'd presumably finish some time in the DISTANT FUTURE.

Comment 1 Adam Williamson 2013-03-20 16:31:46 UTC

Discussed at 2013-03-20 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.log.txt . Accepted as a blocker per criterion cited in description.

Comment 2 Adam Williamson 2013-03-20 19:50:13 UTC

923951 is more useful.

*** This bug has been marked as a duplicate of bug 923951 ***