*** ysandeep|out is now known as ysandeep | 04:25 | |
*** ysandeep is now known as ysandeep|afk | 07:00 | |
*** ysandeep|afk is now known as ysandeep|break | 10:16 | |
*** ysandeep|break is now known as ysandeep | 11:03 | |
*** PrinzElvis_ is now known as PrinzElvis | 11:06 | |
*** tweining___ is now known as tweining | 11:08 | |
*** mnasiadka_ is now known as mnasiadka | 14:25 | |
*** ysandeep is now known as ysandeep|dinner | 14:46 | |
*** ysandeep|dinner is now known as ysandeep | 15:36 | |
*** ysandeep is now known as ysandeep|out | 15:58 | |
gthiemonge | #startmeeting Octavia | 16:00 |
---|---|---|
opendevmeet | Meeting 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 http://wiki.debian.org/MeetBot. | 16:00 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
opendevmeet | The meeting name has been set to 'octavia' | 16:00 |
gthiemonge | hi folks! | 16:00 |
johnsom | o/ | 16:00 |
tweining | o/ | 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 |
johnsom | viks__ Use the load balancer failover function. | 16:02 |
gthiemonge | +1 | 16:02 |
johnsom | #link https://docs.openstack.org/python-octaviaclient/latest/cli/index.html#loadbalancer-failover | 16:03 |
johnsom | Compute 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 Announcements | 16:06 |
gthiemonge | ** OpenStack Zed schedule | 16:07 |
gthiemonge | (same as last week ;)) | 16:07 |
gthiemonge | next week is the Feature Freeze/Final release for client libraries! | 16:07 |
johnsom | Next week is the deadline for octavia-lib | 16:07 |
gthiemonge | I see good progress on the reviews! | 16:07 |
gthiemonge | at least: activity ;-) | 16:08 |
gthiemonge | #link https://releases.openstack.org/zed/schedule.html | 16:08 |
johnsom | I don't think we have anything expected for zed left in octavia-lib | 16:08 |
gthiemonge | ok, and we released octavia-lib 3.1.0 last week | 16: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 change | 16:10 |
johnsom | viks__ 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 |
gthiemonge | hey you might have seen that I have created a lot of backports | 16:11 |
gthiemonge | as the fixes for Zed are getting merged, I'm backporting them (I don't want to miss a fix) | 16:11 |
johnsom | Standalone failover just has a short amount of downtime during a failover, were active/standby does not. | 16:11 |
gthiemonge | reviewing these backports is not really urgent | 16:11 |
johnsom | +1 to doing backports as things merge. | 16:12 |
gthiemonge | I think when Zed is released and those backports are merged, we will deliver a new stable releases | 16:12 |
tweining | also worth mentioning: we had no bare rechecks recently. Our statistics are clean ATM | 16:12 |
tweining | https://etherpad.opendev.org/p/recheck-weekly-summary | 16:12 |
johnsom | lol | 16:12 |
gthiemonge | the script is broken? | 16:13 |
tweining | probably | 16:13 |
gthiemonge | well, this is great ;-) | 16:13 |
gthiemonge | I mean 0 bare recheck | 16:14 |
gthiemonge | Can 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 |
johnsom | viks__ 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 response | 16:17 |
viks__ | only `provision state` is ERROR.. i.e. as mentioned in https://docs.openstack.org/octavia/latest/admin/guides/operator-maintenance.html#monitoring-load-balancers | 16:18 |
gthiemonge | #topic CI Status | 16:18 |
gthiemonge | nothing to report here | 16:18 |
johnsom | viks__ 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 |
johnsom | viks__ Yep. Given the error from nova "No valid host was found.", you probably can't create new load balancers or VMs either. | 16:20 |
johnsom | viks__ 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 response | 16:22 |
gthiemonge | #topic Brief progress reports / bugs needing review | 16:23 |
johnsom | I have been focused on reviews. Making my way through the subnet/multi-vip patch chain | 16:23 |
gthiemonge | I did many reviews... that's all :D | 16:23 |
johnsom | Big and complex patches.... | 16:23 |
tweining | the 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 |
johnsom | Yeah, we should probably abandon those patches too | 16:25 |
gthiemonge | yeah they are outdated and unmaintained | 16:25 |
gthiemonge | Experimental multi-az support is also on the list, I know that it is not ready too | 16: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 Discussion | 16:30 |
johnsom | FYI, from the discuss mailing list, there is more info on this story: https://storyboard.openstack.org/#!/story/2007619 | 16:30 |
johnsom | There 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 stuff | 16:31 | |
gthiemonge | johnsom: is it related to application credentials? | 16:32 |
johnsom | "trust-scoped" tokens. I'm not 100% sure I even know what that is | 16:32 |
johnsom | Kong fixed it for neutron in the past. | 16:33 |
gthiemonge | yeah we should ask for a simple reproducer (or advices for the conf) | 16:34 |
johnsom | I just wanted to bring it up at the meeting so someone might be able to pick this up. | 16:36 |
gthiemonge | johnsom: I will follow up in the story | 16:36 |
johnsom | Awesome, thanks | 16:37 |
gthiemonge | anything else? | 16:39 |
tweining | not from me | 16:40 |
johnsom | I don't think I have anything else | 16:40 |
gthiemonge | ok thank you guys | 16:42 |
gthiemonge | #endmeeting | 16:43 |
opendevmeet | Meeting ended Wed Aug 24 16:43:04 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:43 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/octavia/2022/octavia.2022-08-24-16.00.html | 16:43 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/octavia/2022/octavia.2022-08-24-16.00.txt | 16:43 |
opendevmeet | Log: https://meetings.opendev.org/meetings/octavia/2022/octavia.2022-08-24-16.00.log.html | 16:43 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!