lp:~andersson123/utah

Author: Tim Andersson
Author Date: 2025-08-14 13:35:54 UTC

use --prompt to fix disparities between sudo and sudo-rs

`sudo` and `sudo-rs` have different password prompts by default, but
they both offer the `--prompt` arg, allowing users to specify their own
password prompt.

This fixes the disparities between 25.10+ and 25.04- releases.

Author: Tim Andersson
Author Date: 2025-08-11 14:26:06 UTC

fix: check for sudo prompts from both coreutils and sudo-rs

Since sudo-rs has landed in questing images, the server image promotion
has been failing.

Utah expects the password prompt from coreutils:
```
[sudo] password for $USER:
```

But is instead met with the prompt from sudo-rs:
```
[sudo: authenticate] Password:
```

So this commit modifies Utah to expect one, then the other.

Author: Tim Andersson
Author Date: 2025-07-01 13:26:47 UTC

Make GitHandler behave the same as BzrHandler(branch=False)

lp:ubuntu-test-cases has moved from bzr to git, so this is now a
necessary change.

This functionality is utilised in the live-server smoke testing.

The `.run` files [1] are fetched, parsed, and then the relevant Handler
in vcs.py uses the contents of the `.run` file to fetch the directory
containing the specified test cases. For example, a `.run` file like
this:
```
testsuites:
  - name: multipath
    fetch_method: bzr-export
    fetch_location: https://code.launchpad.net/ubuntu-test-cases/live-server/testsuites/multipath
```
Would, in the case of these smoke tests, run:
```
bzr export multipath https://code.launchpad.net/ubuntu-test-cases/live-server/testsuites/multipath
```
And the multipath directory would then contain everything in
ubuntu-test-cases/testsuites/multipath from the live-server branch.

The GitHandler did not mirror this functionality. It instead would
attempt (and fail) to (with the same `.run` file):
```
git clone https://code.launchpad.net/ubuntu-test-cases/live-server/testsuites/multipath multipath
```

This commit amends the issue. It does so in an admittedly hacky way. It
now assumes to modify the aforementioned `.run` file to:
```
testsuites:
  - name: multipath
    fetch_method: git
    fetch_location: https://code.launchpad.net/ubuntu-test-cases$live-server$testsuites/multipath
```

Wherein utah now parses the branch and path information from the
`fetch_location` string. There's most definitely better ways to do this
but as aforementioned in previous commits I want a minimal delta when
contributing to utah.

utah then does the following:
```
git clone -b live-server -n --depth=1 --filter=tree:0 https://git.launchpad.net/ubuntu-test-cases/ multipath
git sparse-checkout set --no-cone /testsuites/multipath
```

Which almost achieves the same thing as the `bzr export` command
mentioned above, solving the issue. The only extra change required is
then to "squash" the sparse checkout. bzr export exports the contents of
a nested directory to the root of the output directory, whereas git
sparse-checkout preserves the nested directories. There is a flag in the
GitHandler to emulate the bzr export behaviour.

No other automation is using the GitHandler, or even utah, so it's
pretty low risk, and fixes the prevalent issue at hand.

[1] https://git.launchpad.net/ubuntu-test-cases/tree/runlists/multipath.run?h=bzr-import-live-server

Author: Tim Andersson
Author Date: 2024-11-20 09:47:19 UTC

remove preseed from file_list_udi

From plucky onwards, the preseed file is not intended to be in desktop
isos. To avoid more complicated heuristics, rather than checking the
series of each iso, we will just drop the preseed file from
file_list_udi.

Author: Tim Andersson
Author Date: 2024-06-20 12:51:48 UTC

smoke tests hack: issue reboot instead of poweroff in qemu-setup.py

The iso smoke tests (particularly the desktop ones) have recently been
getting flakier and flakier.

The install would succeed, then boot up, run qemu-setup.py, and shut
off. After which, the vm would rarely boot up again. My hunch is there's
a race condition somewhere after line 606 in utah/provisioning/vm.py
[1], in which the `create` command (which boots the vm) seemingly just
wouldn't boot the vm. Tried a lot of cowboys, adding in extra sleeps,
etc, but this seemed to be the only fix that consistently worked.

This commit amends the issue by issuing a reboot command in
qemu-setup.py rather than a poweroff command.

We should keep an eye out for any regressions due to this change on
platform-qa-jenkins, though there haven't been any yet.

[1] https://git.launchpad.net/utah/tree/utah/provisioning/vm.py#n606

Author: Tim Andersson
Author Date: 2023-09-01 13:04:40 UTC

another attempted fix

Author: Tim Andersson
Author Date: 2023-07-11 12:02:56 UTC

fix: Add more forceful vm shutdown commands to delete vm's

Previously vm's on venonat would end up in a "shut off" state without
deleting the storage. This commit amends this and is tested on venonat.

Author: Tim Andersson
Author Date: 2023-06-13 14:06:45 UTC

add check for vm shutoff before undefine

`https://libvirt.gitlab.io/libvirt-appdev-guide-python/libvirt_application_development_guide_using_python-Guest_Domains-Information-State.html`

Author: Paride Legovini
Author Date: 2023-04-05 08:55:45 UTC

Merge remote-tracking branch 'seb128/desktop-udi-provisioning'

Author: Jean-Baptiste Lallement
Author Date: 2021-01-14 08:04:56 UTC

Clean up file list ofr static validation

Following the clean up done in debian-cd (debian-cd/ubuntu r2102) update
the file list accordingly.

Author: Jean-Baptiste Lallement
Author Date: 2020-09-17 10:44:00 UTC

Skip UEFI tests on Groovy

On Groovy, EFI files now reside on their own ESP and the directory
containing them on the ISO has been removed. This directory still exists
on previous releases.
This may be revisited in the future, so skip it only for Groovy until a
decision is made (LP: #1895131)