Re: [ovirt-users] oVirt fails to install on nodes after moving engine to C7 host

[James]

Worked perfectly, thanks so much!

On Tue, 6 Sep 2016, at 07:11 PM, Yedidyah Bar David wrote:
> On Tue, Sep 6, 2016 at 11:54 AM, James  wrote:
> > Thanks for the info. It looks like everything is tied together (as it
> > should be) dependency wise, so downgrading otopi isn't going to be that
> > simple.
> >
> > [root@engine ~]# yum downgrade otopi-1.4.2-1.el7.centos
> > otopi-java-1.4.2-1.el7.centos
> > 
> > Resolving Dependencies
> > --> Running transaction check
> > ---> Package otopi.noarch 0:1.4.2-1.el7.centos will be a downgrade
> > ---> Package otopi.noarch 0:1.5.2-1.el7.centos will be erased
> > ---> Package otopi-java.noarch 0:1.4.2-1.el7.centos will be a downgrade
> > ---> Package otopi-java.noarch 0:1.5.2-1.el7.centos will be erased
> > --> Finished Dependency Resolution
> > Error: Package: ovirt-engine-setup-base-4.0.2.7-1.el7.centos.noarch
> > (@ovirt-4.0)
> >Requires: otopi >= 1.5.0
> >Removing: otopi-1.5.2-1.el7.centos.noarch (@ovirt-4.0)
> >otopi = 1.5.2-1.el7.centos
> >Downgraded By: otopi-1.4.2-1.el7.centos.noarch (ovirt-3.6)
> >otopi = 1.4.2-1.el7.centos
> >Available: otopi-1.4.0-1.el7.noarch (centos-ovirt36)
> >otopi = 1.4.0-1.el7
> >Available: otopi-1.4.0-1.el7.centos.noarch (ovirt-3.6)
> >otopi = 1.4.0-1.el7.centos
> >Available: otopi-1.4.1-1.el7.noarch (centos-ovirt36)
> >otopi = 1.4.1-1.el7
> >Available: otopi-1.4.1-1.el7.centos.noarch (ovirt-3.6)
> >otopi = 1.4.1-1.el7.centos
> >Available: otopi-1.5.0-1.el7.centos.noarch (ovirt-4.0)
> >otopi = 1.5.0-1.el7.centos
> >Available: otopi-1.5.1-1.el7.noarch (centos-ovirt40-release)
> >otopi = 1.5.1-1.el7
> >Available: otopi-1.5.1-1.el7.centos.noarch (ovirt-4.0)
> >otopi = 1.5.1-1.el7.centos
> >  You could try using --skip-broken to work around the problem
> >  You could try running: rpm -Va --nofiles --nodigest
> > [root@engine ~]#
> >
> > Which just goes down a rabbit hole of dependency chasing for most ovirt*
> > packages. I can't think of a good way past this apart from a reinstall?
> 
> It's not really a rabbit hole - if you only upgraded the setup packages,
> it's just them.
> 
> You can downgrade the entire transaction with 'yum history'. Check
> 'yum history' output, 'yum history info ID' with a specific ID to see
> what happened there, then 'yum history undo ID'.
> 
> >
> > On Tue, 6 Sep 2016, at 06:19 PM, Yedidyah Bar David wrote:
> >> On Tue, Sep 6, 2016 at 10:43 AM, James  wrote:
> >> > Thanks for your help! I've pasted the log lines requested below. Also
> >> > worth noting that I tried upgrading it to 4.0 which I think has lead to
> >> > some broken package versions. Everything seems to work, but there are
> >> > some 4.0 packages installed.
> >>
> >> Perhaps that's the problem [1]. Can you try downgrading otopi to 1.4 and
> >> remove /var/cache/ovirt-engine/ovirt-host-deploy.tar on engine machine?
> >>
> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1348091
> >>
> >> Your package state is not very healthy but if above is enough to get you
> >> to install a host, and later you succeed upgrading to 4.0, you should be
> >> ok.
> >>
> >> >
> >> > When trying to install 4.0 I followed the docs (yum update
> >> > engine-setup*) however when running engine-setup it informed me that it
> >> > couldn't take the install to 4.0 because of the 3.5 cluster that
> >> > existed. Currently installed pacakges:
> >> >
> >> > Installed Packages
> >> > ovirt-engine.noarch
> >> >3.6.7.5-1.el7.centos
> >> >  @ovirt-3.6
> >> > ovirt-engine-backend.noarch
> >> >3.6.7.5-1.el7.centos
> >> >  @ovirt-3.6
> >> > ovirt-engine-cli.noarch
> >> >3.6.8.0-1.el7.centos
> >> >  @ovirt-4.0
> >> > ovirt-engine-dbscripts.noarch
> >> >3.6.7.5-1.el7.centos
> >> >  @ovirt-3.6
> >> > ovirt-engine-dwh.noarch
> >> >3.6.6-1.el7.centos
> >> >  @ovirt-3.6
> >> > ovirt-engine-dwh-setup.noarch
> >> >4.0.1-1.el7.centos
> >> >  @ovirt-4.0
> >> > ovirt-engine-extension-aaa-jdbc.noarch
> >> >1.0.7-1.el7
> >> >  @ovirt-3.6
> >> > ovirt-engine-extension-aaa-ldap.noarch
> >> >1.2.1-1.el7
> >> >  @ovirt-4.0
> >> > ovirt-engine-extension-aaa-ldap-setup.noarch
> >> >1.2.1-1.el7
> >> >

Re: [ovirt-users] oVirt fails to install on nodes after moving engine to C7 host

[Yedidyah Bar David]

On Tue, Sep 6, 2016 at 11:54 AM, James  wrote:
> Thanks for the info. It looks like everything is tied together (as it
> should be) dependency wise, so downgrading otopi isn't going to be that
> simple.
>
> [root@engine ~]# yum downgrade otopi-1.4.2-1.el7.centos
> otopi-java-1.4.2-1.el7.centos
> 
> Resolving Dependencies
> --> Running transaction check
> ---> Package otopi.noarch 0:1.4.2-1.el7.centos will be a downgrade
> ---> Package otopi.noarch 0:1.5.2-1.el7.centos will be erased
> ---> Package otopi-java.noarch 0:1.4.2-1.el7.centos will be a downgrade
> ---> Package otopi-java.noarch 0:1.5.2-1.el7.centos will be erased
> --> Finished Dependency Resolution
> Error: Package: ovirt-engine-setup-base-4.0.2.7-1.el7.centos.noarch
> (@ovirt-4.0)
>Requires: otopi >= 1.5.0
>Removing: otopi-1.5.2-1.el7.centos.noarch (@ovirt-4.0)
>otopi = 1.5.2-1.el7.centos
>Downgraded By: otopi-1.4.2-1.el7.centos.noarch (ovirt-3.6)
>otopi = 1.4.2-1.el7.centos
>Available: otopi-1.4.0-1.el7.noarch (centos-ovirt36)
>otopi = 1.4.0-1.el7
>Available: otopi-1.4.0-1.el7.centos.noarch (ovirt-3.6)
>otopi = 1.4.0-1.el7.centos
>Available: otopi-1.4.1-1.el7.noarch (centos-ovirt36)
>otopi = 1.4.1-1.el7
>Available: otopi-1.4.1-1.el7.centos.noarch (ovirt-3.6)
>otopi = 1.4.1-1.el7.centos
>Available: otopi-1.5.0-1.el7.centos.noarch (ovirt-4.0)
>otopi = 1.5.0-1.el7.centos
>Available: otopi-1.5.1-1.el7.noarch (centos-ovirt40-release)
>otopi = 1.5.1-1.el7
>Available: otopi-1.5.1-1.el7.centos.noarch (ovirt-4.0)
>otopi = 1.5.1-1.el7.centos
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> [root@engine ~]#
>
> Which just goes down a rabbit hole of dependency chasing for most ovirt*
> packages. I can't think of a good way past this apart from a reinstall?

It's not really a rabbit hole - if you only upgraded the setup packages,
it's just them.

You can downgrade the entire transaction with 'yum history'. Check
'yum history' output, 'yum history info ID' with a specific ID to see
what happened there, then 'yum history undo ID'.

>
> On Tue, 6 Sep 2016, at 06:19 PM, Yedidyah Bar David wrote:
>> On Tue, Sep 6, 2016 at 10:43 AM, James  wrote:
>> > Thanks for your help! I've pasted the log lines requested below. Also
>> > worth noting that I tried upgrading it to 4.0 which I think has lead to
>> > some broken package versions. Everything seems to work, but there are
>> > some 4.0 packages installed.
>>
>> Perhaps that's the problem [1]. Can you try downgrading otopi to 1.4 and
>> remove /var/cache/ovirt-engine/ovirt-host-deploy.tar on engine machine?
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1348091
>>
>> Your package state is not very healthy but if above is enough to get you
>> to install a host, and later you succeed upgrading to 4.0, you should be
>> ok.
>>
>> >
>> > When trying to install 4.0 I followed the docs (yum update
>> > engine-setup*) however when running engine-setup it informed me that it
>> > couldn't take the install to 4.0 because of the 3.5 cluster that
>> > existed. Currently installed pacakges:
>> >
>> > Installed Packages
>> > ovirt-engine.noarch
>> >3.6.7.5-1.el7.centos
>> >  @ovirt-3.6
>> > ovirt-engine-backend.noarch
>> >3.6.7.5-1.el7.centos
>> >  @ovirt-3.6
>> > ovirt-engine-cli.noarch
>> >3.6.8.0-1.el7.centos
>> >  @ovirt-4.0
>> > ovirt-engine-dbscripts.noarch
>> >3.6.7.5-1.el7.centos
>> >  @ovirt-3.6
>> > ovirt-engine-dwh.noarch
>> >3.6.6-1.el7.centos
>> >  @ovirt-3.6
>> > ovirt-engine-dwh-setup.noarch
>> >4.0.1-1.el7.centos
>> >  @ovirt-4.0
>> > ovirt-engine-extension-aaa-jdbc.noarch
>> >1.0.7-1.el7
>> >  @ovirt-3.6
>> > ovirt-engine-extension-aaa-ldap.noarch
>> >1.2.1-1.el7
>> >  @ovirt-4.0
>> > ovirt-engine-extension-aaa-ldap-setup.noarch
>> >1.2.1-1.el7
>> >  @ovirt-4.0
>> > ovirt-engine-extensions-api-impl.noarch
>> >4.0.2.7-1.el7.centos
>> >  @ovirt-4.0
>> > ovirt-engine-lib.noarch
>> >4.0.2.7-1.el7.centos
>> >  

Re: [ovirt-users] oVirt fails to install on nodes after moving engine to C7 host

[James]

Thanks for the info. It looks like everything is tied together (as it
should be) dependency wise, so downgrading otopi isn't going to be that
simple.

[root@engine ~]# yum downgrade otopi-1.4.2-1.el7.centos
otopi-java-1.4.2-1.el7.centos

Resolving Dependencies
--> Running transaction check
---> Package otopi.noarch 0:1.4.2-1.el7.centos will be a downgrade
---> Package otopi.noarch 0:1.5.2-1.el7.centos will be erased
---> Package otopi-java.noarch 0:1.4.2-1.el7.centos will be a downgrade
---> Package otopi-java.noarch 0:1.5.2-1.el7.centos will be erased
--> Finished Dependency Resolution
Error: Package: ovirt-engine-setup-base-4.0.2.7-1.el7.centos.noarch
(@ovirt-4.0)
   Requires: otopi >= 1.5.0
   Removing: otopi-1.5.2-1.el7.centos.noarch (@ovirt-4.0)
   otopi = 1.5.2-1.el7.centos
   Downgraded By: otopi-1.4.2-1.el7.centos.noarch (ovirt-3.6)
   otopi = 1.4.2-1.el7.centos
   Available: otopi-1.4.0-1.el7.noarch (centos-ovirt36)
   otopi = 1.4.0-1.el7
   Available: otopi-1.4.0-1.el7.centos.noarch (ovirt-3.6)
   otopi = 1.4.0-1.el7.centos
   Available: otopi-1.4.1-1.el7.noarch (centos-ovirt36)
   otopi = 1.4.1-1.el7
   Available: otopi-1.4.1-1.el7.centos.noarch (ovirt-3.6)
   otopi = 1.4.1-1.el7.centos
   Available: otopi-1.5.0-1.el7.centos.noarch (ovirt-4.0)
   otopi = 1.5.0-1.el7.centos
   Available: otopi-1.5.1-1.el7.noarch (centos-ovirt40-release)
   otopi = 1.5.1-1.el7
   Available: otopi-1.5.1-1.el7.centos.noarch (ovirt-4.0)
   otopi = 1.5.1-1.el7.centos
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
[root@engine ~]#

Which just goes down a rabbit hole of dependency chasing for most ovirt*
packages. I can't think of a good way past this apart from a reinstall?

On Tue, 6 Sep 2016, at 06:19 PM, Yedidyah Bar David wrote:
> On Tue, Sep 6, 2016 at 10:43 AM, James  wrote:
> > Thanks for your help! I've pasted the log lines requested below. Also
> > worth noting that I tried upgrading it to 4.0 which I think has lead to
> > some broken package versions. Everything seems to work, but there are
> > some 4.0 packages installed.
> 
> Perhaps that's the problem [1]. Can you try downgrading otopi to 1.4 and
> remove /var/cache/ovirt-engine/ovirt-host-deploy.tar on engine machine?
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1348091
> 
> Your package state is not very healthy but if above is enough to get you
> to install a host, and later you succeed upgrading to 4.0, you should be
> ok.
> 
> >
> > When trying to install 4.0 I followed the docs (yum update
> > engine-setup*) however when running engine-setup it informed me that it
> > couldn't take the install to 4.0 because of the 3.5 cluster that
> > existed. Currently installed pacakges:
> >
> > Installed Packages
> > ovirt-engine.noarch
> >3.6.7.5-1.el7.centos
> >  @ovirt-3.6
> > ovirt-engine-backend.noarch
> >3.6.7.5-1.el7.centos
> >  @ovirt-3.6
> > ovirt-engine-cli.noarch
> >3.6.8.0-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-dbscripts.noarch
> >3.6.7.5-1.el7.centos
> >  @ovirt-3.6
> > ovirt-engine-dwh.noarch
> >3.6.6-1.el7.centos
> >  @ovirt-3.6
> > ovirt-engine-dwh-setup.noarch
> >4.0.1-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-extension-aaa-jdbc.noarch
> >1.0.7-1.el7
> >  @ovirt-3.6
> > ovirt-engine-extension-aaa-ldap.noarch
> >1.2.1-1.el7
> >  @ovirt-4.0
> > ovirt-engine-extension-aaa-ldap-setup.noarch
> >1.2.1-1.el7
> >  @ovirt-4.0
> > ovirt-engine-extensions-api-impl.noarch
> >4.0.2.7-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-lib.noarch
> >4.0.2.7-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-restapi.noarch
> >3.6.7.5-1.el7.centos
> >  @ovirt-3.6
> > ovirt-engine-sdk-python.noarch
> >3.6.8.0-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-setup.noarch
> >4.0.2.7-1.el7.centos
> >  @ovirt-4.0
> > ovirt-engine-setup-base.noarch
> >  

Re: [ovirt-users] oVirt fails to install on nodes after moving engine to C7 host

[James]

Thanks for your help! I've pasted the log lines requested below. Also
worth noting that I tried upgrading it to 4.0 which I think has lead to
some broken package versions. Everything seems to work, but there are
some 4.0 packages installed.

When trying to install 4.0 I followed the docs (yum update
engine-setup*) however when running engine-setup it informed me that it
couldn't take the install to 4.0 because of the 3.5 cluster that
existed. Currently installed pacakges:

Installed Packages
ovirt-engine.noarch 
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-backend.noarch 
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-cli.noarch 
   3.6.8.0-1.el7.centos 
 @ovirt-4.0
ovirt-engine-dbscripts.noarch   
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-dwh.noarch 
   3.6.6-1.el7.centos   
 @ovirt-3.6
ovirt-engine-dwh-setup.noarch   
   4.0.1-1.el7.centos   
 @ovirt-4.0
ovirt-engine-extension-aaa-jdbc.noarch  
   1.0.7-1.el7  
 @ovirt-3.6
ovirt-engine-extension-aaa-ldap.noarch  
   1.2.1-1.el7  
 @ovirt-4.0
ovirt-engine-extension-aaa-ldap-setup.noarch
   1.2.1-1.el7  
 @ovirt-4.0
ovirt-engine-extensions-api-impl.noarch 
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-lib.noarch 
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-restapi.noarch 
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-sdk-python.noarch  
   3.6.8.0-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup.noarch   
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup-base.noarch  
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup-plugin-ovirt-engine.noarch   
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup-plugin-ovirt-engine-common.noarch
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-setup-plugin-websocket-proxy.noarch
   4.0.2.7-1.el7.centos 
 @ovirt-4.0
ovirt-engine-tools.noarch   
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-tools-backup.noarch
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-userportal.noarch  
   3.6.7.5-1.el7.centos 
 @ovirt-3.6
ovirt-engine-vmconsole-proxy-helper.noarch  
   4.0.2.7-1.el7.centos 

Re: [ovirt-users] oVirt fails to install on nodes after moving engine to C7 host

[Yedidyah Bar David]

On Tue, Sep 6, 2016 at 6:08 AM, James  wrote:
> Hey,
>
> I moved our standalone engine from a C6 host to a C7 host and now it
> wont install/setup oVirt nodes. It just responds with messages like
> this:
>
> Host xxx.xxx.xxx installation failed. Unexpected connection termination.
> Failed to install Host xxx.xxx.xxx. Command returned failure code 1
> during SSH session 'r...@xxx.xx.xx.x'.
>
> And from engine.log
>
> 2016-09-06 12:20:08,011 ERROR
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (org.ovirt.thread.pool-8-thread-41) [55397a53] SSH error running command
> r...@xxx.xx.xx.x:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp
> -d -t ovirt-XX)"; trap "chmod -R u+rwX \"${MY
> 2016-09-06 12:20:08,011 ERROR
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (org.ovirt.thread.pool-8-thread-41) [55397a53] SSH error running command
> r...@xxx.xx.xx.x:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp
> -d -t ovirt-XX)"; trap "chmod -R u+rwX \"${MY
> TMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar
> --warning=no-timestamp -C "${MYTMP}" -x &&  "${MYTMP}"/ovirt-host-deploy
> DIALOG/dialect=str:machine DIALOG/customization=bool:True': Command
> returned failure code 1 during SSH session 'r...@xxx.xx.xx.x'
> 2016-09-06 12:20:08,007 ERROR
> [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy)
> [55397a53] Error during deploy dialog: java.io.IOException: Unexpected
> connection termination
> at
> 
> org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:387)
> [otopi.jar:]
> at
> 
> org.ovirt.otopi.dialog.MachineDialogParser.nextEvent(MachineDialogParser.java:404)
> [otopi.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase._threadMain(VdsDeployBase.java:304)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.access$800(VdsDeployBase.java:45)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase$12.run(VdsDeployBase.java:386)
> [bll.jar:]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101]
>
> 2016-09-06 12:20:08,013 ERROR
> [org.ovirt.engine.core.uutils.ssh.SSHDialog]
> (org.ovirt.thread.pool-8-thread-41) [55397a53] Exception:
> java.io.IOException: Command returned failure code 1 during SSH session
> 'r...@xxx.xx.xx.x'
> at
> 
> org.ovirt.engine.core.uutils.ssh.SSHClient.executeCommand(SSHClient.java:527)
> [uutils.jar:]
> at
> 
> org.ovirt.engine.core.uutils.ssh.SSHDialog.executeCommand(SSHDialog.java:312)
> [uutils.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase.execute(VdsDeployBase.java:567)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.installHost(InstallVdsInternalCommand.java:189)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand.executeCommand(InstallVdsInternalCommand.java:93)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1215)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1359)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1982)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:174)
> [utils.jar:]
> at
> 
> org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:116)
> [utils.jar:]
> at
> org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1396)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:378)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.MultipleActionsRunner.executeValidatedCommand(MultipleActionsRunner.java:207)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.MultipleActionsRunner.runCommands(MultipleActionsRunner.java:172)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.bll.MultipleActionsRunner$2.run(MultipleActionsRunner.java:181)
> [bll.jar:]
> at
> 
> org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:89)
> [utils.jar:]
> at
> 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [rt.jar:1.8.0_101]
> at
> 
>