On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels <aw...@redhat.com> wrote:
> Hi, > > Somewhere during master upgrades somehow my admin@internal did not get > permissions to create VMs. Its is compiling about no permissions to assign > a > CPU profile. Its been a while since I tried creating a VM. Can any one > point me > to what is missing and how to fix it? > Perhaps it's https://bugzilla.redhat.com/show_bug.cgi?id=1293338 , and the workaround is to re-run engine-setup, I believe. Y. > > This is the error in the log: > 2016-01-18 15:59:46,843 INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-56) [a6fd12b] Lock Acquired to object 'EngineLock: > {exclusiveLocks='[xxxx=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', > sharedLocks='[00000000-0000-0000-0000-000000000000=<TEMPLATE, > ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName xxxx>]'}' > 2016-01-18 15:59:46,893 WARN [org.ovirt.engine.core.bll.AddVmCommand] > (default task-56) [] Validation of action 'AddVm' failed for user > admin@internal. Reasons: > > VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_NO_PERMISSION_TO_ASSIGN_CPU_PROFILE, > $cpuProfileId f9a05b39-9f57-4655-aab2-2846fe6519f6,$cpuProfileName DEV35 > 2016-01-18 15:59:46,894 INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-56) [] Lock freed to object 'EngineLock: > {exclusiveLocks='[xxxx=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', > sharedLocks='[00000000-0000-0000-0000-000000000000=<TEMPLATE, > ACTION_TYPE_FAILED_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName xxxx>]'}' > > _______________________________________________ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel >
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel