nothing special:
1) upgrade one of the nodes(overall we have 7) it became green
2) engine-setup (it runs on the separate node) db vacuum,etc answered with
yes.
went w/o errors.
3) i try to put into maintenance the next node, error came.
4)failure on migration but success on selecting of SPM.
i have another test system, will try to upgrade tomorrow.
Am 02.08.2017 10:56 vorm. schrieb "Yanir Quinn" <yquinn(a)redhat.com>:
Can you list the steps you did for the upgrade procedure ? (did you
follow
a specific guide perhaps ?)
On Tue, Aug 1, 2017 at 5:37 PM, Arman Khalatyan <arm2arm(a)gmail.com> wrote:
> It is unclear now, I am not able to reproduce the error...probably
> changing the policy fixed the "null" record in the database.
> My upgrade went w/o error from 4.1.3 to 4.1.4.
> The engine.log from yesterday is here: with the password:BUG
>
https://cloud.aip.de/index.php/s/N6xY0gw3GdEf63H (I hope I am not
> imposing the sensitive data:)
> <
https://cloud.aip.de/index.php/s/N6xY0gw3GdEf63H>
>
> most often errors are:
> 2017-07-31 15:17:08,547+02 ERROR [org.ovirt.engine.core.bll.MigrateVmCommand]
> (default task-263) [47ea10c5-0152-4512-ab07-086c59370190] Error during
> ValidateFailure.: java.lang.NullPointerException
>
> and
>
> 2017-07-31 15:17:10,729+02 ERROR
[org.ovirt.engine.core.utils.timer.SchedulerUtilQuartzImpl]
> (DefaultQuartzScheduler4) [11ad31d3] Failed to invoke scheduled method
> performLoadBalancing: null
>
> On Tue, Aug 1, 2017 at 12:01 PM, Doron Fediuck <dfediuck(a)redhat.com>
> wrote:
>
>> Yes, none is a valid policy assuming you don't need any special
>> considerations when running a VM.
>> If you could gather the relevant log entries and the error you see and
>> open a new bug it'll help us
>> track and fix the issue.
>> Please specify exactly from which engine version you upgraded and into
>> which version.
>>
>> On 1 August 2017 at 11:47, Arman Khalatyan <arm2arm(a)gmail.com> wrote:
>>
>>> Thank you for your response,
>>> I am looking now in to records of the menu "Scheduling Policy":
there
>>> is an entry "none", is it suppose to be there??
>>> Because when I selecting it then error occurs.
>>>
>>>
>>> On Tue, Aug 1, 2017 at 10:35 AM, Yanir Quinn <yquinn(a)redhat.com>
wrote:
>>>
>>>> Thanks for the update, we will check if there is a bug in the upgrade
>>>> process
>>>>
>>>> On Mon, Jul 31, 2017 at 6:32 PM, Arman Khalatyan
<arm2arm(a)gmail.com>
>>>> wrote:
>>>>
>>>>> Ok I found the ERROR:
>>>>> After upgrade the schedule policy was "none", I dont know
why it was
>>>>> moved to none but to fix the problem I did following:
>>>>> Edit Cluster->Scheduling Policy-> Select Policy:
>>>>> vm_evently_distributed
>>>>> Now I can run/migrate the VMs.
>>>>>
>>>>> I think there should be a some bug in the upgrade process.
>>>>>
>>>>>
>>>>> On Mon, Jul 31, 2017 at 5:11 PM, Arman Khalatyan
<arm2arm(a)gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Looks like renewed certificates problem, in the
>>>>>> ovirt-engine-setup-xx-xx.log I found following lines:
>>>>>> Are there way to fix it?
>>>>>>
>>>>>>
>>>>>> 2017-07-31 15:14:28 DEBUG otopi.plugins.ovirt_engine_set
>>>>>> up.ovirt_engine.pki.ca ca._enrollCertificates:330 processing:
>>>>>> 'engine'[renew=True]
>>>>>> 2017-07-31 15:14:28 DEBUG otopi.plugins.ovirt_engine_set
>>>>>> up.ovirt_engine.pki.ca plugin.executeRaw:813 execute:
>>>>>> ('/bin/openssl', 'pkcs12', '-in',
'/etc/pki/ovirt-engine/keys/engine.p12',
>>>>>> '-passin', 'pass:**FILTERED**',
'-nokeys'), executable='None', cwd='None',
>>>>>> env=None
>>>>>> 2017-07-31 15:14:28 DEBUG otopi.plugins.ovirt_engine_set
>>>>>> up.ovirt_engine.pki.ca plugin.executeRaw:863 execute-result:
>>>>>> ('/bin/openssl', 'pkcs12', '-in',
'/etc/pki/ovirt-engine/keys/engine.p12',
>>>>>> '-passin', 'pass:**FILTERED**',
'-nokeys'), rc=0
>>>>>> 2017-07-31 15:14:28 DEBUG otopi.plugins.ovirt_engine_set
>>>>>> up.ovirt_engine.pki.ca plugin.execute:921 execute-output:
>>>>>> ('/bin/openssl', 'pkcs12', '-in',
'/etc/pki/ovirt-engine/keys/engine.p12',
>>>>>> '-passin', 'pass:**FILTERED**',
'-nokeys') stdout:
>>>>>> Bag Attributes
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 31, 2017 at 4:54 PM, Arman Khalatyan
<arm2arm(a)gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Sorry, I forgot to mention the error.
>>>>>>> This error throws every time when I try to start the VM:
>>>>>>>
>>>>>>> 2017-07-31 16:51:07,297+02 ERROR
[org.ovirt.engine.core.bll.RunVmCommand]
>>>>>>> (default task-239) [7848103c-98dc-45d1-b99a-4713e3b8e956]
Error
>>>>>>> during ValidateFailure.: java.lang.NullPointerException
>>>>>>> at org.ovirt.engine.core.bll.sche
>>>>>>>
duling.SchedulingManager.canSchedule(SchedulingManager.java:526)
>>>>>>> [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.vali
>>>>>>> dator.RunVmValidator.canRunVm(RunVmValidator.java:157)
[bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.RunV
>>>>>>> mCommand.validate(RunVmCommand.java:967) [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Comm
>>>>>>> andBase.internalValidate(CommandBase.java:836) [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Comm
>>>>>>> andBase.validateOnly(CommandBase.java:365) [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Prev
>>>>>>>
alidatingMultipleActionsRunner.canRunActions(PrevalidatingMultipleActionsRunner.java:113)
>>>>>>> [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Prev
>>>>>>>
alidatingMultipleActionsRunner.invokeCommands(PrevalidatingMultipleActionsRunner.java:99)
>>>>>>> [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Prev
>>>>>>>
alidatingMultipleActionsRunner.execute(PrevalidatingMultipleActionsRunner.java:76)
>>>>>>> [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Back
>>>>>>> end.runMultipleActionsImpl(Backend.java:640) [bll.jar:]
>>>>>>> at org.ovirt.engine.core.bll.Back
>>>>>>> end.runMultipleActions(Backend.java:610) [bll.jar:]
>>>>>>> at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>> Method) [rt.jar:1.8.0_141]
>>>>>>> at sun.reflect.NativeMethodAccess
>>>>>>> orImpl.invoke(NativeMethodAccessorImpl.java:62)
[rt.jar:1.8.0_141]
>>>>>>> at sun.reflect.DelegatingMethodAc
>>>>>>> cessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>> [rt.jar:1.8.0_141]
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>>>>>> [rt.jar:1.8.0_141]
>>>>>>> at org.jboss.as.ee.component.Mana
>>>>>>> gedReferenceMethodInterceptor.processInvocation(ManagedRefer
>>>>>>> enceMethodInterceptor.java:52)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext.proceed(InterceptorContext.java:340)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext$Invocation.proceed(InterceptorContext.java:437)
>>>>>>> at org.jboss.as.weld.ejb.Jsr299Bi
>>>>>>>
ndingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70)
>>>>>>> [wildfly-weld-10.1.0.Final.jar:10.1.0.Final]
>>>>>>> at org.jboss.as.weld.ejb.Jsr299Bi
>>>>>>>
ndingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
>>>>>>> [wildfly-weld-10.1.0.Final.jar:10.1.0.Final]
>>>>>>> at org.jboss.as.weld.ejb.Jsr299Bi
>>>>>>>
ndingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
>>>>>>> [wildfly-weld-10.1.0.Final.jar:10.1.0.Final]
>>>>>>> at org.jboss.as.ee.component.inte
>>>>>>> rceptors.UserInterceptorFactory$1.processInvocation(UserInte
>>>>>>> rceptorFactory.java:63)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext.proceed(InterceptorContext.java:340)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext$Invocation.proceed(InterceptorContext.java:437)
>>>>>>> at org.ovirt.engine.core.bll.inte
>>>>>>> rceptors.CorrelationIdTrackerInterceptor.aroundInvoke(Correl
>>>>>>> ationIdTrackerInterceptor.java:13) [bll.jar:]
>>>>>>> at
sun.reflect.GeneratedMethodAccessor95.invoke(Unknown
>>>>>>> Source) [:1.8.0_141]
>>>>>>> at sun.reflect.DelegatingMethodAc
>>>>>>> cessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>> [rt.jar:1.8.0_141]
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>>>>>> [rt.jar:1.8.0_141]
>>>>>>> at org.jboss.as.ee.component.Mana
>>>>>>> gedReferenceLifecycleMethodInterceptor.processInvocation(Man
>>>>>>> agedReferenceLifecycleMethodInterceptor.java:89)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext.proceed(InterceptorContext.java:340)
>>>>>>> at org.jboss.as.ejb3.component.in
>>>>>>> vocationmetrics.ExecutionTimeInterceptor.processInvocation(E
>>>>>>> xecutionTimeInterceptor.java:43)
[wildfly-ejb3-10.1.0.Final.jar
>>>>>>> :10.1.0.Final]
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext.proceed(InterceptorContext.java:340)
>>>>>>> at org.jboss.invocation.Intercept
>>>>>>> orContext$Invocation.proceed(InterceptorContext.java:437)
>>>>>>> at org.jboss.weld.ejb.AbstractEJB
>>>>>>> RequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRe
>>>>>>> questScopeActivationInterceptor.java:73)
>>>>>>> [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
>>>>>>> at org.jboss.as.weld.ejb.EjbReque
>>>>>>> stScopeActivationInterceptor.processInvocation(EjbRequestSco
>>>>>>> peActivationInterceptor.java:83)
[wildfly-weld-10.1.0.Final.jar
>>>>>>> :10.1.0.Final]
>>>>>>> ....
>>>>>>> etc...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 31, 2017 at 4:06 PM, Arik Hadas
<ahadas(a)redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>> Please provide the engine log so we can figure out which
>>>>>>>> validation fails.
>>>>>>>>
>>>>>>>> On Mon, Jul 31, 2017 at 4:57 PM, Arman Khalatyan <
>>>>>>>> arm2arm(a)gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> I am running in to trouble with 4.1.4 after engine
upgrade I am
>>>>>>>>> not able to start or migrate virtual machines:
>>>>>>>>> getting following error:
>>>>>>>>> General command validation failure
>>>>>>>>> Are there any workarounds?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Users mailing list
>>>>>>>>> Users(a)ovirt.org
>>>>>>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users(a)ovirt.org
>>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>