first touch experience out-of-the-box is hard to use or when in disconnected environment - Execution environment pull failed

[IPvSean]

ISSUE TYPE

• Feature Idea

SUMMARY

Right now if you are in a disconnceted environment (or even if you don't know what registry.redhat.io or how to use it) you will get ansible-navigator failing

e.g. if I am on a system that has access to PAH (private automation hub) it will still fail here:

Trying to pull registry.redhat.io/ansible-automation-platform-20-early-access/ee-supported-rhel8:2.0.0...

It will quit out with an [Error]: Execution environment pull failed

In this case... I know we can set an ansible-navigator.yml file and point to an actual EE that we have.... but I am wondering if this -first touch- experience should be better... and it should at least open when I type in ansible-navigator and tell you that you don't have any EEs?

[IPvSean]

[cidrblock]

tricky one here, we wanted execution environment support enabled by default and the default pull policy to be set to 'tag', since that is generally the default elsewhere

We could probably modify the "HINT" above to suggest disabling execution environment support if disconnected

[bonnevil]

I'd think, though, that if someone is disconnected we also would want to encourage them to configure things to look at their private automation hub or on-site container repository if that's where the EEs are.

[cidrblock]

That..... Is a great point. Should definitely suggest that prior to disabling EE support entirely

[jsast21]

This is exactly where I am right now and I am so stuck - I am in a disconnected environment and I have AAP 2.1 and a private hub and I cannot for the life of me figure out how to get ansible-navigator configured to work. Is there any fix to this? Because this is where I'm failing:

Trying to pull registry.redhat.io/ansible-automation-platform-21/ee-supported-rhel8:latest