Bug 1318297 - rhel-osd-director: Post upgrade to 8.0 adding new nodes to the Overlcoud should use 8.0 images.
Summary: rhel-osd-director: Post upgrade to 8.0 adding new nodes to the Overlcoud shou...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Angus Thomas
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 13:09 UTC by Omri Hochman
Modified: 2016-10-14 15:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 15:29:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Omri Hochman 2016-03-16 13:09:58 UTC
rhel-osd-director: Post upgrade to 8.0 adding new nodes to the Overlcoud should use 8.0 images.   

Environment:
-----------
instack-undercloud-2.2.5-1.el7ost.noarch
instack-0.0.8-2.el7ost.noarch
openstack-heat-engine-5.0.1-3.el7ost.noarch
openstack-tripleo-heat-templates-kilo-0.8.10-2.el7ost.noarch


Description:
-------------
after the upgrade process is finish, the undercloud and overcloud are in 8.0 version, 
but the images on the undercloud remain in 7.3.  so when we will scale-up, and add a new node to the overcloud post-upgrade, 
the new node will use the 7.3 images on the undercloud. 

we should verify that part of the upgrade process is to build the 8.0 newer-images and re-upload them using glance to replace the older 7.3 images.

Comment 1 Mike Burns 2016-04-07 21:14:44 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 2 James Slagle 2016-10-14 15:29:20 UTC
confirmed that this has been documented in the upgrade steps:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/director-installation-and-usage/103-updating-overcloud-images


Note You need to log in before you can comment on or make changes to this bug.