I'm seeing this too on imagebuilder step:
CalledProcessError: Command '['chroot', '/tmp/tmpVNABPa/mountpoint', '/usr/bin/apt-get', 'update']' returned non-zero exit status 100
I added a 5 min sleep on the lander_image_builder jenkins job, 5 min on lander_master before "/srv/lander_jenkins_sub/lander/bin/lander_merge_parameters.py --result-file params.json --service image_builder --output-file all.json --prior-file all.json" and another 5 min in cloud_image.py itself (imagebuilder) but still seeing the same error.
Image builder starting too soon could be an explanation for apt-get install to fail with 100, but I don't understand how apt-get update could fail with 100.
I'm seeing this too on imagebuilder step: /mountpoint' , '/usr/bin/apt-get', 'update']' returned non-zero exit status 100
CalledProcessError: Command '['chroot', '/tmp/tmpVNABPa
I added a 5 min sleep on the lander_ image_builder jenkins job, 5 min on lander_master before "/srv/lander_ jenkins_ sub/lander/ bin/lander_ merge_parameter s.py --result-file params.json --service image_builder --output-file all.json --prior-file all.json" and another 5 min in cloud_image.py itself (imagebuilder) but still seeing the same error.
Image builder starting too soon could be an explanation for apt-get install to fail with 100, but I don't understand how apt-get update could fail with 100.