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

test-ibmcloud-ubuntu1604-x64-1 cannot clean workspace (Docker test issue) #3490

Closed
sophia-guo opened this issue Mar 26, 2024 · 7 comments
Closed

Comments

@sophia-guo
Copy link

test-ibmcloud-ubuntu1604-x64-1

ERROR: Cannot delete workspace :Unable to delete '/home/jenkins/workspace/Grinder/jvmtest/system/reproducibleCompare/temurin-build/.azure-devops/README.md'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.

https://ci.adoptium.net/view/Test_grinder/job/Grinder/9302/

@sxa could you help this ? And could you check the permission of this file? It's weird it's a normal file in the grinder job's workspace.

@sxa sxa self-assigned this Mar 26, 2024
@sxa sxa added this to the 2024-03 (March) milestone Mar 26, 2024
@sxa
Copy link
Member

sxa commented Mar 26, 2024

The whole of the temurin-build directory is owned by root:root including that file which I guess is just the first one in order when you look at the checked out directory.

root@test-ibmcloud-ubuntu1604-x64-1:/home/jenkins/workspace/Grinder/jvmtest/system/reproducibleCompare# ls -ld temurin-build/.azure-devops/README.md 
-rw-r--r-- 1 root root 3417 Mar 25 20:36 temurin-build/.azure-devops/README.md

The directory has now been deleted.

@sxa sxa closed this as completed Mar 26, 2024
@sophia-guo
Copy link
Author

Confused. The same build run on same agent https://ci.adoptium.net/view/Test_grinder/job/Grinder/9301/console, which doesn't have this issue and can delete the workspace correctly.

@sophia-guo
Copy link
Author

sophia-guo commented Mar 27, 2024

I'm hitting the same issue. Can I get root permission to this agent to see what happened? Same issues happen to test-ibmcloud-rhel7-x64-1, test-equinix_esxi-ubuntu2204-x64-1. Feels like common issues hiddened.

@sophia-guo
Copy link
Author

#3490 (comment)

@sxa

@sophia-guo sophia-guo reopened this Mar 27, 2024
@sxa
Copy link
Member

sxa commented Mar 28, 2024

Same issues happen to test-ibmcloud-rhel7-x64-1, test-equinix_esxi-ubuntu2204-x64-1. Feels like common issues hiddened.

I haven't seen the design of what you're doing other than it's replicating the existing reproducible build jobs on via the AQA test process and machines, but normally this would happen if you run things as root inside the container while using a mapped volume from the host inside the container. The normal build processes always run as the jenkins user inside the container. It's also possible that it's related to which docker implementation is on each machine, although I wouldn't expect any problems with the ubuntu2204 system (Note that test-equinix_esxi-ubuntu2204-x64-1 will be decommissioned very soon as part of #3292)

Can I get root permission to this agent to see what happened?

If you need that access, please use the normal process of raising an issue specifically for that. If you're able to do the investigation today then test-equinix_esxi-ubuntu2204-x64-1 might be the best choice.

@sxa
Copy link
Member

sxa commented Mar 28, 2024

Same issues happen to test-ibmcloud-rhel7-x64-1, test-equinix_esxi-ubuntu2204-x64-1.

I've cleaned those two up too.
(Path name for reference: temurin-build under /home/jenkins/workspace/Grinder/jvmtest/system/reproducibleCompare)

@sxa sxa modified the milestones: 2024-03 (March), 2024-04 (April) Apr 4, 2024
@sxa sxa changed the title test-ibmcloud-ubuntu1604-x64-1 cannot clean workspace test-ibmcloud-ubuntu1604-x64-1 cannot clean workspace (Docker test issue) Apr 24, 2024
@sxa
Copy link
Member

sxa commented Apr 24, 2024

Closing this for now as the immediate problem has been fixed, but it may come back :-)

@sxa sxa closed this as completed Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants