kolla

openstack release tag needs to be updated for latest stable mitaka release

Bug #1605061 reported by Rahul Sharma
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Critical
Rahul Sharma
kolla 2.0.3 "mitaka"

Bug Description

Currently, the tag in etc/kolla/globals.yml is:
# Valid option is Docker repository tag
#openstack_release: "2.0.2"

However, the latest release of stable/mitaka builds images with tag "2.0.3". The default value used in etc/kolla/globals.yml needs to be updated.

See original description
Rahul Sharma (rahulsharmaait)
Changed in kolla:
assignee: nobody → Rahul Sharma (rahulsharmaait)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/345166

Swapnil Kulkarni (coolsvap-deactivatedaccount)
Changed in kolla:
status: New → In Progress
importance: Undecided → High
Rahul Sharma (rahulsharmaait)
summary: - docker registry tag needs to be updated for latest stable mitaka release
+ openstack release tag needs to be updated for latest stable mitaka
+ release
Steven Dake (sdake)
Changed in kolla:
importance: High → Critical
milestone: none → newton-3
Revision history for this message
Dave Walker (davewalker) wrote :

So this is a problem I started looking at a few weeks ago, because on Master i kept struggling with image versions always being 3.0.0 - with different results on each node.

I started experimenting, and I was thinking something along the lines of this (shown as a standalone example):
https://github.com/Daviey/tmp-kolla-version

Revision history for this message
Dave Walker (davewalker) wrote :

Note, that tagged releases wouldn't have the devX junk, but the clean version number as desired.

Fresh installs would have globals.yml: openstack_release: "current" and work as expected, but deployers could pin to a version by putting a version number in there.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/345166
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=358bb3821369e206aaaa7796ec618de03baf48b4
Submitter: Jenkins
Branch: stable/mitaka

commit 358bb3821369e206aaaa7796ec618de03baf48b4
Author: Rahul Sharma <email address hidden>
Date: Thu Jul 21 01:26:55 2016 -0400

    updates default registry tag to latest version

    Previously, it was pointing to 2.0.2 and the images built were
    with tag 2.0.3. This fix updates the default version to 2.0.3

    Closes-Bug: 1605061

    Change-Id: I836e553c9054d5ee5948f02c30bdd1324d5c1c73

tags: added: in-stable-mitaka
Swapnil Kulkarni (coolsvap-deactivatedaccount)
Changed in kolla:
milestone: newton-3 → 2.0.3
zhubingbing (zhubingbing)
Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 2.0.3

This issue was fixed in the openstack/kolla 2.0.3 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.