Hello everybody,

I will try this package shortly, but I would like to know why I can't use
my AD as I was doing in ovirt 3.4 before upgrade to ovirt 3.5. I have
executed kinit without problems after some modification in my
/etc/krb5.conf file, as I said in before mail but the error with portal
persists. Any suggestion?

Many thanks in advanced,

Juanjo.

On Wed, Nov 26, 2014 at 3:19 PM, Alon Bar-Lev <[email protected]> wrote:

>
>
> ----- Original Message -----
> > From: "Juan Jose" <[email protected]>
> > To: "Alon Bar-Lev" <[email protected]>
> > Cc: "Ondra Machacek" <[email protected]>, "Yair Zaslavsky" <
> [email protected]>, [email protected]
> > Sent: Wednesday, November 26, 2014 3:04:14 PM
> > Subject: Re: [ovirt-users] Adding domain to oVirt to 3.5 issue
> >
> > Hello Alon and everybody,
> >
> > Check in my ovirt-engine machine for ovirt-engine-aaa-ldap package and it
> > is not available:
> >
> > yum list "ovirt-engine*"
> > Loaded plugins: fastestmirror, refresh-packagekit, security, versionlock
> > Loading mirror speeds from cached hostfile
> >  * base: ftp.udl.es
> >  * epel: mirror.uv.es
> >  * extras: ftp.udl.es
> >  * ovirt-3.5: ftp.nluug.nl
> >  * ovirt-3.5-epel: mirror.uv.es
> >  * ovirt-3.5-jpackage-6.0-generic: mirror.ibcp.fr
> >  * ovirt-epel: mirror.uv.es
> >  * ovirt-jpackage-6.0-generic: mirror.ibcp.fr
> >  * updates: ftp.udl.es
> > Installed Packages
> > ovirt-engine.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-backend.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-cli.noarch
> > 3.3.0.6-1.el6                         @ovirt-3.3.3
> > ovirt-engine-dbscripts.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-extensions-api-impl.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-jboss-as.x86_64
> > 7.1.1-1.el6                           @ovirt-3.5
> > ovirt-engine-lib.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-restapi.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-sdk-python.noarch
> > 3.5.0.8-1.el6                         @ovirt-3.5
> > ovirt-engine-setup.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-setup-base.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-setup-plugin-ovirt-engine.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-setup-plugin-websocket-proxy.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-tools.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-userportal.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-webadmin-portal.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > ovirt-engine-websocket-proxy.noarch
> > 3.5.0.1-1.el6                         @ovirt-3.5
> > Available Packages
> > ovirt-engine-cli.noarch
> > 3.5.0.5-1.el6                         ovirt-3.5
> > ovirt-engine-dwh.noarch
> > 3.5.0-1.el6                           ovirt-3.5
> > ovirt-engine-dwh-setup.noarch
> > 3.5.0-1.el6                           ovirt-3.5
> > ovirt-engine-extensions-api-impl-javadoc.noarch
> > 3.5.0.1-1.el6                         ovirt-3.5
> > ovirt-engine-reports.noarch
> > 3.5.1-0.1.el6                         ovirt-3.5
> > ovirt-engine-reports-setup.noarch
> > 3.5.1-0.1.el6                         ovirt-3.5
> > ovirt-engine-sdk-java.noarch
> > 3.5.0.5-1.el6                         ovirt-3.5
> > ovirt-engine-sdk-java-javadoc.noarch
> > 3.5.0.5-1.el6                         ovirt-3.5
> > ovirt-engine-setup-plugin-allinone.noarch
> >
> > How can I get this package?
>
>
> Thanks for trying!
>
> Package is available at ovirt-3.5-snapshot[1].
>
> [1] http://resources.ovirt.org/pub/ovirt-3.5-snapshot/
>
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to