11 p.m.
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?
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>]'}'
11:38 p.m.
On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels <awels(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
9:50 a.m.
I think this should help:
https://www.mail-archive.com/devel%40ovirt.org/msg05152.html
On Mon, Jan 18, 2016 at 11:38 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels <awels(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
3:07 p.m.
On Tuesday, January 19, 2016 09:50:44 AM Fred Rolland wrote:
I think this should help:
https://www.mail-archive.com/devel%40ovirt.org/msg05152.html
Strange that the admin@internal didn't get this by default, but after adding
that following the mail in the archive, I can once again create VMs.
On Mon, Jan 18, 2016 at 11:38 PM, Yaniv Kaul <ykaul(a)redhat.com>
wrote:
> On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels <awels(a)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_PR
>> OFILE, $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(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
6:43 p.m.
There is a bug for that: https://bugzilla.redhat.com/show_bug.cgi?id=1297920
----- Original Message -----
From: "Alexander Wels" <awels(a)redhat.com>
To: "Fred Rolland" <frolland(a)redhat.com>
Cc: "devel" <devel(a)ovirt.org>
Sent: Tuesday, January 19, 2016 2:07:33 PM
Subject: Re: [ovirt-devel] Missing admin permissions.
On Tuesday, January 19, 2016 09:50:44 AM Fred Rolland wrote:
> I think this should help:
> https://www.mail-archive.com/devel%40ovirt.org/msg05152.html
>
Strange that the admin@internal didn't get this by default, but after adding
that following the mail in the archive, I can once again create VMs.
> On Mon, Jan 18, 2016 at 11:38 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> > On Mon, Jan 18, 2016 at 11:00 PM, Alexander Wels <awels(a)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_PR
> >> OFILE, $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(a)ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
3018
days inactive
3021
days old
4 comments
4 participants
participants (4)
-
Alexander Wels -
Fred Rolland -
Jakub Niedermertl -
Yaniv Kaul