mbronk
commented
1 month ago Separately - if the above gets confirmed as an issue with just a single binding (ex.: pollytts), I'd like to propose considering it (separately) as a potential issue/enhancement for openhab-core (hopefully not karaf itself).
That is, a single addon should ideally not have a system-wide impact and cause all bundles to fail installing (and w/o crisp log allowing to identify the origin ).
PS. Apology for double posting. Just consider this note to be (likely) orthogonal to the primary root cause, so wanted it to be standalone to be able to link directly to it in the future.
openhab-bot
lsiepel
kaikreuzer
wborn
OH
4.2.0fails a 🧹 clean installation w/ pre-populatedaddons.cfgwith the following error:Causing none of the addons to install properly. Subsequent install attempts fail as well. Possibly some ordering/dependency issue between addons and core and may be related to
pollytts❔Full startup log - fresh instance, vanilla state (click to expand)
``` 18:16:34.587 [INFO ] [org.openhab.core.Activator ] - Starting openHAB 4.2.0 (Release Build) [174/12315] 18:16:42.163 [INFO ] [b.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007 18:16:52.377 [INFO ] [re.automation.internal.RuleEngineImpl] - Rule engine started. org.apache.karaf.features.internal.util.MultiException: Error: Error downloading mvn:org.apache.httpcomponents/httpclient-osgi/4.5.13 Error downloading mvn:org.apache.httpcomponents/httpcore-osgi/4.4.13 at org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.Isolation
4.2.0(vsn4.1.3is confirmed working)addons.kardownloaded)Dockerfilebelow)Possible cause:
Did not perform extensive testing (this may be a false lead❗), but on the surface it looks related to
pollyttsand changes introduced in openhab/openhab-addons#16294. Unsure if pollytts is the component at fault though, or just victim to other changes or dependency mix w/ other addons.To reproduce
Using the
Dockerfilelisted below:docker run --name openhab -p 8080:8080 --rm -it $(docker build -q .)addons.kar)docker run --name openhab -p 8080:8080 --rm -it $(docker build -q . --build-arg DOWNLOAD_ADDONS=1)docker run --name openhab -p 8080:8080 --rm -it $(docker build -q . --build-arg OPENHAB_VERSION=4.1.3)addons.kar)docker run --name openhab -p 8080:8080 --rm -it $(docker build -q . --build-arg OPENHAB_VERSION=4.1.3 --build-arg DOWNLOAD_ADDONS=1)
```Dockerfile FROM azul/zulu-openjdk:17-jre-headless-latest RUN apt-get -qq update && \ apt-get -qq -y --no-install-recommends install wget unzip supervisor -y ARG OPENHAB_VERSION="4.2.0" RUN mkdir -p /opt/openhab && \ wget -O /tmp/openhab-download.zip https://github.com/openhab/openhab-distro/releases/download/${OPENHAB_VERSION}/openhab-${OPENHAB_VERSION}.zip && \ unzip /tmp/openhab-download.zip -d/opt/openhab ARG DOWNLOAD_ADDONS=0 RUN /bin/bash -c "if [[ ${DOWNLOAD_ADDONS} -eq 1 ]]; then wget -P /opt/openhab/addons https://github.com/openhab/openhab-distro/releases/download/${OPENHAB_VERSION}/openhab-addons-${OPENHAB_VERSION}.kar; fi" # HACK: Using supervisor just to execute 2 processes (openhab and its console/log tail) in parallel for quick&dirty checks. # This should be replaced by proper orchestration or at least a dedicated entrypoint script (but... since it works...) COPY <
(👆 click to expand...)Dockerfilereproducing the issue (ref. table above for exact commands used)