[one.template.instantiate] User [5] : User Template includes a restricted attribute DISK

Community Support
1

Hi all, we use one 5.4.1 with kvm.
We created a group and a user.
After that we uploaded image from marketplace.
Then we tried to deploy vm with our new user, from this template, but got following error

[one.template.instantiate] User [5] : User Template includes a restricted attribute DISK.

[one.template.instantiate] User [5] : User Template includes a restricted attribute DISK.

There is list of our restricted attr:

VM_RESTRICTED_ATTR = "CONTEXT/FILES"
VM_RESTRICTED_ATTR = "NIC/MAC"
VM_RESTRICTED_ATTR = "NIC/VLAN_ID"
VM_RESTRICTED_ATTR = "NIC/BRIDGE"
VM_RESTRICTED_ATTR = "NIC/INBOUND_AVG_BW"
VM_RESTRICTED_ATTR = "NIC/INBOUND_PEAK_BW"
VM_RESTRICTED_ATTR = "NIC/INBOUND_PEAK_KB"
VM_RESTRICTED_ATTR = "NIC/OUTBOUND_AVG_BW"
VM_RESTRICTED_ATTR = "NIC/OUTBOUND_PEAK_BW"
VM_RESTRICTED_ATTR = “NIC/OUTBOUND_PEAK_KB”
#VM_RESTRICTED_ATTR = “NIC/OPENNEBULA_MANAGED”
#VM_RESTRICTED_ATTR = “NIC/VCENTER_INSTANCE_ID”
#VM_RESTRICTED_ATTR = “NIC/VCENTER_NET_REF”
#VM_RESTRICTED_ATTR = "NIC/VCENTER_PORTGROUP_TYPE"
VM_RESTRICTED_ATTR = "NIC_DEFAULT/MAC"
VM_RESTRICTED_ATTR = "NIC_DEFAULT/VLAN_ID"
VM_RESTRICTED_ATTR = "NIC_DEFAULT/BRIDGE"
VM_RESTRICTED_ATTR = "DISK/TOTAL_BYTES_SEC"
VM_RESTRICTED_ATTR = "DISK/READ_BYTES_SEC"
VM_RESTRICTED_ATTR = "DISK/WRITE_BYTES_SEC"
VM_RESTRICTED_ATTR = "DISK/TOTAL_IOPS_SEC"
VM_RESTRICTED_ATTR = "DISK/READ_IOPS_SEC"
VM_RESTRICTED_ATTR = “DISK/WRITE_IOPS_SEC”
#VM_RESTRICTED_ATTR = “DISK/OPENNEBULA_MANAGED”
#VM_RESTRICTED_ATTR = “DISK/VCENTER_DS_REF”
#VM_RESTRICTED_ATTR = “DISK/VCENTER_INSTANCE_ID”
#VM_RESTRICTED_ATTR = "DISK/SIZE"
VM_RESTRICTED_ATTR = "DISK/ORIGINAL_SIZE"
VM_RESTRICTED_ATTR = "DISK/SIZE_PREV"
VM_RESTRICTED_ATTR = "CPU_COST"
VM_RESTRICTED_ATTR = "MEMORY_COST"
VM_RESTRICTED_ATTR = "DISK_COST"
VM_RESTRICTED_ATTR = "PCI"
VM_RESTRICTED_ATTR = "EMULATOR"
VM_RESTRICTED_ATTR = "RAW"
VM_RESTRICTED_ATTR = "USER_PRIORITY"
VM_RESTRICTED_ATTR = "USER_INPUTS/CPU"
VM_RESTRICTED_ATTR = "USER_INPUTS/MEMORY"
VM_RESTRICTED_ATTR = "USER_INPUTS/VCPU"
VM_RESTRICTED_ATTR = “VCENTER_VM_FOLDER”
#VM_RESTRICTED_ATTR = “RANK”
#VM_RESTRICTED_ATTR = “SCHED_RANK”
#VM_RESTRICTED_ATTR = “REQUIREMENTS”
#VM_RESTRICTED_ATTR = "SCHED_REQUIREMENTS"
IMAGE_RESTRICTED_ATTR = “SOURCE”
#IMAGE_RESTRICTED_ATTR = "TEMPLATE/VCENTER_IMPORTED"
VNET_RESTRICTED_ATTR = "VN_MAD"
VNET_RESTRICTED_ATTR = "PHYDEV"
VNET_RESTRICTED_ATTR = "VLAN_ID"
VNET_RESTRICTED_ATTR = "BRIDGE"
VNET_RESTRICTED_ATTR = "CONF"
VNET_RESTRICTED_ATTR = "BRIDGE_CONF"
VNET_RESTRICTED_ATTR = "IP_LINK_CONF"
VNET_RESTRICTED_ATTR = "AR/VN_MAD"
VNET_RESTRICTED_ATTR = "AR/PHYDEV"
VNET_RESTRICTED_ATTR = "AR/VLAN_ID"
VNET_RESTRICTED_ATTR = “AR/BRIDGE”

2

while experimenting we figure out:
we create image and template with oneadmin user
made this image persistent, and give full rights on it
create vm from it with oneadmin user
remove vm, and made image nonpersistent.

after that we can create vm’s from this imahe with any user

3

Hi Leonid!

Yes, this is a bug of OpenNebula 5.4.1, we fixed this bug for OpenNebula 5.4.2.
Sorry for the problems!

Regards!
Juan Jose