Upgrade `test-ibm-ubuntu1804-x64-1` to Ubuntu 22.04

[targos]

https://ci.nodejs.org/computer/test%2Dibm%2Dubuntu1804%2Dx64%2D1/

It needs Node.js to run linter jobs.
ESLint v9 requires recent versions of Node.js but those cannot run on Ubuntu 18.04.

Blocks: nodejs/node#52780

[targos]

We could also take the opportunity to introduce Ubuntu 24.04 in CI.

[richardlau]

We could also take the opportunity to introduce Ubuntu 24.04 in CI.

Sounds reasonable if it's an option on the providers.

FWIW This machine is one of three jenkins-workspace machines, all of which are meant to be able to run the linter job. The other two are currently hosted on Equinix Metal and need to be migrated somewhere else (#3597).

[targos]

It's not an option yet on IBM Cloud.

I put the machine offline and will wait until it finishes its current jobs.

Looking at https://github.com/nodejs/build/blob/main/ansible/MANUAL_STEPS.md#jenkins-workspace, it seems I need a Coverity login. Do I have to create an account and ask for access?

[richardlau]

Yes. I've invited your email to the project as an owner.

[targos]

I did an "OS reload" on https://cloud.ibm.com/gen1/infrastructure/virtual-server/101642536/details and now I wonder if I made a mistake, because the machine doesn't have a large disk:

root@test-ibm-ubuntu2204-x64-3:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           390M  1.1M  389M   1% /run
/dev/xvda2       24G  1.6G   21G   7% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/xvda1      975M   55M  869M   6% /boot
tmpfs           390M  4.0K  390M   1% /run/user/0

[targos]

Also:

TASK [jenkins-workspace : Link to repository directory from bintmp home] ***********************************************************************************************
changed: [test-ibm-ubuntu2204-x64-3]

TASK [jenkins-workspace : Initialize Git repository] *******************************************************************************************************************
[WARNING]: Module remote_tmp /home/binary_tmp/.ansible/tmp did not exist and was created with a mode of 0700, this may cause issues when running as another user. To
avoid this, create the remote_tmp dir with the correct permissions manually
fatal: [test-ibm-ubuntu2204-x64-3]: FAILED! => {"changed": false, "cmd": "/usr/bin/git clone --bare https://github.com/nodejs/node /home/binary_tmp/binary_tmp.git", "msg": "Cloning into bare repository '/home/binary_tmp/binary_tmp.git'...\nfatal: Invalid path '/home/iojs/build': Permission denied", "rc": 128, "stderr": "Cloning into bare repository '/home/binary_tmp/binary_tmp.git'...\nfatal: Invalid path '/home/iojs/build': Permission denied\n", "stderr_lines": ["Cloning into bare repository '/home/binary_tmp/binary_tmp.git'...", "fatal: Invalid path '/home/iojs/build': Permission denied"], "stdout": "", "stdout_lines": []}

[targos]

I get the same error if I execute the playbook on one of the equinix hosts.

[richardlau]

I did an "OS reload" on https://cloud.ibm.com/gen1/infrastructure/virtual-server/101642536/details and now I wonder if I made a mistake, because the machine doesn't have a large disk:

root@test-ibm-ubuntu2204-x64-3:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           390M  1.1M  389M   1% /run
/dev/xvda2       24G  1.6G   21G   7% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/xvda1      975M   55M  869M   6% /boot
tmpfs           390M  4.0K  390M   1% /run/user/0

The storage tab in the web UI shows the 1000 GB disk is attached so I'd guess we need to mount it. It's probably /dev/xvdc1:

root@test-ibm-ubuntu2204-x64-3:~# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
loop1     7:1    0 40.4M  1 loop /snap/snapd/20671
loop2     7:2    0   87M  1 loop /snap/lxd/27037
loop3     7:3    0 38.7M  1 loop /snap/snapd/21465
loop4     7:4    0 63.9M  1 loop /snap/core20/2264
loop5     7:5    0   87M  1 loop /snap/lxd/28373
loop6     7:6    0 63.9M  1 loop /snap/core20/2318
xvda    202:0    0   25G  0 disk
├─xvda1 202:1    0    1G  0 part /boot
└─xvda2 202:2    0   24G  0 part /
xvdb    202:16   0    2G  0 disk
└─xvdb1 202:17   0    2G  0 part [SWAP]
xvdc    202:32   0 1000G  0 disk
└─xvdc1 202:33   0 1000G  0 part
xvdh    202:112  0   64M  0 disk
root@test-ibm-ubuntu2204-x64-3:~#

I'm not sure if it was supposed to be mounted as /home or /home/iojs.

I wasn't able to find any references to this machine in this repository, but the IBM hosted Docker host may have a similar /etc/fstab entry we could try: #2494 (comment)

The Ansible issue looks like a permissions problem, maybe some refactor to the Ansible scripts since the last time we set up jenkins-workspace machines (#3036) has broken it. IIRC the temp git repository in /home/binary_tmp/binary_tmp.git is owned by binary_tmp but there's a symlink to /home/iojs which is owned by iojs.

[targos]

@richardlau Feel free to take this over if you have the time :)

[ryanaslett]

The other two are currently hosted on Equinix Metal and need to be migrated somewhere else (#3597).

I was about to embark on setting up two new jenkins workspace hosts on mnx.io, so I'm very interested to know if there are changes that need to be made to make that possible (re:)

maybe some refactor to the Ansible scripts since the last time we set up jenkins-workspace machines

[richardlau]

I have the disk mounted now by adding

/dev/xvdc1      /home/iojs   ext4    defaults        0       0

to /etc/fstab and rebooting the machine. (I first tried mounting at /home but it looks like the disk has the contents of a user (iojs)). I'll PR something to MANUAL_STEPS.md.

root@test-ibm-ubuntu2204-x64-3:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           390M  1.1M  389M   1% /run
/dev/xvda2       24G  5.3G   18G  24% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/xvda1      975M  104M  821M  12% /boot
/dev/xvdc1      984G  223G  711G  24% /home/iojs
tmpfs           390M  4.0K  390M   1% /run/user/0
root@test-ibm-ubuntu2204-x64-3:~#

I don't think we'll need to do this for the Equinix machines depending on how the disks were set up (on IBM Cloud the default disk tends to be 25G with additional storage as extra disks).

I'll rerun the Ansible script from #3715 and have a look at the Ansible failure.