Hi, we're already on Epoxy, so there might have been some changes, but I don't have the issue you describe. I could successfully rescue an "orphaned" VM (base image is not present anymore) with a new ISO. In my case it's a "flattened" RBD image (we use Ceph as our storage backend), so it is definitely independent of the deleted base image. Do you have more logs, maybe a complete backtrace? Regards, Eugen Zitat von Francesco Di Nucci <francesco.dinucci@na.infn.it>:
Hi all,
I am on OpenStack Caracal, trying to rescue a VM that's not booting:
* I previously created a SystemRescueCD rescue image (with openstack image create --file ./systemrescue-12.02-amd64.iso --disk-format raw --container-format bare --property hw_rescue_bus=virtio --property hw_rescue_device=disk systemrescuecd_1202) - it works on VMs that still have their base images in Glance * tried to rescue the VM (with openstack server rescue --image systemrescuecd_1202 my-vm-id-here) * but the process fails as it tries to also use the base image used to create that VM, instead of the rescue image only (Instance my-vm-id-here cannot be rescued: Driver Error: Image b78cf456-b395-434f-bf50-a1f2f3684a37 could not be found. ; where b78cf456-b395-434f-bf50-a1f2f3684a37 was a Ubuntu cloud image used to create that VM, since deleted as it's an EOL version)
Is it supposed to also try to use the base image or should the --image bypass it? In case, what could I do?
Thanks in advance
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email:francesco.dinucci@na.infn.it