Support minor updates, which in our case is mostly about Amphora image updates. We added[1] the support for glance tags, which means Octavia will always use the latest (timestamp) image loaded to glance that is tagged with a specific value (amp_image_tag = amphora by default). For security reasons, this is also restricted to a specific image owner, configured in amp_image_owner_id We should test and verify this upgrade process works in a live deployment, and possibly automate the process and have it running in CI. [1] https://review.openstack.org/#/c/284690/
Steps- 1. Upload Amphora image to Glance with proper tag for amphora. 2. Run LB tests 3. Upload different image to Glance with proper tag for amphora. 4. Run LB tests. *!* The image could be build on top of supported OSs( rhel, Centos) or supplied as already LB amphora dedicated images.
(In reply to Alexander Stafeyev from comment #2) > Steps- > > 1. Upload Amphora image to Glance with proper tag for amphora. > 2. Run LB tests > 3. Upload different image to Glance with proper tag for amphora. > 4. Run LB tests. > > *!* The image could be build on top of supported OSs( rhel, Centos) or > supplied as already LB amphora dedicated images. You need to test update including Container update ( while amphora is the old one) and amphora works the same after the update ( new house keeper didn't remove it and HA still works )
This is testing only bug, no dev work required. Putting to POST.
(In reply to Alexander Stafeyev from comment #2) > Steps- > > 1. Upload Amphora image to Glance with proper tag for amphora. > 2. Run LB tests > 3. Upload different image to Glance with proper tag for amphora. > 4. Run LB tests. > > *!* The image could be build on top of supported OSs( rhel, Centos) or > supplied as already LB amphora dedicated images. I would expend the above steps as follows: 1. Upload the first amphora image. 2. Create a loadbalancer and check basic sanity (loadbalancer ACTIVE) 3. via admin user: get the details about the current amphora instance (openstack server show <amphora instance id>) 4. Upload another image to glance. 5. Repeat step 2. 6. Repeat step 3. and verify the instance got created from the newly uploaded imaged.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086