[Bug 1061242] Re: apt-install fails during success-command because target environment cannot resolve DNS
Dmitrijs Ledkovs
launchpad at surgut.co.uk
Thu Dec 6 14:59:49 UTC 2012
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
** Also affects: utah
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1061242
Title:
apt-install fails during success-command because target environment
cannot resolve DNS
Status in Ubuntu Test Automation Harness:
New
Status in “ubiquity” package in Ubuntu:
Incomplete
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/utah/+bug/1061242/+subscriptions
More information about the foundations-bugs
mailing list