-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-navigator not able to list roles in a collection #1186
Comments
@patrick-tang-redhat Thanks for this! Role browsing support was added here: #1059 and will be in the 2.0.0 release of ansible-navigator. The upstream release candidate should be out today and the upstream final 2.0.0 next week. When the RC is out, I'll post a link here so you can give it a run for us and let us know what you think |
Thanks @cidrblock |
@cidrblock Do you know the fix? |
@patrick-tang-redhat I see root there, can you try and install it with the --user flag? (if you didn't)
Still working to get the release candidate out today, keep me posted please |
Sorry, I see you did, let me look |
Can you run it with:
|
@cidrblock Traceback (most recent call last): |
@cidrblock ` After I manually copied the file 'key_value_store.py' to ~/.local/share/ansible_navigator/utils folder. I'm able to launch ansible-navigator command. ` |
Somehow I think your installation is odd, your first message has a mention of |
Can you try with an install in a virtual environment? I can provide the steps, this might be related to an RPM install + a pip installation? Or uninstall the pip version, uninstall the RPM and then install the pip version |
@cidrblock could you provide the steps for virtual environment? I'm not familiar with it. I installed python39 as module, so everything goes together |
This will build a virtual environment and install navigator in it, when you are done, you can delete the directory and nothing will be left over, clean up is easy. Good for testing |
@cidrblock The old error log:
|
You can use the supported ee by supplying it on the command line:
Or putting it in a ansible-navigator settings file. The upstream releases will point to the creator-ee. I need to see what is being done during the downstream RPM build, they might be using a settings file or default being changed. |
BTW, sorry you are having trouble here... we'll get this sorted out |
@cidrblock I just tried with --eei to specify ee-supported image, but it just ran fine in venv. So not sure why i got issue in non-venv . (venv) [root@rhel8 navigator-test]# ansible-navigator collections --eei registry.redhat.io/ansible-automation-platform-21/ee-supported-rhel8:latestExecution environment image and pull policy overviewExecution environment image name: registry.redhat.io/ansible-automation-platform-21/ee-supported-rhel8:latest
|
Something about the way it was installed outside the virtual environment... If you want to use it without the virtual environment, you can deactivate the virtual environment and then remove the RPM installed ansible-navigator and try to install if fresh: $ pip install ansible-navigator==2.0.0b0 --user this might work, I haven't tried a pip install on top of an RPM... |
@patrick-tang-redhat JSYK:
Just released. Let me know if it's ok to close this issue now :) |
@cidrblock ` [root@rhel8 ~]# /usr/local/bin/ansible-navigator collections --eei ee-supported-rhel8Execution environment image and pull policy overviewExecution environment image name: ee-supported-rhel8:latest
|
hmmm I'm wondering if the RPM uninstall didn't remove some of the directories try deleting the /usr/share/ansible_navigator directory |
I uninstall rpm ansible-navigator then install 2.0.0rc1 with pip. So yum should not remove any rc1 directories. ` Transaction Summary ` |
@cidrblock |
It seems the RPM uninstall doesn't remove the directory it created, so when the pip installed version runs it finds that directory, even though it is empty, and tries to load from it. We are trying to get rid of the share directory entirely, which is the real long term fix, given that I'm not sure there is a reason to do anything right now. I think it would be rare for someone to be switching from RPM to pip, unless they are testing or developing... |
@cidrblock |
@cidrblock |
Resolved by #1059 |
ISSUE TYPE
SUMMARY
While we can list roles and check the documents for roles from automation hub, we cannot list roles with cli ansible-navigator ('ansible-navigator collections').
ANSIBLE-NAVIGATOR VERSION
CONFIGURATION
LOG FILE
STEPS TO REPRODUCE
EXPECTED RESULTS
expected: the roles in a collection should be shown.
ACTUAL RESULTS
actual: roles are missing from the content of the collection.
ADDITIONAL INFORMATION
As a comparison, please check following link for example collection to show roles in its content:
https://console.redhat.com/ansible/automation-hub/repo/published/redhat/insights/content?showing=all
The text was updated successfully, but these errors were encountered: