oem-config prompts for tasksel configuration multiple times during the install

Bug #986203 reported by Pete Graner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
High
Unassigned

Bug Description

Installing the /20120419.2/precise-preinstalled-server-armhf+omap4.img.gz image, I get prompted for configuation questions for each tasksel item I selected, in this case, LAMP, Mailserver.

The progress bar increases after each round.

I was prompted for the mysql-server password 3 times and the postfix "which type of installation" 3 times.

Everything did install properly:

ubuntu@panda-es:~$ ps -ef | grep apache
root 9277 1 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 9279 9277 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 9280 9277 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 9281 9277 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 9282 9277 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
www-data 9283 9277 0 20:02 ? 00:00:00 /usr/sbin/apache2 -k start
ubuntu 24210 24179 0 20:13 ttyO2 00:00:00 grep --color=auto apache
ubuntu@panda-es:~$ ps -ef | grep mysql
mysql 5618 1 0 19:58 ? 00:00:04 /usr/sbin/mysqld
ubuntu 24212 24179 0 20:14 ttyO2 00:00:00 grep --color=auto mysql
ubuntu@panda-es:~$ ps -ef | grep postfix
root 6579 1 0 20:00 ? 00:00:00 /usr/lib/postfix/master
postfix 6580 6579 0 20:00 ? 00:00:00 pickup -l -t fifo -u -c
postfix 6581 6579 0 20:00 ? 00:00:00 qmgr -l -t fifo -u
ubuntu 24214 24179 0 20:14 ttyO2 00:00:00 grep --color=auto postfix

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/986203

tags: added: iso-testing
Gema Gomez (gema)
tags: added: qa-manual-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in livecd-rootfs (Ubuntu):
status: New → Confirmed
Revision history for this message
Gema Gomez (gema) wrote :

I have witnessed the exact same thing when installing the pre-release server image.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Did not happen when selecting "basic Ubuntu server" and "SSH server only". I wonder if it is related to LAMP

Revision history for this message
Steve Langasek (vorlon) wrote :

Adam, do you have time to check whether this is fixed by the newly-spinning images today? If not, please unassign.

Changed in livecd-rootfs (Ubuntu):
assignee: nobody → Adam Conrad (adconrad)
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
Adam Conrad (adconrad) wrote :

Okay, I can reproduce this on the latest images. Not entirely sure what to make of it yet. Given that the fields aren't even filled in on the second or third go, it looks like the debconf DB isn't being written to correctly at some point.

Changed in livecd-rootfs (Ubuntu):
status: Triaged → Confirmed
Revision history for this message
Adam Conrad (adconrad) wrote :

I wonder if this might be some debconf-in-debconf madness with oem-config spawning tasksel, and the world having a bit of a sad.

Thankfully, everything works after you answer the prompts 3 times (pre-configure, config, postinst, I assume?), but it sure is an ugly behaviour.

Reassigning to ubiquity for now, as I suspect that might be the issue. Probably don't have the time to delve into it, so unassigning, but I'll look tomorrow while packing.

Changed in livecd-rootfs (Ubuntu):
assignee: Adam Conrad (adconrad) → nobody
affects: livecd-rootfs (Ubuntu) → ubiquity (Ubuntu)
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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