Re: [ovirt-users] bad bond name when setting up hosted engine

[Karli Sjöberg]

Den 8 jan. 2018 08:32 skrev Yedidyah Bar David :On Mon, Jan 8, 2018 at 1:36 AM, Sam McLeod  wrote:Thank you for the information Dan, Dominik and Didi,To avoid logging yet another bug for this issue, I've updated bug https://bugzilla.redhat.com/show_bug.cgi?id=1459229 as you've mentioned with the brief of our conversation here.By the way, it is very useful to name a bonded interface things other than bondXYZ, for example, you might have 6 bonds, each of a different network or native VLAN.It helps with debugging, troubleshooting and logging if the interface is named after the (native) network, e.g. your iSCSI storage network might have a bond called 'storage', while your management or hypervisor network might have a bond named 'mgmt' then perhaps you have 'data' bond that might have several vlans off it such as 'db' (database), 'dmz', 'staff' etc... depending on how and where you chop your network up.When I was a sysadmin I used to call my bonds bondFUNCTION.This way I both had a prefix 'bond' that readily showed it'sa bond, and a suffix showing its function.IMO oVirt should allow any bond names. If we do decide to limitthem at all, I'd limit only in a negative way - what's notallowed. E.g. it makes sense to me if we reject prefixes thatare common for non-bonds (eth, en, wl, br etc), but even thatI am not sure is so important.I agree, while at the same time, I don't understand why you would want to "label" a bond. Even if it's untagged, since you can label the bridge that's ontop of it? So even if the bond is called "bond0", the bridge can be called "data", or whatever, to ease diagnozing etc.What if it's tagged? Would you want to label both bond, vlan and bridge? Like "foobond", "barvlan" and "bazbridge"?/K 
--Sam McLeodhttps://smcleod.nethttps://twitter.com/s_mcleod

On 7 Jan 2018, at 6:08 pm, Yedidyah Bar David  wrote:On Fri, Jan 5, 2018 at 7:44 AM, Dan Kenigsberg  wrote:On Thu, Jan 4, 2018 at 5:50 AM, Sam McLeod  wrote:
> I'm having a problem where when setting up hosted engine deployment it fails
> stating that the selected bond name is bad.
>
> "code=25, message=bad bond name(s): mgmt)"
>
> - Is there a problem similar to
> https://bugzilla.redhat.com/show_bug.cgi?id=1519807 that's known?Please note that this is just but one bug in a series/tree ofrelated bugs, some of which are open. If you decide to followDan's suggestion, perhaps reuse one of the others, or perhapseven better - open a new one, and eventually one or more willbe closed as duplicate of one or more of the others. Sadly,not all of them link properly to each other, and at least onewhich was fixed caused another bug, so the fix was reverted.See also e.g. all of the discussion in:https://bugzilla.redhat.com/show_bug.cgi?id=1459229 
> - If it seems to be this bug, is it preferred that I simply update the
> existing, closed issue as I have done, or open a new bug?
>
> --
> Sam McLeod
> https://smcleod.net
> https://twitter.com/s_mcleod

I see that you are trying to use a bond interface named "mgmt".
To avoid confusion while debugging a system, Vdsm has opted to allow
only bond names starting with "bond" followed by one or more decimal
digits. Anything else is considered "bad bond".

I prefer keeping the "bond" prefix compulsory, but I'd like to hear
why using different names is useful.

You can reopen this bug, but please move it to vdsm and rename it: it
should be something like "Allow any bondXYZ name for bonds" or "Allow
any bond name" and explain there why it is a good idea.

Dominik, is there an Engine-side limitation on bond names?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
-- Didi

-- Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] bad bond name when setting up hosted engine

[Yedidyah Bar David]

On Mon, Jan 8, 2018 at 1:36 AM, Sam McLeod  wrote:

> Thank you for the information Dan, Dominik and Didi,
>
> To avoid logging yet another bug for this issue, I've updated bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1459229 as you've mentioned
> with the brief of our conversation here.
>
> By the way, it is very useful to name a bonded interface things other than
> bondXYZ, for example, you might have 6 bonds, each of a different network
> or native VLAN.
> It helps with debugging, troubleshooting and logging if the interface is
> named after the (native) network, e.g. your iSCSI storage network might
> have a bond called 'storage', while your management or hypervisor network
> might have a bond named 'mgmt' then perhaps you have 'data' bond that might
> have several vlans off it such as 'db' (database), 'dmz', 'staff' etc...
> depending on how and where you chop your network up.
>

When I was a sysadmin I used to call my bonds bondFUNCTION.

This way I both had a prefix 'bond' that readily showed it's
a bond, and a suffix showing its function.

IMO oVirt should allow any bond names. If we do decide to limit
them at all, I'd limit only in a negative way - what's not
allowed. E.g. it makes sense to me if we reject prefixes that
are common for non-bonds (eth, en, wl, br etc), but even that
I am not sure is so important.


>
> --
> Sam McLeod
> https://smcleod.net
> https://twitter.com/s_mcleod
>
> On 7 Jan 2018, at 6:08 pm, Yedidyah Bar David  wrote:
>
> On Fri, Jan 5, 2018 at 7:44 AM, Dan Kenigsberg  wrote:
>
>> On Thu, Jan 4, 2018 at 5:50 AM, Sam McLeod 
>> wrote:
>> > I'm having a problem where when setting up hosted engine deployment it
>> fails
>> > stating that the selected bond name is bad.
>> >
>> > "code=25, message=bad bond name(s): mgmt)"
>> >
>> > - Is there a problem similar to
>> > https://bugzilla.redhat.com/show_bug.cgi?id=1519807 that's known?
>>
>
> Please note that this is just but one bug in a series/tree of
> related bugs, some of which are open. If you decide to follow
> Dan's suggestion, perhaps reuse one of the others, or perhaps
> even better - open a new one, and eventually one or more will
> be closed as duplicate of one or more of the others. Sadly,
> not all of them link properly to each other, and at least one
> which was fixed caused another bug, so the fix was reverted.
> See also e.g. all of the discussion in:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1459229
>
>
>
>> > - If it seems to be this bug, is it preferred that I simply update the
>> > existing, closed issue as I have done, or open a new bug?
>> >
>> > --
>> > Sam McLeod
>> > https://smcleod.net
>> > https://twitter.com/s_mcleod
>>
>> I see that you are trying to use a bond interface named "mgmt".
>> To avoid confusion while debugging a system, Vdsm has opted to allow
>> only bond names starting with "bond" followed by one or more decimal
>> digits. Anything else is considered "bad bond".
>>
>> I prefer keeping the "bond" prefix compulsory, but I'd like to hear
>> why using different names is useful.
>>
>> You can reopen this bug, but please move it to vdsm and rename it: it
>> should be something like "Allow any bondXYZ name for bonds" or "Allow
>> any bond name" and explain there why it is a good idea.
>>
>> Dominik, is there an Engine-side limitation on bond names?
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
> Didi
>
>
>


-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Deploying self-hosted engine - Waiting for VDSM host to become operation + received packet with own address as source

[Sam McLeod]

Hello,

I'm trying to setup a host as a self-hosted engine as per 
https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
 
.
The host is configured with two bonded network interfaces:

bond0 = management network for hypervisors, setup as active/passive.
bond1 = network that has VLANs for various network segments for virtual 
machines to use, setup as LACP bond to upstream switches.

On the host, both networks are operational and work as expected.

When setting up the self-hosted engine, bond0 is selected as network to bridge 
with, and a unique IP is given to the self-hosted engine VM.

During the final stages of the self-hosted engine setup, the installer gets 
stuck on ' Waiting for the VDSM host to become operational'.
While it is repeating this every minute or so the host repeats the message 
'bond0: received packet with own address as source address', which is odd to me 
as it's in active/passive bond and I'd only expect to see this kind of message 
on XOR / load balanced interfaces.

Host console screenshot: https://imgur.com/a/a2JLd 
Host OS: CentOS 7.4
oVirt version: 4.2.0

ip a on host while install is stuck waiting for VDSM:

# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp2s0f0:  mtu 9000 qdisc mq master 
bond1 portid 01373031384833 state UP qlen 1000
link/ether 78:e3:b5:10:74:88 brd ff:ff:ff:ff:ff:ff
3: enp2s0f1:  mtu 9000 qdisc mq master 
bond1 portid 02373031384833 state UP qlen 1000
link/ether 78:e3:b5:10:74:88 brd ff:ff:ff:ff:ff:ff
4: ens1f0:  mtu 1500 qdisc mq master 
bond0 portid 01474835323543 state UP qlen 1000
link/ether 00:9c:02:3c:49:90 brd ff:ff:ff:ff:ff:ff
5: ens1f1:  mtu 1500 qdisc mq master 
bond0 portid 02474835323543 state UP qlen 1000
link/ether 00:9c:02:3c:49:90 brd ff:ff:ff:ff:ff:ff
6: bond1:  mtu 9000 qdisc noqueue state 
UP qlen 1000
link/ether 78:e3:b5:10:74:88 brd ff:ff:ff:ff:ff:ff
inet6 fe80::7ae3:b5ff:fe10:7488/64 scope link
   valid_lft forever preferred_lft forever
7: storage@bond1:  mtu 9000 qdisc noqueue 
state UP qlen 1000
link/ether 78:e3:b5:10:74:88 brd ff:ff:ff:ff:ff:ff
inet 10.51.40.172/24 brd 10.51.40.255 scope global storage
   valid_lft forever preferred_lft forever
inet6 fe80::7ae3:b5ff:fe10:7488/64 scope link
   valid_lft forever preferred_lft forever
9: ovs-system:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether ae:c0:02:25:42:24 brd ff:ff:ff:ff:ff:ff
10: br-int:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether be:92:5d:c3:28:4d brd ff:ff:ff:ff:ff:ff
30: bond0:  mtu 1500 qdisc noqueue 
master ovirtmgmt state UP qlen 1000
link/ether 00:9c:02:3c:49:90 brd ff:ff:ff:ff:ff:ff
46: ovirtmgmt:  mtu 1500 qdisc noqueue state 
UP qlen 1000
link/ether 00:9c:02:3c:49:90 brd ff:ff:ff:ff:ff:ff
inet 10.51.14.112/24 brd 10.51.14.255 scope global ovirtmgmt
   valid_lft forever preferred_lft forever
47: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 8e:c0:25:88:40:de brd ff:ff:ff:ff:ff:ff


Before the self-hosted engine install was run the following did not exist:

;vdsmdummy;
ovs-system
br-int
ovirtmgmt

and bond0 was not a slave of ovirtmgmt.

I'm now going to kick off a complete reinstall of CentOS 7 on the host as I've 
since tried cleaning up the host using the ovirt-hosted-engine-cleanup command 
and removing the packages which seem to leave the network configuration a mess 
an doesn't actually cleanup files on disk as expected.


--
Sam McLeod (protoporpoise on IRC)
https://smcleod.net
https://twitter.com/s_mcleod

Words are my own opinions and do not necessarily represent those of my employer 
or partners.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] bad bond name when setting up hosted engine

[Sam McLeod]

Thank you for the information Dan, Dominik and Didi,

To avoid logging yet another bug for this issue, I've updated bug 
https://bugzilla.redhat.com/show_bug.cgi?id=1459229 
 as you've mentioned with 
the brief of our conversation here.

By the way, it is very useful to name a bonded interface things other than 
bondXYZ, for example, you might have 6 bonds, each of a different network or 
native VLAN.
It helps with debugging, troubleshooting and logging if the interface is named 
after the (native) network, e.g. your iSCSI storage network might have a bond 
called 'storage', while your management or hypervisor network might have a bond 
named 'mgmt' then perhaps you have 'data' bond that might have several vlans 
off it such as 'db' (database), 'dmz', 'staff' etc... depending on how and 
where you chop your network up.

--
Sam McLeod
https://smcleod.net
https://twitter.com/s_mcleod

> On 7 Jan 2018, at 6:08 pm, Yedidyah Bar David  wrote:
> 
> On Fri, Jan 5, 2018 at 7:44 AM, Dan Kenigsberg  > wrote:
> On Thu, Jan 4, 2018 at 5:50 AM, Sam McLeod  > wrote:
> > I'm having a problem where when setting up hosted engine deployment it fails
> > stating that the selected bond name is bad.
> >
> > "code=25, message=bad bond name(s): mgmt)"
> >
> > - Is there a problem similar to
> > https://bugzilla.redhat.com/show_bug.cgi?id=1519807 
> >  that's known?
> 
> Please note that this is just but one bug in a series/tree of
> related bugs, some of which are open. If you decide to follow
> Dan's suggestion, perhaps reuse one of the others, or perhaps
> even better - open a new one, and eventually one or more will
> be closed as duplicate of one or more of the others. Sadly,
> not all of them link properly to each other, and at least one
> which was fixed caused another bug, so the fix was reverted.
> See also e.g. all of the discussion in:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1459229 
> 
> 
>  
> > - If it seems to be this bug, is it preferred that I simply update the
> > existing, closed issue as I have done, or open a new bug?
> >
> > --
> > Sam McLeod
> > https://smcleod.net 
> > https://twitter.com/s_mcleod 
> 
> I see that you are trying to use a bond interface named "mgmt".
> To avoid confusion while debugging a system, Vdsm has opted to allow
> only bond names starting with "bond" followed by one or more decimal
> digits. Anything else is considered "bad bond".
> 
> I prefer keeping the "bond" prefix compulsory, but I'd like to hear
> why using different names is useful.
> 
> You can reopen this bug, but please move it to vdsm and rename it: it
> should be something like "Allow any bondXYZ name for bonds" or "Allow
> any bond name" and explain there why it is a good idea.
> 
> Dominik, is there an Engine-side limitation on bond names?
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
> 
> 
> 
> -- 
> Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Suggestions on changing hosts' network

[Gianluca Cecchi]

On Wed, Jan 3, 2018 at 12:25 PM, Gianluca Cecchi 
wrote:

>
>
> On Wed, Jan 3, 2018 at 11:56 AM, Marcin Mirecki 
> wrote:
>
>> Hello Gianluca,
>>
>> Add/remove would probably be the simplest way to go.
>> The procedure would be:
>> - take host to maintenance
>> - remove host
>> - use vdsm-cient to change the ip of ovirtmgmt
>> - add the host again
>>
>> Just changing the dns configuration sounds quite interesting.
>> I suppose the host certificates should be ok if the host was added by
>> hostname.
>>
>>
> I've already done something similar in September; see here the full thread:
> http://lists.ovirt.org/pipermail/users/2017-September/084411.html
>
> In that case it was more complicated in the sense that vlan change was
> involved for ovirtmgmt and I passed through a new cluster.
> Now it is more simple, but while on September case the hosts were plain
> CentOS hosts, now they are ovirt-node-ng, so my manual ifcfg files
> manipulation doesn't fit.
>
> If vdsm-client command is ok I presume it will be something of type:
>
> # vdsm-client Host setupNetworks
> vdsm-client: Command Host.setupNetworks with args {} failed:
> (code=-32603, message=Attempt to call function:  Global.setupNetworks of > with arguments:
> () error: setupNetworks() takes exactly 4 arguments (1 given))
> #
>
> with some sort of json configuration, but it is not clear to me what to
> give
>
> Can I do the change of ip from the host web cockpit mgmt interface? I
> set/change the ip and then eventually reboot the server to see if it works?
>
> Gianluca
>


hello,
any update on how to give JSON representation (or other way) to use
vdsm-client and change ip/gateway of ovirt-ng node?
Thanks

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Need input please.

[carl langlois]

Hi,

I have attach the delpoy log from the latest attempt..the weird thing is
that if i try to remove it after the UI tell me that the host is setup to
host engine and should be undeploy.. but i do not get the small icon that
say that it can run a hosted-engine.

Thanks


On Sun, Jan 7, 2018 at 9:38 AM, Yaniv Kaul  wrote:

>
>
> On Sun, Jan 7, 2018 at 4:19 PM, carl langlois 
> wrote:
>
>> Hi all,
>>
>> So i got a bit futher on getting everithing back on. After removing the
>> ca.epem certificate and redoing engine-setup on the hosted-engine vm i was
>> able to remove/reinstall one of my 2 hosts. Now i am facing a other
>> problem. I need this new host to be able to run the hosted engine vm. But
>> if re-install the host and in the hosted engine tab set to DEPLOY the host
>> is add successfully and can run vms but it seem that the DEPLOY did not
>> work..
>>
>> If i am not able to make this host run the engine vm i cant
>> fix(re-install) the second host.
>>
>> Any insight would be appreciated.
>>
>
> If you can attach logs, that'd be great.
> Y.
>
>
>>
>> Thanks.
>>
>>
>>
>> On Sat, Jan 6, 2018 at 12:40 PM, carl langlois 
>> wrote:
>>
>>> Yes i have try removing it and re-adding it and i have the problem with
>>> certifcate enrollement..
>>>
>>>
>>>
>>> On Sat, Jan 6, 2018 at 12:08 PM, Donny Davis 
>>> wrote:
>>>
 Have you tried to remove that host and readd it?

 Also there is a bug that throws the same error, not sure if its
 related. Did you have your hosts in maintenance prior to upgrading?

 https://bugzilla.redhat.com/show_bug.cgi?id=1258589

 On Sat, Jan 6, 2018 at 10:52 AM, carl langlois 
 wrote:

> Hi
> I have put the new engine_enrolfail.log that conain the error when
> re-installing .
>
>
> https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
> a6evk6fkrCz8?usp=sharing
>
>
> Thanks
>
> On Sat, Jan 6, 2018 at 10:18 AM, Benny Zlotnik 
> wrote:
>
>> Can you please provide the log with the error?
>>
>> On Sat, Jan 6, 2018 at 5:09 PM, carl langlois > > wrote:
>>
>>> Hi again,
>>>
>>> I manage to go a little bit further.. I was not able to set one host
>>> to maintenance because they had running vm.. so i force it to mark it as
>>> reboot  and flush any vm and now i can try to reinstall the host.. but 
>>> now
>>> i am getting error when the installation try to enroll certificate..
>>>
>>> Any idea?
>>>
>>> Thanks
>>> Carl
>>>
>>>
>>> On Sat, Jan 6, 2018 at 9:41 AM, carl langlois <
>>> crl.langl...@gmail.com> wrote:
>>>
 Hi,

 Thanks for the quick reply.

 Version before the update was the latest 4.1.
 The storage is NFS.
 The host are plain 7.4 Centos.i keep them up to date
 if i remenber the initail deploy of the engine vm was full OS

 The step to upgrade was:

 SSH to hosted engine vm ,
 yum install 4.2 release
 run engine-setup.
 this where i think something when wrong.
 the engine setup was not able to update some certificate.. a quick
 search on the internet and found that moving the ca.pem from the
 /etc/pki/ovrit-engine made the engine-setup work..

 from that point the hosted_engine seem to work fine but all hosts
 and data center are not operational.

 One of my main concern is losing all the template and users vm..



 Engine and vdsm log of one host are here..

 In the engine log there is a lot of this error..

 2018-01-06 08:31:40,459-05 ERROR [org.ovirt.engine.core.vdsbrok
 er.vdsbroker.GetCapabilitiesVDSCommand]
 (EE-ManagedThreadFactory-engineScheduled-Thread-9) [] Command
 'GetCapabilitiesVDSCommand(HostName = hosted_engine_2,
 VdsIdAndVdsVDSCommandParametersBase:{hostId='7d2b3f49-0fbb-493b-8f3c-5283566e830d',
 vds='Host[hosted_engine_2,7d2b3f49-0fbb-493b-8f3c-5283566e830d]'})'
 execution failed: VDSGenericException: VDSNetworkException: General
 SSLEngine problem.

 https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
 a6evk6fkrCz8?usp=sharing

 Thanks for your support

 Carl



 On Sat, Jan 6, 2018 at 8:50 AM, Gianluca Cecchi <
 gianluca.cec...@gmail.com> wrote:

> On Sat, Jan 6, 2018 at 2:42 PM, carl langlois <
> crl.langl...@gmail.com> wrote:
>
>> Hi again all,
>>
>> I really need your input on recovering my failed upgrade to 4.2.
>>
>>
>>
> First two things to do to get appropriate help would be, in my
> opinion:
>
> 1) provide a detailed description of your environment
> 

[ovirt-users] [CORRECTED] Can't create 2nd network for VMs in DMZ zone

[Andrei V]

Hi !

Made a typo in previous message, sorry.

I'm having difficulty to utilize 2nd NIC on HP Proliant server in order
to connect guest VM to DMZ (engine, node and all other guest VMs are on
internal zone).

I tried to use PCI passthrough, downed ifcfg-enp3s4f1 on node host,
created vNic profile "PCI NIC Passthrough", network named "Node10-NIC2",
then Virtual Machines -> Network Interfaces -> nic 2 of type PCI
Passthrough and profile above.
Unfortunately, guest OS (SuSE Leap 42.3) still don't recognize this NIC.

This 2nd NIC is visible on Compute -> Hosts -> Network Interfaces.
I can assign it network named "Node10-NIC2". However, right now I'm
working from the remote, if node net setup get screwed, it will be a big
problem.
In the archive I found that this 2nd NIC must be up with no IP and
default route. Is this correct definition of ifcfg-enp3s4f1?
NetworkManager is disabled on node.

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=no
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NM_CONTROLLED=no
NAME=enp3s4f1
UUID=09f96366-e4a9-4e6e-a090-7267ed102d36
DEVICE=enp3s4f1
ONBOOT=yes

Thanks in advance
Andrei V
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Can't create 2nd network for VMs in DMZ zone

[Andrei V]

Hi !

I'm having difficulty to utilize 2nd NIC on HP Proliant server in order
to connect guest VM to DMZ (engine, node and all other guest VMs are on
internal zone).

I tried to use PCI passthrough, downed ifcfg-enp3s4f1 on node host,
created vNic profile "PCI NIC Passthrough", network named "Node10-NIC2",
then Virtual Machines -> Network Interfaces -> nic 2 of type PCI
Passthrough and profile above.
Unfortunately, guest OS (SuSE Leap 42.3) still don't recognize this NIC.

This 2nd NIC is visible on Compute -> Hosts -> Network Interfaces.
I can assign it network named "Node10-NIC2". However, right now I'm
working from the remote, if node net setup get screwed, it will be a big
problem.
In the archive I found that this 2nd NIC must be up with no IP and
default route. Is this correct definition of ifcfg-enp3s4f1?
NetworkManager is disabled on node.

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NM_CONTROLLED=no
NAME=enp3s4f1
UUID=09f96366-e4a9-4e6e-a090-7267ed102d36
DEVICE=enp3s4f1
ONBOOT=yes

Thanks in advance
Andrei V
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] How to simulate update of ng node from 4.1.7 to 4.1.8

[Gianluca Cecchi]

Suppose I download both the isos:

the fixed one for 4.1.17 here:
http://resources.ovirt.org/pub/ovirt-4.1/iso/ovirt-node-ng-installer-ovirt/4.1-2017110820/ovirt-node-ng-installer-ovirt-4.1-2017110820.iso

and the 4.1.8 here:
http://resources.ovirt.org/pub/ovirt-4.1/iso/ovirt-node-ng-installer-ovirt/4.1-2017121114/ovirt-node-ng-installer-ovirt-4.1-2017121114.iso

and I want to simulate install of 4.1.7 from the iso and then update of the
ng node to 4.1.8 without internet access but using in some way the 4.1.8
iso (or something derived from it) on my local lan, how can I do?

Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.1 hosted engine: Resize or Change "hosted-engine" Data Domain

[yayo (j)]

Hi,

Sorry but I needs to migrate from one hosted-engine to another, so, where I
can restore backup? Before or after the autoimport triggered?

* Create new hosted-engine lun
* Backup current hosted-engine
* From one node execute hosted-engine --deploy --he-remove-storage-vm
--he-remove-hosts
Right? And after that?

Can you help me to better understand?
Thank you!

Il 03 Gen 2018 14:39, "Martin Sivak"  ha scritto:

Hi,

we do not have any nice procedure to do that. Moving hosted engine to
a different storage usually involves backup and restore of the engine
database. See for example here:
http://lists.ovirt.org/pipermail/users/2017-June/082466.html

Best regards

--
Martin Sivak
SLA / oVirt

On Wed, Jan 3, 2018 at 12:20 PM, yayo (j)  wrote:
> hi at all,
>
> We have the "hosted engine" Data domain on a FC LUN too big for only the
> hosted-engine so we want to create another little FC LUN and move the
> hosted-engine vm on this new LUN and destroy old one ...
>
> Is there any official workflow or how to to do this operation? Or, someone
> can  guide me?
>
> Thank you!
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Need input please.

[Yaniv Kaul]

On Sun, Jan 7, 2018 at 4:19 PM, carl langlois 
wrote:

> Hi all,
>
> So i got a bit futher on getting everithing back on. After removing the
> ca.epem certificate and redoing engine-setup on the hosted-engine vm i was
> able to remove/reinstall one of my 2 hosts. Now i am facing a other
> problem. I need this new host to be able to run the hosted engine vm. But
> if re-install the host and in the hosted engine tab set to DEPLOY the host
> is add successfully and can run vms but it seem that the DEPLOY did not
> work..
>
> If i am not able to make this host run the engine vm i cant
> fix(re-install) the second host.
>
> Any insight would be appreciated.
>

If you can attach logs, that'd be great.
Y.


>
> Thanks.
>
>
>
> On Sat, Jan 6, 2018 at 12:40 PM, carl langlois 
> wrote:
>
>> Yes i have try removing it and re-adding it and i have the problem with
>> certifcate enrollement..
>>
>>
>>
>> On Sat, Jan 6, 2018 at 12:08 PM, Donny Davis 
>> wrote:
>>
>>> Have you tried to remove that host and readd it?
>>>
>>> Also there is a bug that throws the same error, not sure if its related.
>>> Did you have your hosts in maintenance prior to upgrading?
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1258589
>>>
>>> On Sat, Jan 6, 2018 at 10:52 AM, carl langlois 
>>> wrote:
>>>
 Hi
 I have put the new engine_enrolfail.log that conain the error when
 re-installing .


 https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
 a6evk6fkrCz8?usp=sharing


 Thanks

 On Sat, Jan 6, 2018 at 10:18 AM, Benny Zlotnik 
 wrote:

> Can you please provide the log with the error?
>
> On Sat, Jan 6, 2018 at 5:09 PM, carl langlois 
> wrote:
>
>> Hi again,
>>
>> I manage to go a little bit further.. I was not able to set one host
>> to maintenance because they had running vm.. so i force it to mark it as
>> reboot  and flush any vm and now i can try to reinstall the host.. but 
>> now
>> i am getting error when the installation try to enroll certificate..
>>
>> Any idea?
>>
>> Thanks
>> Carl
>>
>>
>> On Sat, Jan 6, 2018 at 9:41 AM, carl langlois > > wrote:
>>
>>> Hi,
>>>
>>> Thanks for the quick reply.
>>>
>>> Version before the update was the latest 4.1.
>>> The storage is NFS.
>>> The host are plain 7.4 Centos.i keep them up to date
>>> if i remenber the initail deploy of the engine vm was full OS
>>>
>>> The step to upgrade was:
>>>
>>> SSH to hosted engine vm ,
>>> yum install 4.2 release
>>> run engine-setup.
>>> this where i think something when wrong.
>>> the engine setup was not able to update some certificate.. a quick
>>> search on the internet and found that moving the ca.pem from the
>>> /etc/pki/ovrit-engine made the engine-setup work..
>>>
>>> from that point the hosted_engine seem to work fine but all hosts
>>> and data center are not operational.
>>>
>>> One of my main concern is losing all the template and users vm..
>>>
>>>
>>>
>>> Engine and vdsm log of one host are here..
>>>
>>> In the engine log there is a lot of this error..
>>>
>>> 2018-01-06 08:31:40,459-05 ERROR [org.ovirt.engine.core.vdsbrok
>>> er.vdsbroker.GetCapabilitiesVDSCommand]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-9) [] Command
>>> 'GetCapabilitiesVDSCommand(HostName = hosted_engine_2,
>>> VdsIdAndVdsVDSCommandParametersBase:{hostId='7d2b3f49-0fbb-493b-8f3c-5283566e830d',
>>> vds='Host[hosted_engine_2,7d2b3f49-0fbb-493b-8f3c-5283566e830d]'})'
>>> execution failed: VDSGenericException: VDSNetworkException: General
>>> SSLEngine problem.
>>>
>>> https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
>>> a6evk6fkrCz8?usp=sharing
>>>
>>> Thanks for your support
>>>
>>> Carl
>>>
>>>
>>>
>>> On Sat, Jan 6, 2018 at 8:50 AM, Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>
 On Sat, Jan 6, 2018 at 2:42 PM, carl langlois <
 crl.langl...@gmail.com> wrote:

> Hi again all,
>
> I really need your input on recovering my failed upgrade to 4.2.
>
>
>
 First two things to do to get appropriate help would be, in my
 opinion:

 1) provide a detailed description of your environment
 exact version before the update; kind of storage (Gluster, NFS,
 iSCSI, FC), kind of hosts (plain OS and which version or node-ng and 
 which
 version before and after), kind of deploy executed for hosted engine 
 VM at
 initial install time (appliance, full OS).
 Describe steps used for upgrading.

 2) upload to a shared file services all the possible logs:
 engine logs before and after the upgrade and logs of engine-setup

Re: [ovirt-users] Need input please.

[carl langlois]

Hi all,

So i got a bit futher on getting everithing back on. After removing the
ca.epem certificate and redoing engine-setup on the hosted-engine vm i was
able to remove/reinstall one of my 2 hosts. Now i am facing a other
problem. I need this new host to be able to run the hosted engine vm. But
if re-install the host and in the hosted engine tab set to DEPLOY the host
is add successfully and can run vms but it seem that the DEPLOY did not
work..

If i am not able to make this host run the engine vm i cant fix(re-install)
the second host.

Any insight would be appreciated.

Thanks.



On Sat, Jan 6, 2018 at 12:40 PM, carl langlois 
wrote:

> Yes i have try removing it and re-adding it and i have the problem with
> certifcate enrollement..
>
>
>
> On Sat, Jan 6, 2018 at 12:08 PM, Donny Davis  wrote:
>
>> Have you tried to remove that host and readd it?
>>
>> Also there is a bug that throws the same error, not sure if its related.
>> Did you have your hosts in maintenance prior to upgrading?
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1258589
>>
>> On Sat, Jan 6, 2018 at 10:52 AM, carl langlois 
>> wrote:
>>
>>> Hi
>>> I have put the new engine_enrolfail.log that conain the error when
>>> re-installing .
>>>
>>>
>>> https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
>>> a6evk6fkrCz8?usp=sharing
>>>
>>>
>>> Thanks
>>>
>>> On Sat, Jan 6, 2018 at 10:18 AM, Benny Zlotnik 
>>> wrote:
>>>
 Can you please provide the log with the error?

 On Sat, Jan 6, 2018 at 5:09 PM, carl langlois 
 wrote:

> Hi again,
>
> I manage to go a little bit further.. I was not able to set one host
> to maintenance because they had running vm.. so i force it to mark it as
> reboot  and flush any vm and now i can try to reinstall the host.. but now
> i am getting error when the installation try to enroll certificate..
>
> Any idea?
>
> Thanks
> Carl
>
>
> On Sat, Jan 6, 2018 at 9:41 AM, carl langlois 
> wrote:
>
>> Hi,
>>
>> Thanks for the quick reply.
>>
>> Version before the update was the latest 4.1.
>> The storage is NFS.
>> The host are plain 7.4 Centos.i keep them up to date
>> if i remenber the initail deploy of the engine vm was full OS
>>
>> The step to upgrade was:
>>
>> SSH to hosted engine vm ,
>> yum install 4.2 release
>> run engine-setup.
>> this where i think something when wrong.
>> the engine setup was not able to update some certificate.. a quick
>> search on the internet and found that moving the ca.pem from the
>> /etc/pki/ovrit-engine made the engine-setup work..
>>
>> from that point the hosted_engine seem to work fine but all hosts and
>> data center are not operational.
>>
>> One of my main concern is losing all the template and users vm..
>>
>>
>>
>> Engine and vdsm log of one host are here..
>>
>> In the engine log there is a lot of this error..
>>
>> 2018-01-06 08:31:40,459-05 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetCapabilitiesVDSCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-9) [] Command
>> 'GetCapabilitiesVDSCommand(HostName = hosted_engine_2,
>> VdsIdAndVdsVDSCommandParametersBase:{hostId='7d2b3f49-0fbb-493b-8f3c-5283566e830d',
>> vds='Host[hosted_engine_2,7d2b3f49-0fbb-493b-8f3c-5283566e830d]'})'
>> execution failed: VDSGenericException: VDSNetworkException: General
>> SSLEngine problem.
>>
>> https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJ
>> a6evk6fkrCz8?usp=sharing
>>
>> Thanks for your support
>>
>> Carl
>>
>>
>>
>> On Sat, Jan 6, 2018 at 8:50 AM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Sat, Jan 6, 2018 at 2:42 PM, carl langlois <
>>> crl.langl...@gmail.com> wrote:
>>>
 Hi again all,

 I really need your input on recovering my failed upgrade to 4.2.



>>> First two things to do to get appropriate help would be, in my
>>> opinion:
>>>
>>> 1) provide a detailed description of your environment
>>> exact version before the update; kind of storage (Gluster, NFS,
>>> iSCSI, FC), kind of hosts (plain OS and which version or node-ng and 
>>> which
>>> version before and after), kind of deploy executed for hosted engine VM 
>>> at
>>> initial install time (appliance, full OS).
>>> Describe steps used for upgrading.
>>>
>>> 2) upload to a shared file services all the possible logs:
>>> engine logs before and after the upgrade and logs of engine-setup
>>> run during update
>>> vdsm logs before and after the upgrade
>>>
>>>
>>> Gianluca
>>>
>>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/use

Re: [ovirt-users] Local storage and multiple hosts in cluster

[Fred Rolland]

No, you cannot.
This is by design. If you want to use local storage, you can have only one
host in the cluster/data center.

On Fri, Jan 5, 2018 at 4:14 PM, Waqar Khan  wrote:

> Hi,
> I have 1 engine manager and 2 nodes. The 2 nodes are using local storage
> (this is for testing out ovirt and learning about it). I cannot however add
> 2 hosts to the same cluster in the same data centre without shared storage.
> Is there a workaround for this?
>
> Regards
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users