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

Self Hosted RHEL Azure Pipelines Agents do not detect Oracle JDK installation #5050

Closed
1 of 4 tasks
manselp opened this issue Nov 27, 2024 · 1 comment
Closed
1 of 4 tasks

Comments

@manselp
Copy link

manselp commented Nov 27, 2024

Describe your question

Our self hosted RHEL Azure Pipelines Agents are not detecting the Oracle JDK installation, and therefore not adding Java to system capabilities.
We have set JAVA_HOME environment variable and added the directory to the path.
The behaviour is a bit odd as when we SSH to the instance we can run java -version as the ado-agent user and it correctly gives the below output:

[ado-agent@ip-******]$ java -version
java version "21.0.3" 2024-04-16 LTS
Java(TM) SE Runtime Environment (build 21.0.3+7-LTS-152)
Java HotSpot(TM) 64-Bit Server VM (build 21.0.3+7-LTS-152, mixed mode, sharing)

However, when we use a yaml pipeline to run the same command (and as the same user), it fails:

whoami: 
ado-agent
java -version:
/opt/ado-agent/_work/_temp/e45baab2-88de-4c50-92aa-4427d072d072.sh: line 5: java: command not found

Thanks

Versions

Azure DevOps Agent version: 3.248.0 / RHEL 8.10

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Operation system

No response

Version controll system

No response

Azure DevOps Server Version (if applicable)

No response

@vmapetr vmapetr added bug and removed triage labels Nov 27, 2024
@manselp manselp closed this as not planned Won't fix, can't repro, duplicate, stale Dec 2, 2024
@manselp
Copy link
Author

manselp commented Dec 2, 2024

I discovered there was an issue with the profile that was set up, rather than the agent software.
Hence closing issue as not required.
Thanks

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

No branches or pull requests

2 participants