Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Nicolas Ecarnot

Le 01/02/2017 à 18:18, Nicolas Ecarnot a écrit :

Le 01/02/2017 à 17:37, Michael Watters a écrit :

I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts.  I am seeing errors when the engine attempts to
check for updates as follows.

Failed to check for available updates on host ovirt-node-production2
with message 'Command returned failure code 1 during SSH session
'root@ovirt-node-production2''.

I checked the logs on the host and it appears to be an issue with
yum.

2017-01-30 10:21:05 ERROR
otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum:
Cannot queue package ovirt-imageio-daemon: Package
ovirt-imageio-daemon cannot be found

2017-01-30 10:21:05 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Package installation': Package
ovirt-imageio-daemon cannot be found

Is there a way to resolve this?  I don't see any package named
ovirt-imageio-daemon in my repos when running a yum search.



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



Hello Michael,

Last time we spoke about this issue, it was the fault of ipV6 that had
to be turn down (I let you search the relevant posts).


OK Michael,
Your case is different.

Anyway, for the record, I was referring to this :

http://lists.ovirt.org/pipermail/users/2016-September/076113.html



-
cat /etc/sysctl.d/noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
-




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


[ovirt-users] How to update ovirt nodes

2017-02-01 Thread Shalabh Goel
Hi

Ovirt 4.1 has been released, I want to to know how to upgrade the Ovirt
nodes to 4.1. I was able to upgrade ovirt-engine but I could not find how
to upgrade node.

Thank You

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


Re: [ovirt-users] VM has been paused due to storage I/O problem

2017-02-01 Thread Gianluca Cecchi
On Wed, Feb 1, 2017 at 8:22 PM, Gianluca Cecchi 
wrote:

>
> OK. In the mean time I have applied your suggested config and restarted
> the 2 nodes.
> Let we test and see if I find any problems running also some I/O tests.
> Thanks in the mean time,
> Gianluca
>


Quick test without much success

Inside the guest I run this loop
while true
do
time dd if=/dev/zero bs=1024k count=1024 of=/home/g.cecchi/testfile
sleep 5
done

BTW: my home is inside / filesystem on guest that has space to accomodate
1Gb of the dd command:
[g.cecchi@ol65 ~]$ df -h /home/g.cecchi/
FilesystemSize  Used Avail Use% Mounted on
/dev/mapper/vg_ol65-lv_root
   20G  4.9G   14G  27% /
[g.cecchi@ol65 ~]$

After about 7 rounds I get this in messages of the host where the VM is
running:

Feb  1 23:31:39 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:39 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:44 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:45 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:45 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:47 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:50 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:50 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:56 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  1 23:31:57 ovmsrv06 kernel: dd: sending ioctl 80306d02 to a partition!

Nothing on the other host.
In web admin events pane:
Feb 1, 2017 11:31:44 PM VM ol65 has been paused due to no Storage space
error.
Feb 1, 2017 11:31:44 PM VM ol65 has been paused.

I stop the dd loop and after some seconds:
Feb 1, 2017 11:32:32 PM VM ol65 has recovered from paused back to up

Multipath status for my device:

3600a0b8000299aa8d08b55014119 dm-2 IBM ,1814  FAStT
size=4.0T features='3 queue_if_no_path pg_init_retries 50' hwhandler='1
rdac' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| |- 0:0:1:3 sdj 8:144 active undef running
| `- 2:0:1:3 sdp 8:240 active undef running
`-+- policy='service-time 0' prio=0 status=enabled
  |- 0:0:0:3 sdd 8:48  active undef running
  `- 2:0:0:3 sdk 8:160 active undef running

In engine.log

2017-02-01 23:22:01,449 INFO
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-15)
[530aee87] Running command: CreateUserSessionCommand internal: false.
2017-02-01 23:22:04,011 INFO
[org.ovirt.engine.docs.utils.servlet.ContextSensitiveHelpMappingServlet]
(default task-12) [] Context-sensitive help is not installed. Manual
directory doesn't exist: /usr/share/ovirt-engine/manual
2017-02-01 23:31:43,936 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(ForkJoinPool-1-worker-10) [10c15e39] VM
'932db7c7-4121-4cbe-ad8d-09e4e99b3cdd'(ol65) moved from 'Up' --> 'Paused'
2017-02-01 23:31:44,087 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-10) [10c15e39] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: VM ol65 has been paused.
2017-02-01 23:31:44,227 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-10) [10c15e39] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: VM ol65 has been paused due to no
Storage space error.
2017-02-01 23:32:32,100 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(DefaultQuartzScheduler5) [1c02a371] VM
'932db7c7-4121-4cbe-ad8d-09e4e99b3cdd'(ol65) moved from 'Paused' --> 'Up'
2017-02-01 23:32:32,259 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler5) [1c02a371] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: VM ol65 has recovered from paused back
to up.


In vdsm.log of the host where the VM is running I see this:

mailbox.SPMMonitor::DEBUG::2017-02-01 23:31:37,729::storage_mailbox:
:733::Storage.Misc.excCmd::(_chec
kForMail) /usr/bin/taskset --cpu-list 0-7 dd if=/rhev/data-center/588237b8-
0031-02f6-035d-013
6/mastersd/dom_md/inbox iflag=direct,fullblock count=1 bs=1024000 (cwd None)
mailbox.SPMMonitor::DEBUG::2017-02-01 23:31:37,764::storage_mailbox:
:733::Storage.Misc.excCmd::(_chec
kForMail) SUCCESS:  = '1+0 records in\n1+0 records out\n1024000 bytes
(1.0 MB) copied, 0.0061866
 s, 166 MB/s\n';  = 0
periodic/8::INFO::2017-02-01
23:31:39,699::vm::1028::virt.vm::(extendDrivesIfNeeded)
vmId=`932db7c7-4
121-4cbe-ad8d-09e4e99b3cdd`::Requesting extension for volume
66615920-619f-4f52-ad5a-3f062c054094 on
domain 922b5269-ab56-4c4d-838f-49d33427e2ab (apparent: 12884901888,
capacity: 96636764160, allocated:
 12355698688, physical: 12884901888)
periodic/8::DEBUG::2017-02-01
23:31:39,699::vm::1093::virt.vm::(__extendDriveVolume)
vmId=`932db7c7-4
121-4cbe-ad8d-09e4e99b3cdd`::Requesting an extension for the volume:
{'newSize': 

Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Victor Jose Acosta
So, that's the problem, engine is looking for updates for version 4, it 
does not matter if your node is version 3.6, i think this is a bug. 
Engine should be looking for node version updates instead of engine version.



On 01/02/17 17:33, users-requ...@ovirt.org wrote:

Re:  ovirt-engine failed to check for updates


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


Re: [ovirt-users] VM has been paused due to storage I/O problem

2017-02-01 Thread Michael Watters
I'm also seeing this error using a Dell MD3800i array.  The multipath
errors shown in our logs are different however.

Feb  1 15:11:58 ovirt-node-production2 kernel: dd: sending ioctl
80306d02 to a partition!
Feb  1 15:21:01 ovirt-node-production2 multipathd: dm-31: remove map
(uevent)
Feb  1 15:21:01 ovirt-node-production2 multipathd: dm-31: devmap not
registered, can't remove
Feb  1 15:21:01 ovirt-node-production2 multipathd: dm-31: remove map
(uevent)

The dd error seems to happen every time that SPM runs a test.


On 01/31/2017 09:23 AM, Nathanaël Blanchet wrote:
>
> exactly the same issue by there with FC EMC domain storage...
>
>
> Le 31/01/2017 à 15:20, Gianluca Cecchi a écrit :
>> Hello,
>> my test environment is composed by 2 old HP blades BL685c G1
>> (ovmsrv05 and ovmsrv06) and they are connected in a SAN with
>> FC-switches to an old IBM DS4700 storage array.
>> Apart from being old, they seem all ok from an hw point of view.
>> I have configured oVirt 4.0.6 and an FCP storage domain.
>> The hosts are plain CentOS 7.3 servers fully updated.
>> It is not an hosted engine environment: the manager is a vm outside
>> of the cluster.
>> I have configured power mgmt on both and it works good.
>>
>> I have at the moment  only one VM for test and it is doing quite nothing.
>>
>> Starting point: ovmsrv05 is in maintenance (since about 2 days) and
>> the VM is running on ovmsrv06.
>> I update qemu-kvm package on ovmsrv05 and then I restart it from web
>> admin gui:
>> Power Mgmt --> Restart
>>
>> Sequence of events in pane and the problem in subject:
>> Jan 31, 2017 10:29:43 AM Host ovmsrv05 power management was verified
>> successfully.
>> Jan 31, 2017 10:29:43 AM Status of host ovmsrv05 was set to Up.
>> Jan 31, 2017 10:29:38 AM Executing power management status on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>> Jan 31, 2017 10:29:29 AM Activation of host ovmsrv05 initiated by
>> admin@internal-authz.
>> Jan 31, 2017 10:28:05 AM VM ol65 has recovered from paused back to up.
>> Jan 31, 2017 10:27:55 AM VM ol65 has been paused due to storage I/O
>> problem.
>> Jan 31, 2017 10:27:55 AM VM ol65 has been paused.
>> Jan 31, 2017 10:25:52 AM Host ovmsrv05 was restarted by
>> admin@internal-authz.
>> Jan 31, 2017 10:25:52 AM Host ovmsrv05 was started by
>> admin@internal-authz.
>> Jan 31, 2017 10:25:52 AM Power management start of Host ovmsrv05
>> succeeded.
>> Jan 31, 2017 10:25:50 AM Executing power management status on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>> Jan 31, 2017 10:25:37 AM Executing power management start on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>> Jan 31, 2017 10:25:37 AM Power management start of Host ovmsrv05
>> initiated.
>> Jan 31, 2017 10:25:37 AM Auto fence for host ovmsrv05 was started.
>> Jan 31, 2017 10:25:37 AM All VMs' status on Non Responsive Host
>> ovmsrv05 were changed to 'Down' by admin@internal-authz
>> Jan 31, 2017 10:25:36 AM Host ovmsrv05 was stopped by
>> admin@internal-authz.
>> Jan 31, 2017 10:25:36 AM Power management stop of Host ovmsrv05
>> succeeded.
>> Jan 31, 2017 10:25:34 AM Executing power management status on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>> Jan 31, 2017 10:25:15 AM Executing power management stop on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>> Jan 31, 2017 10:25:15 AM Power management stop of Host ovmsrv05
>> initiated.
>> Jan 31, 2017 10:25:12 AM Executing power management status on Host
>> ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.
>>
>> Watching the timestamps, the culprit seems the reboot time of
>> ovmsrv05 that detects some LUNs in owned state and other ones in unowned
>> Full messages of both hosts here:
>> https://drive.google.com/file/d/0BwoPbcrMv8mvekZQT1pjc0NMRlU/view?usp=sharing
>> and
>> https://drive.google.com/file/d/0BwoPbcrMv8mvcjBCYVdFZWdXTms/view?usp=sharing
>>
>> At this time there are 4 LUNs globally seen by the two hosts but only
>> 1 of them is currently configured as the only storage domain in oVirt
>> cluster.
>>
>> [root@ovmsrv05 ~]# multipath -l | grep ^36
>> 3600a0b8000299aa8d08b55014119 dm-5 IBM ,1814  FAStT 
>> 3600a0b8000299902cd3c5501458f dm-3 IBM ,1814  FAStT 
>> 3600a0b8000299902ccf855011198 dm-2 IBM ,1814  FAStT 
>> 3600a0b8000299aa8d08955014098 dm-4 IBM ,1814  FAStT 
>>
>> the configured one:
>> [root@ovmsrv05 ~]# multipath -l 3600a0b8000299aa8d08b55014119
>> 3600a0b8000299aa8d08b55014119 dm-5 IBM ,1814  FAStT 
>> size=4.0T features='0' hwhandler='1 rdac' wp=rw
>> |-+- policy='service-time 0' prio=0 status=active
>> | |- 0:0:1:3 sdl 8:176 active undef running
>> | `- 2:0:1:3 sdp 8:240 active undef running
>> `-+- policy='service-time 0' prio=0 status=enabled
>>   |- 0:0:0:3 sdd 8:48  active undef running
>>   `- 2:0:0:3 sdi 8:128 active undef running

Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Michael Watters
The engine is 4.0, the host nodes are running 3.6 with VDSM 4.17.35.


On 02/01/2017 02:41 PM, Victor Jose Acosta wrote:
> Hello
>
> ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
> version 4 or 3.6?

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


Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Victor Jose Acosta

Hello

ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
version 4 or 3.6?


On 01/02/17 16:37, users-requ...@ovirt.org wrote:

Send Users mailing list submissions to
users@ovirt.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-requ...@ovirt.org

You can reach the person managing the list at
users-ow...@ovirt.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."


Today's Topics:

1. Re:  ovirt-engine failed to check for updates (Nicolas
   Ecarnot) (Victor Jose Acosta)


--

Message: 1
Date: Wed, 1 Feb 2017 16:37:35 -0300
From: Victor Jose Acosta 
To: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-engine failed to check for updates
(NicolasEcarnot)
Message-ID: <205a0dae-7d8a-1239-36b6-490a0e520...@gmail.com>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

Hello

ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
version 4 or 3.6?


On 01/02/17 16:22, users-requ...@ovirt.org wrote:

Send Users mailing list submissions to
users@ovirt.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-requ...@ovirt.org

You can reach the person managing the list at
users-ow...@ovirt.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."


Today's Topics:

 1. Re:  ovirt-engine failed to check for updates (Nicolas Ecarnot)
 2. Re:  NIC Teaming x Bonding (Fernando Frediani)
 3. Re:  NIC Teaming x Bonding (Yaniv Kaul)
 4. Re:  NIC Teaming x Bonding (Fernando Frediani)
 5. Re:  ovirt-engine failed to check for updates (Michael Watters)
 6. Re:  VM has been paused due to storage I/O problem
(Gianluca Cecchi)


--

Message: 1
Date: Wed, 1 Feb 2017 18:18:20 +0100
From: Nicolas Ecarnot 
To: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-engine failed to check for updates
Message-ID: 
Content-Type: text/plain; charset=windows-1252; format=flowed

Le 01/02/2017 ? 17:37, Michael Watters a ?crit :

I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts.  I am seeing errors when the engine attempts to
check for updates as follows.

Failed to check for available updates on host ovirt-node-production2
with message 'Command returned failure code 1 during SSH session
'root@ovirt-node-production2''.

I checked the logs on the host and it appears to be an issue with
yum.

2017-01-30 10:21:05 ERROR
otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum:
Cannot queue package ovirt-imageio-daemon: Package
ovirt-imageio-daemon cannot be found

2017-01-30 10:21:05 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Package installation': Package
ovirt-imageio-daemon cannot be found

Is there a way to resolve this?  I don't see any package named
ovirt-imageio-daemon in my repos when running a yum search.



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


Hello Michael,

Last time we spoke about this issue, it was the fault of ipV6 that had
to be turn down (I let you search the relevant posts).

-
cat /etc/sysctl.d/noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
-



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


Re: [ovirt-users] ovirt-engine failed to check for updates (Nicolas Ecarnot)

2017-02-01 Thread Victor Jose Acosta

Hello

ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
version 4 or 3.6?


On 01/02/17 16:22, users-requ...@ovirt.org wrote:

Send Users mailing list submissions to
users@ovirt.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-requ...@ovirt.org

You can reach the person managing the list at
users-ow...@ovirt.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."


Today's Topics:

1. Re:  ovirt-engine failed to check for updates (Nicolas Ecarnot)
2. Re:  NIC Teaming x Bonding (Fernando Frediani)
3. Re:  NIC Teaming x Bonding (Yaniv Kaul)
4. Re:  NIC Teaming x Bonding (Fernando Frediani)
5. Re:  ovirt-engine failed to check for updates (Michael Watters)
6. Re:  VM has been paused due to storage I/O problem
   (Gianluca Cecchi)


--

Message: 1
Date: Wed, 1 Feb 2017 18:18:20 +0100
From: Nicolas Ecarnot 
To: users@ovirt.org
Subject: Re: [ovirt-users] ovirt-engine failed to check for updates
Message-ID: 
Content-Type: text/plain; charset=windows-1252; format=flowed

Le 01/02/2017 ? 17:37, Michael Watters a ?crit :

I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts.  I am seeing errors when the engine attempts to
check for updates as follows.

Failed to check for available updates on host ovirt-node-production2
with message 'Command returned failure code 1 during SSH session
'root@ovirt-node-production2''.

I checked the logs on the host and it appears to be an issue with
yum.

2017-01-30 10:21:05 ERROR
otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum:
Cannot queue package ovirt-imageio-daemon: Package
ovirt-imageio-daemon cannot be found

2017-01-30 10:21:05 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Package installation': Package
ovirt-imageio-daemon cannot be found

Is there a way to resolve this?  I don't see any package named
ovirt-imageio-daemon in my repos when running a yum search.



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


Hello Michael,

Last time we spoke about this issue, it was the fault of ipV6 that had
to be turn down (I let you search the relevant posts).

-
cat /etc/sysctl.d/noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
-



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


[ovirt-users] a2fcc701-96ed-2bdc-dd98-630e814b7...@ecarnot.net

2017-02-01 Thread Victor Jose Acosta

Hello

ovirt-imageio-daemon is part of ovirt 4 repository, is your engine 
version 4 or 3.6?

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


Re: [ovirt-users] VM has been paused due to storage I/O problem

2017-02-01 Thread Gianluca Cecchi
On Wed, Feb 1, 2017 at 8:39 AM, Nir Soffer  wrote:

>
>
> Hi Gianluca,
>
> This should be a number, not a string, maybe multipath is having trouble
> parsing this and it ignores your value?
>

I don't think so. Also because reading dm multipath guide at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterp
rise_Linux/7/html/DM_Multipath/multipath_config_confirm.html
It seems that in RH EL 7.3 the "show config" command has this behaviour:

"
For example, the following command sequence displays the multipath
configuration, including the defaults, before exiting the console.

# multipathd -k
> > show config
> > CTRL-D
"

So the output has to include the default too. Anyway I changed it, see below

< BEGIN OF PARENTHESIS
In theory it should be the same on RH EL 6.8
(see https://access.redhat.com/documentation/en-US/Red_Hat_Enterp
rise_Linux/6/html/DM_Multipath/multipath_config_confirm.html )
but it is not so for me on a system that is on 6.5, with
device-mapper-multipath-0.4.9-93.el6.x86_64 and connected to Netapp

In /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf.defaults


#   vendor "NETAPP"
#   product "LUN.*"
#   path_grouping_policy group_by_prio
#   getuid_callout "/lib/udev/scsi_id --whitelisted
--device=/dev/%n"
#   path_selector "round-robin 0"
#   path_checker tur
#   features "3 queue_if_no_path pg_init_retries 50"
#   hardware_handler "0"
#   prio ontap
#   failback immediate
#   rr_weight uniform
#   rr_min_io 128
#   rr_min_io_rq 1
#   flush_on_last_del yes
#   fast_io_fail_tmo 5
#   dev_loss_tmo infinity
#   retain_attached_hw_handler yes
#   detect_prio yes
#   reload_readwrite yes
#   }



My customization in multipath.conf, based on Netapp guidelines and my
Netapp storage array setup:

devices {
   device {
   vendor "NETAPP"
   product "LUN.*"
   getuid_callout "/lib/udev/scsi_id -g -u -d /dev/%n"
   hardware_handler "1 alua"
   prio alua
}

If I run "multipathd show config" I see only 1 entry for NETAPP/LUN
vendor/product and it is a merge of default and my custom.

device {
vendor "NETAPP"
product "LUN.*"
path_grouping_policy group_by_prio
getuid_callout "/lib/udev/scsi_id -g -u -d /dev/%n"
path_selector "round-robin 0"
path_checker tur
features "3 queue_if_no_path pg_init_retries 50"
hardware_handler "1 alua"
prio alua
failback immediate
rr_weight uniform
rr_min_io 128
rr_min_io_rq 1
flush_on_last_del yes
fast_io_fail_tmo 5
dev_loss_tmo infinity
retain_attached_hw_handler yes
detect_prio yes
reload_readwrite yes
}

So this difference confused me when configuring multipath in CentOS 7.3. I
have to see when I'm going to update from 6.5 to 6.8 if this changes.

< END OF PARENTHESIS


> > }
> > }
> >
> > So I put exactly the default device config for my IBM/1814 device but
> > no_path_retry set to 12.
>
> Why 12?
>
> This will do 12 retries, 5 seconds each when no path is available. This
> will
> block lvm commands for 60 seconds when no path is available, blocking
> other stuff in vdsm. Vdsm is not designed to handle this.
>
> I recommend value of 4.
>

OK.



> But note that this will is not related to the fact that your devices are
> not
> initialize properly after boot.
>

In fact it could be also a ds4700 overall problem The LUNs are
configured as LNX CLUSTER type, that should be ok in theory, even if this
kind of storage was never so supported with Linux.
Initially one had to use proprietary IBM kernel modules/drivers.
I will see consistency and robustness through testing.
I have to do a POC and this is the hw I have and I should at least try to
have a working solution for it.


>
> > In CentOS 6.x when you do something like this, "show config" gives you
> the
> > modified entry only for your device section.
> > Instead in CentOS 7.3 it seems I get anyway the default one for IBM/1814
> and
> > also the customized one at the end of the output
>
> Maybe your device configuration does not match exactly the builtin config.
>

I think it is the different behaviour as outlined above. I think you can
confirm in another system where some customization has been done too...


>
>
> Maybe waiting a moment helps the storage/switches to clean up
> properly after a server is shut down?
>

I think so too. Eventually when possible, if errors repeat with the new
config, I'll manage to do stop/start instead of restart


>
> 

Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Michael Watters
I don't think IPv6 is the cause.  When the engine checks for updates
there is a yum error shown in the debug logs as follows.

2017-02-01 10:38:39 INFO otopi.plugins.ovirt_host_mgmt.packages.update 
update.info:98 Yum: Performing yum transaction rollback
2017-02-01 10:38:39 DEBUG otopi.context context._executeMethod:142 method 
exception
Traceback (most recent call last):
  File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/context.py", line 132, in 
_executeMethod
method['method']()
  File 
"/tmp/ovirt-J9X39w5eHd/otopi-plugins/ovirt-host-mgmt/packages/update.py", line 
110, in _packagesCheck
packages=self.environment[omgmt.PackagesEnv.PACKAGES],
  File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/miniyum.py", line 851, in install
**kwargs
  File "/tmp/ovirt-J9X39w5eHd/pythonlib/otopi/miniyum.py", line 500, in _queue
package=package,
RuntimeError: Package ovirt-imageio-daemon cannot be found

I've searched for a repo that provides this package but it looks like
this package is part of oVirt 4.0 instead of 3.6 which is what we are using.


On 02/01/2017 12:18 PM, Nicolas Ecarnot wrote:
> Hello Michael,
>
> Last time we spoke about this issue, it was the fault of ipV6 that had
> to be turn down (I let you search the relevant posts).
>
> -
> cat /etc/sysctl.d/noipv6.conf
> net.ipv6.conf.all.disable_ipv6 = 1
> net.ipv6.conf.default.disable_ipv6 = 1
> -
>

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


Re: [ovirt-users] NIC Teaming x Bonding

2017-02-01 Thread Fernando Frediani

Hi Yaniv. Not that much.

As I am starting a new environment I wanted to make usage of some new 
features present in Teaming. Guess suport will come soon.


Thanks for replying.

Fernando


On 01/02/2017 16:49, Yaniv Kaul wrote:



On Wed, Feb 1, 2017 at 8:06 PM, Fernando Frediani 
> 
wrote:


Well, I just found that Teaming doesn't seem to be recognized by
oVirt, only Bonding. Am I correct ?


Yes, that's correct. Does it make a difference in your deployment?
Y.



Fernando



On 30/01/2017 12:59, Fernando Frediani wrote:

Has anyone used NIC Teaming in production with oVirt Node ?
How are you finding it compared to Bonding ?

Has it helped in some way with the new features it brings.

For example: one feature VMware does it when you create a
given portgroup for a group of VMs you may set that portgroup
to use one physical NIC as Active and others as Backup, while
in another portgroup you may set otherwise. Then you have both
failover for both portgroups and better bandwidth usage.

Does Teaming do that kind of thing when used along with
oVirt/libvirt+KVM ?

Thanks

Fernando


___
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] NIC Teaming x Bonding

2017-02-01 Thread Yaniv Kaul
On Wed, Feb 1, 2017 at 8:06 PM, Fernando Frediani <
fernando.fredi...@upx.com.br> wrote:

> Well, I just found that Teaming doesn't seem to be recognized by oVirt,
> only Bonding. Am I correct ?


Yes, that's correct. Does it make a difference in your deployment?
Y.


>
> Fernando
>
>
>
> On 30/01/2017 12:59, Fernando Frediani wrote:
>
>> Has anyone used NIC Teaming in production with oVirt Node ? How are you
>> finding it compared to Bonding ?
>>
>> Has it helped in some way with the new features it brings.
>>
>> For example: one feature VMware does it when you create a given portgroup
>> for a group of VMs you may set that portgroup to use one physical NIC as
>> Active and others as Backup, while in another portgroup you may set
>> otherwise. Then you have both failover for both portgroups and better
>> bandwidth usage.
>>
>> Does Teaming do that kind of thing when used along with oVirt/libvirt+KVM
>> ?
>>
>> Thanks
>>
>> Fernando
>>
>>
> ___
> 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] NIC Teaming x Bonding

2017-02-01 Thread Fernando Frediani
Well, I just found that Teaming doesn't seem to be recognized by oVirt, 
only Bonding. Am I correct ?


Fernando


On 30/01/2017 12:59, Fernando Frediani wrote:
Has anyone used NIC Teaming in production with oVirt Node ? How are 
you finding it compared to Bonding ?


Has it helped in some way with the new features it brings.

For example: one feature VMware does it when you create a given 
portgroup for a group of VMs you may set that portgroup to use one 
physical NIC as Active and others as Backup, while in another 
portgroup you may set otherwise. Then you have both failover for both 
portgroups and better bandwidth usage.


Does Teaming do that kind of thing when used along with 
oVirt/libvirt+KVM ?


Thanks

Fernando



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


Re: [ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Nicolas Ecarnot

Le 01/02/2017 à 17:37, Michael Watters a écrit :

I have ovirt-engine 3.6 set up on a dedicated host which is managing
two ovirt hosts.  I am seeing errors when the engine attempts to
check for updates as follows.

Failed to check for available updates on host ovirt-node-production2
with message 'Command returned failure code 1 during SSH session
'root@ovirt-node-production2''.

I checked the logs on the host and it appears to be an issue with
yum.

2017-01-30 10:21:05 ERROR
otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum:
Cannot queue package ovirt-imageio-daemon: Package
ovirt-imageio-daemon cannot be found

2017-01-30 10:21:05 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Package installation': Package
ovirt-imageio-daemon cannot be found

Is there a way to resolve this?  I don't see any package named
ovirt-imageio-daemon in my repos when running a yum search.



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



Hello Michael,

Last time we spoke about this issue, it was the fault of ipV6 that had 
to be turn down (I let you search the relevant posts).


-
cat /etc/sysctl.d/noipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
-

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


[ovirt-users] ovirt-engine failed to check for updates

2017-02-01 Thread Michael Watters
I have ovirt-engine 3.6 set up on a dedicated host which is managing two
ovirt hosts.  I am seeing errors when the engine attempts to check for
updates as follows.

Failed to check for available updates on host ovirt-node-production2 with 
message 'Command returned failure code 1 during SSH session 
'root@ovirt-node-production2''.

I checked the logs on the host and it appears to be an issue with yum.

2017-01-30 10:21:05 ERROR otopi.plugins.ovirt_host_mgmt.packages.update 
update.error:102 Yum: Cannot queue package ovirt-imageio-daemon: Package 
ovirt-imageio-daemon cannot be found

2017-01-30 10:21:05 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Package installation': Package ovirt-imageio-daemon cannot be 
found

Is there a way to resolve this?  I don't see any package named
ovirt-imageio-daemon in my repos when running a yum search.



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


Re: [ovirt-users] Request for oVirt Ansible modules testing feedback

2017-02-01 Thread Jiří Sléžka

Hi,


On 02/01/2017 04:06 PM, Ondra Machacek wrote:

On Wed, Feb 1, 2017 at 3:27 PM, Jiří Sléžka  wrote:

Hi Ondra,


I am testing oVirt ansible modules and I am stucked in this simple scenario.
I would like to create a new vm with new bootable disk attached to it.

I wrote this simple role for it

http://pastebin.com/XwwyCH4b

when I run it I got


$ ansible-playbook site.yml

PLAY [create ovirt vm]
*

TASK [setup]
***
ok: [localhost]

TASK [create_vm : ovirt_auth]
**
ok: [localhost]

TASK [create_vm : ovirt_disks]
*
changed: [localhost]

TASK [create_vm : ovirt_vms]
***
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg":
"Fault reason is \"Operation Failed\". Fault detail is \"[Cannot run VM
without at least one bootable disk.\nAlternatives:\n- Create a disk for this
VM, and rerun the VM.\n- Change the boot sequence using the Edit VM command
(Boot Option Sub-Tab).\n- Use the 'Run Once' command to select a different
boot option and rerun the VM.]\". HTTP response code is 409."}
to retry, use: --limit
@/home/dron/#work/#cit/ovirt/ansible/ovirt/site.retry

PLAY RECAP
*
localhost  : ok=3changed=1unreachable=0 failed=1


In the manager I can see the is disk successfully created, vm too, disk is
attached to vm but not activated.

When I activate it manually, I am able to run this vm.

Any ideas how can I achieve this via ansible?


Yes, this is bug which was fixed[1], but wasn't backported to 2.2.

But since you are using role you are good.
Just download lastest vms module[2] and put it into the library directory,
which you must create in your role, for example:

 $ mkdir roles/vm-create-role/library
 $ cd roles/vm-create-role/library
 $ wget 
https://raw.githubusercontent.com/ansible/ansible-modules-extras/devel/cloud/ovirt/ovirt_vms.py


yes, it is the way.

I have downloaded devel version of module, put it into library 
directory. It was correctly used by ansible but it failed with an error


"msg": "'NoneType' object has no attribute 'append'"

never mind, I will wait till Ansible 2.3 and then I'll try it once more.

Cheers,

Jiri



Then it should work OK, at least I think the modules in library has
higher priority.
If not then renaming that module should work, for example:

 $ mv ovirt_vms.py ovirt_vms_dev.py

and then use it as:

tasks:
  ...
  - name: Create vm
ovirt_vms_dev:
  name: vm0
  ...

Btw. in ~month there should be Ansible 2.3 release, with has much more features,
and also will have this issue fixed.

[1] https://github.com/ansible/ansible-modules-extras/pull/3322
[2] 
https://raw.githubusercontent.com/ansible/ansible-modules-extras/devel/cloud/ovirt/ovirt_vms.py




Thanks in advance,

Jiri Slezka





On 12/02/2016 02:12 PM, Ondra Machacek wrote:


Hello all,

I would like to kindly ask everyone who is Ansible or oVirt user for
testing of the new Ansible oVirt modules. For everyone who is familiar
with the Ansible and oVirt, this[1] describes the steps you need to do,
to setup oVirt modules library and start using those modules (Most of
those modules will be available in Ansible 2.3, some of them are already
in 2.2).

If you have any issue setting this up, please contact me, I will do the
best to help you.

If you have an issue, which you think is a bug, please open an issue
here[2]. Please note that Ansible is merging it's repositories, so since
next week it will actually be stored here[3]. If you are missing
anything please open an issue as well, or just contact me, and I will
do fix it. You are also very welcome to sent PR with fixes.

For those who don't have testing environment which can test against,
I've created an Vagrant project which will deploy you the oVirt instance
using Ansible playbooks. You can find how to use it here[4].

The repository also contains few examples[5], so you don't have to
copy-paste them from the source.

Thanks all for reading this and any feedback,
Ondra

[1] https://github.com/machacekondra/ovirt-tests/releases/tag/0.1
[2] https://github.com/ansible/ansible-modules-extras/issues
[3] https://github.com/ansible/ansible
[4] https://github.com/machacekondra/ovirt-tests
[5] https://github.com/machacekondra/ovirt-tests/tree/master/examples
___
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






smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org

Re: [ovirt-users] Request for oVirt Ansible modules testing feedback

2017-02-01 Thread Ondra Machacek
On Wed, Feb 1, 2017 at 3:27 PM, Jiří Sléžka  wrote:
> Hi Ondra,
>
>
> I am testing oVirt ansible modules and I am stucked in this simple scenario.
> I would like to create a new vm with new bootable disk attached to it.
>
> I wrote this simple role for it
>
> http://pastebin.com/XwwyCH4b
>
> when I run it I got
>
>
> $ ansible-playbook site.yml
>
> PLAY [create ovirt vm]
> *
>
> TASK [setup]
> ***
> ok: [localhost]
>
> TASK [create_vm : ovirt_auth]
> **
> ok: [localhost]
>
> TASK [create_vm : ovirt_disks]
> *
> changed: [localhost]
>
> TASK [create_vm : ovirt_vms]
> ***
> fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg":
> "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot run VM
> without at least one bootable disk.\nAlternatives:\n- Create a disk for this
> VM, and rerun the VM.\n- Change the boot sequence using the Edit VM command
> (Boot Option Sub-Tab).\n- Use the 'Run Once' command to select a different
> boot option and rerun the VM.]\". HTTP response code is 409."}
> to retry, use: --limit
> @/home/dron/#work/#cit/ovirt/ansible/ovirt/site.retry
>
> PLAY RECAP
> *
> localhost  : ok=3changed=1unreachable=0 failed=1
>
>
> In the manager I can see the is disk successfully created, vm too, disk is
> attached to vm but not activated.
>
> When I activate it manually, I am able to run this vm.
>
> Any ideas how can I achieve this via ansible?

Yes, this is bug which was fixed[1], but wasn't backported to 2.2.

But since you are using role you are good.
Just download lastest vms module[2] and put it into the library directory,
which you must create in your role, for example:

 $ mkdir roles/vm-create-role/library
 $ cd roles/vm-create-role/library
 $ wget 
https://raw.githubusercontent.com/ansible/ansible-modules-extras/devel/cloud/ovirt/ovirt_vms.py

Then it should work OK, at least I think the modules in library has
higher priority.
If not then renaming that module should work, for example:

 $ mv ovirt_vms.py ovirt_vms_dev.py

and then use it as:

tasks:
  ...
  - name: Create vm
ovirt_vms_dev:
  name: vm0
  ...

Btw. in ~month there should be Ansible 2.3 release, with has much more features,
and also will have this issue fixed.

[1] https://github.com/ansible/ansible-modules-extras/pull/3322
[2] 
https://raw.githubusercontent.com/ansible/ansible-modules-extras/devel/cloud/ovirt/ovirt_vms.py

>
>
> Thanks in advance,
>
> Jiri Slezka
>
>
>
>
>
> On 12/02/2016 02:12 PM, Ondra Machacek wrote:
>>
>> Hello all,
>>
>> I would like to kindly ask everyone who is Ansible or oVirt user for
>> testing of the new Ansible oVirt modules. For everyone who is familiar
>> with the Ansible and oVirt, this[1] describes the steps you need to do,
>> to setup oVirt modules library and start using those modules (Most of
>> those modules will be available in Ansible 2.3, some of them are already
>> in 2.2).
>>
>> If you have any issue setting this up, please contact me, I will do the
>> best to help you.
>>
>> If you have an issue, which you think is a bug, please open an issue
>> here[2]. Please note that Ansible is merging it's repositories, so since
>> next week it will actually be stored here[3]. If you are missing
>> anything please open an issue as well, or just contact me, and I will
>> do fix it. You are also very welcome to sent PR with fixes.
>>
>> For those who don't have testing environment which can test against,
>> I've created an Vagrant project which will deploy you the oVirt instance
>> using Ansible playbooks. You can find how to use it here[4].
>>
>> The repository also contains few examples[5], so you don't have to
>> copy-paste them from the source.
>>
>> Thanks all for reading this and any feedback,
>> Ondra
>>
>> [1] https://github.com/machacekondra/ovirt-tests/releases/tag/0.1
>> [2] https://github.com/ansible/ansible-modules-extras/issues
>> [3] https://github.com/ansible/ansible
>> [4] https://github.com/machacekondra/ovirt-tests
>> [5] https://github.com/machacekondra/ovirt-tests/tree/master/examples
>> ___
>> 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Nicolas Ecarnot

Le 01/02/2017 à 15:31, Yura Poltoratskiy a écrit :

Here you are:

iSCSI multipathing


network setup of a host




01.02.2017 15:31, Nicolas Ecarnot пишет:

Hello,

Before replying further, may I ask you, Yura, to post a screenshot of
your iSCSI multipathing setup in the web GUI?

And also the same for the network setup of a host ?

Thank you.





Thank you Yura.

To Yaniv and Pavel, yes, this leads to this oVirt feature of iSCSI 
multipathing, indeed.


I would be curious to see (on Yura's hosts for instance) the translation 
of the oVirt iSCSI multipathing in CLI commands (multipath -ll, iscsiadm 
-m session -P3, dmsetup table, ...)


Yura's setup seems to be perfectly fitted to oVirt (2 NICs, 2 VLANs, 2 
targets in different VLANs, iSCSI multipathing), but I'm trying to see 
how I could make this work with our Equallogic presenting one and only 
one virtual ip (thus one target VLAN)...


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


Re: [ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Yura Poltoratskiy

Here you are:

iSCSI multipathing 



network setup of a host 





01.02.2017 15:31, Nicolas Ecarnot пишет:

Hello,

Before replying further, may I ask you, Yura, to post a screenshot of 
your iSCSI multipathing setup in the web GUI?


And also the same for the network setup of a host ?

Thank you.



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


Re: [ovirt-users] Request for oVirt Ansible modules testing feedback

2017-02-01 Thread Jiří Sléžka

Hi Ondra,


I am testing oVirt ansible modules and I am stucked in this simple 
scenario. I would like to create a new vm with new bootable disk 
attached to it.


I wrote this simple role for it

http://pastebin.com/XwwyCH4b

when I run it I got


$ ansible-playbook site.yml

PLAY [create ovirt vm] 
*


TASK [setup] 
***

ok: [localhost]

TASK [create_vm : ovirt_auth] 
**

ok: [localhost]

TASK [create_vm : ovirt_disks] 
*

changed: [localhost]

TASK [create_vm : ovirt_vms] 
***
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": 
"Fault reason is \"Operation Failed\". Fault detail is \"[Cannot run VM 
without at least one bootable disk.\nAlternatives:\n- Create a disk for 
this VM, and rerun the VM.\n- Change the boot sequence using the Edit VM 
command (Boot Option Sub-Tab).\n- Use the 'Run Once' command to select a 
different boot option and rerun the VM.]\". HTTP response code is 409."}
	to retry, use: --limit 
@/home/dron/#work/#cit/ovirt/ansible/ovirt/site.retry


PLAY RECAP 
*
localhost  : ok=3changed=1unreachable=0 
failed=1



In the manager I can see the is disk successfully created, vm too, disk 
is attached to vm but not activated.


When I activate it manually, I am able to run this vm.

Any ideas how can I achieve this via ansible?


Thanks in advance,

Jiri Slezka




On 12/02/2016 02:12 PM, Ondra Machacek wrote:

Hello all,

I would like to kindly ask everyone who is Ansible or oVirt user for
testing of the new Ansible oVirt modules. For everyone who is familiar
with the Ansible and oVirt, this[1] describes the steps you need to do,
to setup oVirt modules library and start using those modules (Most of
those modules will be available in Ansible 2.3, some of them are already
in 2.2).

If you have any issue setting this up, please contact me, I will do the
best to help you.

If you have an issue, which you think is a bug, please open an issue
here[2]. Please note that Ansible is merging it's repositories, so since
next week it will actually be stored here[3]. If you are missing
anything please open an issue as well, or just contact me, and I will
do fix it. You are also very welcome to sent PR with fixes.

For those who don't have testing environment which can test against,
I've created an Vagrant project which will deploy you the oVirt instance
using Ansible playbooks. You can find how to use it here[4].

The repository also contains few examples[5], so you don't have to
copy-paste them from the source.

Thanks all for reading this and any feedback,
Ondra

[1] https://github.com/machacekondra/ovirt-tests/releases/tag/0.1
[2] https://github.com/ansible/ansible-modules-extras/issues
[3] https://github.com/ansible/ansible
[4] https://github.com/machacekondra/ovirt-tests
[5] https://github.com/machacekondra/ovirt-tests/tree/master/examples
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Nicolas Ecarnot

Hello,

Before replying further, may I ask you, Yura, to post a screenshot of 
your iSCSI multipathing setup in the web GUI?


And also the same for the network setup of a host ?

Thank you.

--
Nicolas ECARNOT

Le 01/02/2017 à 13:14, Yura Poltoratskiy a écrit :

Hi,

As for me personally I have such a config: compute nodes with 4x1G nics
and storages with 2x1G nics and 2 switches (not stackable). All servers
runs on CentOS 7.X (7.3 at this monent).

On compute nodes I have bonding with two nic1 and nic2 (attached to
different switches) for mgmt and VM's network, and the other two nics
nic3 and nic4 without bonding (and also attached to different switches).
On storage nodes I have no bonding and nics nic1 and nic2 connected to
different switches.

I have two networks for iSCSI: 10.0.2.0/24 and 10.0.3.0/24, nic1 of
storage and nic3 of computes connected to one network; nic2 of storage
and nic4 of computes - to another one.

On webUI I've created network iSCSI1 and iSCSI2 for nic3 and nic4, also
created multipath. To have active/active links with double bw throughput
I've added 'path_grouping_policy "multibus"' in defaults section of
/etc/multipath.conf.

After all of that, I have 200+MB/sec throughput to the storage (like
raid0 with 2 sata hdd) and I can lose one nic/link/swith without
stopping vms.

[root@compute02 ~]# multipath -ll
360014052f28c9a60 dm-6 LIO-ORG ,ClusterLunHDD
size=902G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 6:0:0:0 sdc 8:32  active ready running
  `- 8:0:0:0 sdf 8:80  active ready running
36001405551a9610d09b4ff9aa836b906 dm-40 LIO-ORG ,SSD_DOMAIN
size=915G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 7:0:0:0 sde 8:64  active ready running
  `- 9:0:0:0 sdh 8:112 active ready running
360014055eb8d30a91044649bda9ee620 dm-5 LIO-ORG ,ClusterLunSSD
size=135G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 6:0:0:1 sdd 8:48  active ready running
  `- 8:0:0:1 sdg 8:96  active ready running

[root@compute02 ~]# iscsiadm -m session
tcp: [1] 10.0.3.200:3260,1 iqn.2015-09.lab.lnx-san:storage (non-flash)
tcp: [2] 10.0.3.203:3260,1 iqn.2016-10.local.ntu:storage3 (non-flash)
tcp: [3] 10.0.3.200:3260,1 iqn.2015-09.lab.lnx-san:storage (non-flash)
tcp: [4] 10.0.3.203:3260,1 iqn.2016-10.local.ntu:storage3 (non-flash)

[root@compute02 ~]# ip route show | head -4
default via 10.0.1.1 dev ovirtmgmt
10.0.1.0/24 dev ovirtmgmt  proto kernel  scope link  src 10.0.1.102
10.0.2.0/24 dev enp5s0.2  proto kernel  scope link  src 10.0.2.102
10.0.3.0/24 dev enp2s0.3  proto kernel  scope link  src 10.0.3.102

[root@compute02 ~]# brctl show ovirtmgmt
bridge name bridge id   STP enabled interfaces
ovirtmgmt   8000.000475b4f262   no bond0.1001

[root@compute02 ~]# cat /proc/net/bonding/bond0 | grep "Bonding\|Slave
Interface"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Slave Interface: enp4s6
Slave Interface: enp6s0


01.02.2017 12:50, Nicolas Ecarnot пишет:

Hello,

I'm starting over on this subject because I wanted to clarify what was
the oVirt way to manage multipathing.

(Here I will talk only about the data/iSCSI/SAN/LUN/you name it
networks.)
According to what I see in the host network setup, one can assign
*ONE* data network to an interface or to a group of interfaces.

That implies that if my host has two data-dedicated interfaces, I can
- either group them using bonding (and oVirt is handy for that in the
host network setup), then assign the data virtual network to this bond
- either assign each nic a different ip in each a different VLAN, then
use two different data networks, and assign them each a different data
network. I never played this game and don't know where it's going to.

At first, may the oVirt storage experts comment on the above to check
it's ok.

Then, as many users here, our hardware is this :
- Hosts : Dell poweredge, mostly blades (M610,620,630), or rack servers
- SANs : Equallogic PS4xxx and PS6xxx

Equallogic's recommendation is that bonding is evil in iSCSI access.
To them, multipath is the only true way.
After reading tons of docs and using Dell support, everything is
telling me to use at least two different NICs with different ip, not
bonded - using the same network is bad but ok.

How can oVirt handle that ?






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


[ovirt-users] [ANN] oVirt 4.1.0 Release is now available

2017-02-01 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.1.0 Release, as of February 1st, 2017

This major release update is the first of the 4.1 release series.
4.1.0 brings more than 260 enhancements and 790 bugfixes, including 340
high or urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.

This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)
* oVirt Node 4.1

Notes:
- oVirt Live iso is already available[2]
- oVirt Node NG iso is already available[2]
- Hosted Engine appliance is already available.
- oVirt Windows Guest Tools iso is already available[2]
- Mirrors[3] might need up to one day to synchronize.


Additional Resources:
* Read more about the oVirt 4.1.0 release highlights:
http://www.ovirt.org/release/4.1.0/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.1.0/
[2] http://resources.ovirt.org/pub/ovirt-4.1/iso/
[3] http://www.ovirt.org/Repository_mirrors#Current_mirrors


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Yura Poltoratskiy

Hi,

As for me personally I have such a config: compute nodes with 4x1G nics 
and storages with 2x1G nics and 2 switches (not stackable). All servers 
runs on CentOS 7.X (7.3 at this monent).


On compute nodes I have bonding with two nic1 and nic2 (attached to 
different switches) for mgmt and VM's network, and the other two nics 
nic3 and nic4 without bonding (and also attached to different switches). 
On storage nodes I have no bonding and nics nic1 and nic2 connected to 
different switches.


I have two networks for iSCSI: 10.0.2.0/24 and 10.0.3.0/24, nic1 of 
storage and nic3 of computes connected to one network; nic2 of storage 
and nic4 of computes - to another one.


On webUI I've created network iSCSI1 and iSCSI2 for nic3 and nic4, also 
created multipath. To have active/active links with double bw throughput 
I've added 'path_grouping_policy "multibus"' in defaults section of 
/etc/multipath.conf.


After all of that, I have 200+MB/sec throughput to the storage (like 
raid0 with 2 sata hdd) and I can lose one nic/link/swith without 
stopping vms.


[root@compute02 ~]# multipath -ll
360014052f28c9a60 dm-6 LIO-ORG ,ClusterLunHDD
size=902G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 6:0:0:0 sdc 8:32  active ready running
  `- 8:0:0:0 sdf 8:80  active ready running
36001405551a9610d09b4ff9aa836b906 dm-40 LIO-ORG ,SSD_DOMAIN
size=915G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 7:0:0:0 sde 8:64  active ready running
  `- 9:0:0:0 sdh 8:112 active ready running
360014055eb8d30a91044649bda9ee620 dm-5 LIO-ORG ,ClusterLunSSD
size=135G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 6:0:0:1 sdd 8:48  active ready running
  `- 8:0:0:1 sdg 8:96  active ready running

[root@compute02 ~]# iscsiadm -m session
tcp: [1] 10.0.3.200:3260,1 iqn.2015-09.lab.lnx-san:storage (non-flash)
tcp: [2] 10.0.3.203:3260,1 iqn.2016-10.local.ntu:storage3 (non-flash)
tcp: [3] 10.0.3.200:3260,1 iqn.2015-09.lab.lnx-san:storage (non-flash)
tcp: [4] 10.0.3.203:3260,1 iqn.2016-10.local.ntu:storage3 (non-flash)

[root@compute02 ~]# ip route show | head -4
default via 10.0.1.1 dev ovirtmgmt
10.0.1.0/24 dev ovirtmgmt  proto kernel  scope link  src 10.0.1.102
10.0.2.0/24 dev enp5s0.2  proto kernel  scope link  src 10.0.2.102
10.0.3.0/24 dev enp2s0.3  proto kernel  scope link  src 10.0.3.102

[root@compute02 ~]# brctl show ovirtmgmt
bridge name bridge id   STP enabled interfaces
ovirtmgmt   8000.000475b4f262   no bond0.1001

[root@compute02 ~]# cat /proc/net/bonding/bond0 | grep "Bonding\|Slave 
Interface"

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Slave Interface: enp4s6
Slave Interface: enp6s0


01.02.2017 12:50, Nicolas Ecarnot пишет:

Hello,

I'm starting over on this subject because I wanted to clarify what was 
the oVirt way to manage multipathing.


(Here I will talk only about the data/iSCSI/SAN/LUN/you name it 
networks.)
According to what I see in the host network setup, one can assign 
*ONE* data network to an interface or to a group of interfaces.


That implies that if my host has two data-dedicated interfaces, I can
- either group them using bonding (and oVirt is handy for that in the 
host network setup), then assign the data virtual network to this bond
- either assign each nic a different ip in each a different VLAN, then 
use two different data networks, and assign them each a different data 
network. I never played this game and don't know where it's going to.


At first, may the oVirt storage experts comment on the above to check 
it's ok.


Then, as many users here, our hardware is this :
- Hosts : Dell poweredge, mostly blades (M610,620,630), or rack servers
- SANs : Equallogic PS4xxx and PS6xxx

Equallogic's recommendation is that bonding is evil in iSCSI access.
To them, multipath is the only true way.
After reading tons of docs and using Dell support, everything is 
telling me to use at least two different NICs with different ip, not 
bonded - using the same network is bad but ok.


How can oVirt handle that ?



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


Re: [ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Pavel Gashev
Nicolas,

Take a look at
http://www.ovirt.org/documentation/admin-guide/chap-Storage/#configuring-iscsi-multipathing

The recommended way is to use different VLANs. Equallogic has to be connected 
to the different VLANs as well.


On Wed, 2017-02-01 at 11:50 +0100, Nicolas Ecarnot wrote:

Hello,

I'm starting over on this subject because I wanted to clarify what was
the oVirt way to manage multipathing.

(Here I will talk only about the data/iSCSI/SAN/LUN/you name it networks.)
According to what I see in the host network setup, one can assign *ONE*
data network to an interface or to a group of interfaces.

That implies that if my host has two data-dedicated interfaces, I can
- either group them using bonding (and oVirt is handy for that in the
host network setup), then assign the data virtual network to this bond
- either assign each nic a different ip in each a different VLAN, then
use two different data networks, and assign them each a different data
network. I never played this game and don't know where it's going to.

At first, may the oVirt storage experts comment on the above to check
it's ok.

Then, as many users here, our hardware is this :
- Hosts : Dell poweredge, mostly blades (M610,620,630), or rack servers
- SANs : Equallogic PS4xxx and PS6xxx

Equallogic's recommendation is that bonding is evil in iSCSI access.
To them, multipath is the only true way.
After reading tons of docs and using Dell support, everything is telling
me to use at least two different NICs with different ip, not bonded -
using the same network is bad but ok.

How can oVirt handle that ?


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


[ovirt-users] Multipath handling in oVirt

2017-02-01 Thread Nicolas Ecarnot

Hello,

I'm starting over on this subject because I wanted to clarify what was 
the oVirt way to manage multipathing.


(Here I will talk only about the data/iSCSI/SAN/LUN/you name it networks.)
According to what I see in the host network setup, one can assign *ONE* 
data network to an interface or to a group of interfaces.


That implies that if my host has two data-dedicated interfaces, I can
- either group them using bonding (and oVirt is handy for that in the 
host network setup), then assign the data virtual network to this bond
- either assign each nic a different ip in each a different VLAN, then 
use two different data networks, and assign them each a different data 
network. I never played this game and don't know where it's going to.


At first, may the oVirt storage experts comment on the above to check 
it's ok.


Then, as many users here, our hardware is this :
- Hosts : Dell poweredge, mostly blades (M610,620,630), or rack servers
- SANs : Equallogic PS4xxx and PS6xxx

Equallogic's recommendation is that bonding is evil in iSCSI access.
To them, multipath is the only true way.
After reading tons of docs and using Dell support, everything is telling 
me to use at least two different NICs with different ip, not bonded - 
using the same network is bad but ok.


How can oVirt handle that ?

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


Re: [ovirt-users] "Setup Host Networks" fails (was: Ovirt 4 failing to setup CentOS 7.2 host (everything default))

2017-02-01 Thread Edward Haas
The server seems to have a special network configuration that limits its
communication to the Gateway through SCOPE definition.
IPADDR=176.9.146.137
NETMASK=255.255.255.255
SCOPE="peer 176.9.146.129"

oVirt host does not support such a setup.
VDSM acquires the iface and tries to configure it based on the existing
values, ignoring the SCOPE.
It ends up with a full mask set and lost of connectivity.

Please set your server with a 'regular' ip/mask/gateway settings.
If you want to keep the limitations of SCOPE, you can set some firewall
rules instead.

Thanks,
Edy.



On Tue, Jan 31, 2017 at 1:19 PM, Eidmantas Ivanauskas <
eidmantasivanaus...@gmail.com> wrote:

> Thank you for tidying up the thread. Never used these mailing lists (at
> all on any platform), so I am trying to minimize damage ;).
>
> Here are some additional logs from the host. (upon using Setup Host
> Networks).
>
> ### messages
> .
> Jan 31 10:44:28 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is
> Down
> Jan 31 10:44:29 CentOS-73-64-minimal systemd: Started /usr/sbin/ifup
> enp4s0.
> Jan 31 10:44:29 CentOS-73-64-minimal systemd: Starting /usr/sbin/ifup
> enp4s0.
> Jan 31 10:44:29 CentOS-73-64-minimal kernel: IPv6: ADDRCONF(NETDEV_UP):
> enp4s0: link is not ready
> Jan 31 10:44:29 CentOS-73-64-minimal kernel: 8021q: adding VLAN 0 to HW
> filter on device enp4s0
> Jan 31 10:44:33 CentOS-73-64-minimal daemonAdapter: libvirt: Network
> Driver error : Network not found: no network with matching name
> 'vdsm-ovirtmgmt'
> Jan 31 10:44:33 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is Up
> 1000 Mbps Full Duplex, Flow Control: Rx/Tx
> Jan 31 10:44:33 CentOS-73-64-minimal kernel: IPv6:
> ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
> Jan 31 10:46:34 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is
> Down
> Jan 31 10:46:34 CentOS-73-64-minimal systemd: Started /usr/sbin/ifup
> enp4s0.
> Jan 31 10:46:34 CentOS-73-64-minimal systemd: Starting /usr/sbin/ifup
> enp4s0.
> Jan 31 10:46:34 CentOS-73-64-minimal kernel: IPv6: ADDRCONF(NETDEV_UP):
> enp4s0: link is not ready
> Jan 31 10:46:34 CentOS-73-64-minimal kernel: 8021q: adding VLAN 0 to HW
> filter on device enp4s0
> Jan 31 10:46:38 CentOS-73-64-minimal journal: vdsm vds ERROR connectivity
> check failed#012Traceback (most recent call last):#012  File
> "/usr/share/vdsm/API.py", line 1473, in setupNetworks#012
> supervdsm.getProxy().setupNetworks(networks, bondings, options)#012  File
> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
> __call__#012return callMethod()#012  File 
> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py",
> line 51, in #012**kwargs)#012  File "", line 2, in
> setupNetworks#012  File "/usr/lib64/python2.7/multiprocessing/managers.py",
> line 773, in _callmethod#012raise convert_to_error(kind,
> result)#012ConfigNetworkError: (10, 'connectivity check failed')
> Jan 31 10:46:39 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is Up
> 1000 Mbps Full Duplex, Flow Control: Rx/Tx
> Jan 31 10:46:39 CentOS-73-64-minimal kernel: IPv6:
> ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
>
>
>
>
>
>
>
>  journalctl
>
> Jan 31 11:05:07 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is
> Down
> Jan 31 11:05:07 CentOS-73-64-minimal systemd[1]: Started /usr/sbin/ifup
> enp4s0.
> Jan 31 11:05:07 CentOS-73-64-minimal systemd[1]: Starting /usr/sbin/ifup
> enp4s0.
> Jan 31 11:05:07 CentOS-73-64-minimal kernel: IPv6: ADDRCONF(NETDEV_UP):
> enp4s0: link is not ready
> Jan 31 11:05:07 CentOS-73-64-minimal kernel: 8021q: adding VLAN 0 to HW
> filter on device enp4s0
> Jan 31 11:05:11 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is Up
> 1000 Mbps Full Duplex, Flow Control: Rx/Tx
> Jan 31 11:05:11 CentOS-73-64-minimal kernel: IPv6:
> ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
> Jan 31 11:05:11 CentOS-73-64-minimal daemonAdapter[11064]: libvirt:
> Network Driver error : Network not found: no network with matching name
> 'vdsm-ovirtmgmt'
> Jan 31 11:07:12 CentOS-73-64-minimal kernel: e1000e: enp4s0 NIC Link is
> Down
> Jan 31 11:07:12 CentOS-73-64-minimal systemd[1]: Started /usr/sbin/ifup
> enp4s0.
> Jan 31 11:07:12 CentOS-73-64-minimal systemd[1]: Starting /usr/sbin/ifup
> enp4s0.
> Jan 31 11:07:12 CentOS-73-64-minimal kernel: IPv6: ADDRCONF(NETDEV_UP):
> enp4s0: link is not ready
> Jan 31 11:07:12 CentOS-73-64-minimal kernel: 8021q: adding VLAN 0 to HW
> filter on device enp4s0
> Jan 31 11:07:16 CentOS-73-64-minimal vdsm[11340]: vdsm vds ERROR
> connectivity check failed
>   Traceback (most recent
> call last):
> File
> "/usr/share/vdsm/API.py", line 1473, in setupNetworks
>   
> supervdsm.getProxy().setupNetworks(networks,
> bondings, options)
> File
>