Instance in ERROR state - libvirtError - VNC server bind socket error - during reboot / rescue - unrescue

Solution In Progress - Updated -

Issue

  • Instances end up in ERROR state after rebooting which were live-migrated in the past

  • Instance reboot fails with error

Sep 16 08:17:48 compute  journal: 2020-09-16 08:17:48.568+0000: 9701: error : qemuProcessReportLogError:1923 : internal error: qemu unexpectedly closed the monitor: 2020-09-16T08:17:48.551605Z qemu-kvm: -vnc 172.16.20.136:3,tls,x509verify=/etc/pki/libvirt-vnc: Failed to start VNC server: Failed to bind socket: Cannot assign requested address

Environment

  • Red Hat OpenStack Platform 13.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content