[Yahoo-eng-team] [Bug 954335] Re: registering new image from existing s3 location does not respect kernel/ramdisk/name
** Changed in: ec2-api Status: New = Fix Released -- 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): Confirmed Bug description: $ cloud-publish-image --type kernel --rename my-kernel.img amd64 my.img my-bucket aki-000fmy-bucket/my-kernel.img.manifest.xml $ cloud-publish-image --type ramdisk --rename my-ramdisk.img amd64 my.img my-bucket ari-0010my-bucket/my-ramdisk.img.manifest.xml $ cloud-publish-image --type image --rename my-image-01.img amd64 my.img my-bucket ami-0011my-bucket/my-image-01.img.manifest.xml $ euca-register my-bucket/my-image-01.img.manifest.xml --kernel aki-000f --ramdisk ari-0010 --name my-bucket/my-image-01-with-kenrel-ramdisk.img IMAGE ami-0012 $ euca-describe-images ami-0012 IMAGE ami-0012my-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-000f --ramdisk ari-0010 ami-0013my-bucket/my-image-02.img.manifest.xml $ euca-describe-images ami-0013 IMAGE ami-0013my-bucket/my-image-02.img.manifest.xml available private x86_64 machine aki-000fari-0010 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-000fmy-bucket/my-kernel.img.manifest.xml available private x86_64 kernel instance-store IMAGE ari-0010my-bucket/my-ramdisk.img.manifest.xml available private x86_64 ramdisk instance-store IMAGE ami-0011my-bucket/my-image-01.img.manifest.xml available private x86_64 machine instance-store IMAGE ami-0012my-bucket/my-image-01.img.manifest.xml available private x86_64 machine instance-store IMAGE ami-0013my-bucket/my-image-02.img.manifest.xml available private x86_64 machine aki-000fari-0010 instance-store $ glance index /dev/null | grep my-bucket 09e381db-4281-4678-9c4b-854158148643 my-bucket/my-image-02.img ami ami10485760 f90dd1a9-301c-4ee9-9636-af1fd2454872 my-bucket/my-image-01-with-ken ami ami10485760 4799f149-0d04-4b5a-bd2a-f0bf96e97a1d my-bucket/my-image-01.img ami ami10485760 909651a3-e3c1-4858-946e-17433ef73aed my-bucket/my-ramdisk.img ari ari10485760 228a64fd-dadc-4cec-9954-92fef2251413 my-bucket/my-kernel.imgaki aki10485760 To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-api/+bug/954335/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 954335] Re: registering new image from existing s3 location does not respect kernel/ramdisk/name
** Also affects: ec2-api Importance: Undecided Status: New -- 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: New Status in OpenStack Compute (Nova): Confirmed Bug description: $ cloud-publish-image --type kernel --rename my-kernel.img amd64 my.img my-bucket aki-000fmy-bucket/my-kernel.img.manifest.xml $ cloud-publish-image --type ramdisk --rename my-ramdisk.img amd64 my.img my-bucket ari-0010my-bucket/my-ramdisk.img.manifest.xml $ cloud-publish-image --type image --rename my-image-01.img amd64 my.img my-bucket ami-0011my-bucket/my-image-01.img.manifest.xml $ euca-register my-bucket/my-image-01.img.manifest.xml --kernel aki-000f --ramdisk ari-0010 --name my-bucket/my-image-01-with-kenrel-ramdisk.img IMAGE ami-0012 $ euca-describe-images ami-0012 IMAGE ami-0012my-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-000f --ramdisk ari-0010 ami-0013my-bucket/my-image-02.img.manifest.xml $ euca-describe-images ami-0013 IMAGE ami-0013my-bucket/my-image-02.img.manifest.xml available private x86_64 machine aki-000fari-0010 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-000fmy-bucket/my-kernel.img.manifest.xml available private x86_64 kernel instance-store IMAGE ari-0010my-bucket/my-ramdisk.img.manifest.xml available private x86_64 ramdisk instance-store IMAGE ami-0011my-bucket/my-image-01.img.manifest.xml available private x86_64 machine instance-store IMAGE ami-0012my-bucket/my-image-01.img.manifest.xml available private x86_64 machine instance-store IMAGE ami-0013my-bucket/my-image-02.img.manifest.xml available private x86_64 machine aki-000fari-0010 instance-store $ glance index /dev/null | grep my-bucket 09e381db-4281-4678-9c4b-854158148643 my-bucket/my-image-02.img ami ami10485760 f90dd1a9-301c-4ee9-9636-af1fd2454872 my-bucket/my-image-01-with-ken ami ami10485760 4799f149-0d04-4b5a-bd2a-f0bf96e97a1d my-bucket/my-image-01.img ami ami10485760 909651a3-e3c1-4858-946e-17433ef73aed my-bucket/my-ramdisk.img ari ari10485760 228a64fd-dadc-4cec-9954-92fef2251413 my-bucket/my-kernel.imgaki aki10485760 To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-api/+bug/954335/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
