Bug #1159

Restricted attributes in template must not be restricted if template has "use" ACL

Added by olivier sallou over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:03/07/2012
Priority:NormalDue date:
Assignee:-% Done:


Category:Core & System
Target version:Release 3.4 - Beta
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.2


If oneadmin creates a template containing restricted attributes, and make this template available to all (with the use ACL), restricted attributes should not apply.

This prevent the cloud administrator to propose some templates to the users when those attributes are requires (especially CONTEXT/FILES).

Associated revisions

Revision a9d7a9b0
Added by Carlos Martín over 9 years ago

Bug #1159: Move restricted attribute checks to RM. Do not check restricted attributes when a template owned by oneadmin is instantiated


#1 Updated by Ruben S. Montero over 9 years ago

  • Category set to Core & System
  • Status changed from New to Assigned
  • Target version set to Release 3.4


This is totally reasonable. We will not check the attributes in the templates created by oneadmin, and just check the USE permission.

THANKS for the feedback!

#2 Updated by Ruben S. Montero over 9 years ago

  • Target version changed from Release 3.4 to Release 3.4 - Beta

#3 Updated by Ruben S. Montero over 9 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Also available in: Atom PDF