Skip to content
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/artifactory] default admin credentials are not used/applied #294

Closed
olwe0002 opened this issue Jun 2, 2023 · 7 comments · Fixed by #339
Closed

[ansible/artifactory] default admin credentials are not used/applied #294

olwe0002 opened this issue Jun 2, 2023 · 7 comments · Fixed by #339
Labels
enhancement New feature or request

Comments

@olwe0002
Copy link

olwe0002 commented Jun 2, 2023

Is this a request for help?:


Is this a BUG REPORT or FEATURE REQUEST? (choose one): both
Which installer: ansible
Which product and version : ansible & JFrog Platform 10.12.3 release
Which operating system and version(eg: ubuntu & version - 20.4): ubuntu & version - 20.4
Which product license (Enterprise/Pro): Enterprise

What happened:

The default admin credentials can be defined, default variables are defined for that:

but they are not applied on a installation, as this variables are not used at all in any role

What you expected to happen:

login with the provided credentials is possible, at least on a new installation

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

@chukka chukka added the enhancement New feature or request label Jun 2, 2023
@itssiri
Copy link

itssiri commented Jun 2, 2023

Thanks. We will take this as an internal enhancement.

@olwe0002
Copy link
Author

olwe0002 commented Nov 3, 2023

thx. I tried to use the new collection version, but it failed:

TASK [jfrog.platform.artifactory : Set up Artifactory admin account] ***********
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [vm-artifactory-1]: FAILED! => changed=false 
  msg: |-
    Could not find or access 'bootstrap.creds'
    Searched in:
            /root/.ansible/collections/ansible_collections/jfrog/platform/roles/artifactory/templates/bootstrap.creds
            /root/.ansible/collections/ansible_collections/jfrog/platform/roles/artifactory/bootstrap.creds
            /root/.ansible/collections/ansible_collections/jfrog/platform/roles/artifactory/tasks/templates/bootstrap.creds
            /root/.ansible/collections/ansible_collections/jfrog/platform/roles/artifactory/tasks/bootstrap.creds
            /builds/alm/artifactory/jfrog-platform-on-openstack/ansible/playbooks/./templates/bootstrap.creds
            /builds/alm/artifactory/jfrog-platform-on-openstack/ansible/playbooks/./bootstrap.creds on the Ansible Controller.
    If you are using a module and expect the file to exist on the remote, see the remote_src option

root cause is that the template file is name bootstrap.creds.j2, but in the task you are using bootstrap.creds as template name

please fix

@bbaassssiiee
Copy link
Contributor

Thanks for your report! I'll create a hotfix

bbaassssiiee added a commit to TeamSalvador/JFrog-Cloud-Installers that referenced this issue Nov 3, 2023
@olwe0002
Copy link
Author

olwe0002 commented Nov 3, 2023

@bbaassssiiee additionally, the dest is wrong, as the file name is missing. it doesn't work to use a directory there. Fails with msg: Destination .../artifactory/var/etc/access not writable

@bbaassssiiee
Copy link
Contributor

This issue is closed, please continue this review in Pull Request 340

chukka pushed a commit that referenced this issue Nov 3, 2023
chukka pushed a commit that referenced this issue Nov 3, 2023
@chukka
Copy link
Collaborator

chukka commented Nov 3, 2023

@bbaassssiiee @olwe0002 Thanks for the PR and fixed via #343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants