On Wed, Feb 24, 2016 at 3:16 PM, Fabian Deutsch <fdeutsch(a)redhat.com> wrote:
On Wed, Feb 24, 2016 at 3:10 PM, Yaniv Bronheim
<ybronhei(a)redhat.com> wrote:
> I suspect that it relates to the desire to remove the dependency in vdsm-cli
> -
https://gerrit.ovirt.org/#/c/53831/ which is not merged yet. and Fabian
> created the iso without vdsm-cli so the deploy failed in the middle. after
> it failed it couldn't recover even when vdsm-cli was installed. sounds
> reasonable?
Sounds reasonable - if host deploy can mess up networking that much.
Eli, can you restart with a clean installation and install vdsm-cli
before trying to add the host?
(This is actually what I do in my testing: Install, add vdsm-cli, then add host)
For now I've added a hack to pull in vdsm-cli until
https://gerrit.ovirt.org/#/c/53831/ is merged.
The squashfs img in ~1hr should have the fix.
- fabian
- fabian
> On Wed, Feb 24, 2016 at 4:01 PM, Dan Kenigsberg <danken(a)redhat.com> wrote:
>>
>> On Wed, Feb 24, 2016 at 08:16:45AM -0500, Eli Mesika wrote:
>> > Hi Guys
>> >
>> > I am working on NGN
>> > I had installed a ovirt-node from ISO, it (by mistake) did not include
>> > the vdsm-cli package, so host-deploy failed on that
>> > Fabian asked me to install vdsm-cli manually using :
>> >
>> > yum --enablerepo=ovirt* install vdsm-cli
>> >
>> > In that time the host was installed but did not came up having
>> > networking issues (see attached logs)
>> >
>> > Fabian thinks that this is regression in VDSM, he said that same method
>> > was tested 2 weeks ago with no problems
>>
>> Let's see {super,vdsm}.log, then and the exact vdsm version involved.
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
>
> --
> Yaniv Bronhaim.
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat