yahoo-eng-team team mailing list archive

["Davanum Srinivas \(DIMS\)" <davanum@xxxxxxxxx>]

** Changed in: nova
       Status: Confirmed => Won't Fix

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

Title:
  registering new image from existing s3 location does not respect
  kernel/ramdisk/name

Status in ec2-api:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  $ cloud-publish-image --type kernel --rename my-kernel.img amd64 my.img my-bucket
  aki-0000000f    my-bucket/my-kernel.img.manifest.xml
  $ cloud-publish-image --type ramdisk --rename my-ramdisk.img amd64 my.img my-bucket
  ari-00000010    my-bucket/my-ramdisk.img.manifest.xml
  $ cloud-publish-image --type image --rename my-image-01.img amd64 my.img my-bucket
  ami-00000011    my-bucket/my-image-01.img.manifest.xml
  $ euca-register my-bucket/my-image-01.img.manifest.xml --kernel aki-0000000f --ramdisk ari-00000010 --name my-bucket/my-image-01-with-kenrel-ramdisk.img
  IMAGE   ami-00000012

  $ euca-describe-images ami-00000012
  IMAGE   ami-00000012    my-bucket/my-image-01.img.manifest.xml          available       private         x86_64  machine                 instance-store

  However, if you pass --kernel/--ramdisk the first time you register that s3 location, then it works.
  $ cloud-publish-image --type image --rename my-image-02.img amd64 my.img my-bucket --kernel aki-0000000f --ramdisk ari-00000010
  ami-00000013    my-bucket/my-image-02.img.manifest.xml
  $ euca-describe-images ami-00000013
  IMAGE   ami-00000013    my-bucket/my-image-02.img.manifest.xml          available       private         x86_64  machine aki-0000000f    ari-00000010    instance-store

  The desired behavior is basically to re-register that s3 location but
  with different kernel/ramdisk (or --name) parameters.

  
  Euca-describe-images shows the following:
  $ euca-describe-images | grep my-bucket/
  IMAGE   aki-0000000f    my-bucket/my-kernel.img.manifest.xml               available       private         x86_64  kernel                  instance-store
  IMAGE   ari-00000010    my-bucket/my-ramdisk.img.manifest.xml              available       private         x86_64  ramdisk                 instance-store
  IMAGE   ami-00000011    my-bucket/my-image-01.img.manifest.xml             available       private         x86_64  machine                 instance-store
  IMAGE   ami-00000012    my-bucket/my-image-01.img.manifest.xml             available       private         x86_64  machine                 instance-store
  IMAGE   ami-00000013    my-bucket/my-image-02.img.manifest.xml             available       private         x86_64  machine aki-0000000f    ari-00000010    instance-store

  
  $ glance index </dev/null | grep my-bucket
  09e381db-4281-4678-9c4b-854158148643 my-bucket/my-image-02.img      ami                  ami                        10485760
  f90dd1a9-301c-4ee9-9636-af1fd2454872 my-bucket/my-image-01-with-ken ami                  ami                        10485760
  4799f149-0d04-4b5a-bd2a-f0bf96e97a1d my-bucket/my-image-01.img      ami                  ami                        10485760
  909651a3-e3c1-4858-946e-17433ef73aed my-bucket/my-ramdisk.img       ari                  ari                        10485760
  228a64fd-dadc-4cec-9954-92fef2251413 my-bucket/my-kernel.img        aki                  aki                        10485760

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/954335/+subscriptions