Alan Rominger

There are a number of issues prefixed with `[hop node]` which are part of that work https://github.com/ansible/awx/issues?q=is%3Aissue+is%3Aopen+hop+node

Thank you for the report. I have put a patch up at https://github.com/ansible/awx/pull/15138 but it will take a while to fully verify it because the migration testing takes a while.

The patch for this issue is merged into the `devel` branch.

Thanks for the contribution! I hope we can get this merged with some modifications. To get it out of the way now, next time you push, it would help to...

This is definitely on my agenda at some point. There are just too many other things ahead of it. I can't get to it soon.

I thought the issue here was resolved by the merge of https://github.com/ansible/awx/pull/12073 by @fosterseth I want to understand a little bit about what that didn't do which is now being...

https://github.com/ansible/awx/pull/13644 was the recent patch I was trying to think of. I didn't understand your test case fully.

oh right, I forgot, this was in some fedora-specific repo. It makes sense that we wouldn't support it, but I still don't know what would mean for the metadata.

This is blocked on https://github.com/ansible/ansible-runner/pull/530 because `config.container_name` is needed to reference the container at whatever point stats are gathered.

I tested in conjunction with AWX / AAP controller, and normal jobs error with this from the worker: ``` {'private_data_dir': '/tmp/awx_91_2oshmw_9', 'ident': UUID('91c14a59-dd60-4e57-b589-cc430806c44b'), 'binary': None, 'playbook': None, 'module': None, 'module_args':...