[openstack-dev] [Fuel] Failed upgrade chain - 5.1 -> 5.1.1 -> 6.0
ikalnitsky at mirantis.com
Fri Nov 14 12:24:57 UTC 2014
I've filed a bug  and provide you a puppet output inside Nailgun
If I remove /etc/yum.repos.d/5.1.1_nailgun - the puppet works fine.
On Fri, Nov 14, 2014 at 1:51 PM, Matthew Mosesohn
<mmosesohn at mirantis.com> wrote:
> I'm trying to figure out where the failure is. The 5.1.1 and 6.0
> prebuilt containers contain the correct version of nailgun RPM
> pre-installed. It shouldn't matter if the versions are identical
> (which is a problem for sure).
> Can you open a bug and post upgrade logs? I'm interested to see which
> pieces cause the failure and this is some area I didn't plan for in
> container upgrades.
> Best Regards,
> Matthew Mosesohn
> On Fri, Nov 14, 2014 at 3:43 PM, Igor Kalnitsky <ikalnitsky at mirantis.com> wrote:
>> Hi folks,
>> Yesterday I performed the following upgrade chain:
>> 5.1 -> 5.1.1 -> 6.0
>> and upgrading to 6.0 was failed. I did some research and figure out
>> that Nailgun's container doesn't have Nailgun at all. So here's what
>> 1. When we're upgrading to 6.0 we already have three repos in the
>> system: 5.1, 5.1.1 and 6.0.
>> 2. When we start a new Nailgun container, it runs start.sh which runs
>> puppet .
>> 3. And puppet fails to install a Nailgun package. Why it's happened?
>> We have the same Nailgun version in both 5.1.1 and 6.0 repos, but
>> those packages have different dependencies. From yum's point of view,
>> the packages are same (since they have the same version), so yum tries
>> to install the Nailgun from 5.1.1 repo, but the container contains
>> already installed dependencies for the Nailgun from 6.0 (they were
>> installed during building container), and obviously it fails with
>> failed dependencies errors (we have higher versions in the system).
>> Well, the issue blocks complex upgrade chains and definitely we have
>> to do something ASAP.
>> In order to protect us from similar issues in future I propose next changes:
>> 1. Increase versions of all Fuel packages at least once per release.
>> 2. Remove a package installation code from manifests - the container
>> should not install packages, they should be installed during container
>> building process.
>> What do you think, folks?
>> : https://github.com/stackforge/fuel-main/blob/master/docker/nailgun/start.sh#L11
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev