AWX <-> Foreman, disabled status no longer functioning?

Archives AWX Project
1

Hi folk!

I sync AWX with our local foreman instance via the Satellite 6 (foreman) inventory sync. One of the things we make use of is the ability to disable a host in Foreman and have that reflect in AWX disabling the host as well on next sync. However, for some reason that appears to have stopped working. (It’s unclear to me if it stopped after I updated to 19.2.2 or more recent than that) I can clearly see in the host varables that enabled is set to false, but the host is still “on” in AWX. Any ideas what might be going on? Did I miss a change that I need to adjust for?

PS. if I manually toggle it to off in AWX, it toggles back to on at next sync. (which is of course expected if the sync itself is considering the host to be enabled)

Thanks!

Daniel

2

Double check that the “Overwrite and Overwrite Variables” are still checked for that Source definition. That somehow got turned off on one of mine previously and that was what I had to re-enable to ensure the synced inventories were correctly updated in AWX.

3

Dag. Was hoping that was it but they are still checked. =(

4

Did you turn it off and back on? Seriously, an Off run and then an On run…

This is still hitting me wrong as I swear I wound up having to patch this same type of issue back in late 2018 with a sync on satellite doing the same thing…
This may have something to do with it or along the same lines:
https://community.theforeman.org/t/ansible-inventory-unable-to-parse-foreman-py/11124/2

Anything in the logs that you can discern when running just the updates?
Are new hosts added?
Are deleted hosts removed?

5

Hrm. Sadly no, toggling notifications off and on didn’t help anything. I also tried another host and same issue. It’s so weird that it started happening out of no where — on one hand it leads me to think foreman updated and is causing the problem, but ony the other hand it clearly shows “enabled: false” in the variables inside AWX so ?? It’s been a bit since I updated AWX so I don’t think an AWX update caused it. I’m not currently seeing anything obvious in the logs, and I need to find some time to turn on debugging and see if I notice something.