When apt sources are changed, the old config is left behind causing conflicts
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://
W: Duplicate sources.list entry http://
W: You may want to run apt-get update to correct these problems
The issues seems to be inside the mirror_
deb https:/
deb http://
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) |
summary: |
- Duplicate sources.list entry for mariadb during kilo upgrade + When apt sources are changed, the old config is left behind causing + conflicts |
I can confirm I'm seeing this on a 10.1.10 to kilo head (SHA 221daab63f6a1d2 032eddb132cf258 46f3d893ec) upgrade. However, my install finished successfully.