If someone reports problems upgrading their firefly cluster to hammer, and
the problem is in firefly, will we publish a new firefly release?
If someone reports problems upgrading their dumpling cluster to firefly, and
the problem is in dumpling, will we publish a new dumpling release?
Probably not. But, we do know that upgrades work now and so any new
failures must be a failure of the new version of Hammer. That, we
would hopefully avoid releasing, and would definitely issue a fix
release for. :) We can't strand users!
Several people have looked at the upgrade/firefly-x (hammer) failures
and nobody has found anything that wasn't an issue with the tests
themselves. Maybe you could take a look, too?
http://pulpito.ceph.com/teuthology-2017-01-30_20:52:09-upgrade:firefly-x-hammer-distro-basic-vps/
Note that this QE run was done against the old gitbuilder build system.
Yuri has some special technique for achieving that ;-)
This is because the old builds that are needed to run the tests were/are
missing in the new build system. Injecting the old gitbuilder builds
into the new system is apparently possible, but a manual hit-or-miss
process. See http://tracker.ceph.com/issues/18089
(David Galloway has been _very_ helpful there, but the issues persist.)
This issue is affecting the jewel rados suite, even, since that suite
includes a couple tests that install various dumpling and firefly
releases and then upgrade them.
Thanks,
Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
