yahoo-eng-team team mailing list archive

[Hemant Sonawane <1916891@xxxxxxxxxxxxxxxxxx>]

** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1916891

Title:
  Horizon could not identify image id (Recoverable error:
  volume_image_metadata)

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  openstack horizon stable/victoria issue

  In our case we migrated some volumes from different env to our current
  one and its strange that when we try to boot the instance from the
  migrated volume and then try to see the instance details we
  encountered some issue in horizon stable/victoria

  "Error: Failed to get attached volume. Details volume_image_metadata".

  I also tried to see in horizon logs but i could only able find this

  2021-02-25 12:25:27.511270 Recoverable error: volume_image_metadata

  apache logs:

  AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.233.80.6. Set the 'ServerName' directive globally to suppress this message
  [Thu Feb 25 08:40:03.711351 2021] [mpm_event:notice] [pid 1:tid 140542017477568] AH00489: Apache/2.4.29 (Ubuntu) mod_wsgi/4.5.17 Python/3.6 configured -- resuming normal operations
  [Thu Feb 25 08:40:03.711503 2021] [core:notice] [pid 1:tid 140542017477568] AH00094: Command line: 'apache2 -D FOREGROUND'

  It looks like horizon could not identify the image from migrated
  volumes.

  Then i tried to create volume without image and made it bootable and
  then launch instance from it and i encountered same issue. which means
  if image gets deleted or in fact there is no image in volume the
  Keyerror gets triggered. But in my case the migrated volume does
  contain image and it instance works completely fine its horizon which
  could not identify the image id in metadata section.

  so please take a look and try to reproduce it on your end and let me
  know if there is any solution for this bug. Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1916891/+subscriptions