Instances with encrypted disks fail to start after compute reboot

Solution In Progress - Updated -

Issue

There are two issues here:

  • The EmptyCatalog exception raised as the bare bones admin context we are using during nova-compute startup doesn't contain a service catalog.

  • The fact that even if the service catalog is populated an admin by default still wouldn't be able to gain access to the user secrets required to attach an encrypted volume.

Environment

Red Hat OpenStack Platform 13
Red Hat OpenStack Platform 16.1

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