lae
lae
@lexxxel are you using v1.9.1? I just got around to double checking but Dimitri fixed this in cf670893c9e97b153a20cbf2b1433d79161df9fa/#282 a few months ago, I believe.
I'm attempting to reproduce this atm but after fixing my vagrant-libvirt issues it turns out I only have like half a GB free on my system and thus can't bring...
@btravouillon assigned to you, but I might go ahead and do this if you're busy so I can include this in the next release. I think this task should probably...
Also maybe `pve_default_kernel_version` is a better name given the content. The current name makes me think it should be a boolean.
Added in #267
I was able to reproduce this with multiple resources, including one with a `description` of "Install complete". Manually removing the `description` attribute from the state works around the issue. Looking...
I believe we can still use the same task, just use the `omit` filter for the port/login password. Although since `netbox_database_port` technically has a default I guess `omit` wouldn't make...
should probably be considered a fix for #214 (and I ran into this environment-crippling issue as well after being forced to update from 17.0.0)
I have to agree with @bluecamel, I finally got around to refreshing our monitoring deployment (we were still on Prom 0.18.x) and the new grey on white color scheme is...
The task, `Check for kernel update`, is only run once. The `collect_kernel_info` module is indeed used twice, but with different task names. You state that you're getting an error the...