nodepool/unmanaged_image_id-cf916620abc630e4.yaml at 75adc01f0a3c8bba3db9fd34aa7880cf04faff88 - nodepool - OpenDev: Free Software Needs Free Tools

zuul/nodepool

David Shrewsbury d39cc6d7ce Fix for referencing cloud image by ID

For pre-existing cloud images (not managed by nodepool), referencing
them by ID was failing since they could not be found with this data,
only by name.

Current code expects the shade get_image() call to accept a dict with
an 'id' key, which will return that same dict without any provider API
calls. This dict can then be used in createServer() to bypass looking
up the image to get the image ID. However, shade does not accept a dict
for this purpose, but an object with an 'id' attribute. This is
possibly a bug in shade to not accept a dict. But since nodepool knows
whether or not it has an ID (image-id) vs. an image name (image-name),
it can bypass shade altogether when image-id is used in the config.

Note: There is currently no image ID validation done before image
creation when an image-id value is supplied. Not even shade validated
the image ID with a passed in object. Server creation will fail with
an easily identifiable message about this, though.

Change-Id: I732026d1a305c71af53917285f4ebb2beaf3341d
Story: 2002013
Task: 19653

2018-07-03 15:26:33 -04:00

7 lines

181 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     For pre-existing cloud images (not managed by nodepool), referencing
     them by ID was failing since they could not be found with this data,
     only by name.