Wednesday, 2022-08-24

*** ysandeep|out is now known as ysandeep04:25
*** ysandeep is now known as ysandeep|afk07:00
*** ysandeep|afk is now known as ysandeep|break10:16
*** ysandeep|break is now known as ysandeep11:03
*** PrinzElvis_ is now known as PrinzElvis11:06
*** tweining___ is now known as tweining11:08
*** mnasiadka_ is now known as mnasiadka14:25
*** ysandeep is now known as ysandeep|dinner14:46
*** ysandeep|dinner is now known as ysandeep15:36
*** ysandeep is now known as ysandeep|out15:58
gthiemonge#startmeeting Octavia16:00
opendevmeetMeeting started Wed Aug 24 16:00:24 2022 UTC and is due to finish in 60 minutes.  The chair is gthiemonge. Information about MeetBot at
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'octavia'16:00
gthiemongehi folks!16:00
viks__hi, how do i change the load balancer status from ERROR to ACTIVE as the loadbalancer is working fine.. the loadbalancer went in to error state because of compute node rebooting..16:02
johnsomviks__ Use the load balancer failover function.16:02
johnsomCompute node rebooting (or the VM for that matter) can mean some of the cryptographic information was lost as it's in an encrypted RAM drive inside the amphora.16:04
gthiemonge#topic Announcements16:06
gthiemonge** OpenStack Zed schedule16:07
gthiemonge(same as last week ;))16:07
gthiemongenext week is the Feature Freeze/Final release for client libraries!16:07
johnsomNext week is the deadline for octavia-lib16:07
gthiemongeI see good progress on the reviews!16:07
gthiemongeat least: activity ;-)16:08
gthiemonge#link 16:08
johnsomI don't think we have anything expected for zed left in octavia-lib16:08
gthiemongeok, and we released octavia-lib 3.1.0 last week16:08
viks__johnsom: thanks..  for failover we need active-standby setup with anti-affinity right? with single node, it goes in to ` Pending Update ` and then back to `error`16:09
tweining... which means that I was able to finish the failover circuit breaker change16:10
johnsomviks__ No, it works with standalone as well.  It should not go back to error. What do the logs say for why it is going back to error?16:10
gthiemongehey you might have seen that I have created a lot of backports16:11
gthiemongeas the fixes for Zed are getting merged, I'm backporting them (I don't want to miss a fix)16:11
johnsomStandalone failover just has a short amount of downtime during a failover, were active/standby does not.16:11
gthiemongereviewing these backports is not really urgent16:11
johnsom+1 to doing backports as things merge.16:12
gthiemongeI think when Zed is released and those backports are merged, we will deliver a new stable releases16:12
tweiningalso worth mentioning: we had no bare rechecks recently. Our statistics are clean ATM16:12
gthiemongethe script is broken?16:13
gthiemongewell, this is great ;-)16:13
gthiemongeI mean 0 bare recheck16:14
gthiemongeCan we have a badge?16:14
gthiemonge"7 days since the last bare recheck"16:14
viks__johnsom: ` ComputeBuildException: Failed to build compute instance due to: {u'message': u'No valid host was found. There are not enough hosts available`16:15
johnsomviks__ Ok, so your nova is broken and we can't build a new amphora. You need to fix nova, then try again.16:16
viks__but the amphora instances are running fine, and the requests sent to load balancer being sent to the instances behind it..  i get appropriate response16:17
viks__only `provision state` is ERROR.. i.e. as mentioned in
gthiemonge#topic CI Status16:18
gthiemongenothing to report here16:18
johnsomviks__ Yep, that can be the case. Operating status will reflect that. But it may be out of sync with the control plane.16:18
viks__`provisioning status of ERROR, but an operating status of ONLINE`16:19
viks__is there any way to bring back the operating status in sysnc with control plane in such scenarios?16:19
johnsomviks__ Yep. Given the error from nova "No valid host was found.", you probably can't create new load balancers or VMs either.16:20
johnsomviks__ Yes, the failover mechanism is for correcting this issue.16:20
viks__johnsom: ok... i'll will further investigate  whats happening.. thanks for the quick response16:22
gthiemonge#topic Brief progress reports / bugs needing review16:23
johnsomI have been focused on reviews. Making my way through the subnet/multi-vip patch chain16:23
gthiemongeI did many reviews... that's all :D16:23
johnsomBig and complex patches....16:23
tweiningthe octavia priority review list lists two notifications implementations in addition to the one that was merged recently. shouldn't we remove them from the list?16:24
johnsomYeah, we should probably abandon those patches too16:25
gthiemongeyeah they are outdated and unmaintained16:25
gthiemongeExperimental multi-az support is also on the list, I know that it is not ready too16:25
gthiemonge"Use vip_subnet_selection_tag to select subnets" will conflict with the multi-subnets on members and multi-vip patches :/16:27
gthiemonge#topic Open Discussion16:30
johnsomFYI, from the discuss mailing list, there is more info on this story:!/story/200761916:30
johnsomThere appears to be an issue with one of the "special" token types and accessing barbican.16:31
* johnsom notes this is not related to the scoped tokens RBAC stuff16:31
gthiemongejohnsom: is it related to application credentials?16:32
johnsom"trust-scoped" tokens. I'm not 100% sure I even know what that is16:32
johnsomKong fixed it for neutron in the past.16:33
gthiemongeyeah we should ask for a simple reproducer (or advices for the conf)16:34
johnsomI just wanted to bring it up at the meeting so someone might be able to pick this up.16:36
gthiemongejohnsom: I will follow up in the story16:36
johnsomAwesome, thanks16:37
gthiemongeanything else?16:39
tweiningnot from me16:40
johnsomI don't think I have anything else16:40
gthiemongeok thank you guys16:42
opendevmeetMeeting ended Wed Aug 24 16:43:04 2022 UTC.  Information about MeetBot at . (v 0.1.4)16:43
opendevmeetMinutes (text):

Generated by 2.17.3 by Marius Gedminas - find it at!