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] Install doesn't work with non-default artifactory_user and artifactory_group #331

Open
Hiruma31 opened this issue Sep 14, 2023 · 1 comment

Comments

@Hiruma31
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Which installer:
ansible

Which product and version (eg: ansible & collection version - 7.24.2):
collection version - 10.15.0 (latest atm)
ansible version - 2.15.3

Which operating system and version(eg: ubuntu & version - 20.4):
Rocky Linux 9

Which product license (Enterprise/Pro):
Enterprise

JFrog support reference (if already raised with support team):
NA

What happened:
When setting artifactory_user and artifactory_group to something non-default (i.e. jfrog-artifactory) the installer sets {{ artifactory_home }}/app to artifactory:artifactory instead of the custom user:group.

Based on the documentation, installService.sh should take the user and group as optional arguments (default to artifactory)

Since the permissions are incorrect on intsall, Artifactory refuses to start because it expects the whole directory to be owned by the artifactory. The logs even suggest to run chown -R artifactory:artifactory.

What you expected to happen:
The whole directory should be owned by the specified user and group, and Artifactory should start properly.

How to reproduce it (as minimally and precisely as possible):
Use the following vars:

artifactory_user: jfrog-artifactory
artifactory_group: jfrog-artifactory

Anything else we need to know:
No

Hiruma31 added a commit to Hiruma31/JFrog-Cloud-Installers that referenced this issue Sep 14, 2023
@Logeshwarsn
Copy link
Contributor

HI @Hiruma31 ,Thanks for raising this PR. We will take this into our subsequent release. ETA will be 3 weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants