yahoo-eng-team team mailing list archive

[hongbin <hongbin034@xxxxxxxxx>]

@mustang,

I see the problem now. Since horizon assumes cinder volume must be
attached to nova instance, it tried to locate the nova instance from the
volume attachment and failed. The error you were seeing is due to a
request to locate the nova instance and nova returned a 404 response.

For now, you can disregard the error since it is not a Zun's issue (I
will add horizon to this report so that someone from horizon might help
fixing the volume panel). I didn't see any error in the zun-compute log
so it seems the cinder volume was successfully attached to the
container.

If you run a container with a cinder volume bind-mounted, write some
data to the volume, then delete and re-created the container with the
same volume. Are the data still there. If it is, things are working as
expected.

** Also affects: horizon
   Importance: Undecided
       Status: New

-- 
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/1813459

Title:
  Mounting the cinder storage dashboard shows that the mount was
  successful but it turns out that the local store is the one mounted

Status in OpenStack Dashboard (Horizon):
  New
Status in Zun:
  Won't Fix

Bug description:
  1:Dashboard: Error: Unable to retrieve attachment information.

  2:My configuration:
  vim  /etc/zun/zun.conf
  [volume]
  driver = cinder
  volume_dir = /var/lib/zun/mnt

  3:Once the container is up, a directory is generated at /var/lib/zun/mnt/
  /var/lib/zun/mnt/8bb97e08-dd28-43e8-a9df-cbad4cf924d7

  4:Container after deleting the/var/lib/zun/mnt/8bb97e08-dd28-43e8
  -a9df-cbad4cf924d7 will be deleted

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