settingsLogin | Registersettings

[openstack-dev] [tripleo] TripleO Ocata release blockers

0 votes

I found useful to share the reasons why we didn't release TripleO RC1
last week and what are the remaining blockers.

  • Nova from trunk doesn't work for TripleO. We have to pin Nova to
    ocata-3 if we want to continue the promotions in our CI.

Some work is in progress to solve this problem, you can follow it here:
https://review.openstack.org/#/q/status:open+topic:bug/1661360

TL;DR: we're disabling Nova API in WSGI with Apache when deploying
TripleO & Puppet OpenStack CI.

  • Fix updating images in promotion pipeline:
    https://review.openstack.org/#/c/429713

  • Upgrades from Newton to Ocata. The list of bugs / work in progress
    is still consequent, it doesn't make sense to release before we have
    them fixed. Composable upgrades are our essential blueprint for Ocata.

I proposed https://review.openstack.org/#/c/428416/ to prepare TripleO
RC1 but I won't update it before our blockers are solved.

Any help, feedback or question is very welcome.
Thanks,
--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Feb 14, 2017 in openstack-dev by emilien_at_redhat.co (36,940 points)   2 7 13

3 Responses

0 votes

Quick updates:

At this stage, I believe we can release TripleO Ocata RC1 by Thursday
17th, considering Congress will be landed, 1663187 fixed, no new
blocker in CI.

I think upgrade folks will still have some patches after Thursday, but
I don't think it's a big deal, we'll just backport them to
stable/ocata.

Please let us know asap if you see more blockers for Ocata RC1.

On Mon, Feb 6, 2017 at 9:19 AM, Emilien Macchi emilien@redhat.com wrote:
I found useful to share the reasons why we didn't release TripleO RC1
last week and what are the remaining blockers.

  • Nova from trunk doesn't work for TripleO. We have to pin Nova to
    ocata-3 if we want to continue the promotions in our CI.

Some work is in progress to solve this problem, you can follow it here:
https://review.openstack.org/#/q/status:open+topic:bug/1661360

TL;DR: we're disabling Nova API in WSGI with Apache when deploying
TripleO & Puppet OpenStack CI.

  • Fix updating images in promotion pipeline:
    https://review.openstack.org/#/c/429713

  • Upgrades from Newton to Ocata. The list of bugs / work in progress
    is still consequent, it doesn't make sense to release before we have
    them fixed. Composable upgrades are our essential blueprint for Ocata.

I proposed https://review.openstack.org/#/c/428416/ to prepare TripleO
RC1 but I won't update it before our blockers are solved.

Any help, feedback or question is very welcome.
Thanks,
--
Emilien Macchi

--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 12, 2017 by emilien_at_redhat.co (36,940 points)   2 7 13
0 votes

On 02/12/2017 02:24 PM, Emilien Macchi wrote:
Quick updates:

At this stage, I believe we can release TripleO Ocata RC1 by Thursday
17th, considering Congress will be landed, 1663187 fixed, no new
blocker in CI.

I think upgrade folks will still have some patches after Thursday, but
I don't think it's a big deal, we'll just backport them to
stable/ocata.

Please let us know asap if you see more blockers for Ocata RC1.

I would like to propose https://bugs.launchpad.net/tripleo/+bug/1664331
as a release blocker, mostly because if someone ran an undercloud
upgrade without us fixing that I believe it could break their undercloud
Heat in a way that would be difficult to recover from (should probably
discuss that with the Heat team though to make sure I'm not wrong about
the impact).

If we can't fix it before release, then I think we should at least merge
the stackrcexists fix and essentially block undercloud upgrades until
we fix the member role logic. That way we can backport the fix knowing
that no one has run a bad upgrade.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 13, 2017 by Ben_Nemec (19,660 points)   2 3 3
0 votes

On 02/13/2017 12:52 PM, Ben Nemec wrote:

On 02/12/2017 02:24 PM, Emilien Macchi wrote:

Quick updates:

At this stage, I believe we can release TripleO Ocata RC1 by Thursday
17th, considering Congress will be landed, 1663187 fixed, no new
blocker in CI.

I think upgrade folks will still have some patches after Thursday, but
I don't think it's a big deal, we'll just backport them to
stable/ocata.

Please let us know asap if you see more blockers for Ocata RC1.

I would like to propose https://bugs.launchpad.net/tripleo/+bug/1664331
as a release blocker, mostly because if someone ran an undercloud
upgrade without us fixing that I believe it could break their undercloud
Heat in a way that would be difficult to recover from (should probably
discuss that with the Heat team though to make sure I'm not wrong about
the impact).

If we can't fix it before release, then I think we should at least merge
the stackrcexists fix and essentially block undercloud upgrades until
we fix the member role logic. That way we can backport the fix knowing
that no one has run a bad upgrade.

I take it all back. :-)

After some more investigation into this, I discovered that this is a
workaround for a problem that dates back to the downstream-only kilo
release, so it's absence isn't actually a critical problem. There's a
simple manual workaround that users would have had to use in the
intervening releases anyway.

It would still be nice to fix this, but it doesn't need to block the
release.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Feb 14, 2017 by Ben_Nemec (19,660 points)   2 3 3
...