OMR Jenkins: Risc-v node offline

Summary

Related #5254 (closed)

Our Risc-v node (172.30.206.102) provided by EF is offline and won't connect to jenkins.

https://ci.eclipse.org/omr/computer/riscv%2Dbuild1/

Won't respond to ping either

Steps to reproduce

(How one can reproduce the issue - this is very important)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")

added IT-prioritymedium IT-severitynormal service:jenkins statetodo team:releng labels

The node needed reboot due to some system issues.

Agent is back online.

closed

removed statetodo label

assigned to @pstankie

Thanks, Pawel. Looks good now.

mentioned in issue #5879 (closed)