Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oracular and devel images fails due to systemd-resolved issue in Ubuntu 24.10 #598

Open
mr-cal opened this issue Jul 19, 2024 · 0 comments
Labels
Bug Something isn't working

Comments

@mr-cal
Copy link
Collaborator

mr-cal commented Jul 19, 2024

Bug Description

ubuntu.BuilddBaseAlias.ORACULAR and ubuntu.BuilddBaseAlias.DEVEL fail when launching a LXD container due to a problem with the buildd images and systemd-resolved.

Same as canonical/snapcraft#4921

To Reproduce

Run script below:

part yaml

#! /usr/bin/env python3

from pathlib import Path
import logging

from craft_providers import bases, lxd

logging.basicConfig(level="DEBUG")

provider = lxd.LXDProvider(lxd_project="project1")

provider.ensure_provider_is_available()

alias = bases.BuilddBaseAlias.ORACULAR
my_base = bases.BuilddBase(alias=alias)

with provider.launched_environment(
    project_name = "hello-world",
    project_path = Path().absolute(),
    base_configuration=my_base,
    build_base=alias.value,
    instance_name = "test-instance",
    allow_unstable=True,
) as instance:
    instance.execute_run(["ls"])

Relevant log output

Failed to setup systemd-resolved.
* Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v7-c-9d4e2b684569fe719a0d -- env CRAFT_MANAGED_MODE=1 SNAPCRAFT_BUILD_INFO=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl restart systemd-resolved'
* Command exit code: 1
* Command standard error output: b'Job for systemd-resolved.service failed because the control process exited with error code.\nSee "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details.\n'

...

systemctl status systemd-resolved.service
× systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2024-07-11 14:57:45 UTC; 37s ago
 Invocation: fe747a54d0294da4af991ec064327654
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
   Main PID: 99 (code=exited, status=243/CREDENTIALS)
@mr-cal mr-cal added the Bug Something isn't working label Jul 19, 2024
lengau added a commit to canonical/charmcraft that referenced this issue Jul 22, 2024
Ubuntu Mantic is now EOL, causing launches to fail. Unfortunately, we
cannot replace this with oracular due to
canonical/craft-providers#598
lengau added a commit to canonical/charmcraft that referenced this issue Jul 22, 2024
Ubuntu Mantic is now EOL, causing launches to fail. Unfortunately, we
cannot replace this with oracular due to
canonical/craft-providers#598

Fix for Oracular is scheduled in
#1748

Spread test failure is fixed in #1744
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant