David Galloway [Sat, 20 Dec 2025 20:30:00 +0000 (15:30 -0500)]
maas: Add'l error handling for unlocking
Fixed Scenario:
- lock is supposed to lock 3 machines
- lock starts deployment on the 2 non-broken machines
- lock encounters one of those machines is not in a MaaS state it expects (e.g., Broken)
- lock "unlocks" the 2 non-broken machines but they are not locked because Deployment is still running
- lock thinks it's done but the other 2 machines are still Deploying and will end up Allocated instead of Unlocked & Ready
Signed-off-by: David Galloway <david.galloway@ibm.com>
Zack Cerza [Wed, 19 Mar 2025 18:35:11 +0000 (12:35 -0600)]
lock.ops.unlock_one_safe: Invert run-match logic
When unlock_one_safe is called with run_name, the caller means to express
"unlock this node if it belongs to this run".
When it is called with run_name and job_id, it means "unlock this node if it
belongs to this job in this run".
We had inverted the logic, causing leaks on reimage failures.
Matan Breizman [Wed, 19 Nov 2025 13:49:36 +0000 (15:49 +0200)]
teuthology/task/pexec.py: add logs to command executed
The current output by pexec is:
```
INFO:teuthology.run_tasks:Running task pexec...
INFO:teuthology.task.pexec:Executing custom commands...
INFO:teuthology.task.pexec:Running commands on host ubuntu@smithi012.front.sepia.ceph.com
DEBUG:teuthology.orchestra.run.smithi012:> TESTDIR=/home/ubuntu/cephtest bash -s
```
The output should include the acutal command executed, similar to
exec.py:
```
INFO:teuthology.run_tasks:Running task exec...
INFO:teuthology.task.exec:Executing custom commands...
INFO:teuthology.task.exec:Running commands on role client.0 host ubuntu@smithi168.front.sepia.ceph.com
DEBUG:teuthology.orchestra.run.smithi168:> sudo TESTDIR=/home/ubuntu/cephtest bash -c 'sudo ceph osd pool create low_tier 4'
```