Bug #5289
Updated by laforge over 2 years ago
As can be seen in https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian10/feed=nightly,label=repo-install-test/289/consoleFull , osmo-repo-install-* tests currently fail on all tested distributions with some osmo-hnodeb related error: <pre> + services_feed= osmo-bsc osmo-bts-virtual osmo-gbproxy osmo-gtphub osmo-hlr osmo-hnbgw osmo-mgw osmo-msc osmo-pcap-client osmo-pcu osmo-sgsn osmo-sip-connector osmo-stp osmo-pcap-server osmo-hnodeb + systemctl start osmo-bsc osmo-bts-virtual osmo-gbproxy osmo-gtphub osmo-hlr osmo-hnbgw osmo-mgw osmo-msc osmo-pcap-client osmo-pcu osmo-sgsn osmo-sip-connector osmo-stp osmo-pcap-server osmo-hnodeb Failed to start osmo-hnodeb.service: Unit osmo-hnodeb.service not found. + ret=1 + [ -n ] + docker container kill debian10-repo-install-test-nightly debian10-repo-install-test-nightly + exit 1 Build step 'Execute shell' marked build as failure Sending e-mails to: jenkins-notifications@lists.osmocom.org Finished: FAILURE </pre> <pre> First I thought the service file was not being packaged, but it is. The problem seems to be that the step "Installing all repository packages" doesn't actually install osmo-hnodeb. Further, it seems that the package is not building, it fails on each and every distribution and architecture: https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-hnodeb
