← Back to issue list

Building with charm version 3.x does not install on bionic (Python >=3.7 is required, 3.6.9 is present)

View original Github issue

Metadata

Project
charmcraft
Number
#888
Type
issue
State
closed
Author
esunar
Labels
—
Created
Updated
Closed

Current evaluation

Closed as not a charmcraft bug: the 22.04-build/18.04-run config was invalid (OS Python 3.6.9 < 3.7), and the bionic build break was an upstream charm-tools 3.x regression fixed in juju/charm-tools#641; broader fix tracked in #878.

Resolution: closed not a bug

Reason: Maintainer facundobatista closed it on 2022-10-12 stating the original report had a wrong config (building on jammy for bionic/focal run-on) while the bionic build failure was fixed upstream in charm-tools (juju/charm-tools#641), and that remaining charmcraft-side work is tracked in #878.

Evaluated by: mr-cal-bot

No scores available.

Issue body

When we pack with charm 3.x does not install on bionic [Running functional tests with 3.x:](https://pastebin.ubuntu.com/p/ZyKf6V2hFg/) ``` type: charm parts: charm: source: src plugin: reactive build-snaps: - charm bases: - build-on: - name: ubuntu channel: "22.04" architectures: ["amd64"] run-on: - name: ubuntu channel: "22.04" architectures: - amd64 - name: ubuntu channel: "20.04" architectures: - amd64 - name: ubuntu channel: "18.04" architectures: - amd64 ``` [Running functional tests with 2.x:](https://pastebin.ubuntu.com/p/6nJVMzJZDN/) ``` type: charm parts: charm: source: src plugin: reactive build-snaps: - charm/2.x/stable bases: - build-on: - name: ubuntu channel: "22.04" architectures: ["amd64"] run-on: - name: ubuntu channel: "22.04" architectures: - amd64 - name: ubuntu channel: "20.04" architectures: - amd64 - name: ubuntu channel: "18.04" architectures: - amd64 ``` created a demo branch for easy tesing: ``` git clone -b charmcraft-bionic-bug https://git.launchpad.net/~esunar/charm-graylog make charm3 #fails make charm2 #sucess ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug Closed as not a charmcraft bug: the 22.04-build/18.04-run config was invalid (OS Python 3.6.9 < 3.7), and the bionic build break was an upstream charm-tools 3.x regression fixed in juju/charm-tools#641; broader fix tracked in #878.
stealth/space-bunny-alpha — closed not a bug Closed as not a charmcraft bug: the install failure was user config (building on Jammy for bionic target); the genuine bionic build break was fixed upstream in juju/charm-tools#641. Broader build-packages fix tracked in #878.
stealth/space-bunny-alpha — closed resolved Charm 3.x builds on Bionic were fixed upstream in juju/charm-tools#641. The separate Python mismatch resulted from building on Jammy for an Ubuntu 18.04 target.
stealth/space-bunny-alpha — closed resolved Charmcraft 3.x failed to build on Bionic because of charm-tools; fixed upstream by juju/charm-tools#641. Broader packaging work is tracked in charmcraft#878.
qwen3.6-35b-a3b-mtp-q6 — — Closed as invalid. The Python version error stemmed from a misconfigured build environment. The underlying charm-tools failure was fixed upstream in juju/charm-tools#641. Broader packaging improvements are tracked in #878.
qwen/qwen3.6-35b-a3b — — Closed as resolved. The failure originated from an incorrect build configuration. The underlying charm-tools 3.x bionic compatibility issue was fixed in juju/charm-tools#641. Broader packaging improvements are tracked in #878.
qwen3.6-35b-a3b-mtp-q6 — — Closed as resolved. Initial failure stemmed from a misconfigured bases setup. Subsequent bionic build failures were fixed upstream in juju/charm-tools#641. Broader improvements are tracked in issue #878.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#878 (confidence 90%)

    Reactive plugin not populating charm-tools build packages; the maintainer pointed to it as the place for the remaining charmcraft-side improvement

  • Likely Fixed By: charm-tools#641 (confidence 85%)

    fnordahl cited this upstream charm-tools fix as resolving the bionic/18.04 build failure caused by the 2.x-to-3.x migration

Related issues

Issue Project State Summary Similarity
#589 Unable to build a charm that deploys on xenial charmcraft closed Not a charmcraft bug: the charm failed on xenial because ops 1.2.0 (the pinned latest release) broke on Python 3.5 (canonical/operator#517). Author confirmed building with the latest operator framework from git deploys fine.
75%
#2259 Builds fail for 20.04 (in some common circumstances) charmcraft closed Fixed in canonical/charmcraft#2275 (commit 65d01ed5): charm builds now apply a bundled setuptools-scm constraint, avoiding the Python 3.8/3.9 all-source dependency cycle.
74%