Paweł Kubica

I have similar problem using podman on CentOS Stream 9 ``` # glances Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/docker/api/client.py", line 268, in _raise_for_status response.raise_for_status() File "/usr/lib/python3.9/site-packages/requests/models.py", line 943, in...

Using below configuration I can create cluster with FIP assigned to all VMs: ``` openstack = { source = "terraform-provider-openstack/openstack" version = "~> 1.43.0" } ``` ``` resource "openstack_containerinfra_clustertemplate_v1" "clustertemplate_1"...

I have just pushed PR that should fix 2) problem.

@jan-di-cgm my PR (fixing this issue) wasn't merged and released yet ;-)

> Hmm on our OpenStack cluster changing the number of nodes was working fine (IIRC our magnum is running train version). Maybe magnum changed something in the API... I'm testing...

> I am guessing that if this is the right fix, it would also applies to {min,max}_node_count on the nodegroup resource as well. That's true. I have also fixed this...

Differences such as annotations are obvious, so they were omitted in my comparison. Due to the fact that Helm Chart and Manifest are provided in scope of the same repository,...

@Pionerd Can you update this PR?

/remove-lifecycle stale

/remove-lifecycle stale