Bug 1899468 - [RFE][OSP 18] Provide a workaround option and/or nova-manage command to force the refresh of connection_info during a hard reboot
Summary: [RFE][OSP 18] Provide a workaround option and/or nova-manage command to force...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Lee Yarwood
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks: 1999582 1999583 1999588
TreeView+ depends on / blocked
 
Reported: 2020-11-19 10:43 UTC by Lee Yarwood
Modified: 2023-03-21 19:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1999582 (view as bug list)
Environment:
Last Closed: 2022-01-24 09:55:19 UTC
Target Upstream Version: Xena
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 800634 0 None NEW WIP nova-manage: Introduce bdm show, refresh, get_connector commands 2021-07-27 21:31:54 UTC
Red Hat Issue Tracker OSP-624 0 None None None 2021-11-18 15:11:32 UTC

Description Lee Yarwood 2020-11-19 10:43:17 UTC 
Description of problem:
Provide a workaround option and/or nova-manage command to force the refresh of connection_info during a hard reboot.

This is useful in the context of live migration rollback failures, environmental changes and other future issues where the fact that Nova caches connection_info for a given volume from Cinder can cause issues.

A workaround option and/or nova-manage command would allow operators to resolve these issues without requiring code changes or a cold migration to another host.

This should only be possible when the instance is SHUTOFF or when hard rebooting the instance.

Version-Release number of selected component (if applicable):
All.

How reproducible:
Always.

Steps to Reproduce:
1. Cause stale connection_info to be populated for a given block_device_mapping in the Nova database.

Actual results:
There is no way to force a refresh of this stale connection_info without code changes or a cold migration to another host.

Expected results:
An operator should be able to force a refresh of the connection_info while the associated instance is SHUTOFF.

Additional info:
Note You need to log in before you can comment on or make changes to this bug.