upgrade step might fail due to old yum caches

Bug #1588738 reported by Michele Baldessari on 2016-06-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

So before we do a yum update -q -y in the main upgrade step. We need to do a yum clean all before as

I noticed my L->M upgrades failing because the newly added mitaka repos were not picked up
automatically by yum. I overwrote the existing liberty repos with the following steps:

curl -o /etc/yum.repos.d/delorean.repo http://trunk.rdoproject.org/centos7-mitaka/current-passed-ci/delorean.repo
curl -o /etc/yum.repos.d/delorean-deps.repo http://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo

Changed in tripleo:
importance: Undecided → High
status: New → Triaged
Jiří Stránský (jistr) wrote :

This could be an issue on all node types. I wonder if we should clean the cache globally as part of major-upgrade-pacemaker-init.yaml step.

Michele Baldessari (michele) wrote :

I think this makes sense yes. It would reduce the chance of any errors on all nodes

Emilien Macchi (emilienm) wrote :

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in tripleo:
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for tripleo because there has been no activity for 60 days.]

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

Other bug subscribers