Project

General

Profile

Actions

Bug #5336

closed

jenkins nodes use outdated version of debian-stretch-titan image

Added by osmith about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/03/2021
Due date:
% Done:

100%

Spec Reference:

Description

fixeria wrote:

I am trying to inderstand what's wrong with Docker here: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-msc-test/1484/consoleFull
ttcn3-msc-test #1484 Console [Jenkins]
Skip to content Dashboard TTCN3 ttcn3-msc-test #1484 Back to Project Status Changes Console Output View as plain text View Build Information Parameters Git Build Data Test Result Previous Build
it does `pip3 install git+git://git.osmocom.org/python/osmo-python-tests`, as far as I can see
---> Using cache
then ttcn3-tcpdump-stop.sh says: 'Missing osmo_interact_vty.py from osmo-python-tests!'
if I do the same commands in my local Docker environment, everything works

What happened:
  • debian-stretch-titan gets built locally on the jenkins node before ttcn3-msc-test. This version is up-to-date (has osmo-python-tests).
  • when building ttcn3-msc-test, the version built previously gets disregarded and instead debian-stretch-titan from the registry is used
  • the version from the registry does not get updated/pulled beforehand, so in this case it was an old version (did not have osmo-python-tests)
Two problems:
  • building debian-stretch-titan locally doesn't make sense, we use the version from the registry instead (the point is to use the registry as cache, so it gets built less frequently)
  • the version from the registry needs to be updated before using it

I'm about to post fixes for the two problems.

Actions #1

Updated by osmith about 1 year ago

  • % Done changed from 50 to 90

building debian-stretch-titan locally doesn't make sense

https://gerrit.osmocom.org/c/docker-playground/+/26442

the version from the registry needs to be updated before using it

https://gerrit.osmocom.org/c/docker-playground/+/26443

I have verified that this works as expected, by pushing to a branch and running ttcn3-msc-test from that branch. The unnecessary build is not done anymore, and the image used as base for ttcn3-msc-test is up-to-date. The "Missing osmo_interact_vty.py from osmo-python-tests!" message is gone. As usually done, afterwards I've deleted the build so it does not interfere with the daily test results.

Actions #2

Updated by osmith about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)