Hi folks
Been fiddling with the Bigdata charms today to try and update them as there are some required changes in there.
Anyway, with them updated, I try and kick them off on Xenial I’m seeing a lot of stuff like:
2020-09-29 15:14:03 DEBUG install Installing build dependencies: finished with status 'error'
2020-09-29 15:14:03 DEBUG install Complete output from command /var/lib/juju/agents/unit-namenode-5/.venv/bin/python3 -m pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-7q53pdh1 --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links wheelhouse -- setuptools>=42 wheel setuptools_scm[toml]>=3.4.1:
2020-09-29 15:14:03 DEBUG install Looking in links: wheelhouse
2020-09-29 15:14:03 DEBUG install Collecting setuptools>=42
2020-09-29 15:14:03 DEBUG install Could not find a version that satisfies the requirement setuptools>=42 (from versions: scm-1.17.0, 41.6.0)
2020-09-29 15:14:03 DEBUG install No matching distribution found for setuptools>=42
I’ve seen a few similar topics and also tried to use an older layer-basic and so on, but I’ve not yet found a winning combination. Any ideas?
I believe I’ve just hit the wheelhouse.txt lucky dip jackpot of:
pip>=18.1,<19.0
setuptools<42
toml
path <=13.0.0
setuptools-scm>=3.0<=3.4.1
charmhelpers>=0.4.0,<1.0.0
charms.reactive>=0.1.0,<2.0.0
wheel<0.34
zipp < 2.0.0
cory_fu
29 September 2020 19:36
3
Yeah, unfortunately these crop up from time to time because some requirement wants to pull in a newer version of setuptools, sometimes indirectly, which had hard compatibility breaks with older versions of pip which come from apt on older machines series. The latest one in layer-basic was netaddr and because of the way that the wheelhouse.txt files were processed with charm build, pinning it in the base layer didn’t get carried forward. The latest charm snap changed how the wheelhouse was built to address that, so make sure you’re using that, but you might still run into it due to requirements specified in other layers.
The new framework takes the approach of bundling the actual venv into the charm, rather than just the packages. This avoids the need to build the venv at install time but has the risk of making the charm architecture dependent if any binary / compiled packages are included (and also makes the charm itself larger). I’m not sure if there is something done to mitigate that risk, but it might be worth backporting the charmcraft behavior to charm build with a flag to choose which behavior you want.
dgft
1 April 2021 09:51
4
Still have some errors today (2021-04-01 no pun)
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Installing build dependencies: finished with status 'error'
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Complete output from command /var/lib/juju/agents/unit-zkf-0/.venv/bin/python3 -m pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-hfwk12fs --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links wheelhouse -- setuptools>=42 wheel setuptools_scm[toml]>=3.4.1:
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Looking in links: wheelhouse
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Collecting setuptools>=42
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Could not find a version that satisfies the requirement setuptools>=42 (from versions: scm-1.17.0, 41.6.0)
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install No matching distribution found for setuptools>=42
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install ----------------------------------------
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Command "/var/lib/juju/agents/unit-zkf-0/.venv/bin/python3 -m pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-hfwk12fs --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links wheelhouse -- setuptools>=42 wheel setuptools_scm[toml]>=3.4.1" failed with error code 1 in None
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install Traceback (most recent call last):
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install File "/var/lib/juju/agents/unit-zkf-0/charm/hooks/install", line 8, in <module>
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install basic.bootstrap_charm_deps()
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install File "lib/charms/layer/basic.py", line 208, in bootstrap_charm_deps
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install env=_get_subprocess_env())
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install raise CalledProcessError(retcode, cmd)
unit-zkf-0: 09:50:15 DEBUG unit.zkf/0.install subprocess.CalledProcessError: Command '['/var/lib/juju/agents/unit-zkf-0/.venv/bin/pip', 'install', '-U', '--force-reinstall', '--no-index', '--no-cache-dir', '-f', 'wheelhouse', 'charms.templating.jinja2', 'charmhelpers', 'wheel', 'path.py', 'jujuresources', 'pbr', 'six', 'netifaces', 'path', 'MarkupSafe', 'pyaml', 'Tempita', 'netaddr', 'charms.reactive', 'jujubigdata', 'PyYAML', 'Jinja2']' returned non-zero exit status 1.
unit-zkf-0: 09:50:15 ERROR juju.worker.uniter.operation hook "install" failed: exit status 1
unit-zkf-0: 09:50:27 DEBUG unit.zkf/0.install Reading package lists...
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install Building dependency tree...
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install Reading state information...
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install build-essential is already the newest version (12.4ubuntu1).
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install python3-setuptools is already the newest version (39.0.1-2).
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install python3-yaml is already the newest version (3.12-1build2).
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install python3-wheel is already the newest version (0.30.0-0.2).
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install python3-dev is already the newest version (3.6.7-1~18.04).
unit-zkf-0: 09:50:28 DEBUG unit.zkf/0.install python3-pip is already the newest version (9.0.1-2.3~ubuntu1.18.04.4).```
`charm` version (snap) is `2.8.2`
regards,
david
