Launchpad CI job errors out on a snap error when using 'mantic' / 'noble' series

Bug #2038812 reported by Sebastien Bacher
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
lpci
In Progress
Low
Jürgen Gmach

Bug Description

I'm trying a simple CI job
https://git.launchpad.net/~seb128/update-manager/tree/.launchpad.yaml

But it's failing on launchpad
https://launchpadlibrarian.net/690716120/buildlog_ci_update-manager_4d3ff13726e3e20c09be1eed82f186f30fbb9d58_BUILDING.txt.gz

```
Running linter:0
cmd_run.go:1046: WARNING: cannot create user data directory: cannot create snap home dir: mkdir /nonexistent: permission denied
Sorry, home directories outside of /home needs configuration.
See https://forum.snapcraft.io/t/11209 for details.
Job failed
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lpbuildd/target/run_ci.py", line 240, in run
    self.run_job()
  File "/usr/lib/python3/dist-packages/lpbuildd/target/run_ci.py", line 232, in run_job
    self.run_build_command(args, env=env)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/run_ci.py", line 173, in run_build_command
    super().run_build_command(
  File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 62, in run_build_command
    return self.backend.run(args, cwd=cwd, env=full_env, **kwargs)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 716, in run
    subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-mantic-amd64', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/lpbuildd-git-proxy', '--env', 'SNAPPY_STORE_NO_CDN=1', '--', '/bin/sh', '-c', "cd /build/tree && linux64 runuser -u buildd -g buildd -G lxd -- /bin/bash -o pipefail -c 'lpci -v run-one --output-directory /build/output linter 0 2>&1 | tee /build/output/linter/0/log'"]' returned non-zero exit status 1.
```

Locally with the 0.2.4 snap the same job is failing with a key error on 'mantic' as series. Changing to 'devel' and the job is working locally but then launchpad is not even giving it a try as showed by the previous commit on https://code.launchpad.net/~seb128/update-manager/+git/update-manager/+ref/main

summary: - Launchpad job errors out on snap error when using 'mantic' serie
+ Launchpad CI job errors out on a snap error when using 'mantic' serie
Guruprasad (lgp171188)
summary: - Launchpad CI job errors out on a snap error when using 'mantic' serie
+ Launchpad CI job errors out on a snap error when using 'mantic' series
Jürgen Gmach (jugmac00)
Changed in lpci:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Jürgen Gmach (jugmac00) wrote : Re: Launchpad CI job errors out on a snap error when using 'mantic' series
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Still a problem for 'oracular' despite https://github.com/canonical/craft-providers/blob/main/craft_providers/bases/__init__.py#L64.

I also confirm 'devel' doesn't even run.

Revision history for this message
Barry Price (barryprice) wrote :

Seeing this on noble also. No issues under jammy.

Haw Loeung (hloeung)
summary: - Launchpad CI job errors out on a snap error when using 'mantic' series
+ Launchpad CI job errors out on a snap error when using 'mantic' /
+ 'noble' series
Revision history for this message
Jürgen Gmach (jugmac00) wrote :

Thanks for your patience! I might have missed the updates to this ticket.

@Nathan:
Yes, I can confirm, oracular support has not yet been added. I will work on that this morning.

@Nathan:
I cannot confirm that devel is not working, at least it works locally for me. Could you please link to a failing build?

@Barry:
I cannot confirm that building on noble is broken, at least it works locally for me. Could you please link to a failing build?

Revision history for this message
Jürgen Gmach (jugmac00) wrote (last edit ):

Update:
While oracular support has been added to the main branch for craft-providers, there is no released version on that. I will reach out to the Starcraft folks.

https://github.com/canonical/craft-providers/issues/580

Revision history for this message
Barry Price (barryprice) wrote (last edit ):

I've pastebinned a build log here showing this error on a noble build (Canonical internal only):

https://pastebin.canonical.com/p/GPJ9trkgpV/

The submodule errors are just noise, we see those on jammy as well but they're non-fatal.

The relevant errors begin at line 1540 in the paste.

To be clear, the same job works fine with jammy set in .launchpad.yaml, the diff that raises the errors is literally just s/jammy/noble/g

Revision history for this message
Jürgen Gmach (jugmac00) wrote :

@barryprice

While the other reported errors are about "Key not found for xyz series", your's is definitely different, as the error message reads like that:

```
cmd_run.go:1129: WARNING: cannot create user data directory: cannot create snap home dir: mkdir /nonexistent: permission denied
Sorry, home directories outside of /home needs configuration.
See https://forum.snapcraft.io/t/11209 for details.
```

Could you please create a new issue with all relevant information?
(maybe even a private one where you could share internal information; I think this would be related to your build, and not only to the fact that you use noble, as in general, noble works meanwhile).

Thank you!

Revision history for this message
Barry Price (barryprice) wrote :

That's the same error as given in the initial report, aside from the line number (cmd_run.go:1046 vs cmd_run.go:1129), but yeah, I don't see the second issue.

No problem, I've filed a separate private bug as LP:2069708

Jürgen Gmach (jugmac00)
Changed in lpci:
assignee: nobody → Jürgen Gmach (jugmac00)
status: Triaged → In Progress
Revision history for this message
Nathan Teodosio (nteodosio) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.