Request for LAB IP CIDRs

Description

We would like to test OpenCI workload integrated with LAVA/TuxSuite running in Linaro. Our staging Jenkins is set up to allow only access to allowed IP addresses. LAVA/TuxSuite needs to fetch artifacts stored in (staging) Jenkins. For this purpose, could you please provide us LAVA/TuxSuite CIDRs so that we can allow accesss from those to staging Jenkins.

Environment

None

Activity

Show:

Paul Sokolovskyy December 6, 2024 at 9:17 AM

No longer needed, we have made https://jenkins.openci-test.arm.com/ public

, that’s good news, would cover “LAVA/Tux can’t access artifacts“ blocker. Do we expect proxy connection to still be needed for some services in the future, or can we “forget” about it?

Saheer Babu December 5, 2024 at 6:49 PM
Edited

Close this please. No longer needed, we have made https://jenkins.openci-test.arm.com/ public

Benjamin Copeland December 5, 2024 at 10:37 AM

it would be helpful if you could drop the line that you see it the issue, so I don’t have to crawl through the log

 

So it tempates here waiting for LAVA/Tux jobs. Which isn’t very helpful. The IP I gave you is lab, but like I say, Tux is a AWS pool of addresses so its there isn't a CIDR. Not unless you just open up a massive range. This needs debugging from your side to tell me where your system is hitting the block then I can advise on what to open

Saheer Babu December 4, 2024 at 4:08 PM

Thanks

Is 51.148.40.10 lab IP of LAVA or TuxSuite? From what I see TuxSuite/LAVA jobs are still failing to fetch the artifacts. What information would you need? This is the job we are executing: https://jenkins.openci-test.arm.com/view/TF-M/job/tf-m-nightly/4/

Karen Power December 3, 2024 at 10:33 AM

HI Please let us know if we can close this ticket now that has provided the IP address? Thanks.

Unresolved

Details

Assignee

Reporter

Share Visibility

Paul Sokolovskyy

Priority

Checklist

Sentry

Created November 19, 2024 at 1:40 PM
Updated December 6, 2024 at 9:17 AM