The Cloud-Services project tag is not intended to have any tasks. Please check the list on https://phabricator.wikimedia.org/project/profile/832/ and replace it with a more specific project tag to this task. Thanks!

UPDATE: The instance has restarted but apparently has no longer the key pair associated. I tried to ssh in from login.toolforge.org and bastion.wmflabs.org, without success.

Mentioned in SAL (#wikimedia-cloud) [2025-01-24T15:37:25Z] <dhinus> openstack server migrate {petscan5_id} T384642

Migrating the VM fixed the issue, probably caused by T383583: VM nova records attached to incorrect cloudcephmon IPs.

@Magnus uh weird, it was working for my user so I assumed that fixed it for everyone. Looking.

My key pair was gone so I just made a new PetScan one, if that helps?

The keys that I would expect to work are the ones you can find listed at https://ldap.toolforge.org/user/magnus

Yes I meant the OpenStack keys

petscan's "This web service cannot be reached" has continued to come and go (T384464), and is currently at issue (despite that other ticket's being closed). Could it be that the root cause of this issue is remains unresolved @Magnus ? Thank you for your help.

Restarted the VM, seems to work now

Hi, this is still an issue, the tool as of today is not reachable :/

It appears that this is not a software issue of PetScan, but the frequent need to reboot the VM perhaps has something to do with T385288.

Hello, also see

• https://github.com/magnusmanske/petscan_rs/issues/187
• https://phabricator.wikimedia.org/T384464

Working on it.

I have limited the RAM for PetScan via systemctl, which also should restart PetScan after VM reboot. Please let me know if that doesn't take care of the problem.