If we confirm that its a race condition, then the bug should be punted to 4.5
On 6/11/14, 11:38 AM, "Min Chen" <min.c...@citrix.com> wrote: >I have assigned CLOUDSTACK-6825 to me. But from the stack trace, it seems >failing in doing check access on the snapshot owner that is not active >anymore, feel like a racing condition happening on automation setup. >Rayees, several points to clarify: >1. Is this still happening on recent automation run on KVM? Based on the >error, it should be hypervisor independent. >2. Is the owner of the snapshot passed in createTemplate call already >deleted? > >Thanks >-min > > > >On 6/11/14 10:58 AM, "Alena Prokharchyk" <alena.prokharc...@citrix.com> >wrote: > >>CLOUDSTACK-6825 happens while doing object access check in >>ParamProcessWorker. Min/Prachi, can you take a look to see if its related >>to RBAC feature? >> >> >>-Alena. >> >>On 6/11/14, 10:45 AM, "Amogh Vasekar" <amogh.vase...@citrix.com> wrote: >> >>>Hi, >>> >>>AFAIK a couple of Automation blockers [1] [2], which had no owner >>>assigned, were moved to critical. >>> >>>[1] CLOUDSTACK-6842 >>>[2] CLOUDSTACK-6825 >>> >>>Thanks, >>>Amogh >>> >>> >>> >>>On 6/11/14 10:33 AM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> >>>wrote: >>> >>>>we have four blockers remaining...all network >>>>oriented. >>>> >>>>Murali Reddy has two. All four have an owner and presumably progress is >>>>being made. >>> >> >
