You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL-7.7 (and 7.4) - controller, various versions of RHEL on agents (not related to this issue).
Reproduction steps
Configure an OpenStack agent that will use a volumeFromImage boot source.
Provision the agent.
Configure CLI access to the OpenStack cloud.
Display agent VM properties via CLI (openstack server show <vm-name>)
Expected Results
The VM uses just a volume created from the image, but not the image itself. I. e. the image field in the VM properties shows N/A (booted from volume).
Actual Results
The VM uses both the volume created from image (which is fine), but also the image the volume was created from. I. e. the image field in the VM properties shows the image name.
The reason this is actually a problem is that if you need to manipulate with the image being used (say, delete the image and recreate an updated one with the same name), it fails. For comparison, if you create a VM via OpenStack web UI that boots from a volume based on an image, it behaves in the expected way (no image associated to the VM after it has been spun up, therefore it's possible to delete the image).
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL-7.7 (and 7.4) - controller, various versions of RHEL on agents (not related to this issue).
Reproduction steps
volumeFromImage
boot source.openstack server show <vm-name>
)Expected Results
The VM uses just a volume created from the image, but not the image itself. I. e. the
image
field in the VM properties showsN/A (booted from volume)
.Actual Results
The VM uses both the volume created from image (which is fine), but also the image the volume was created from. I. e. the
image
field in the VM properties shows the image name.The reason this is actually a problem is that if you need to manipulate with the image being used (say, delete the image and recreate an updated one with the same name), it fails. For comparison, if you create a VM via OpenStack web UI that boots from a volume based on an image, it behaves in the expected way (no image associated to the VM after it has been spun up, therefore it's possible to delete the image).
Anything else?
No response
The text was updated successfully, but these errors were encountered: