No image with a name or ID of 'bm-deploy-kernel' exists.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Derek Higgins |
Bug Description
We have had quit a lot of ci failures lately with
2015-10-01 16:43:52.366 | + /tmp/tripleo.sh --register-nodes
2015-10-01 16:43:52.381 | #################
2015-10-01 16:43:52.381 | tripleo.sh -- Register nodes
2015-10-01 16:43:52.381 | #################
2015-10-01 16:43:52.381 | You must source a stackrc file for the Undercloud.
2015-10-01 16:43:52.381 | Attempting to source stackrc at /home/stack/stackrc
2015-10-01 16:43:52.486 | Done.
2015-10-01 16:44:02.112 | +------
2015-10-01 16:44:02.112 | | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance |
2015-10-01 16:44:02.112 | +------
2015-10-01 16:44:02.113 | | 493d532e-
2015-10-01 16:44:02.113 | | 1d783320-
2015-10-01 16:44:02.113 | +------
2015-10-01 16:44:04.359 | No image with a name or ID of 'bm-deploy-kernel' exists.
2015-10-01 16:44:04.407 | + postci
Digging into the image build logs the error can be seen
+ echo dib-run-parts Thu Oct 1 16:26:34 UTC 2015 Running /var/tmp/
dib-run-parts Thu Oct 1 16:26:34 UTC 2015 Running /var/tmp/
+ target_
+ date +%s.%N
+ /var/tmp/
find: './proc/4352': No such file or directory
/dev/loop0: [2049]:1054013 (/var/tmp/
We fixed this a while back by preventing find from traversing the proc filesystem /review. openstack. org/#/c/ 230448/
https:/