I wonder about that dirty yum upgrade bit -- I upgraded a remote F15 server to F16 yesterday using preupgrade-cli and then went on to configure that server as engine+host as you're doing. It worked fine.
On 03/01/2012 10:41 AM, Michal Kopacki wrote: > -------------------------------------------------------------- > On 2012-03-01 17:42:42 , Itamar Heim (ih...@redhat.com) wrote: >> >> not sure about the error below, but installing vdsm requires more >> configuration done by engine when you choose to add a host. > I'm not sure what you mean by "more configuration". As I understand > after install of vdsm it will be started as a service which apparently > is not going well. >> can you try adding the host via the engine (it will reboot in the last >> phase...). > It's exactly what I did. After vsdm install I went to ovirt-engine > page and add host (localhost in this case). In event window i saw that > there are components installing and after reboot i can see information > as below: > > "This host is in non responding state. Try to Activate it; If the > problem persists, switch Host to Maintenance mode and try to reinstall it." > > Of course Activate solves nothing. > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users