Bug #945

oneimage update does not update VM name in listing

Added by Karl Katzke over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:10/27/2011
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:invalid Pull request:
Affected Versions:OpenNebula 3.0


I used 'oneimage update [#]' to update an image's name, and it produced no changes in the listing of the CLI. We're not using sunstone at this point, so I can't comment on whether or not it is changed in there.

Steps to reproduce:
  1. Create an image using oneimage create (template file)
  2. use oneimage list to display a list of images
  3. use oneimage update 0 to update that image. Change the 'Name' of the image.
  4. use oneimage list to verify that the name field did not update

Source install of 3.0 on Debian Wheezy with Ruby 1.8.7.


#1 Updated by Carlos Martín over 9 years ago

  • Status changed from New to Closed
  • Resolution set to invalid


The Image template is processed only at the creation of the Image to extract the internal attributes like NAME. When the template is updated later, it is not processed, thus if you change meaningful attributes they are ignored.

If you take a look at the 'oneimage show <id> -x' output, you'll see that IMAGE/NAME still has the previous name and IMAGE/TEMPLATE/NAME contains the updated one.

For the moment you can't rename resources, but it has been requested in ticket #934 and will be available in future versions.

We are aware that this behaviour is not intuitive, and we are fixing it in the development version. You will have a different command to change each "internal" attribute, and the 'oneimage update' command will only present you extra or descriptive attributes.

I hope that was clear.


Also available in: Atom PDF