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

Charmcraft 3.1.1 removed support for parts - when documentation clearly states it is deprecated #1782

Closed
MiaAltieri opened this issue Aug 2, 2024 · 5 comments · Fixed by #1785
Assignees
Labels
Bug Something isn't working triaged

Comments

@MiaAltieri
Copy link

Bug Description

Hi Charmcraft Team ⭐️

I am sure that someone has already notified you. But the recent release of charmcraft 3.1.1 has started breaking CI which uses snap in the parts file of VM Charms.

Granted : Warning: use of 'prime' in a charm part is deprecated and no longer works, see https://juju.is/docs/sdk/include-extra-files-in-a-charm

So I understand that prime is to eventually go away. But I would expect it to be still usable since the docs say:

If your charm currently uses the prime key to include extra files:

Note that, starting with Charmcraft 3.0, this key will become obsolete and you will see lint errors indicating that unknown additional files have been added.

Users can still use this method to filter existing files.

The key here being Users can still use this method to filter existing files.

So my question here, is Charmcraft broken or are the docs incorrect. Thank you

To Reproduce

charmcraft pack any charm that uses a parts section

Environment

Ubuntu - 22.04
Charmcraft - 3.1.1
LXD - 5.0.3-80aeff7

charmcraft.yaml

# Copyright 2023 Canonical Ltd.
# See LICENSE file for licensing details.

type: charm
bases:
  - build-on:
      - name: "ubuntu"
        channel: "22.04"
    run-on:
      - name: "ubuntu"
        channel: "22.04"
parts:
  charm:
    override-build: |
      rustup default stable
      craftctl default
    build-snaps:
      - rustup
    charm-binary-python-packages:
      - setuptools
      - cryptography
    build-packages:
      - build-essential
      - libffi-dev
      - libssl-dev
      - pkg-config
      - rustc
      - cargo
    prime:
      - charm_version
      - charm_internal_version
      - workload_version

Relevant log output

build-production: commands[0]> charmcraft pack
Warning: use of 'prime' in a charm part is deprecated and no longer works, see https://juju.is/docs/sdk/include-extra-files-in-a-charm
Warning: use of 'prime' in a charm part is deprecated and no longer works, see https://juju.is/docs/sdk/include-extra-files-in-a-charm
Failed to refresh package list: failed to run apt update.


===========================

cat /home/ubuntu/.local/state/charmcraft/log/charmcraft-20240802-121344.047276.log
2024-08-02 12:13:44.050 Starting charmcraft, version 3.1.1
2024-08-02 12:13:44.050 Log verbosity level set to BRIEF
2024-08-02 12:13:44.050 Configuring application...
2024-08-02 12:13:44.050 Preparing application...
2024-08-02 12:13:44.051 Build plan: platform=None, build_for=None
2024-08-02 12:13:44.053 Loading project file '/home/ubuntu/mongodb-operator/charmcraft.yaml'
2024-08-02 12:13:44.056 Warning: use of 'prime' in a charm part is deprecated and no longer works, see https://juju.is/docs/sdk/include-extra-files-in-a-charm
2024-08-02 12:13:44.067 Processing grammar (on amd64 for amd64)
2024-08-02 12:13:44.067 Processing grammar for override-build: rustup default stable
craftctl default
2024-08-02 12:13:44.067 Processing grammar for build-snaps: ['rustup']
2024-08-02 12:13:44.067 Not processing grammar for non-grammar enabled keyword charm-binary-python-packages
2024-08-02 12:13:44.067 Processing grammar for build-packages: ['build-essential', 'libffi-dev', 'libssl-dev', 'pkg-config', 'rustc', 'cargo']
2024-08-02 12:13:44.067 Processing grammar for prime: ['charm_version', 'charm_internal_version', 'workload_version']
2024-08-02 12:13:44.069 Running charmcraft:ubuntu-22.04-amd64 in amd64 instance...
2024-08-02 12:13:44.069 Preparing managed instance 'charmcraft-mongodb-on-amd64-for-amd64-1806485'
2024-08-02 12:13:44.069 Using hostname 'charmcraft-mongodb-on-amd64-for-amd64-1806485'
2024-08-02 12:13:44.077 Retrieved snap config: {}
2024-08-02 12:13:44.077 Using default provider 'lxd' on linux system.
2024-08-02 12:13:44.077 Checking if LXD is installed.
2024-08-02 12:13:44.113 LXD snap status: active
2024-08-02 12:13:44.113 Checking if LXD is installed.
2024-08-02 12:13:44.141 LXD snap status: active
2024-08-02 12:13:44.231 Executing on host: lxc --project default profile show local:default
2024-08-02 12:13:44.311 Launching managed ubuntu 22.04 instance...
2024-08-02 12:13:44.311 Executing on host: lxc remote list --format=yaml
2024-08-02 12:13:44.387 Remote 'craft-com.ubuntu.cloud-buildd' already exists.
2024-08-02 12:13:44.387 Executing on host: lxc project list local: --format=yaml
2024-08-02 12:13:44.457 Set LXD instance name to 'charmcraft-mongodb-on-amd64-for-amd64-1806485'
2024-08-02 12:13:44.457 Checking for instance 'charmcraft-mongodb-on-amd64-for-amd64-1806485' in project 'charmcraft' in remote 'local'
2024-08-02 12:13:44.457 Executing on host: lxc --project charmcraft list local: --format=yaml
2024-08-02 12:13:44.589 Instance 'charmcraft-mongodb-on-amd64-for-amd64-1806485' does not exist.
2024-08-02 12:13:44.589 Set LXD instance name to 'base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9'
2024-08-02 12:13:44.589 Checking for base instance 'base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9' in project 'charmcraft' in remote 'local'
2024-08-02 12:13:44.589 Executing on host: lxc --project charmcraft list local: --format=yaml
2024-08-02 12:13:44.715 Checking validity of instance 'base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9'.
2024-08-02 12:13:44.715 Executing on host: lxc --project charmcraft info local:base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9
2024-08-02 12:13:44.811 Executing on host: lxc --project charmcraft info local:base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9
2024-08-02 12:13:44.887 Executing on host: lxc --project charmcraft config get local:base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9 user.craft_providers.status
2024-08-02 12:13:44.958 Instance 'base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9' is ready.
2024-08-02 12:13:44.958 Instance is valid.
2024-08-02 12:13:44.958 Creating instance from base instance
2024-08-02 12:13:44.958 Creating instance from base instance 'base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9'.
2024-08-02 12:13:44.958 Executing on host: lxc --project charmcraft list local: --format=yaml
2024-08-02 12:13:45.100 Executing on host: lxc --project charmcraft copy local:base-instance-charmcraft-buildd-base-v7--910533fdd664bd2cdbe9 local:charmcraft-mongodb-on-amd64-for-amd64-1806485
2024-08-02 12:14:25.147 Executing on host: lxc --project charmcraft list local: --format=yaml
2024-08-02 12:14:25.289 Executing on host: lxc --project charmcraft config set local:charmcraft-mongodb-on-amd64-for-amd64-1806485 raw.idmap 'both 1000 0'
2024-08-02 12:14:25.396 Executing on host: lxc --project charmcraft config get local:charmcraft-mongodb-on-amd64-for-amd64-1806485 raw.idmap
2024-08-02 12:14:25.479 Got LXD idmap for instance 'charmcraft-mongodb-on-amd64-for-amd64-1806485': 'both 1000 0'
2024-08-02 12:14:25.479 Starting instance
2024-08-02 12:14:25.480 Executing on host: lxc --project charmcraft start local:charmcraft-mongodb-on-amd64-for-amd64-1806485
2024-08-02 12:14:25.955 Executing on host: lxc --project charmcraft file push /tmp/tmp2bjxahfj local:charmcraft-mongodb-on-amd64-for-amd64-1806485/etc/hostname --mode=0644
2024-08-02 12:14:26.061 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical chown root:root /etc/hostname
2024-08-02 12:14:26.176 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical hostname -F /etc/hostname
2024-08-02 12:14:26.285 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical test -f /etc/craft-instance.conf
2024-08-02 12:14:26.451 Executing on host: lxc --project charmcraft file pull local:charmcraft-mongodb-on-amd64-for-amd64-1806485/etc/craft-instance.conf /home/ubuntu/tmpoow4eyog.tmp-craft/tmphaae4c79
2024-08-02 12:14:26.526 Instance has already been setup.
2024-08-02 12:14:26.526 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical cat /etc/os-release
2024-08-02 12:14:26.716 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical test -f /etc/craft-instance.conf
2024-08-02 12:14:26.933 Executing on host: lxc --project charmcraft file pull local:charmcraft-mongodb-on-amd64-for-amd64-1806485/etc/craft-instance.conf /home/ubuntu/tmpl9xlw3sj.tmp-craft/tmpgnbbh79w
2024-08-02 12:14:27.048 Instance is compatible with compatibility tag 'charmcraft-buildd-base-v7'
2024-08-02 12:14:27.048 No cache path set, not mounting cache directories.
2024-08-02 12:14:27.048 Waiting for environment to be ready...
2024-08-02 12:14:27.048 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl is-system-running
2024-08-02 12:14:27.226 systemctl is-system-running status: starting
2024-08-02 12:14:27.476 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl is-system-running
2024-08-02 12:14:27.636 Waiting for networking to be ready...
2024-08-02 12:14:27.636 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical getent hosts snapcraft.io
2024-08-02 12:14:27.834 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical snap unset system proxy.http
2024-08-02 12:14:28.470 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical snap unset system proxy.https
2024-08-02 12:14:28.923 Installing snap 'charmcraft' with channel=None and classic=True
2024-08-02 12:14:28.923 Installing snap 'charmcraft' from host (classic=True)
2024-08-02 12:14:28.926 Installing base snap 'core22' for 'charmcraft' from host
2024-08-02 12:14:28.926 Installing snap 'core22' from host (classic=False)
2024-08-02 12:14:28.930 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical test -f /etc/craft-instance.conf
2024-08-02 12:14:29.197 Executing on host: lxc --project charmcraft file pull local:charmcraft-mongodb-on-amd64-for-amd64-1806485/etc/craft-instance.conf /home/ubuntu/tmpf6t11fbd.tmp-craft/tmp0n6bcj7s
2024-08-02 12:14:29.305 Revisions found: host='1380', target='1380'
2024-08-02 12:14:29.305 Skipping snap injection: target is already up-to-date with revision on host
2024-08-02 12:14:29.306 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical test -f /etc/craft-instance.conf
2024-08-02 12:14:29.471 Executing on host: lxc --project charmcraft file pull local:charmcraft-mongodb-on-amd64-for-amd64-1806485/etc/craft-instance.conf /home/ubuntu/tmp_cl59koe.tmp-craft/tmp9retsmi5
2024-08-02 12:14:29.561 Revisions found: host='4264', target='4264'
2024-08-02 12:14:29.561 Skipping snap injection: target is already up-to-date with revision on host
2024-08-02 12:14:29.690 Setting instance timezone to match host timezone 'Etc/UTC'.
2024-08-02 12:14:29.690 Executing on host: lxc --project charmcraft config set local:charmcraft-mongodb-on-amd64-for-amd64-1806485 environment.TZ Etc/UTC
2024-08-02 12:14:29.955 Executing on host: lxc --project charmcraft config device show local:charmcraft-mongodb-on-amd64-for-amd64-1806485
2024-08-02 12:14:30.042 Executing on host: lxc --project charmcraft config device add local:charmcraft-mongodb-on-amd64-for-amd64-1806485 disk-/root/project disk source=/home/ubuntu/mongodb-operator path=/root/project
2024-08-02 12:14:30.518 Instance launched and working directory mounted
2024-08-02 12:14:30.518 Pushing bashrc to instance
2024-08-02 12:14:30.518 Executing on host: lxc --project charmcraft file push /tmp/tmpep5v513o local:charmcraft-mongodb-on-amd64-for-amd64-1806485/root/.bashrc --mode=644
2024-08-02 12:14:30.610 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical chown root:root /root/.bashrc
2024-08-02 12:14:31.070 Executing ['charmcraft', 'pack'] in instance location /root/project with {'env': {'CRAFT_PLATFORM': 'ubuntu-22.04-amd64', 'CRAFT_VERBOSITY_LEVEL': 'BRIEF'}}.
2024-08-02 12:14:31.070 Emitter: Pausing control of the terminal
2024-08-02 12:15:17.668 Emitter: Resuming control of the terminal
2024-08-02 12:15:17.669 Executing in container: lxc --project charmcraft exec local:charmcraft-mongodb-on-amd64-for-amd64-1806485 -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical test -f /tmp/charmcraft.log
2024-08-02 12:15:17.785 Executing on host: lxc --project charmcraft file pull local:charmcraft-mongodb-on-amd64-for-amd64-1806485/tmp/charmcraft.log /home/ubuntu/tmp6hm8j0ec.tmp-craft/tmp72vxiive
2024-08-02 12:15:17.892 Logs retrieved from managed instance:
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.079 Starting charmcraft, version 3.1.1
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.079 Log verbosity level set to BRIEF
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.079 Configuring application...
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.079 Preparing application...
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.081 Build plan: platform=ubuntu-22.04-amd64, build_for=None
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.084 Loading project file '/root/project/charmcraft.yaml'
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.086 Warning: use of 'prime' in a charm part is deprecated and no longer works, see https://juju.is/docs/sdk/include-extra-files-in-a-charm
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Processing grammar (on amd64 for amd64)
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Processing grammar for override-build: rustup default stable
2024-08-02 12:15:17.892 :: craftctl default
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Processing grammar for build-snaps: ['rustup']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Not processing grammar for non-grammar enabled keyword charm-binary-python-packages
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Processing grammar for build-packages: ['build-essential', 'libffi-dev', 'libssl-dev', 'pkg-config', 'rustc', 'cargo']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.099 Processing grammar for prime: ['charm_version', 'charm_internal_version', 'workload_version']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.101 Setting up PackageService
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.102 Initialising lifecycle manager in /root
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.102 Project vars: {'version': 'unversioned'}
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.102 Adopting part: None
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.103 Using parallel build count of 8 from CPU count
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.104 is_snap: True, SNAP_NAME set to charmcraft
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 process charm:Step.PULL
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 add action charm:Step.PULL(ActionType.RUN)
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 process charm:Step.BUILD
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 add action charm:Step.BUILD(ActionType.RUN)
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 process charm:Step.STAGE
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 add action charm:Step.STAGE(ActionType.RUN)
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 process charm:Step.PRIME
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.105 add action charm:Step.PRIME(ActionType.RUN)
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 Initialising lifecycle
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 ignore patterns: []
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 part build packages: ['build-essential', 'libffi-dev', 'libssl-dev', 'pkg-config', 'rustc', 'cargo']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 plugin build packages: {'python3-setuptools', 'python3-pip', 'python3-dev', 'python3-venv', 'python3-wheel'}
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 part build snaps: ['rustup']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 Installing build-packages
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:36.106 Requested build-packages: ['build-essential', 'cargo', 'libffi-dev', 'libssl-dev', 'pkg-config', 'python3-dev', 'python3-pip', 'python3-setuptools', 'python3-venv', 'python3-wheel', 'rustc']
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.732 Marking python3-dev (and its dependencies) to be fetched
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.733 package: python3-dev
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.742 Marking python3-venv (and its dependencies) to be fetched
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.742 package: python3-venv
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.758 Marking libffi-dev (and its dependencies) to be fetched
2024-08-02 12:15:17.892 :: 2024-08-02 12:14:37.758 package: libffi-dev
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.772 Marking python3-wheel (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.772 package: python3-wheel
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.779 Marking python3-setuptools (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.779 package: python3-setuptools
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.788 Marking rustc (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.788 package: rustc
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.800 Marking libssl-dev (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.801 package: libssl-dev
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.818 Marking cargo (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.818 package: cargo
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.835 Marking pkg-config (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.835 package: pkg-config
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.853 Marking build-essential (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.853 package: build-essential
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.860 Marking python3-pip (and its dependencies) to be fetched
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.860 package: python3-pip
2024-08-02 12:15:17.893 :: 2024-08-02 12:14:37.896 Executing: ['apt-get', 'update']
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:09.460 :: Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:09.461 :: Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:09.461 :: Ign:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:09.489 :: Ign:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:10.463 :: Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:10.464 :: Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:10.464 :: Ign:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:10.493 :: Ign:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:12.465 :: Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:12.466 :: Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:12.467 :: Ign:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:12.495 :: Ign:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.467 :: Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.467 :: Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.468 :: Err:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.468 :: Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.469 :: Err:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.469 :: Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.496 :: Err:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:16.496 :: Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to security.ubuntu.com:80 (91.189.91.81), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to security.ubuntu.com:80 (91.189.91.83), connection timed out
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.490 :: Reading package lists...
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.502 :: E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease  Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.502 :: E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease  Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.502 :: E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease  Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.502 :: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to security.ubuntu.com:80 (91.189.91.81), connection timed out Could not connect to security.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to security.ubuntu.com:80 (91.189.91.83), connection timed out
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.502 :: E: Some index files failed to download. They have been ignored, or old ones used instead.
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.503 Failed to refresh package list: failed to run apt update.
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508 Traceback (most recent call last):
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/packages/deb.py", line 448, in refresh_packages_list
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     process_run(cmd)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/packages/deb.py", line 819, in process_run
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     os_utils.process_run(command, logger.debug, **kwargs)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/utils/os_utils.py", line 344, in process_run
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     raise subprocess.CalledProcessError(ret, command)
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508 subprocess.CalledProcessError: Command '['apt-get', 'update']' returned non-zero exit status 100.
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508 The above exception was the direct cause of the following exception:
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508 Traceback (most recent call last):
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_application/services/lifecycle.py", line 256, in run
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     with self._lcm.action_executor() as aex:
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/executor/executor.py", line 307, in __enter__
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     self._executor.prologue()
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/executor/executor.py", line 89, in prologue
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     self._install_build_packages()
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/executor/executor.py", line 249, in _install_build_packages
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     packages.Repository.install_packages(sorted(build_packages))
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/packages/deb.py", line 570, in install_packages
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     cls.refresh_packages_list()
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_parts/packages/deb.py", line 450, in refresh_packages_list
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508     raise errors.PackageListRefreshError(
2024-08-02 12:15:17.893 :: 2024-08-02 12:15:17.508 craft_parts.packages.errors.PackageListRefreshError: Failed to refresh package list: failed to run apt update.
2024-08-02 12:15:17.893 Executing on host: lxc --project charmcraft config device show local:charmcraft-mongodb-on-amd64-for-amd64-1806485
2024-08-02 12:15:17.975 Executing on host: lxc --project charmcraft config device remove local:charmcraft-mongodb-on-amd64-for-amd64-1806485 disk-/root/project
2024-08-02 12:15:18.109 Executing on host: lxc --project charmcraft stop local:charmcraft-mongodb-on-amd64-for-amd64-1806485
2024-08-02 12:15:22.213 Failed to execute charmcraft in instance.
2024-08-02 12:15:22.222 Traceback (most recent call last):
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_application/application.py", line 376, in run_managed
2024-08-02 12:15:22.222     instance.execute_run(  # pyright: ignore[reportUnknownMemberType,reportUnknownVariableType]
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_providers/lxd/lxd_instance.py", line 293, in execute_run
2024-08-02 12:15:22.222     return self.lxc.exec(
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_providers/lxd/lxc.py", line 387, in exec
2024-08-02 12:15:22.222     return runner(final_cmd, timeout=timeout, check=check, **kwargs)
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/usr/lib/python3.10/subprocess.py", line 526, in run
2024-08-02 12:15:22.222     raise CalledProcessError(retcode, process.args,
2024-08-02 12:15:22.222 subprocess.CalledProcessError: Command '['lxc', '--project', 'charmcraft', 'exec', 'local:charmcraft-mongodb-on-amd64-for-amd64-1806485', '--cwd', '/root/project', '--', 'env', 'CRAFT_MANAGED_MODE=1', 'CHARMCRAFT_MANAGED_MODE=1', 'DEBIAN_FRONTEND=noninteractive', 'DEBCONF_NONINTERACTIVE_SEEN=true', 'DEBIAN_PRIORITY=critical', 'CRAFT_PLATFORM=ubuntu-22.04-amd64', 'CRAFT_VERBOSITY_LEVEL=BRIEF', 'charmcraft', 'pack']' returned non-zero exit status 1.
2024-08-02 12:15:22.222
2024-08-02 12:15:22.222 The above exception was the direct cause of the following exception:
2024-08-02 12:15:22.222 Traceback (most recent call last):
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_application/application.py", line 541, in run
2024-08-02 12:15:22.222     self.run_managed(platform, build_for)
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/charmcraft/application/main.py", line 137, in run_managed
2024-08-02 12:15:22.222     super().run_managed(platform, build_for)
2024-08-02 12:15:22.222   File "/snap/charmcraft/4264/lib/python3.10/site-packages/craft_application/application.py", line 383, in run_managed
2024-08-02 12:15:22.222     raise craft_providers.ProviderError(
2024-08-02 12:15:22.222 craft_providers.errors.ProviderError: Failed to execute charmcraft in instance.
2024-08-02 12:15:22.222 Full execution log: '/home/ubuntu/.local/state/charmcraft/log/charmcraft-20240802-121344.047276.log'
ubuntu@ip-172-31-18-133:~/mongodb-operator$
@MiaAltieri MiaAltieri added the Bug Something isn't working label Aug 2, 2024
@jnsgruk
Copy link
Member

jnsgruk commented Aug 2, 2024

Yeh, we definitely still need to support parts - if this was intentional I'd like to understand why? :)

@carlcsaposs-canonical
Copy link
Contributor

Yeh, we definitely still need to support parts

fyi, it's still possible to prime files with something like canonical/mysql-operator#496

but the use of "deprecated" is confusing, since it's been removed instead of deprecated

Gu1nness added a commit to canonical/mongodb-operator that referenced this issue Aug 2, 2024
@lengau lengau added the triaged label Aug 2, 2024
@lengau lengau self-assigned this Aug 2, 2024
lengau added a commit that referenced this issue Aug 2, 2024
lengau added a commit to lengau/mongodb-operator that referenced this issue Aug 2, 2024
This fixes the charm packing incorrectly due to a behaviour change in
charmcraft 3.

See: canonical/charmcraft#1782
@lengau
Copy link
Collaborator

lengau commented Aug 2, 2024

Hi! Thanks for the report.

I agree the wording is confusing, so I've made a PR with hopefully better wording, and I will update the documentation too. I've also made this PR in the mongodb-operator charm as part of my testing.

@lengau
Copy link
Collaborator

lengau commented Aug 2, 2024

@MiaAltieri @carlcsaposs-canonical please this updated documentation and let me know if it needs further clarification:
https://juju.is/docs/sdk/include-extra-files-in-a-charm

Mehdi-Bendriss added a commit to canonical/mongodb-operator that referenced this issue Aug 6, 2024
## Issue

In Charmcraft 3, the behaviour of the `prime` keyword has changed, and
the warning and documentation are not clear about the change. See:
canonical/charmcraft#1782

## Solution

Use the `dump` plugin to include extra files, priming only the files
needed.

---------

Co-authored-by: Mehdi Bendriss <[email protected]>
@lengau
Copy link
Collaborator

lengau commented Aug 7, 2024

I haven't heard back so I presume these doc changes are okay. The code changes are included in the 3.1.2 hotfix, but please let me know if the doc changes are still confusing.

@lengau lengau closed this as completed Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants