install fails due to 404 error message

Bug #364321 reported by Brian Murray on 2009-04-20
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Wubi
Low
Agostino Russo

Bug Description

I was trying to install using Wubi (rev 128) from an Ubuntu i386 Desktop CD dated 20090420.1 and was notified, during the "Checking installation files" portion, that a download was unsuccessful due to receiving a HTTP Error 404 message. After clicking okay the installation quit and I was left with a partially installed Ubuntu.

Brian Murray (brian-murray) wrote :
Brian Murray (brian-murray) wrote :

Things seem to start to go wrong around here:

04-20 14:02 ERROR CommonBackend: Invalid md5 for ISO C:\ubuntu\install\installation.iso (b55eeb37baaf256831466c524d26cf1c != 66fa77789c7b8ff63130e5d5a272d67b)
None
04-20 14:02 DEBUG TaskList: ### Finished check_iso
04-20 14:02 DEBUG CommonBackend: Searching for local ISO
04-20 14:02 DEBUG CommonBackend: Could not find any ISO or CD, downloading one now
04-20 14:02 DEBUG TaskList: New task download
04-20 14:02 DEBUG TaskList: ### Running download...
04-20 14:02 DEBUG btdownloader: downloading http://cdimage.ubuntu.com/daily-live/20090420/jaunty-desktop-i386.iso.torrent > C:\ubuntu\install\jaunty-desktop-i386.iso
04-20 14:02 ERROR TaskList: problem getting response info - HTTP Error 404: Not Found

Dave Morley (davmor2) wrote :

this has happened to me too with the real build. I'm going to try removing 128 from the cd and see if I can get it to reproduce with the wubi-r128 built this morning instead

Changed in wubi:
status: New → Confirmed
Brian Murray (brian-murray) wrote :

It looks like the metalink files on cdimage that wubi checks were not up to date and the wrong md5sum and torrent link were being grabbed.

Regardless, wubi should deal with this somewhat better and not just quit with a partially installed system.

Agostino Russo (ago) wrote :

Brian, if the md5 check fails for an existing ISO/CD, and all download attempts fail, there isn't much else we can do I am afraid. Maybe we might have a more informative error message with so that users are notified that their ISO/CD is probably corrupted and they can either ignore the md5 check and/or download another ISO manually.

Brian Murray (brian-murray) wrote :

When attempting to install again after the metalink was fixed I had to first uninstall the installation that exploded. Could the install be rolled back so one doesn't have to perform the uninstall?

Agostino Russo (ago) wrote :

Yes, but in the next release, can you please open a new bug for that?

Changed in wubi:
assignee: nobody → Agostino Russo (ago)
importance: Undecided → Low

It seems wubi simply hangs on any error condition, not just 404. Another vote for this bug.

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers