← Back to issue list

Charm packing error not logged

View original Github issue

Metadata

Project
charmcraft
Number
#587
Type
issue
State
closed
Author
cmatsuoka
Labels
—
Created
Updated
Closed

Current evaluation

Missing pip errors were already logged by Charmcraft 1.3+90.g5e5efc7, so the report was closed as already resolved.

Resolution: closed resolved

Reason: Maintainer facundobatista reproduced the packing failure and confirmed the missing-package error appeared in the execution log on version 1.3+90.g5e5efc7.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This happend when working on top of e2fc372 so it may be the result of a non-implemented or partially implemented feature. In this case, please ignore this report. If I run `charmcraft pack --verbose` on a project that requests a bad python package, it fails with the error message: ``` (...) 2021-11-02 18:52:45.723 :: 2021-11-02 21:52:44.321 :: 2021-11-02 21:52:44.321 Installing dependencies 2021-11-02 18:52:46.307 :: 2021-11-02 21:52:45.723 :: 2021-11-02 21:52:44.321 Running external command ['python3', '-m', 'venv', '/root/parts/charm/build/staging-venv'] 2021-11-02 18:52:46.327 :: 2021-11-02 21:52:46.306 :: 2021-11-02 21:52:45.722 Running external command ['/root/parts/charm/build/staging-venv/bin/pip3', '--version'] 2021-11-02 18:52:47.290 :: 2021-11-02 21:52:46.327 :: 2021-11-02 21:52:46.306 :: pip 20.0.2 from /root/parts/charm/build/staging-venv/lib/python3.8/site-packages/pip (python 3.8) 2021-11-02 18:52:47.290 :: 2021-11-02 21:52:47.289 :: 2021-11-02 21:52:46.327 Running external command ['/root/parts/charm/build/staging-venv/bin/pip3', 'install', '--upgrade', '--no-binary', ':all:', 'nonexisting'] 2021-11-02 18:52:47.330 :: 2021-11-02 21:52:47.290 :: 2021-11-02 21:52:47.289 :: ERROR: Could not find a version that satisfies the requirement nonexisting (from versions: none) 2021-11-02 18:52:47.330 :: 2021-11-02 21:52:47.330 :: 2021-11-02 21:52:47.290 :: ERROR: No matching distribution found for nonexisting (...) ``` However, if i just run `charmcraft --pack` on the same project and look at the log file after packing fails, it seems that the error message is not logged: ``` $ charmcraft pack Failed to build charm for bases index '0'. Full execution log: '/home/claudio/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20211102-185622.766340.log' $ grep ERROR /home/claudio/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20211102-185622.766340.log | wc -l 0

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Missing pip errors were already logged by Charmcraft 1.3+90.g5e5efc7, so the report was closed as already resolved.
stealth/space-bunny-alpha — closed resolved Already fixed in Charmcraft 1.3+; the missing pip installation errors now appear in packing logs.
qwen3.6-35b-a3b-mtp-q6 — — Resolved in version 1.3+. Testing confirmed pip installation failures are now correctly recorded in the execution log, closing the report as fixed.
qwen/qwen3.6-35b-a3b — — Charm packing errors were not captured in the execution log. The issue was resolved, with verification in version 1.3+90.g5e5efc7 confirming ERROR messages now correctly appear in logs upon build failure.
qwen3.6-35b-a3b-mtp-q6 — — Charm packing errors were not logged during failed builds. Closed as fixed; later testing confirms error messages now correctly appear in the execution log.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#922 Unable to pack charms on a GCP instance charmcraft closed Closed as not a Charmcraft bug: Focal's old setuptools broke pip's wheel installation. Preinstalling setuptools via charm-python-packages works around it; #923 tracked the same regression.
72%
#701 `charmcraft pack` doesn't include all error output charmcraft closed Missing charmcraft pack error output was fixed in Charmcraft 1.5 through improved managed-instance log retrieval; the reporter was using 1.4.0, so the issue was closed.
71%