From 7970deddd7ef5bd3a3dc4a402efca97df405f522 Mon Sep 17 00:00:00 2001 From: Lee Yarwood Date: Wed, 8 Apr 2020 14:32:37 +0100 Subject: [PATCH] fup: Remove the use of the term `unstable rescue` INFO logs As discussed in I0e1241ae691afd2af12ef15706c454c05d9f932c this isn't the correct term and could be alarming to Ops when seen. Change-Id: I14a1efa15aa6c4228aba4017072ffe80ecefe564 --- nova/virt/libvirt/driver.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/nova/virt/libvirt/driver.py b/nova/virt/libvirt/driver.py index ecc4a8b465..a4a7ecb76d 100644 --- a/nova/virt/libvirt/driver.py +++ b/nova/virt/libvirt/driver.py @@ -3473,9 +3473,9 @@ class LibvirtDriver(driver.ComputeDriver): image_meta = objects.ImageMeta.from_dict(image_meta_dict) else: - LOG.info("Attempting an unstable device rescue", instance=instance) - # NOTE(lyarwood): An unstable rescue only provides the rescue - # device and the original root device so we don't need to provide + LOG.info("Attempting rescue", instance=instance) + # NOTE(lyarwood): A legacy rescue only provides the rescue device + # and the original root device so we don't need to provide # block_device_info to the get_disk_info call. block_device_info = None