Ubuntu
ubiquity package

apt-install fails during success-command because target environment cannot resolve DNS

Bug #1061242 reported by Max Brustkern
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
High
Dimitri John Ledkov
ubiquity (Ubuntu)
Invalid
High
Unassigned

Bug Description

I'm trying to preseed an install using a quantal amd64 desktop image:
Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121002)
with md5sum 5d984d0bcf7e4f8752a7110fafca9201. apt-install commands run during the ubiquity success-command in a preseed are failing. When I open a console and chroot into /target, I don't appear to have DNS resolution.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.12.7
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.325
Date: Wed Oct 3 21:15:16 2012
InstallCmdLine: automatic-ubiquity boot=casper keyboard-configuration/layoutcode=us noprompt
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121002)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

lp:~xnox/utah/fix-chroot
Max Brustkern (community): Approve
Diff: 15 lines (+2/-3)
1 file modified
utah/provisioning/provisioning.py (+2/-3)
Revision history for this message
Max Brustkern (nuclearbob) wrote :
Brian Murray (brian-murray)
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Gema Gomez (gema)
tags: added: rls-r-incoming
tags: added: iso-testing qa-daily-testing
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Looking at the logs:
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-desktop-amd64-smoke-default/20/

The bug description does not much the logs.

Looking at lp:utah the code there does not much the generated late-command in the jenkins job.

Can you please clarify the source code that generates the late-command?

To fix the issue you are experiencing please try the following in the late_command:
* bind mount /run as /target/run before chroot into /target

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Javier Collado (javier.collado)
Changed in utah:
status: New → Triaged
importance: Undecided → High
Dimitri John Ledkov (xnox)
Changed in utah:
status: Triaged → Confirmed
assignee: nobody → Dmitrijs Ledkovs (xnox)
Javier Collado (javier.collado)
Changed in utah:
status: Confirmed → Triaged
Max Brustkern (nuclearbob)
Changed in utah:
status: Triaged → In Progress
Javier Collado (javier.collado)
Changed in utah:
status: In Progress → Fix Committed
Javier Collado (javier.collado)
Changed in utah:
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

Given that this was fixed in UTAH, I'm going to assume the ubiquity task is Invalid.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.