do-release-upgrade failure (trusty->xenial) when squid3 is installed

Bug #1575946 reported by David Britton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
squid3 (Ubuntu)
New
Undecided
Unassigned
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hit errors completing the upgrade from trusty with 1.9.1 installed to xenial. Attaching contents of /var/log/dist-upgrade

Revision history for this message
David Britton (dpb) wrote :
Changed in maas:
milestone: none → 2.0.0
status: New → Triaged
Gavin Panella (allenap)
Changed in maas:
status: Triaged → New
Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
Revision history for this message
Newell Jensen (newell-jensen) wrote :

David,

I just upgraded from trusty to xenial with MAAS 1.9.1 installed and I did not run into the same errors that you did. I am wondering if it had to do with the options that you chose while upgrading?

1. I had some warning about squid3 and I clicked on 'y' to continue.
2. There was a long message about upgrading from postgresql-9.3 to postgresql-9.5, I clicked 'OK'.
3. There was a message about postgresql-common being modified locally, I clicked on 'Install package maintainer's version'. (I assume this is where you might have chosen differently).

Upgrading proceeded without any errors and I have a fully functional MAAS 2.0 version with xenial.

Could you verify the steps/options you chose while doing the upgrade?

Thanks,

Newell

Changed in maas:
status: New → Incomplete
Revision history for this message
Newell Jensen (newell-jensen) wrote :

David,

Actually I see the options you chose in screen.log. Taking a look now.

Revision history for this message
Newell Jensen (newell-jensen) wrote :

David,

My questions from comment #2 stand as from screenlog.0 it is hard to discern what options you chose for the popup questions. Thanks.

David Britton (dpb)
Changed in maas:
status: Incomplete → New
Revision history for this message
Blake Rouse (blake-rouse) wrote :

Others have ran into a similar issues perform "dist-upgrade" looking at the log has to do something with our dependency ordering.

dpkg: dependency problems prevent configuration of maas-region-controller:
 maas-region-controller depends on maas-dns (= 2.0.0~beta3+bzr4941-0ubuntu1); however:
  Package maas-dns is not configured yet.
 maas-region-controller depends on maas-region-api (= 2.0.0~beta3+bzr4941-0ubuntu1); however:
  Package maas-region-api is not installed.

dpkg: error processing package maas-region-controller (--configure):
 dependency problems - leaving unconfigured

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
tags: added: dist-upgrade
Revision history for this message
Blake Rouse (blake-rouse) wrote :

The reason the other dependencies didn't install:

dpkg: dependency problems prevent configuration of squid3:
 squid3 depends on squid3-common (= 3.3.8-1ubuntu6.6); however:
  Package squid3-common is not installed.
  Version of squid3-common on system, provided by squid-common:all, is <none>.
 squid (3.5.12-1ubuntu7) breaks squid3 (<< 3.5.12-1ubuntu1~) and is unpacked but not configured.
  Version of squid3 to be configured is 3.3.8-1ubuntu6.6.

dpkg: error processing package squid3 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maas-dns:
 maas-dns depends on maas-region-api (= 2.0.0~beta3+bzr4941-0ubuntu1); however:
  Package maas-region-api is not installed.

Revision history for this message
David Britton (dpb) wrote :

(sorry, I thought I commented earlier but I must not have hit post)

The options that Newell posted are the ones I selected.

LaMont Jones (lamont)
affects: maas → squid3 (Ubuntu)
Changed in squid3 (Ubuntu):
assignee: Newell Jensen (newell-jensen) → nobody
importance: Critical → Undecided
milestone: 2.0.0 → none
status: Triaged → New
summary: - dist-upgrade from trusty to xenial errors (maas 1.9 -> 2.0)
+ dist-upgrade from trusty to xenial errors when squid3 is installed on
+ trusty
summary: - dist-upgrade from trusty to xenial errors when squid3 is installed on
- trusty
+ do-release-upgrade failure (trusty->xenial) when squid3 is installed
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.