When apt sources are changed, the old config is left behind causing conflicts

Bug #1473525 reported by Bjoern
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Low
Major Hayden
Kilo
Fix Released
Low
Major Hayden
Liberty
Fix Released
Low
Major Hayden
Trunk
Invalid
Low
Major Hayden

Bug Description

A upgrade from 10.1.10 to kilo (branch) did fail with the error during a apt-get update :

0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.W: Duplicate sources.list entry http://mirror.rackspace.com/mariadb/repo/5.5/ubuntu/ trusty/main amd64 Packages (/var/lib/apt/lists/mirror.rackspace.com_mariadb_repo_5.5_ubuntu_dists_trusty_main_binary-amd64_Packages)
W: Duplicate sources.list entry http://mirror.rackspace.com/mariadb/repo/5.5/ubuntu/ trusty/main i386 Packages (/var/lib/apt/lists/mirror.rackspace.com_mariadb_repo_5.5_ubuntu_dists_trusty_main_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems

The issues seems to be inside the mirror_rackspace_com_mariadb_repo_5_5_ubuntu.list after we added the https mirror URL

deb https://mirror.rackspace.com/mariadb/repo/5.5/ubuntu trusty main
deb http://mirror.rackspace.com/mariadb/repo/5.5/ubuntu trusty main

inside the apt_repository task.
At this point we should unregister the old repo (http)

Changed in openstack-ansible:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Bjoern Teipel (bjoern-teipel)
Revision history for this message
Nolan Brubaker (nolan-brubaker) wrote :

I can confirm I'm seeing this on a 10.1.10 to kilo head (SHA 221daab63f6a1d2032eddb132cf25846f3d893ec) upgrade. However, my install finished successfully.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/201691

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/201696

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-ansible-deployment (kilo)

Change abandoned by Jesse Pretorius (<email address hidden>) on branch: kilo
Review: https://review.openstack.org/201691
Reason: Abandoning the kilo review until the master review https://review.openstack.org/201696 is merged.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote : Re: Duplicate sources.list entry for mariadb during kilo upgrade

As there doesn't appear to be any consensus on the approach and the patch hasn't been actively worked on for some time, the milestone target has been shifted to 11.1.1. Please discuss this at either of the two community meetings (Tue/Thu) if this is not a suitable milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-ansible-deployment (master)

Change abandoned by Jesse Pretorius (<email address hidden>) on branch: master
Review: https://review.openstack.org/201696
Reason: No activity for over a month. Please restore this patch if/when it will be worked on again.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote : Re: Duplicate sources.list entry for mariadb during kilo upgrade

Removing the assignee and changing the status to new to discuss this at the next bug triage meeting.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Setting trunk to invalid as this is not applicable to the Kilo->Liberty upgrade.

Revision history for this message
Bjoern (bjoern-t) wrote :

FYI, during the latest upgrade test I did not see this issues again, because we are simply not adding the SSL repo in the repo file anymore.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Marking as invalid as per BJoern's feedback.

Revision history for this message
Bjoern (bjoern-t) wrote :

It seems we still encounter this issue reported at 1506975

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Setting trunk to invalid as this is not applicable to the Kilo->Liberty upgrade.

summary: - Duplicate sources.list entry for mariadb during kilo upgrade
+ When apt sources are changed, the old config is left behind causing
+ conflicts
Revision history for this message
Bjoern (bjoern-t) wrote :

So it seems this issue make more sense to fix once https://github.com/ansible/ansible-modules-core/pull/2696 has been merged.
That fix will add the option to specify a fixed filename for a repo configuration.
Other then that we can only proceed with https://review.openstack.org/#/c/201696/ which would remove old files before putting a new config in place.

Revision history for this message
Major Hayden (rackerhacker) wrote :

It looks like the ansible module PR merged -- can this bug move forward now, Bjoern?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/289977

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (kilo)

Reviewed: https://review.openstack.org/289977
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=235c2b29be7fa4777a455377f401066e557c9f21
Submitter: Jenkins
Branch: kilo

commit 235c2b29be7fa4777a455377f401066e557c9f21
Author: Major Hayden <email address hidden>
Date: Tue Mar 22 08:03:09 2016 -0500

    Remove old MariaDB apt sources

    In Juno, MariaDB's apt sources used plaintext HTTP. This causes
    problems for Kilo upgrades since the new apt sources use HTTPS urls.
    This patch adds an upgrade playbook that removes any sources left
    over from Juno that use HTTP.

    Closes-Bug: 1473525

    Change-Id: Ia10d9dc1eff624bca785805a910ee7835a559463

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
David Wilde (dave-wilde) wrote :

This will need to be forwarded into Liberty as environments that upgraded to older versions of Kilo and then on to Liberty will hit this issue.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (liberty)

Reviewed: https://review.openstack.org/309170
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=613473db20fec87501f157811905a116639dc4f9
Submitter: Jenkins
Branch: liberty

commit 613473db20fec87501f157811905a116639dc4f9
Author: Major Hayden <email address hidden>
Date: Thu Apr 21 15:17:09 2016 -0500

    Remove old MariaDB repos during upgrades

    This upgrade playbook removes older MariaDB apt repositories
    which used HTTP URLs.

    Closes-bug: 1473525

    Change-Id: Id02c4aca108bb35182a622865e8a00d9b7182f5a

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.15

This issue was fixed in the openstack/openstack-ansible 11.2.15 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.12

This issue was fixed in the openstack/openstack-ansible 12.0.12 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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