March 2023 - openstack-discuss - lists.openstack.org

[CloudKitty] Virtual PTG March 2023
by Rafael Weingärtner 21 Mar '23

21 Mar '23

Hello everyone, As you probably heard our next PTG will be held virtually in March, 2023. We've marked March 31, at 13:00-15:00 UTC [1]. However, if you guys would like some other dates and/or time, just let me know. The room we selected is called "Bexar". I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/march2023-ptg-cloudkitty -- Rafael Weingärtner

1 0

[Octavia][PTG] Bobcat PTG planning
by Gregory Thiemonge 21 Mar '23

21 Mar '23

Hi Folks, A reminder: the Octavia PTG will be on March 28th (14:00-18:00 UTC), There's a dedicated etherpad for this session: https://etherpad.opendev.org/p/bobcat-ptg-octavia Feel free to add your topic, Greg

1 0

[Glance]Weekly Meeting Cancelled for this week
by Pranali Deore 21 Mar '23

21 Mar '23

Hello, As discussed during last weekly meeting[1], Glance upstream weekly meeting for this week i.e., 23rd March, 2023 has been cancelled. See you all at PTG ! Thanks & Regards, Pranali [1]: https://meetings.opendev.org/irclogs/%23openstack-meeting/%23openstack-meet…

1 0

[neutron]
by Kamil Madac 21 Mar '23

21 Mar '23

Hi All, I'm in the process of planning a small public cloud based on OpenStack. I have quite experience with kolla-ansible deployments which use OVS networking and I have no issues with that. It works stable for my use cases (Vlan provider networks, DVR, tenant networks, floating IPs). For that new deployment I'm looking at OVN deployment which from what I read should be more performant (faster build of instances) and with ability to cover more networking features in OVN instead of needing external software like iptables/dnsmasq. Does anyone use OVN in production and what is your experience (pros/cons)? Is OVN mature enough to replace OVS in the production deployment (are there some basic features from OVS missing)? Thanks in advance for sharing the experience. -- Kamil Madac <https://kmadac.github.io/>

3 4

[ironic][ptg] vPTG scheduling
by Jay Faulkner 21 Mar '23

21 Mar '23

Hey all, The vPTG will be upon us soon, the week of March 27. I booked the following times on behalf of Ironic + BM SIG Operator hour, in accordance with what times worked in Antelope. It's my hope that since we've had little contributor turnover, these times continue to work. I'm completely open to having things moved around if it's more convenient to participants. I've booked the following times, all in Folsom: - Tuesday 1400 UTC - 1700 UTC - Wednesday 1300 UTC Operator hour: baremetal SIG - Wednesday 1400 UTC - 1600 UTC - Wednesday 2200 - 2300 UTC I propose that after the Ironic meeting on March 20, we shortly sync up in the Bobcat PTG etherpad (https://etherpad.opendev.org/p/ironic-bobcat-ptg) to pick topics and assign time. Again, this is all meant to be a suggestion, I'm happy to move things around but didn't want us to miss out on getting things booked. - Jay Faulkner Ironic PTL TC Member

2 6

[tacker] Cancelling next two IRC meetings
by Yasufumi Ogawa 20 Mar '23

20 Mar '23

Hi, I'd like to skip the next two IRC meetings due to a holiday tomorrow for many of us joining from Japan and next week for the bobcat vPTG. I'm looking forward to meet you guys on the vPTG! Cheers, Yasufumi

1 0

[neutron] Bug deputy report for week of March 13th
by Brian Haley 20 Mar '23

20 Mar '23

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian High bugs --------- * https://bugs.launchpad.net/neutron/+bug/2011573 - [ovn-octavia-provider] Job pep8 failing due to bandit new lint rule - https://review.opendev.org/c/openstack/ovn-octavia-provider/+/877357 * https://bugs.launchpad.net/neutron/+bug/2011590 - Startup times for large OVN dbs is greatly increased by frozen_row() calls - https://review.opendev.org/c/openstack/neutron/+/877383 * https://bugs.launchpad.net/neutron/+bug/2011600 - functional test_get_datapath_id fails with neutron.common.utils.WaitTimeout: Timed out after 5 seconds - needs owner * https://bugs.launchpad.net/neutron/+bug/2011800 - ovn qos extension: update router does not remove no longer present qos rules - https://review.opendev.org/c/openstack/neutron/+/877603 (test only) - Needs code fix still Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/2011377 - test_agent_resync_on_non_existing_bridge failing intermittently sp - https://review.opendev.org/c/openstack/neutron/+/877535 * https://bugs.launchpad.net/neutron/+bug/2011724 - [OVN] Method "create_metadata_port" should pass the "fixed_ips" when creating the port - https://review.opendev.org/c/openstack/neutron/+/877528 * https://bugs.launchpad.net/neutron/+bug/2012104 - Neutron picking incorrect ovn records - Possibly related to https://bugs.launchpad.net/neutron/+bug/1951149 - OVN chassis deleted issue - does user need to manually clean-up? Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/2011687 - O flag is not enabled when ipv6_ra_mode is dhcpv6-stateful - O=1 is actually unnecessary in this case with M=1 based on the RFC, will need to figure out how to update code and/or docs to be in sync - https://review.opendev.org/c/openstack/neutron/+/877601 Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/2012144 - [OVN] adding/removing floating IPs neutron server errors about binding port - Mech driver shows ovn-bridge-mappings=[], but ovn-sbctl has them - Asked for more information Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/2011422 - [RFE] The Neutron agents should report the sync process status * https://bugs.launchpad.net/neutron/+bug/2012069 - [OVN] Flooding issue on provider networks with disabled port security - https://review.opendev.org/c/openstack/neutron/+/877675

1 0

[openstack-helm][tacker]
by TAKAHASHI TOSHIAKI(高橋　敏明) 20 Mar '23

20 Mar '23

Hi Openstack-helm team, I’m Toshiaki Takahashi, Tacker’s core developer. To my understanding, OpenStack-helm does not currently provide a Tacker’s helm chart. Recently there have been some requests to deploy Tacker with helm, and we would like to proceed with development of it if possible. Do we need to take any action such as to participate meeting of Openstack-helm project and propose our plan? Or, if OpenStack-helm is planning to have a PTG, I’d like to propose the plan at PTG, but is it planned? (I don't see any schedule at the moment). Regards, Toshiaki

2 3

[interop][ptg] Virtual Bobcat vPTG Planning
by Martin Kopec 20 Mar '23

20 Mar '23

Hello everyone, here is [1] our etherpad for the 2023.2 Bobcat PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots for our session(s), so that they fit your schedule, at [2]. If you have any questions, feel free to reach out to me. [1] https://etherpad.opendev.org/p/bobcat-ptg-interop [2] https://framadate.org/2IPXOCvJNNoSGqHu Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[kolla-ansible][yoga][Magnum] Cannot attach cinder volume to pod
by wodel youchi 20 Mar '23

20 Mar '23

Hi, I am trying to attach a cinder volume to my pod, but it does not work. The long story, the default version of kubernetes used in Yoga is 1.23.3 fcore35. When creating a default kubernetes cluster we got : > Image: quay.io/k8scsi/csi-attacher:v2.0.0 > Image: quay.io/k8scsi/csi-provisioner:v1.4.0 > Image: quay.io/k8scsi/csi-snapshotter:v1.2.2 > Image: quay.io/k8scsi/csi-resizer:v0.3.0 > Image: docker.io/k8scloudprovider/cinder-csi-plugin:v1.18.0 > Image: quay.io/k8scsi/csi-node-driver-registrar:v1.1.0 > Image: > docker.io/k8scloudprovider/openstack-cloud-controller-manager:v1.18.1 > Which 1 - Does not correspond to the documentation of Magnum, the documentation states these defaults for yoga : > Image: 10.0.0.165:4000/csi-attacher:v3.3.0 > Image: 10.0.0.165:4000/csi-provisioner:v3.0.0 > Image: 10.0.0.165:4000/csi-snapshotter:v4.2.1 > Image: 10.0.0.165:4000/csi-resizer:v1.3.0 > Image: 10.0.0.165:4000/cinder-csi-plugin:v1.26.2 > Image: 10.0.0.165:4000/csi-node-driver-registrar:v2.4.0 > Image: 10.0.0.165:4000/cinder-csi-plugin:v1.26.2 > (cinder-csi-plugin:v1.23.0 which does not exists anymore) > 2 - And does not work, csi-cinder-controllerplugin keeps crashing. I tried to use the updates images (using a local registry), but I couldn't attach the cinder-volume, I got : Volumes: html-volume: Type: Cinder (a Persistent Disk resource in OpenStack) VolumeID: f780cb46-ed2a-405d-b901-7201b49c3df1 FSType: ext4 ReadOnly: false SecretRef: nil kube-api-access-slqf4: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: <nil> DownwardAPI: true QoS Class: Burstable Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- * Warning FailedMount 26m (x10 over 135m) kubelet Unable to attach or mount volumes: unmounted volumes=[html-volume], unattached volumes=[kube-api-access-slqf4 html-volume]: timed out waiting for the condition Warning FailedAttachVolume 3m39s (x40 over 146m) attachdetach-controller AttachVolume.Attach failed for volume "cinder.csi.openstack.org-f780cb46-ed2a-405d-b901-7201b49c3df1" : Attach timeout for volume f780cb46-ed2a-405d-b901-7201b49c3df1 Warning FailedMount 104s (x54 over 146m) kubelet Unable to attach or mount volumes: unmounted volumes=[html-volume], unattached volumes=[html-volume kube-api-access-slqf4]: timed out waiting for the condition* "volume":{"capacity_bytes":5368709120,"volume_id":"7e377933-4ae6-47b7-a685-f484d35153af"}},{"status":{"published_node_ids":["c2531ccf-842e-44d1-85bd-72c811cea199"]},"volume":{"capacity_bytes":1073741824,"volume_id":"f9d5273b-e73d-4b37-8b50-1fcecb910b2a"}}]} I0319 12:36:50.910443 1 connection.go:201] GRPC error: <nil> I0319 12:36:56.925658 1 controller.go:210] Started VA processing "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.925682 1 csi_handler.go:224] CSIHandler: processing VA "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.925687 1 csi_handler.go:251] Attaching "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.925691 1 csi_handler.go:421] Starting attach operation for "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.925705 1 csi_handler.go:740] Found NodeID 472bf42d-5ce0-4751-8fec-57bede0024d6 in CSINode k8intcalnewer-56bgom6jntbm-node-0 I0319 12:36:56.925828 1 csi_handler.go:312] VA finalizer added to "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.925836 1 csi_handler.go:326] NodeID annotation added to "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:56.947632 1 connection.go:193] GRPC call: /csi.v1.Controller/ControllerPublishVolume I0319 12:36:56.947646 1 connection.go:194] GRPC request: {"node_id":"472bf42d-5ce0-4751-8fec-57bede0024d6","volume_capability":{"AccessType":{"Mount":{"fs_type":"ext4"}},"access_mode":{"mode":1}},"volume_id":"f780cb46-ed2a-405d-b901-7201b49c3df1"} I0319 12:36:58.343821 1 connection.go:200] GRPC response: {"publish_context":{"DevicePath":"/dev/vdc"}} I0319 12:36:58.343834 1 connection.go:201] GRPC error: <nil> I0319 12:36:58.343841 1 csi_handler.go:264] Attached "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.343848 1 util.go:38] Marking as attached "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" *I0319 12:36:58.348467 1 csi_handler.go:234] Error processing "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7": failed to mark as attached: volumeattachments.storage.k8s.io <http://volumeattachments.storage.k8s.io> "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" is forbidden: User "system:serviceaccount:kube-system:csi-cinder-controller-sa" cannot patch resource "volumeattachments/status" in API group "storage.k8s.io <http://storage.k8s.io>" at the cluster scope* I0319 12:36:58.348503 1 controller.go:210] Started VA processing "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348509 1 csi_handler.go:224] CSIHandler: processing VA "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348513 1 csi_handler.go:251] Attaching "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348517 1 csi_handler.go:421] Starting attach operation for "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348525 1 csi_handler.go:740] Found NodeID 472bf42d-5ce0-4751-8fec-57bede0024d6 in CSINode k8intcalnewer-56bgom6jntbm-node-0 I0319 12:36:58.348540 1 csi_handler.go:304] VA finalizer is already set on "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348552 1 csi_handler.go:318] NodeID annotation is already set on "csi-9f81405424dc2cf210b6465f8b649ef20f85024f169b660fab235c03f64753b7" I0319 12:36:58.348564 1 connection.go:193] GRPC call: /csi.v1.Controller/ControllerPublishVolume I0319 12:36:58.348567 1 connection.go:194] GRPC request: {"node_id":"472bf42d-5ce0-4751-8fec-57bede0024d6","volume_capability":{"AccessType":{"Mount":{"fs_type":"ext: The I tried even the most updated images : > 10.0.0.165:4000/cinder-csi-plugin:v1.26.2 > 10.0.0.165:4000/csi-provisioner:v3.4.0 > 10.0.0.165:4000/csi-resizer:v1.7.0 > 10.0.0.165:4000/csi-snapshotter:v6.2.1 > 10.0.0.165:4000/csi-attacher:v4.2.0 > 10.0.0.165:4000/csi-node-driver-registrar:v2.7.0 > I had the same problem. Then I tried to use an older version of kubernetes : 1.21.11 with the older images shown above (following this link https://www.roksblog.de/deploy-kubernetes-clusters-in-openstack-within-minu…) and it worked, the cinder volume was successfully mounted inside my nginx pod. - What is the meaning of the error I am having? - Is it magnum related or kubernetes related or both? Regards.

4 6