slefol

I am same issue with : ansible 2.9.6 ansible-api 0.5.0 ansible-runner 1.4.6 a possible next fix for this issue ?

> I am same issue with : > ansible 2.9.6 > ansible-api 0.5.0 > ansible-runner 1.4.6 > > a possible next fix for this issue ? i installed from the...

tested again with Rancher 2.6.8 and RKE2 v1.24.8+rke2r1. Still the networkpolicies are containing the wrong IP adresses for the nodes themselves, making the entire feature of "Project network separation" unusable...

Hi @dineshbaburam91, are there any updates fot this issue ? Please keep me updated about the progress.

Hi, I installedHelm chart version : 0.11.0 and the issue is still present. Can you please look into this issue ?

@LaurenceJJones Thank you for your interest in my request. I defined in the lapi environment a GID property of 2000 but I get this error : ComparisonError: error calculating structured...

my values.yaml : ```yaml container_runtime: containerd tls: enabled: true bouncer: reflector: namespaces: ["traefik"] agent: # Specify each pod whose logs we want to process acquisition: # The namespace where the...

No, the permissions are : ``` kubectl -n crowdsec exec -it crowdsec-lapi-98f7577d6-bv4tb -- sh Defaulted container "crowdsec-lapi" out of: crowdsec-lapi, dashboard, fetch-metabase-config (init) / # ls -la /var/lib/crowdsec/data total 100...

I encounter the same bug with napalm.napalm.get_facts and juniper.device.table modules. Like netwrknerd, the bug occurs upon installation of ansible-core version 2.12.9 or greater and while using 'juniper.device.pyez' connection type ('local'...

the solution given on the page https://github.com/ansible/ansible/issues/79371 works ! (ansible-core version 2.14.3)