Fixed. It was the trailing 0's in ifcfg-em1 (IPADDR0, etc...) which had to
be removed.
2013/12/9 Pascal Jakobi
> [root@lab2 ~]# vdsClient -s 0 getVdsCaps
> HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
> 'iqn.1994-05.com.redhat:4334926278c1'}]}
> ISCSIInitiatorName = 'iqn.1994-0
[root@lab2 ~]# vdsClient -s 0 getVdsCaps
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:4334926278c1'}]}
ISCSIInitiatorName = 'iqn.1994-05.com.redhat:4334926278c1'
bondings = {'bond0': {'addr': '',
'cfg': {},
- Original Message -
> ok. I reinstalled everything. My F19 host has only an em1 ethernet I/F. I am
> on 3.3.
> However, setting up the host fails in its last stage (setting up mgmt
> network).
Can you please attach updated output of 'vdsClient -s 0 getVdsCaps' on this
host?
> 2013/12/
Hi Pascal,
VDSM for 3.3 is only working on F19 so since you downgraded the host you won't
get it.
Try to upgrade the host back to F19 and use the workaround suggested by Toni
(create the ifcfg file for your NIC).
Or am I missing something in your setup?
P.S. I also have a working F19 host
[root@lab2 ~]# vdsClient -s localhost getVdsCaps | grep cluster
*clusterLevels = ['3.0', '3.1', '3.2']*
[root@lab2 ~]# cd /etc/yum.repos.d/
[root@lab2 yum.repos.d]# ls
fedora.repo fedora-updates.repo fedora-updates-testing.repo
fedora-virt-preview.repo ovirt.repo
[root@lab2 yum.repos.d]# cat
- Original Message -
> From: "Pascal Jakobi"
> To: "Antoni Segura Puimedon"
> Cc: "Pascal Jakobi" , users@ovirt.org
> Sent: Wednesday, December 4, 2013 10:37:22 PM
> Subject: Re: [Users] ovirtmgmt not installed
>
> I have done this a
ers@ovirt.org
> Sent: Wednesday, December 4, 2013 9:37:22 PM
> Subject: Re: [Users] ovirtmgmt not installed
> I have done this and it solves the issue.
> However, the next issue I found was that the host was not able to join a 3.3
> cluster (i.e. the "default" cluster)
m: "Assaf Muller"
> > To: "Pascal Jakobi"
> > Cc: users@ovirt.org
> > Sent: Wednesday, December 4, 2013 9:09:18 AM
> > Subject: Re: [Users] ovirtmgmt not installed
> >
> > I personally have a F19 host working against 3.3 engine. Could y
- Original Message -
> From: "Assaf Muller"
> To: "Pascal Jakobi"
> Cc: users@ovirt.org
> Sent: Wednesday, December 4, 2013 9:09:18 AM
> Subject: Re: [Users] ovirtmgmt not installed
>
> I personally have a F19 host working against 3.3 engine.
@ovirt.org
Sent: Wednesday, December 4, 2013 8:22:05 AM
Subject: Re: [Users] ovirtmgmt not installed
At the end, I could not make an F19 Fedora host work against a 3.3 engine. I
suggest someone from the eng team has a look at it. some stuff just does not
work there.
Therefore, I downgraded the fedora
cal Jakobi" , "Moti Asayag"
>
> Cc: users@ovirt.org
> Sent: Tuesday, December 3, 2013 1:11:36 PM
> Subject: Re: [Users] ovirtmgmt not installed
>
> Still the same, even with networking working like a charm...
> Any idea ?
>
> [root@lab2 vdsm]# vdsClient -
Still the same, even with networking working like a charm...
Any idea ?
[root@lab2 vdsm]# vdsClient -s 0 getVdsCaps
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:a0bc8a5f9a5d'}]}
ISCSIInitiatorName = 'iqn.1994-05.com.redhat:a0bc8a5f9a5d'
bondings = {'bo
As a matter of fact, when I installed F19, it created an eno1 device,
aliased to em1. Don't know why, yet.
Even adding a "GATEWAY" clause in /etc/sysconfig/network does not seem to
change the problem
Will check how to change the device name.
2013/12/1 Moti Asayag
> Hi Pascal,
>
> - Ori
Hi Pascal,
- Original Message -
> From: "Pascal Jakobi"
> To: "Mike Kolesnik"
> Cc: users@ovirt.org, masa...@redhat.com
> Sent: Sunday, December 1, 2013 10:58:40 AM
> Subject: Re: ovirtmgmt not installed
>
> Mike
>
> Here you go. However, please note that I must investigate the connect
Did you install VDSM from nightly or stable?
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: "Pascal Jakobi"
To: "Mike Kolesnik"
Cc: users@ovirt.org
Sent: Sunday, December 1, 2013 10:58:40 AM
Subject: Re: [Users] ovirtmgmt not installed
Mike
Here you go. However, please note that I must investigate the connection
issue that Alon saw. will do it tomorrow.
Many thanks to you folks.
P
[root@lab2 ~]# vdsClient -s 0 getVdsCaps
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:eea139a8'}]}
ISCSI
- Original Message -
> Hi there
Hi Pascal,
> I installed a console on F19, then a F19 host (time 11:09 today).
> Everything works fine, apart from the installation of the mgmt network at the
> end.
> Can someone tell me what's going wrong ?
Can you please send the output of vdsCaps fro
- Original Message -
> From: "Alon Bar-Lev"
> To: "Pascal Jakobi"
> Cc: users@ovirt.org
> Sent: Saturday, November 30, 2013 2:40:33 AM
> Subject: Re: [Users] ovirtmgmt not installed
>
>
>
> - Original Message -
> > Fr
- Original Message -
> From: "Pascal Jakobi"
> To: users@ovirt.org
> Sent: Saturday, November 30, 2013 1:24:23 AM
> Subject: [Users] ovirtmgmt not installed
>
> Hi there
>
> I installed a console on F19, then a F19 host (time 11:09 today).
>
- Original Message -
> From: "Pascal Jakobi"
> To: users@ovirt.org
> Sent: Saturday, November 30, 2013 1:24:23 AM
> Subject: [Users] ovirtmgmt not installed
>
> Hi there
>
> I installed a console on F19, then a F19 host (time 11:09 today).
>
20 matches
Mail list logo