[openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

Alan Pevec apevec at gmail.com
Mon Mar 13 16:26:39 UTC 2017

2017-03-13 15:49 GMT+01:00 Doug Hellmann <doug at doughellmann.com>:
> We test this upgrade scenario in the upstream CI, too. The difference
> is that grenade can tell pip "install exactly the version I am
> pointing to in this directory on disk," rather than relying on
> version numbers to notice that an upgrade is needed (or should be
> avoided, as the case may be).
> Is it possible to do that with system packages in some way, too, without
> pinning package versions in puppet or tripleo?

That would not test the regular update flow, we'd have to use
workaround for the period before milestone 1
and run explicit yum downgrade with the explicit package list to force
lower version packages to install.
That means real upgrades would not be tested until this kludge is
removed after first milestone is released.
Instead, I'll look at adding automatic bump in RDO Trunk builder
before milestone1 i.e. when it detects master version is lower than
stable branches.


More information about the OpenStack-dev mailing list