Bug 1625681 - [OSP13][OCTAVIA] OSP13 minor update causes existing Octavia LBs to be in PENDING_UPDATE state
Summary: [OSP13][OCTAVIA] OSP13 minor update causes existing Octavia LBs to be in PEND...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Carlos Goncalves
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-05 14:20 UTC by rlopez
Modified: 2019-09-10 14:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-03 20:41:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
First Part of tar.xz (15.00 MB, application/x-xz)
2018-09-05 14:20 UTC, rlopez
no flags Details
Second Part of tar.xz (15.00 MB, application/octet-stream)
2018-09-05 14:20 UTC, rlopez
no flags Details
Third Part of tar.xz (1.70 MB, application/octet-stream)
2018-09-05 14:21 UTC, rlopez
no flags Details

Description rlopez 2018-09-05 14:20:22 UTC
Created attachment 1481103 [details]
First Part of tar.xz

Description of problem:

I recently just successfully completed a minor OSP13 update that completed succesfully, however, it has left my existing Octavia load balancers in a PENDING_STATE and the amphora image in a PENDING_CREATE state. I believe this might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1623146 , however, the /var/log/containers/octavia directory does not show any errors in the logs. Aside from the SOS report from controller-0, let me know if you need anything else. Due to the size of the SOS report, I broke it up into 3 parts. 

This command can be used to recombine it:

ls -1c -v sosreport-RLopez-20180905131839.tar.xz.part* | xargs -I {} cat {} >> sosreport-RLopez-20180905131839.tar.xz


Steps to Reproduce:
1. Create LBs on an existing OSP13 environment
2. Do a minor update of the OSP13 environment as seen in this document: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/keeping_red_hat_openstack_platform_updated/ 

3. Check status of the LBs: openstack loadbalancer list

4. Check status of the amphora: openstack loadbalancer amphora list

Comment 1 rlopez 2018-09-05 14:20:58 UTC
Created attachment 1481104 [details]
Second Part of tar.xz

Comment 2 rlopez 2018-09-05 14:21:24 UTC
Created attachment 1481105 [details]
Third Part of tar.xz

Comment 3 rlopez 2018-09-11 14:25:49 UTC
Can I get an update to this BZ? I'm planning on removing the resources but want to know if you need anything else before I do.

Thanks,

Roger

Comment 4 Nir Magnezi 2018-10-03 13:17:02 UTC
Carlos will take a look at this one.

Comment 5 Carlos Goncalves 2018-10-03 16:18:11 UTC
From the logs you provided, I can't see anything relevant either. Most likely logs from other controllers would help, but I understand if you don't have the deployment anymore. If you can reproduce it, please attach sosreports from all controllers.

Comment 6 rlopez 2018-10-03 20:28:01 UTC
Hi Carlos,

Yeah I don't have this deployment anymore. If I run into this again I will open a new BZ.

Comment 7 Carlos Goncalves 2018-10-03 20:41:08 UTC
Understood. Thank you nonetheless for testing and reporting!


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