Manuel Laug

I've experienced the same problem with FAM 2.2.0. The behaviour changed probably due to https://github.com/theforeman/foreman-ansible-modules/commit/d0050d1386f93b2427b4c2b26a0eedb7a35eed08. I can assist in debugging FAM (and Foreman) if you need someone with access to...

I'm using Velero 1.9.0 as well but together with Velero-Plugin-for-AWS 1.5.0 with exactly the same problem: `velero backup logs ` and `velero backup describe --details` hangs endlessly. When enabling Velero...

@reasonerjt, the same command also fails for backups created with Velero v1.9.0. We are running the official images (`velero/velero:v1.9.0` and `velero/velero-plugin-for-aws:v1.5.0`). I just had a look into the target S3...

As a short-term relieve, I've added a second import source and split the import into two distinct groups. Also, I've extended the LDAP filter to only import groups containing members...

I do see the exact same behaviour with check_procs. After reaching 64k on stdout of `/bin/ps axwo 'stat uid pid ppid vsz rss pcpu etime comm args'` (which is executed...

IIRC this was possible with versions < 4 but was changed during the major release 4.0.0 - but no idea why. That might be the reason, the docs still mention...

@stevesloka, yes the authserver was healthy and using a self-signed cert (as per https://projectcontour.io/guides/external-authorization/).

Reloading the VSCode window seems to help.

I see the same behaviour with Vault 1.12.1 and missing vault_core_active metric after some time. We've used the absence of that metric to determine missing leaders and got alerted by...

I can confirm that setting `defaultNamespaces` to `default` and all the other namespace parameters to `fission` also works and the pods seem to be happy.