[ovirt-users] Re: Ovirt 4.3 RC missing glusterfs-gnfs

2019-02-20 Thread Sandro Bonazzola
Il giorno mer 20 feb 2019 alle ore 21:02 Strahil Nikolov <
hunter86...@yahoo.com> ha scritto:

> Hi Sahina, Sandro,
>
> can you guide me through the bugzilla.redhat.com in order to open a bug
> for the missing package. ovirt-4.3-centos-gluster5 still lacks package
> for the 'glusterfs-gnfs' (which is a dependency for vdsm-gluster):
>


The issue is being tracked in
https://bugzilla.redhat.com/show_bug.cgi?id=1672711
it's still missing a fix on gluster side for CentOS Storage SIG.
Niels, Yaniv, we are escalating this, can you please help getting this
fixed?




>
> [root@ovirt2 ~]# yum --disablerepo=*
> --enablerepo=ovirt-4.3-centos-gluster5 list available --show-duplicates |
> grep gluster-gnfs
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Cannot upload enabled repos report, is this client registered?
>
>
> This leads to the following (output truncated):
> --> Finished Dependency Resolution
> Error: Package: glusterfs-gnfs-3.12.15-1.el7.x86_64
> (@ovirt-4.2-centos-gluster312)
>Requires: glusterfs(x86-64) = 3.12.15-1.el7
>Removing: glusterfs-3.12.15-1.el7.x86_64
> (@ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.15-1.el7
>Updated By: glusterfs-5.3-1.el7.x86_64
> (ovirt-4.3-centos-gluster5)
>glusterfs(x86-64) = 5.3-1.el7
>Available: glusterfs-3.12.0-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.0-1.el7
>
>Available: glusterfs-3.12.1-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.1-1.el7
>Available: glusterfs-3.12.1-2.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.1-2.el7
>Available: glusterfs-3.12.2-18.el7.x86_64 (base)
>glusterfs(x86-64) = 3.12.2-18.el7
>Available: glusterfs-3.12.3-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.3-1.el7
>Available: glusterfs-3.12.4-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.4-1.el7
>Available: glusterfs-3.12.5-2.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.5-2.el7
>Available: glusterfs-3.12.6-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.6-1.el7
>Available: glusterfs-3.12.8-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.8-1.el7
>Available: glusterfs-3.12.9-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.9-1.el7
>Available: glusterfs-3.12.11-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.11-1.el7
>Available: glusterfs-3.12.13-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.13-1.el7
>Available: glusterfs-3.12.14-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs(x86-64) = 3.12.14-1.el7
>Available: glusterfs-5.0-1.el7.x86_64
> (ovirt-4.3-centos-gluster5)
>glusterfs(x86-64) = 5.0-1.el7
>Available: glusterfs-5.1-1.el7.x86_64
> (ovirt-4.3-centos-gluster5)
>glusterfs(x86-64) = 5.1-1.el7
>Available: glusterfs-5.2-1.el7.x86_64
> (ovirt-4.3-centos-gluster5)
>glusterfs(x86-64) = 5.2-1.el7
> Error: Package: glusterfs-gnfs-3.12.15-1.el7.x86_64
> (@ovirt-4.2-centos-gluster312)
>Requires: glusterfs-client-xlators(x86-64) = 3.12.15-1.el7
>Removing: glusterfs-client-xlators-3.12.15-1.el7.x86_64
> (@ovirt-4.2-centos-gluster312)
>glusterfs-client-xlators(x86-64) = 3.12.15-1.el7
>
>Updated By: glusterfs-client-xlators-5.3-1.el7.x86_64
> (ovirt-4.3-centos-gluster5)
>glusterfs-client-xlators(x86-64) = 5.3-1.el7
>Available: glusterfs-client-xlators-3.12.0-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs-client-xlators(x86-64) = 3.12.0-1.el7
>Available: glusterfs-client-xlators-3.12.1-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs-client-xlators(x86-64) = 3.12.1-1.el7
>Available: glusterfs-client-xlators-3.12.1-2.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs-client-xlators(x86-64) = 3.12.1-2.el7
>Available: glusterfs-client-xlators-3.12.2-18.el7.x86_64 (base)
>glusterfs-client-xlators(x86-64) = 3.12.2-18.el7
>Available: glusterfs-client-xlators-3.12.3-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>glusterfs-client-xlators(x86-64) = 3.12.3-1.el7
>Available: glusterfs-client-xlators-3.12.4-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>

[ovirt-users] Re: When I want to use the VNC tool to connect to the virtual machine, I am prompted to enter the virtual machine VNC password

2019-02-20 Thread Yedidyah Bar David
On Thu, Feb 21, 2019 at 8:04 AM  wrote:
>
> Hi,
> When I want to use the VNC tool to connect to the virtual machine, I will be 
> prompted for the virtual machine VNC password. The virtual machine XML file 
> is shown below. Where can I query passwd in the VNC configuration?
>passwdValidTo='1970-01-01T00:00:01'>
>   
> 
> Do you need to change the listen parameter in the libvirtd.conf configuration 
> file.

Is this about an oVirt-managed VM, or a plain libvirt one?

With oVirt, the engine creates time-limited tickets for console access.

If you connect via the web ui, this should work seamlessly. If it's not,
it's probably a bug somewhere.

Perhaps explain what you are trying to do and how.

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MOSQIMC37UW3KN7H4K5TUBNZDWFL5UMM/


[ovirt-users] When I want to use the VNC tool to connect to the virtual machine, I am prompted to enter the virtual machine VNC password

2019-02-20 Thread xilazz
Hi,
When I want to use the VNC tool to connect to the virtual machine, I will be 
prompted for the virtual machine VNC password. The virtual machine XML file is 
shown below. Where can I query passwd in the VNC configuration?  
  
  

Do you need to change the listen parameter in the libvirtd.conf configuration 
file.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BHU33INCDCYPKJRMMVUNQDQD35UBKOPE/


[ovirt-users] Preserve vm state

2019-02-20 Thread Leo David
Hi Everyone,
I have this challange where I need to rollback a couple  of vms to a
certain base snapshot everytime it starts, for a school computer lab.
It there a way to configure this feature somehow in the UI ?
Thank you very much !

Leo
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFJYUTPEOOQDHVECXKVZSKBHPAU34O3I/


[ovirt-users] Re: Unable to change cluster and data center compatibility version

2019-02-20 Thread Staniforth, Paul
Does oVirt 4.0 support Centos6 hosts?


Regards,

 Paul S.


From: Jonathan Mathews 
Sent: 20 February 2019 06:25
To: Shani Leviim
Cc: Ovirt Users
Subject: [ovirt-users] Re: Unable to change cluster and data center 
compatibility version

Hi Shani

Yes, I did try and change the cluster compatibility first, and that's when I 
got the error: Ovirt: Some of the hosts still use legacy protocol which is not 
supported by cluster 3.6 or higher. In order to change it a host needs to be 
put to maintenance and edited in advanced options section.

I did go through the article you suggested, however, I did not see anything 
that would help.

Thanks


On Tue, Feb 19, 2019 at 3:46 PM Shani Leviim 
mailto:slev...@redhat.com>> wrote:
Hi Jonathan,

Did you try first to change the compatibility of all clusters and then change 
the data center's compatibility?
This once seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1375567

Regards,
Shani Leviim


On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews 
mailto:jm3185...@gmail.com>> wrote:
Good Day

I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run into 
an issue where I am unable to change the cluster and data center compatibility 
version.

I get the following error in the GUI:

Ovirt: Some of the hosts still use legacy protocol which is not supported by 
cluster 3.6 or higher. In order to change it a host needs to be put to 
maintenance and edited in advanced options section.

This error was received with all VM's off and all hosts in maintenance.

The environment has the following currently installed:

Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5
Host1 - CentOS 6.9 - VDSM 4.16.30
Host2 - CentOS 6.9 - VDSM 4.16.30
Host3 - CentOS 6.9 - VDSM 4.16.30

I also have the following from engine.log

[root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log
2018-09-22 07:11:33,920 INFO  
[org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher] 
(DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS 
'd82a026c-31b4-4efc-8567-c4a6bdcaa826'
2018-09-22 07:11:34,685 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] 
(DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH, 
DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9
2018-09-22 07:11:34,687 INFO  
[org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand] 
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command: 
DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected : 
 ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
2018-09-22 07:11:34,706 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] 
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START, 
DisconnectStorageServerVDSCommand(HostName = ovhost3, 
StorageServerConnectionManagementVDSParameters:{runAsync='true', 
hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826', 
storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS', 
connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e',
 connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1', iqn='null', 
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', 
nfsTimeo='null', iface='null', netIfaceName='null'}, 
StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606', 
connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null', 
mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', 
iface='null', netIfaceName='null'}, 
StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117', 
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null', 
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', 
nfsTimeo='null', iface='null', netIfaceName='null'}, 
StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2', 
connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null', 
vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null', 
nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6
2018-09-22 07:11:34,991 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] 
(DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH, 
DisconnectStorageServerVDSCommand, return: 
{3fdffb4c-250b-4a4e-b914-e0da1243550e=0, 
29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0, 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0, 
4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6
2018-09-22 07:11:56,367 WARN  [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] 
(default task-29) [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for 
user admin@internal. Reasons: 
VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION
2018-09-22 07:12:41,017 WARN  
[org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default task-29) 
[efd285b] CanDoAction of action 'UpdateStoragePool' failed for user 

[ovirt-users] failed to import vm from a standalone kvm host

2019-02-20 Thread adam...@adagene.com.cn
Hello, everyone. I'm testing ovirt 4.3.0 now and when I try to import a vm from 
a standalone kvm host, it failed. My ovirt cluster's backend storage is a HPE 
FC device. here's my step:

1. shutdown the vm in that kvm host.
2. Enable public key authentication between the proxy host (ovirt1) and the KVM 
host:
3. Enter the URI of the KVM host. qemu+ssh://root@192.168.49.191/system
4. Enter the username and password
5. click "Load" and I can get the vm list.
6. select the vm and  use the arrows to move them to the Virtual Machines to 
Import list.
7. click "next" and select os type to RHEL 6.x X64.
8. click OK.

then the progress of Importing VM centos6 to Cluster Default failed. log in the 
proxy host ovirt1 here:
[0.5] preparing for copy
[0.5] Copying disk 1/1 to 
/rhev/data-center/mnt/blockSD/b842aa93-d374-45ef-8555-ffdb1be274fc/images/18f1ceeb-a28f-4b05-8cd6-1b614cad9445/21380c99-696d-4f62-9f48-d6959041b162
(0/100%)^M(0/100%)^M(100/100%)^MTraceback (most recent call last):
  File "/usr/libexec/vdsm/kvm2ovirt", line 22, in 
kvm2ovirt.main()
  File "/usr/lib/python2.7/site-packages/vdsm/kvm2ovirt.py", line 255, in main
handle_volume(con, diskno, src, dst, options)
  File "/usr/lib/python2.7/site-packages/vdsm/kvm2ovirt.py", line 196, in 
handle_volume
options.bufsize)
  File "/usr/lib/python2.7/site-packages/vdsm/kvm2ovirt.py", line 159, in 
download_disk_sparse
stream.sparseRecvAll(bytesWriteHandler, recvSkipHandler, op)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 6122, in 
sparseRecvAll
ret = holeHandler(self, length, opaque)
  File "/usr/lib/python2.7/site-packages/vdsm/kvm2ovirt.py", line 82, in 
recvSkipHandler
return os.ftruncate(fd, cur)
OSError: [Errno 22] Invalid argument

So how could I fix that error, is there anything wrong in my step?
Thanks.



yours Adam
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/H3PZKAVE7HZ6YN2TQRMLN4DBCXHG67VP/


[ovirt-users] Re: left over volume after failed disk move

2019-02-20 Thread Bill James
thank you. just to follow up for this thread, create Bug 1679355


On Sat, Feb 16, 2019 at 9:55 PM Eyal Shenitzky  wrote:

> Can you please open a bug - https://bugzilla.redhat.com/
> 
>
> Please attach the engine.log and the vdsm.log.
>
> Thanks
>
> On Fri, Feb 15, 2019 at 8:11 AM Bill James  wrote:
>
>> I tried moving some disks from one gluster volume to another.
>> 8 worked, 6 failed.
>>
>> I can't retry the move because ovirt says:
>> 2019-02-14 21:36:49,450-08 ERROR
>> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler4)
>> [2d9789d1] BaseAsyncTask::logEndTaskFailure: Task '2a0e703b-0239-41f8-a920
>> -50c1ae096590' (Parent Command 'CreateImagePlaceholder', Parameters Type
>> 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with
>> failure:
>> -- Result: 'cleanSuccess'
>> -- Message: 'VDSGenericException: VDSErrorException: Failed in vdscommand
>> to HSMGetAllTasksStatusesVDS, error = Volume already exists:
>> ('d33e8048-a4b4-4b85-bf44-20be65b854f2',)',
>>
>>
>> How do I clear up the gluster volume of these failed images?
>> I'm running :
>> ovirt-engine-4.1.8.2-1.el7.centos.noarch
>> glusterfs-3.8.15-2.el7.x86_64
>> vdsm-4.19.43-1.el7.centos.x86_64
>>
>>
>> Some errors from the first failed disk move:
>> 2019-02-14 21:23:44,114-08 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand]
>> (DefaultQuartzScheduler2) [7adfa09d-d0d6-4478-9a6a-c505535e325b] Failed
>>  in 'VmReplicateDiskFinishVDS' method
>> 2019-02-14 21:23:44,125-08 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (DefaultQuartzScheduler2) [7adfa09d-d0d6-4478-9a6a-c505535e325b] EVENT_ID: V
>> DS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack:
>> null, Custom ID: null, Custom Event ID: -1, Message: VDSM
>> ovirt4.j2noc.com command VmReplicateDiskFinishVDS fai
>> led: Resource unavailable
>>
>> attached is engine.log.
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GAOGBS7CWLEK2IKSIFQKGGSCHUI7GJ5S/
>>
>
>
> --
> Regards,
> Eyal Shenitzky
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4TLSWVGFPHNOPKJEKK2YDWPIKRZV7PN4/


[ovirt-users] Re: Stuck completing last step of 4.3 upgrade

2019-02-20 Thread Darrell Budic
I was just helping Tristam on #ovirt with a similar problem, we found that his 
two upgraded nodes were running multiple glusterfsd processes per brick (but 
not all bricks). His volume & brick files in /var/lib/gluster looked normal, 
but starting glusterd would often spawn extra fsd processes per brick, seemed 
random. Gluster bug? Maybe related to  
https://bugzilla.redhat.com/show_bug.cgi?id=1651246 
, but I’m helping debug 
this one second hand… Possibly related to the brick crashes? We wound up 
stopping glusterd, killing off all the fsds, restarting glusterd, and repeating 
until it only spawned one fsd per brick. Did that to each updated server, then 
restarted glusterd on the not-yet-updated server to get it talking to the right 
bricks. That seemed to get to a mostly stable gluster environment, but he’s 
still seeing 1-2 files listed as needing healing on the upgraded bricks (but 
not the 3.12 brick). Mainly the DIRECT_IO_TEST and one of the dom/ids files, 
but he can probably update that. Did manage to get his engine going again, 
waiting to see if he’s stable now.

Anyway, figured it was worth posting about so people could check for multiple 
brick processes (glusterfsd) if they hit this stability issue as well, maybe 
find common ground.

Note: also encountered https://bugzilla.redhat.com/show_bug.cgi?id=1348434 
 trying to get his engine 
back up, restarting libvirtd let us get it going again. Maybe un-needed if he’d 
been able to complete his third node upgrades, but he got stuck before then, 
so...

  -Darrell

> On Feb 14, 2019, at 1:12 AM, Sahina Bose  wrote:
> 
> On Thu, Feb 14, 2019 at 2:39 AM Ron Jerome  wrote:
>> 
>> 
>>> 
>>> Can you be more specific? What things did you see, and did you report bugs?
>> 
>> I've got this one: https://bugzilla.redhat.com/show_bug.cgi?id=1649054
>> and this one: https://bugzilla.redhat.com/show_bug.cgi?id=1651246
>> and I've got bricks randomly going offline and getting out of sync with the 
>> others at which point I've had to manually stop and start the volume to get 
>> things back in sync.
> 
> Thanks for reporting these. Will follow up on the bugs to ensure
> they're addressed.
> Regarding brciks going offline - are the brick processes crashing? Can
> you provide logs of glusterd and bricks. Or is this to do with
> ovirt-engine and brick status not being in sync?
> 
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: 
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: 
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/3RVMLCRK4BWCSBTWVXU2JTIDBWU7WEOP/
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4PKJSVDIH3V4H7Q2RKS2C4ZUMWDODQY6/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DYFZAC4BPJNGZP3PEZ6ZP2AB3C3JVAFM/


[ovirt-users] Re: understanding ovirt communication

2019-02-20 Thread Greg Sheremeta
Firewall requirements are documented here:
https://www.ovirt.org/documentation/install-guide/chap-System_Requirements.html#networking-requirements

Your logs contain a bunch of Connection refused messages, so I'd start with
verifying all those ports are open.

Best wishes,
Greg

On Wed, Feb 20, 2019 at 3:46 PM  wrote:

> Dear Greg,
>
>
> I configured 4 hosts. (see tab)
> "rhnode" is a real-node, all other are test-hosts.
> IP with 192 are RFC1918.
>
> if I click on the link host:rhnode:install nothing happens.
> rhnode:/root/.ssh/authorized_keys already configured
>
> Howto understanding ovirt communication?
>
>   ovirt-engine.py - node:vdsm:46463  node:libvirt:16509
>  |
>sql-db:5432
>
> Is this correct?
>
> Regards Heiko
>
>
>
> Host: 1 - 4
> Name Kommentar Hostname/IP Cluster Data-Center Status Virtuelle Maschinen
> Arbeitsspeicher CPU Netzwerk SPM
> elmo t2e 141.xxx.xxx.244 Default Default InstallFailed 0 0% 0% 0% Normal
> leni t1i 192.xxx.xxx.198 Default Default NonResponsive 0 0% 0% 0% Normal
> mb_h1 t3xen 141.xxx.xxx.240 Default Default NonResponsive 0 0% 0% 0% Normal
> rhnode t4node 192.xxx.xxx.153 Default Default InstallFailed 0 0% 0% 0%
> Normal
>
>
>
> [1] hxxps://
> w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/57a7fb3c-f344-4617-9b15-df48247b1500/vdsm.log-190214
> [2] hxxps://
> w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/5aa5663b-db98-4cd3-90da-63a132e29175/engine.log-20190213.a.gz
> [3] hxxps://
> w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/9494a8a5-7a01-4dfb-b7b7-7f43f5a65518/engine.log-20190214.a.gz
> links expires on one week
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6EXY67RIQ2DDF4HNPUV2JOU5Y66DRCCH/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UJVK35OCLF2IOSBDMRW5UXN5BARBLPFR/


[ovirt-users] Re: understanding ovirt communication

2019-02-20 Thread hlmstu
Dear Greg,


I configured 4 hosts. (see tab)
"rhnode" is a real-node, all other are test-hosts.
IP with 192 are RFC1918.

if I click on the link host:rhnode:install nothing happens.
rhnode:/root/.ssh/authorized_keys already configured

Howto understanding ovirt communication?

  ovirt-engine.py - node:vdsm:46463  node:libvirt:16509
 |
   sql-db:5432

Is this correct?

Regards Heiko



Host: 1 - 4
Name Kommentar Hostname/IP Cluster Data-Center Status Virtuelle Maschinen 
Arbeitsspeicher CPU Netzwerk SPM
elmo t2e 141.xxx.xxx.244 Default Default InstallFailed 0 0% 0% 0% Normal
leni t1i 192.xxx.xxx.198 Default Default NonResponsive 0 0% 0% 0% Normal
mb_h1 t3xen 141.xxx.xxx.240 Default Default NonResponsive 0 0% 0% 0% Normal
rhnode t4node 192.xxx.xxx.153 Default Default InstallFailed 0 0% 0% 0% Normal



[1] 
hxxps://w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/57a7fb3c-f344-4617-9b15-df48247b1500/vdsm.log-190214
[2] 
hxxps://w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/5aa5663b-db98-4cd3-90da-63a132e29175/engine.log-20190213.a.gz
[3] 
hxxps://w3.fh-lausitz.de/alfresco/d/d/workspace/SpacesStore/9494a8a5-7a01-4dfb-b7b7-7f43f5a65518/engine.log-20190214.a.gz
links expires on one week
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6EXY67RIQ2DDF4HNPUV2JOU5Y66DRCCH/


[ovirt-users] Re: How to upgrade ovirt node host?

2019-02-20 Thread Staniforth, Paul
I don't think yum remove ovirt-release42 removes the repo files ( maybe because 
they're configuration files)?


rpm -qf /etc/yum.repos.d/ovirt-4.2*


yum erase ovirt-release42 ( if the package still installed)


rm  /etc/yum.repos.d/ovirt-4.2* ( to actually remove the repositories)


Regards,

Paul S.


From: adam...@adagene.com.cn 
Sent: 20 February 2019 00:41
To: Juhani Rautiainen
Cc: ovirtlist; Lucie Leistnerova
Subject: [ovirt-users] Re: How to upgrade ovirt node host?

Hi, Juhani. I followed the steps below:
1. yum remove ovirt-release42
2. yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
3. yum update ovirt-node-ng-image-update
4. reboot
5. yum update

and the ovirt-4.2.repo comes back after I reboot the node host.



yours Adam

From: Juhani Rautiainen
Date: 2019-02-19 21:58
To: adam...@adagene.com.cn
CC: ovirtlist; Lucie 
Leistnerova
Subject: [ovirt-users] Re: How to upgrade ovirt node host?
On Tue, Feb 19, 2019 at 3:30 PM adam...@adagene.com.cn
 wrote:
>
> Thank you. Your answer solved my problems.
>  After I installed the big rpm and reboot.  there are two repo files remains  
> in /etc/yum.repos.d/
> ovirt-4.2-dependencies.repo
> ovirt-4.2.repo
> maybe I should remove the 2 files to avoid any conflicts?
>
I think that they'll disappear if you do

yum remove ovirt-release42

-Juhani
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2PE4TWKZHMCJYIIDUWC7QL7JXOYV67TN/
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OEWJTKC535X2O5ZQXKY6DGF5SZILPMEC/


[ovirt-users] Re: process stuck while adding disk

2019-02-20 Thread Dev Ops
I found a task running in the db that was was my task and was just spinning 
apparently. I deleted it and this zombie process is gone. 

engine=# select * from job order by start_time desc;
-[ RECORD 1 ]-+-
job_id| 7c6b899e-ada2-456e-9562-4cff569c9820
action_type   | AddDisk
description   | Adding Disk
status| STARTED
owner_id  | 04876849-fe47-4bc7-9e03-782fd9289e86
visible   | t
start_time| 2019-02-19 17:43:12.843-05
end_time  |
last_update_time  | 2019-02-19 19:02:43.278-05
correlation_id| 1cc61003-942b-4622-92d7-9067a000d1ba
is_external   | f
is_auto_cleared   | t
engine_session_seq_id | 14703

engine=# select DeleteJob('7c6b899e-ada2-456e-9562-4cff569c9820');
-[ RECORD 1 ]
deletejob |

This has been resolved just sharing what I did to clear it. 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5MHBIYKKBKMZ2UC3XCYSGW3HHVHVDNFT/


[ovirt-users] Re: Ovirt 4.3 RC missing glusterfs-gnfs

2019-02-20 Thread Strahil Nikolov
 Hi Sahina, Sandro,
can you guide me through the bugzilla.redhat.com in order to open a bug for the 
missing package. ovirt-4.3-centos-gluster5 still lacks package for the 
'glusterfs-gnfs' (which is a dependency for vdsm-gluster):
[root@ovirt2 ~]# yum --disablerepo=* --enablerepo=ovirt-4.3-centos-gluster5 
list available --show-duplicates | grep gluster-gnfsRepository 
centos-sclo-rh-release is listed more than once in the configurationRepository 
centos-sclo-rh-release is listed more than once in the configurationCannot 
upload enabled repos report, is this client registered?

This leads to the following (output truncated):--> Finished Dependency 
ResolutionError: Package: glusterfs-gnfs-3.12.15-1.el7.x86_64 
(@ovirt-4.2-centos-gluster312)           Requires: glusterfs(x86-64) = 
3.12.15-1.el7           Removing: glusterfs-3.12.15-1.el7.x86_64 
(@ovirt-4.2-centos-gluster312)               glusterfs(x86-64) = 3.12.15-1.el7  
         Updated By: glusterfs-5.3-1.el7.x86_64 (ovirt-4.3-centos-gluster5)     
          glusterfs(x86-64) = 5.3-1.el7           Available: 
glusterfs-3.12.0-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.0-1.el7
           Available: glusterfs-3.12.1-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs(x86-64) = 3.12.1-1.el7    
       Available: glusterfs-3.12.1-2.el7.x86_64 (ovirt-4.2-centos-gluster312)   
            glusterfs(x86-64) = 3.12.1-2.el7           Available: 
glusterfs-3.12.2-18.el7.x86_64 (base)               glusterfs(x86-64) = 
3.12.2-18.el7           Available: glusterfs-3.12.3-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs(x86-64) = 3.12.3-1.el7    
       Available: glusterfs-3.12.4-1.el7.x86_64 (ovirt-4.2-centos-gluster312)   
            glusterfs(x86-64) = 3.12.4-1.el7           Available: 
glusterfs-3.12.5-2.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.5-2.el7           Available: 
glusterfs-3.12.6-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.6-1.el7           Available: 
glusterfs-3.12.8-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.8-1.el7           Available: 
glusterfs-3.12.9-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.9-1.el7           Available: 
glusterfs-3.12.11-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.11-1.el7           Available: 
glusterfs-3.12.13-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.13-1.el7           Available: 
glusterfs-3.12.14-1.el7.x86_64 (ovirt-4.2-centos-gluster312)               
glusterfs(x86-64) = 3.12.14-1.el7           Available: 
glusterfs-5.0-1.el7.x86_64 (ovirt-4.3-centos-gluster5)               
glusterfs(x86-64) = 5.0-1.el7           Available: glusterfs-5.1-1.el7.x86_64 
(ovirt-4.3-centos-gluster5)               glusterfs(x86-64) = 5.1-1.el7         
  Available: glusterfs-5.2-1.el7.x86_64 (ovirt-4.3-centos-gluster5)             
  glusterfs(x86-64) = 5.2-1.el7Error: Package: 
glusterfs-gnfs-3.12.15-1.el7.x86_64 (@ovirt-4.2-centos-gluster312)           
Requires: glusterfs-client-xlators(x86-64) = 3.12.15-1.el7           Removing: 
glusterfs-client-xlators-3.12.15-1.el7.x86_64 (@ovirt-4.2-centos-gluster312)    
           glusterfs-client-xlators(x86-64) = 3.12.15-1.el7
           Updated By: glusterfs-client-xlators-5.3-1.el7.x86_64 
(ovirt-4.3-centos-gluster5)               glusterfs-client-xlators(x86-64) = 
5.3-1.el7           Available: glusterfs-client-xlators-3.12.0-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.0-1.el7           Available: glusterfs-client-xlators-3.12.1-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.1-1.el7           Available: glusterfs-client-xlators-3.12.1-2.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.1-2.el7           Available: glusterfs-client-xlators-3.12.2-18.el7.x86_64 
(base)               glusterfs-client-xlators(x86-64) = 3.12.2-18.el7           
Available: glusterfs-client-xlators-3.12.3-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.3-1.el7           Available: glusterfs-client-xlators-3.12.4-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.4-1.el7           Available: glusterfs-client-xlators-3.12.5-2.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.5-2.el7           Available: glusterfs-client-xlators-3.12.6-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.6-1.el7           Available: glusterfs-client-xlators-3.12.8-1.el7.x86_64 
(ovirt-4.2-centos-gluster312)               glusterfs-client-xlators(x86-64) = 
3.12.8-1.el7           

[ovirt-users] Re: Forcing vdsm to configure another NIC as the bridge (oVirt 4.2.8)

2019-02-20 Thread zachary . winter
Unfortunately, it is continuing to hang when I drag and drop and never resolves.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7FTCK7MWFZKSYVBGQ45HH6WAG5KL64FU/


[ovirt-users] Re: How to recreate Ovirt CA from scratch

2019-02-20 Thread Giorgio Biacchi
On 2/20/19 7:47 AM, Yedidyah Bar David wrote:
> On Tue, Feb 19, 2019 at 3:18 PM Giorgio Biacchi  wrote:
>>
>> Hi list,
>> during our datacenter lifetime many things changed. We moved the engine
>> twice on different hosts with, of course, different FQDNs, and many
>> other changes. Now we are stuck with an error when we try to upload an
>> image to a data domain. The error is somehow bound to a failure to
>> validate the ovirt-imageio-proxy certificate and, since the current root
>> CA certificate is still signed with sha1WithRSAEncryption we'd like to
>> regenerate the whole CA.
> 
> Is "sha1" all your problem? You might want to check:
> 
> https://www.ovirt.org/develop/migrate-pki-to-sha256.html

Today I repeated the procedure described in the link here above and
finally I was successful. Maybe yesterday I was too quick to fall back
to the original state but my enviroment is in production and I was scared...

I had some problems while enrolling the new certificate on the
hypervisors, but removing/rebooting/readding did the trick.

Our engine have an SSO_ALTERNATE_ENGINE_FQDN (before it was the real
engine FQDN) so I found that ImageProxyAddress was still pointing to the
old name. I'm now able (as before) to access the admin portal with both
names but only one (the one with the green lock in the browser) is the
FQDN in the certificate, so I did:

engine-config --set ImageProxyAddress=realFQDN:54323

and now I have sha256 certs and ovirt-imageio-proxy working as expected. :)

Thanks for your hints..

> 
>>
>> That's the steps we've done.. without success...
>>
>> 1) Make a tar.gz of the /etc/pki/ovirt-engine as backup
>> 2) Create a new CA cert using the same private key:
>> openssl req -key /etc/pki/ovirt-engine/private/ca.pem -new -x509 
>> -days
>> 3650 -sha256 -extensions v3_ca -out newca.cert.pem
>> 3) Put the new CA cert in place
>> mv ca.pem ca.pem.orig.20190219;mv newca.cert.pem ca.pem
>> 4) Resign all the other certs
>> names="engine apache websocket-proxy jboss imageio-proxy"
>> for name in $names; do
>> subject="$(
>> openssl \
>> x509 \
>> -in /etc/pki/ovirt-engine/certs/"${name}".cer \
>> -noout \
>> -subject \
>> | sed \
>> 's;subject= \(.*\);\1;' \
>> )"
>> /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \
>> --name="${name}" \
>> --password=mypass \
>> --subject="${subject}" \
>> --keep-key
>> done
>> 5) Restart all the services
>> systemctl restart httpd
>> systemctl restart ovirt-engine
>> systemctl restart ovirt-websocket-proxy
>> systemctl restart ovirt-imageio-proxy
>>
>>
>> The following step was to take the backup at 1) and fall back to the
>> initial state because nothing worked as expected.
>>
>> There's any documented procedure about how to recreate Ovirt CA from
>> scratch??
> 
> I do not think so.
> 
> Seems like this isn't what you want to do, either, as you try to keep
> the existing keys (and recreate only certs).
> 
> If that's really what you want to do, you can simply remove
> everything under /etc/pki/ovirt-engine that's not packaged by
> any rpm, e.g. using:
> 
> find . -type f | xargs rpm -qf | awk '/is not owned by any package/ {print 
> $2}'
> 
> and then run engine-setup.
> 
> Obviously, this will break everything - you will have to
> reinstall all hosts (or at least "Enroll Certificates" from
> the web ui) etc. If it's a hosted-engine, make sure to move
> it to global maintenance beforehand.
> 
> See also:
> 
> https://ovirt.org/develop/release-management/features/infra/pki-renew.html
> 
> So far, we didn't make engine-setup suggest to renew pki
> on the grounds of not using sha256, considering it not-yet-
> mandatory, and only documented the above link (and made new
> setups use sha256 by default). Feel free to open an RFE for
> this, and once it's fixed, the answer to your question will
> be "Run engine-setup"...
> 
> Best regards,
> 

-- 
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ME4HOKHGSPPXVUUAJA7EPBJHBM72S7YF/


[ovirt-users] Re: Unable to upload images

2019-02-20 Thread Michael Blanchard
That fixed it!  I actually downloaded it 7 times on two different machines and 
used 3 different browsers.

Get Outlook for Android


From: Nir Soffer 
Sent: Tuesday, February 19, 2019 6:21:14 PM
To: Michael Blanchard
Cc: users; Daniel Erez; qemu-block
Subject: Re: [ovirt-users] Re: Unable to upload images

On Wed, Feb 20, 2019 at 1:01 AM 
mailto:mich...@wanderingmad.com>> wrote:
qemu-img info:
LM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
image: LoadMaster-VLM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
file format: raw
virtual size: 16G (17179869696 bytes)
disk size: 16G

This is raw image, so it may work, but

ls -l:
-rwxrwxrwx 1 michael michael 17179869185 Jan  7 16:43 
LoadMaster-VLM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk

The image size is invalid. raw image size must be aligned to 512 bytes, this is 
why
we block such images in the UI.

Is it possible that the image was truncated?

According to qemu-img info, the size is 17179869696. qemu-img lie about the 
size by rounding
up to the next multiple of 512.

I think this will fix your image:

truncate -s 17179869696 
LoadMaster-VLM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk

After that uploading the image should work.

Downloading the image again and verifying the image checksum with the vendor is 
probably
a good idea if you are not sure about the contents of this image.

Nir

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HF23RD4RVVCLB5HXSJE32ZBGBIH6J3Z3/


[ovirt-users] Re: oVirt 4.3.1 test day

2019-02-20 Thread Jason P. Thomas
I had a somewhat related issue.  An NFS domain I was using for an iso 
domain failed.  It set off a sequence of constantly rebooting hosts 
(when fencing was enabled) and constantly deactivating/reactivating 
hosts (when I disabled fencing).  For about a day, oVirt was completely 
unusable.  All because an iso domain died.




On 2/12/19 5:16 AM, Hetz Ben Hamo wrote:

Hi,

Well, there is a severe bug that I complained about it on 4.2 (or 4.1? 
I don't remember) and it's regarding "yanking the power cable".
Basically I'm performing a simple test: kill all hosts immediately to 
simulate a power loss without UPS.


For this test I have 2 nodes, and  4 storage domains: hosted_storage 
(that was setup during the HE installation), 1 iSCSI domain, 1 NAS 
domain and 1 ISO domain.


After all the nodes loose power, I power them on and the following 
procedure happens:
1. The node with HE finishes booting, and it takes few minutes until 
the HE is up.
2. When the HE is up, all the storage domains comes back to life as 
online and VM's with high availability starting to boot.
3. Few minutes later, *all* (with the exception of  hosted_storage) 
storage domains are going down
4. After about 5 minutes, all the other storage domains which went 
down, are coming up, but by then, and VM's without high availability 
that are not hosted on hosted_storage remains down, you'll need to 
power them manually back.


This whole procedure takes about 15-25 minutes after booting the 
nodes, and this issue is always repeatable, just kill the power to the 
nodes, power them up again and see for yourself.


The solution would be to change the code and if a storage domain is up 
- *leave it up*, skip the check.


Thanks


On Tue, Feb 12, 2019 at 11:56 AM Sandro Bonazzola > wrote:


Hi,
We are planning to release the first candidate of 4.3.1 on
February 20th[1] and the final release on February 26th.
Please join us testing this release candidate right after it will
be announced!
We are going to coordinate the testing effort with a public Trello
board at https://trello.com/b/5ZNJgPC3


You'll find instructions on how to use the board there.

If you have an environment dedicated to testing, remember you can
setup a few VMs and test the deployment with nested virtualization.
To ease the setup of such environment you can use Lago
(https://github.com/lago-project

)

The oVirt team will monitor the Trello board, the #ovirt IRC
channel on irc.oftc.net


server and the users@ovirt.org  mailing
list to assist with the testing.

[1]

https://www.ovirt.org/develop/release-management/releases/4.3.z/release-management.html


[ovirt-users] Re: oVirt 4.3.1 test day

2019-02-20 Thread Sandro Bonazzola
Il giorno mer 20 feb 2019 alle ore 16:07 Guillaume Pavese <
guillaume.pav...@interactiv-group.com> ha scritto:

> I am on the Trello board, but I can not create cards
>

Sorry for that, try using
https://trello.com/invite/b/5ZNJgPC3/f1b1826ee4902f348c44607765a15099/ovirt-431-test-day-1
for joining the board



>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
>
> On Wed, Feb 20, 2019 at 10:05 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno mar 12 feb 2019 alle ore 10:49 Sandro Bonazzola <
>> sbona...@redhat.com> ha scritto:
>>
>>> Hi,
>>> We are planning to release the first candidate of 4.3.1 on February
>>> 20th[1] and the final release on February 26th.
>>> Please join us testing this release candidate right after it will be
>>> announced!
>>> We are going to coordinate the testing effort with a public Trello board
>>> at https://trello.com/b/5ZNJgPC3
>>> You'll find instructions on how to use the board there.
>>>
>>> If you have an environment dedicated to testing, remember you can setup
>>> a few VMs and test the deployment with nested virtualization.
>>> To ease the setup of such environment you can use Lago (
>>> https://github.com/lago-project)
>>>
>>> The oVirt team will monitor the Trello board, the #ovirt IRC channel on
>>> irc.oftc.net server and the users@ovirt.org mailing list to assist with
>>> the testing.
>>>
>>> [1]
>>> https://www.ovirt.org/develop/release-management/releases/4.3.z/release-management.html
>>>
>>
>> The release candidate has been announced, please join us testing it!
>>
>>
>>
>>>
>>>
>>> --
>>>
>>> SANDRO BONAZZOLA
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> 
>>>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BMNW5ITQO3AGPRWI7O6UEG4ZBY2WEXD3/
>>
>

-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CZQTA2YYGUVNQW4TOOKJ3O2SX7OG427U/


[ovirt-users] Re: oVirt 4.3.1 test day

2019-02-20 Thread Guillaume Pavese
I am on the Trello board, but I can not create cards

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group


On Wed, Feb 20, 2019 at 10:05 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno mar 12 feb 2019 alle ore 10:49 Sandro Bonazzola <
> sbona...@redhat.com> ha scritto:
>
>> Hi,
>> We are planning to release the first candidate of 4.3.1 on February
>> 20th[1] and the final release on February 26th.
>> Please join us testing this release candidate right after it will be
>> announced!
>> We are going to coordinate the testing effort with a public Trello board
>> at https://trello.com/b/5ZNJgPC3
>> You'll find instructions on how to use the board there.
>>
>> If you have an environment dedicated to testing, remember you can setup a
>> few VMs and test the deployment with nested virtualization.
>> To ease the setup of such environment you can use Lago (
>> https://github.com/lago-project)
>>
>> The oVirt team will monitor the Trello board, the #ovirt IRC channel on
>> irc.oftc.net server and the users@ovirt.org mailing list to assist with
>> the testing.
>>
>> [1]
>> https://www.ovirt.org/develop/release-management/releases/4.3.z/release-management.html
>>
>
> The release candidate has been announced, please join us testing it!
>
>
>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BMNW5ITQO3AGPRWI7O6UEG4ZBY2WEXD3/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G5LBYKVR7HPZ5D4CVDRKWGUNYWSYSQL4/


[ovirt-users] Re: cannot start vm after upgrade to ovirt-4.3

2019-02-20 Thread Nir Soffer
On Tue, Feb 19, 2019, 14:19 Moritz Baumann  Thank you Simone,
>
> that worked.
>
>
>
> On 19.02.19 12:40, Simone Tiraboschi wrote:
> >
> >
> > On Tue, Feb 19, 2019 at 12:18 PM Moritz Baumann
> > mailto:moritz.baum...@inf.ethz.ch>> wrote:
> >
> > After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
> >
> > I try to start the vm with run once on a specific node (ovirt-node04)
> > and this is the output of /var/log/vdsm/vdsm.log
> >
> >
> > VolumeDoesNotExist: Volume does not exist:
> > (u'482698c2-b1bd-4715-9bc5-e222405260df',)
> > 2019-02-19 12:08:34,322+0100 INFO  (vm/abee17b9)
> > [storage.TaskManager.Task]
> > (Task='d04f3abb-f3d3-4e2f-902f-d3c5e4fabc36')
> > aborting: Task is aborted: "Volume does not exist:
> > (u'482698c2-b1bd-4715-9bc5-e222405260df',)" - code 201 (task:1181)
> > 2019-02-19 12:08:34,322+0100 ERROR (vm/abee17b9) [storage.Dispatcher]
> > FINISH prepareImage error=Volume does not exist:
> > (u'482698c2-b1bd-4715-9bc5-e222405260df',) (dispatcher:81)
> > 2019-02-19 12:08:34,322+0100 ERROR (vm/abee17b9) [virt.vm]
> > (vmId='abee17b9-079e-452c-a97d-99eff951dc39') The vm start process
> > failed (vm:937)
> > Traceback (most recent call last):
> > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line
> > 866, in
> > _startUnderlyingVm
> >   self._run()
> > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line
> 2749,
> > in _run
> >   self._devices = self._make_devices()
> > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line
> 2589,
> > in _make_devices
> >   disk_objs = self._perform_host_local_adjustment()
> > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line
> 2662,
> > in _perform_host_local_adjustment
> >   self._preparePathsForDrives(disk_params)
> > File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line
> 1011,
> > in _preparePathsForDrives
> >   drive['path'] = self.cif.prepareVolumePath(drive, self.id
> > )
> > File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line
> 415,
> > in prepareVolumePath
> >   raise vm.VolumeError(drive)
> > VolumeError: Bad volume specification {'index': 1, 'domainID':
> >
> >
> > Hi,
> > I think you hit this bug: https://bugzilla.redhat.com/1666795
> >
> > Manually setting back all the disk image files in the storage domain as
> > vdm:kvm (36:36), 660 is a temporary workaround.
>

Based on the discussion in tbe bug, this the only way to migrate vms from
version<4.3 to 4.3.

Another waybis to shut down the vm and start it again on 4.3 host.

Fiture vdsm version will fix this issue using libirt hook.


> Adding all_squash,anonuid=36,anongid=36 to the configuration of your NFS
> > share should avoid that until a proper fix will be released.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UDGUDT3GMJXYXPZQVTJ3TM6HLZCK/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7NXXNPTQWMV6CG4LZR4C3VWNWIE3IBKR/


[ovirt-users] Re: oVirt 4.3.1 test day

2019-02-20 Thread Sandro Bonazzola
Il giorno mar 12 feb 2019 alle ore 10:49 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:

> Hi,
> We are planning to release the first candidate of 4.3.1 on February
> 20th[1] and the final release on February 26th.
> Please join us testing this release candidate right after it will be
> announced!
> We are going to coordinate the testing effort with a public Trello board
> at https://trello.com/b/5ZNJgPC3
> You'll find instructions on how to use the board there.
>
> If you have an environment dedicated to testing, remember you can setup a
> few VMs and test the deployment with nested virtualization.
> To ease the setup of such environment you can use Lago (
> https://github.com/lago-project)
>
> The oVirt team will monitor the Trello board, the #ovirt IRC channel on
> irc.oftc.net server and the users@ovirt.org mailing list to assist with
> the testing.
>
> [1]
> https://www.ovirt.org/develop/release-management/releases/4.3.z/release-management.html
>

The release candidate has been announced, please join us testing it!



>
>
> --
>
> SANDRO BONAZZOLA
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BMNW5ITQO3AGPRWI7O6UEG4ZBY2WEXD3/


[ovirt-users] [ANN] oVirt 4.3.1 First Release Candidate is now available

2019-02-20 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.3.1 First Release Candidate, as of February 20th, 2019.

This update is a release candidate of the first in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)

Experimental tech preview for x86_64 and s390x architectures for Fedora 28
is also included.

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available for EL7 only
- oVirt Node is available for EL7 only [2]
- Fedora 28 based appliance and node couldn't be built due to a bug in
Lorax (the tool used to build the images) affecting Fedora 28.

Additional Resources:
* Read more about the oVirt 4.3.1 release highlights:
http://www.ovirt.org/release/4.3.1/
* 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.3.1/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5FFYKEIDHLGZUB6QVB2HBYETL7IFG2HN/


[ovirt-users] Re: Creating a static route

2019-02-20 Thread Greg Sheremeta
Thanks all. I agree with Lev, mostly because it's a better experience for
our users. And we typically document workaround type things in the
appendices. I could argue vdsm hooks are all workarounds for something and
we document those pretty extensively :)

Maybe this section would make sense?
https://www.ovirt.org/documentation/admin-guide/appe-Custom_Network_Properties.html

Sandro, your opinion please?

Greg

On Wed, Feb 20, 2019 at 7:21 AM Lev Veyde  wrote:

> Hi Edward,
>
> Thanks for your feedback on the issue.
>
> I still think that we do need to to add a note to the documentation, so
> that customers/integrators who want to add custom static routes will be
> aware of the issue.
> As previously discussed we should note of course, that this feature is
> currently not officially supported, and adding the routes manually is a
> workaround.
>
> Thanks in advance,
>
> On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:
>
>> As mentioned in this thread oVirt currently does not support customized
>> routes.
>> It supports only a host level default route and per network gateways
>> (default route per network).
>>
>> If someone understands well the Linux network details, workarounds may be
>> applied to overcome oVirt limitations.
>> With that said, as oVirt manages the host network details, the community
>> and future development cannot take into account such workarounds.
>>
>> To solve this problem correctly, oVirt needs to support customize routes.
>> From my perspective, this workaround should not be formally documented.
>>
>> Thanks,
>> Edy.
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ENLA36PL2CPVDIJNZTOGLWYTZCPUGJ6Z/


[ovirt-users] Re: Creating a static route

2019-02-20 Thread Edward Haas
On Wed, Feb 20, 2019 at 2:14 PM Lev Veyde  wrote:

> Hi Edward,
>
> Thanks for your feedback on the issue.
>
> I still think that we do need to to add a note to the documentation, so
> that customers/integrators who want to add custom static routes will be
> aware of the issue.
>

Unfortunately, the users can't do that today in a safe manner. I do not
think we should document things that are breakable or that is tailored to
work for a specific user.
If we document it, it means we support it.

If someone is willing to write a blog on how to add a custom route, as a
non formal documentation, it will be great.

As previously discussed we should note of course, that this feature is
> currently not officially supported, and adding the routes manually is a
> workaround.
>
> Thanks in advance,
>
> On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:
>
>> As mentioned in this thread oVirt currently does not support customized
>> routes.
>> It supports only a host level default route and per network gateways
>> (default route per network).
>>
>> If someone understands well the Linux network details, workarounds may be
>> applied to overcome oVirt limitations.
>> With that said, as oVirt manages the host network details, the community
>> and future development cannot take into account such workarounds.
>>
>> To solve this problem correctly, oVirt needs to support customize routes.
>> From my perspective, this workaround should not be formally documented.
>>
>> Thanks,
>> Edy.
>>
>> On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:
>>
>>> Hi Doug,
>>>
>>> Thanks for the update, I'm glad that we could help and everything
>>> worked out just fine!
>>>
>>> I also opened a BZ, asking to add a note in the documentation regarding
>>> this issue.
>>>
>>> Thanks in advance,
>>>
>>> On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield <
>>> doug.l.maxfi...@emcins.com> wrote:
>>>
 Lev,

 Just wanted to update you on the progress.  We created the persistent
 static routes and rules and the data is routing correctly over the required
 gateway.



 Thank you for all of your help!!!



 [image: Count On EMC] 

 *Doug Maxfield *| Senior Operating Systems Analyst

 *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
 Tel: 515.345.4507 | Fax: 866.331.1522
 doug.l.maxfi...@emcins.com | www.emcins.com





 *From:* Lev Veyde 
 *Sent:* Thursday, February 14, 2019 9:14 AM
 *To:* Doug Maxfield 
 *Cc:* users 
 *Subject:* Re: [ovirt-users] Creating a static route



 Hi Doug,

 Just one more thing that I forgot to mention, even though it may be
 obvious - you can use subnets in both rules and routes.

 So if all the IPs you want to route sit in the same subnet then you can
 contain them with a single command e.g. "to 172.22.20.0/24 priority
 32764"

 Thanks in advance,



 On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:

 Hi Doug,

 Sure, np.



 >> 1. - yes it is the priority setting of the specific rule. Basically
 you put in the file the post "ip rule add" part of the command e.g. for "ip
 rule add to 172.22.20.31 priority 32764" you need to put a line of "to
 172.22.20.31 priority 32764"

 >> 2. - yes, the same priority can be used for all of them. E.g. if you
 want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
 add:

 to 172.22.20.31 priority 32764
 to 172.22.34.56 priority 32764
 to 172.22.67.89 priority 32764

 into the rule- file e.g. rule-ovirtmgmt or rule-eno3.



 Please note that you will also need to add the static route for each
 one of these as well w/ "ip route add ... " command e.g. "ip route add
 172.22.20.31 via 172.21.12.61".

 You can also use the route- putting just the route info
 part, similar to the "ip rule" e.g. for equivalent of "ip route add
 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
 content "172.22.20.31 via 172.21.12.61".

 For routes it's important to use specifically the route-ovirtmgmt file
 since the script automatically adds the device to the route command i.e.
 you can put the following lines into your route-ovirtmgmt file:

 172.22.20.31 via 172.21.12.61
 172.22.34.56 via 172.21.12.61
 172.22.67.89 via 172.21.12.68

 (In case the first 2 of the mentioned IPs should be routed through the
 172.21.12.61 gateway, and the last one should be routed through the
 172.21.12.68 gateway).



 For the reference you can take a look at the
 /etc/sysconfig/network-scripts/ifup-routes script.
 It does the actual processing of both "route" and "rule" files for all
 network interfaces on a system.



 Please feel free to contact if you 

[ovirt-users] Re: Creating a static route

2019-02-20 Thread Lev Veyde
Hi Edward,

Thanks for your feedback on the issue.

I still think that we do need to to add a note to the documentation, so
that customers/integrators who want to add custom static routes will be
aware of the issue.
As previously discussed we should note of course, that this feature is
currently not officially supported, and adding the routes manually is a
workaround.

Thanks in advance,

On Wed, Feb 20, 2019 at 1:41 PM Edward Haas  wrote:

> As mentioned in this thread oVirt currently does not support customized
> routes.
> It supports only a host level default route and per network gateways
> (default route per network).
>
> If someone understands well the Linux network details, workarounds may be
> applied to overcome oVirt limitations.
> With that said, as oVirt manages the host network details, the community
> and future development cannot take into account such workarounds.
>
> To solve this problem correctly, oVirt needs to support customize routes.
> From my perspective, this workaround should not be formally documented.
>
> Thanks,
> Edy.
>
> On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:
>
>> Hi Doug,
>>
>> Thanks for the update, I'm glad that we could help and everything
>> worked out just fine!
>>
>> I also opened a BZ, asking to add a note in the documentation regarding
>> this issue.
>>
>> Thanks in advance,
>>
>> On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield 
>> wrote:
>>
>>> Lev,
>>>
>>> Just wanted to update you on the progress.  We created the persistent
>>> static routes and rules and the data is routing correctly over the required
>>> gateway.
>>>
>>>
>>>
>>> Thank you for all of your help!!!
>>>
>>>
>>>
>>> [image: Count On EMC] 
>>>
>>> *Doug Maxfield *| Senior Operating Systems Analyst
>>>
>>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>>> Tel: 515.345.4507 | Fax: 866.331.1522
>>> doug.l.maxfi...@emcins.com | www.emcins.com
>>>
>>>
>>>
>>>
>>>
>>> *From:* Lev Veyde 
>>> *Sent:* Thursday, February 14, 2019 9:14 AM
>>> *To:* Doug Maxfield 
>>> *Cc:* users 
>>> *Subject:* Re: [ovirt-users] Creating a static route
>>>
>>>
>>>
>>> Hi Doug,
>>>
>>> Just one more thing that I forgot to mention, even though it may be
>>> obvious - you can use subnets in both rules and routes.
>>>
>>> So if all the IPs you want to route sit in the same subnet then you can
>>> contain them with a single command e.g. "to 172.22.20.0/24 priority
>>> 32764"
>>>
>>> Thanks in advance,
>>>
>>>
>>>
>>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>>
>>> Hi Doug,
>>>
>>> Sure, np.
>>>
>>>
>>>
>>> >> 1. - yes it is the priority setting of the specific rule. Basically
>>> you put in the file the post "ip rule add" part of the command e.g. for "ip
>>> rule add to 172.22.20.31 priority 32764" you need to put a line of "to
>>> 172.22.20.31 priority 32764"
>>>
>>> >> 2. - yes, the same priority can be used for all of them. E.g. if you
>>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>>> add:
>>>
>>> to 172.22.20.31 priority 32764
>>> to 172.22.34.56 priority 32764
>>> to 172.22.67.89 priority 32764
>>>
>>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>>
>>>
>>>
>>> Please note that you will also need to add the static route for each one
>>> of these as well w/ "ip route add ... " command e.g. "ip route add
>>> 172.22.20.31 via 172.21.12.61".
>>>
>>> You can also use the route- putting just the route info
>>> part, similar to the "ip rule" e.g. for equivalent of "ip route add
>>> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
>>> content "172.22.20.31 via 172.21.12.61".
>>>
>>> For routes it's important to use specifically the route-ovirtmgmt file
>>> since the script automatically adds the device to the route command i.e.
>>> you can put the following lines into your route-ovirtmgmt file:
>>>
>>> 172.22.20.31 via 172.21.12.61
>>> 172.22.34.56 via 172.21.12.61
>>> 172.22.67.89 via 172.21.12.68
>>>
>>> (In case the first 2 of the mentioned IPs should be routed through the
>>> 172.21.12.61 gateway, and the last one should be routed through the
>>> 172.21.12.68 gateway).
>>>
>>>
>>>
>>> For the reference you can take a look at the
>>> /etc/sysconfig/network-scripts/ifup-routes script.
>>> It does the actual processing of both "route" and "rule" files for all
>>> network interfaces on a system.
>>>
>>>
>>>
>>> Please feel free to contact if you have further questions.
>>>
>>>
>>>
>>> Thanks in advance,
>>>
>>>
>>>
>>> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield <
>>> doug.l.maxfi...@emcins.com> wrote:
>>>
>>> Lev,
>>>
>>> Thanks for the response.  I was just getting ready to contact you about
>>> this.  I do have 2 follow-up questions, if you don’t mind.
>>>
>>>
>>>
>>>1. When we were talking about creating the route that would be
>>>enabled again after a reboot, you said to modify “the
>>>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt 
>>> or
>>>rule-eno3 (just put in the file "to 

[ovirt-users] Re: Local Storage domain to Shared

2019-02-20 Thread Greg Sheremeta
On Tue, Feb 19, 2019 at 6:03 PM Matt Simonsen  wrote:

> Hello all,
>
> I have a few nodes with local storage, and I've considered exporting
> them via NFS to migrate into shared storage, more than a few times.
>
> I have thought of this post on the ovirt-users list many times:
> https://lists.ovirt.org/pipermail/users/2017-December/085521.html
>
> Is this procedure documented & fully supported? Or is it something that
> just happens to work?
>

@Nir Soffer  what do you think?


>
> The instructions provided by Gianluca seem very clear. If this isn't
> documented better, ie: a blog for the site, what are the things that I
> should include to make it of value for going on the site?
>

Good questions. If it's supported and valuable, it should be documented
probably in the Admin Guide [
https://ovirt.org/documentation/admin-guide/administration-guide.html]
Else, perhaps a blog post would suffice. I much prefer /documentation,
though, if that makes sense to Nir.


>
> Thanks,
>
> Matt
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VEPO3YLV6TBUSCNGUESMYQDJHG43445V/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KFDGFE5CYOXBBKJWU7U2Z6GRH555CVF7/


[ovirt-users] Re: Ovirt project source code download problem

2019-02-20 Thread Greg Sheremeta
The documentation for setting up a developer environment for ovirt-engine
is currently in a poor state.
It might help you to use this role:
https://github.com/gregsheremeta/ovirt-engine-devel

Greg

On Wed, Feb 20, 2019 at 3:44 AM xil...@126.com  wrote:

>
> Thank you very much. I have found it now.
> --
> xil...@126.com
>
>
> *From:* Joey Ma 
> *Date:* 2019-02-20 15:13
> *To:* xilazz 
> *CC:* users 
> *Subject:* Re: [ovirt-users] Ovirt project source code download problem
> Hi,
>
> You could get all the source codes relevant to oVirt from Gerrit [1] and
> Github [2].
>
> [1]: https://gerrit.ovirt.org
> [2]: https://github.com/oVirt
>
> On Wed, Feb 20, 2019 at 3:02 PM  wrote:
>
>> Hi,The dear.
>> May I ask where I can find the source code of ovirt project? I want to
>> test the environment through compilation and installation. At present, most
>> of the methods are online installation, so I cannot modify some contents.
>> Thank you very much for your help. Thank you very much.
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WXKM46UDXFMHPOXY7TRQ6XXCSI5WER77/
>>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SDOT3FRCBQYJBYY4JN3TVOF3AQYNLZY6/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DFWFOH2AEQ64QTXMNIEE6SMHJERNYJXM/


[ovirt-users] Re: Facing issues with settings up shared data-center

2019-02-20 Thread Jinesh Ks
Hi Oliver,

Could you please have some light on this?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SHRZQJQAS7F667DCCTN6WSVOVP74LW3X/


[ovirt-users] Re: Creating a static route

2019-02-20 Thread Edward Haas
As mentioned in this thread oVirt currently does not support customized
routes.
It supports only a host level default route and per network gateways
(default route per network).

If someone understands well the Linux network details, workarounds may be
applied to overcome oVirt limitations.
With that said, as oVirt manages the host network details, the community
and future development cannot take into account such workarounds.

To solve this problem correctly, oVirt needs to support customize routes.
>From my perspective, this workaround should not be formally documented.

Thanks,
Edy.

On Tue, Feb 19, 2019 at 2:22 AM Lev Veyde  wrote:

> Hi Doug,
>
> Thanks for the update, I'm glad that we could help and everything
> worked out just fine!
>
> I also opened a BZ, asking to add a note in the documentation regarding
> this issue.
>
> Thanks in advance,
>
> On Mon, Feb 18, 2019 at 7:15 PM Doug Maxfield 
> wrote:
>
>> Lev,
>>
>> Just wanted to update you on the progress.  We created the persistent
>> static routes and rules and the data is routing correctly over the required
>> gateway.
>>
>>
>>
>> Thank you for all of your help!!!
>>
>>
>>
>> [image: Count On EMC] 
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Thursday, February 14, 2019 9:14 AM
>> *To:* Doug Maxfield 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] Creating a static route
>>
>>
>>
>> Hi Doug,
>>
>> Just one more thing that I forgot to mention, even though it may be
>> obvious - you can use subnets in both rules and routes.
>>
>> So if all the IPs you want to route sit in the same subnet then you can
>> contain them with a single command e.g. "to 172.22.20.0/24 priority
>> 32764"
>>
>> Thanks in advance,
>>
>>
>>
>> On Thu, Feb 14, 2019 at 4:59 PM Lev Veyde  wrote:
>>
>> Hi Doug,
>>
>> Sure, np.
>>
>>
>>
>> >> 1. - yes it is the priority setting of the specific rule. Basically
>> you put in the file the post "ip rule add" part of the command e.g. for "ip
>> rule add to 172.22.20.31 priority 32764" you need to put a line of "to
>> 172.22.20.31 priority 32764"
>>
>> >> 2. - yes, the same priority can be used for all of them. E.g. if you
>> want to route 172.22.20.31, 172.22.34.56 and 172.22.67.89 you will need to
>> add:
>>
>> to 172.22.20.31 priority 32764
>> to 172.22.34.56 priority 32764
>> to 172.22.67.89 priority 32764
>>
>> into the rule- file e.g. rule-ovirtmgmt or rule-eno3.
>>
>>
>>
>> Please note that you will also need to add the static route for each one
>> of these as well w/ "ip route add ... " command e.g. "ip route add
>> 172.22.20.31 via 172.21.12.61".
>>
>> You can also use the route- putting just the route info
>> part, similar to the "ip rule" e.g. for equivalent of "ip route add
>> 172.22.20.31 via 172.21.12.61" you need put in the file a line with the
>> content "172.22.20.31 via 172.21.12.61".
>>
>> For routes it's important to use specifically the route-ovirtmgmt file
>> since the script automatically adds the device to the route command i.e.
>> you can put the following lines into your route-ovirtmgmt file:
>>
>> 172.22.20.31 via 172.21.12.61
>> 172.22.34.56 via 172.21.12.61
>> 172.22.67.89 via 172.21.12.68
>>
>> (In case the first 2 of the mentioned IPs should be routed through the
>> 172.21.12.61 gateway, and the last one should be routed through the
>> 172.21.12.68 gateway).
>>
>>
>>
>> For the reference you can take a look at the
>> /etc/sysconfig/network-scripts/ifup-routes script.
>> It does the actual processing of both "route" and "rule" files for all
>> network interfaces on a system.
>>
>>
>>
>> Please feel free to contact if you have further questions.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> On Thu, Feb 14, 2019 at 3:39 PM Doug Maxfield 
>> wrote:
>>
>> Lev,
>>
>> Thanks for the response.  I was just getting ready to contact you about
>> this.  I do have 2 follow-up questions, if you don’t mind.
>>
>>
>>
>>1. When we were talking about creating the route that would be
>>enabled again after a reboot, you said to modify “the
>>/etc/sysconfig/network-scripts/rule- e.g. rule-ovirtmgmt 
>> or
>>rule-eno3 (just put in the file "to 172.22.20.31 priority 32764”.  Is
>>priority 32764 for the ip rule command?
>>2. If I have multiple IPs that I would need to create a static route,
>>would the priority be 32764 for all of them?
>>
>>
>>
>> Once again, thank you for all of your help with this!!
>>
>>
>>
>> [image: Count On EMC] 
>>
>> *Doug Maxfield *| Senior Operating Systems Analyst
>>
>> *EMC Insurance Companies *717 Mulberry St | Des Moines, IA 50265
>> Tel: 515.345.4507 | Fax: 866.331.1522
>> doug.l.maxfi...@emcins.com | www.emcins.com
>>
>>
>>
>>
>>
>> *From:* Lev Veyde 
>> *Sent:* Thursday, February 14, 2019 3:19 AM
>> 

[ovirt-users] Re: VM stats are not shown in HE-web interface and MOM is not available

2019-02-20 Thread Andrej Krejcir
Hi,

Check if ovirt-guest-agent is installed on the VM.
If not, some statistics can be missing, like free memory on the VM.

If you are using version 4.3, the MOM issue will be fixed by:
https://bugzilla.redhat.com/show_bug.cgi?id=1676695


Best regards,
Andrej

On Wed, 20 Feb 2019 at 09:25,  wrote:

> So the problem is that virtual machine statistics are not shown in Ovirt
> Virualization Manager and something is wrong with MOM service.
>
> [root@ovirt-04 ~]# service vdsmd status
> Redirecting to /bin/systemctl status vdsmd.service
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Tue 2019-02-19 17:13:31 MSK; 16h ago
>  Main PID: 17676 (vdsmd)
> Tasks: 63
>CGroup: /system.slice/vdsmd.service
>├─17676 /usr/bin/python2 /usr/share/vdsm/vdsmd
>├─26249 /usr/libexec/ioprocess --read-pipe-fd 77
> --write-pipe-fd 76 --max-threads 10 --max-queued-requests 10
>└─26269 /usr/libexec/ioprocess --read-pipe-fd 82
> --write-pipe-fd 81 --max-threads 10 --max-queued-requests 10
>
> Feb 20 09:11:14 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
> Feb 20 09:11:14 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available,
> KSM stats will be missing.
> Feb 20 09:23:47 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
> Feb 20 09:23:47 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available,
> KSM stats will be missing.
> Feb 20 09:36:20 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
> Feb 20 09:36:20 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available,
> KSM stats will be missing.
> Feb 20 09:48:53 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
> Feb 20 09:48:53 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available,
> KSM stats will be missing.
> Feb 20 10:01:25 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
> Feb 20 10:01:25 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available,
> KSM stats will be missing.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/CWUZHHGBTF7FYPDZX5N5MPNEBUNU7T7R/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/R332MYBONBHHRPJ4GN26UXCICPEG5Z3A/


[ovirt-users] Re: Ovirt project source code download problem

2019-02-20 Thread xil...@126.com

Thank you very much. I have found it now.


xil...@126.com
 
From: Joey Ma
Date: 2019-02-20 15:13
To: xilazz
CC: users
Subject: Re: [ovirt-users] Ovirt project source code download problem
Hi,

You could get all the source codes relevant to oVirt from Gerrit [1] and Github 
[2].

[1]: https://gerrit.ovirt.org
[2]: https://github.com/oVirt

On Wed, Feb 20, 2019 at 3:02 PM  wrote:
Hi,The dear.
May I ask where I can find the source code of ovirt project? I want to test the 
environment through compilation and installation. At present, most of the 
methods are online installation, so I cannot modify some contents.
Thank you very much for your help. Thank you very much.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WXKM46UDXFMHPOXY7TRQ6XXCSI5WER77/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SDOT3FRCBQYJBYY4JN3TVOF3AQYNLZY6/


[ovirt-users] VM stats are not shown in HE-web interface and MOM is not available

2019-02-20 Thread v . voroncov
So the problem is that virtual machine statistics are not shown in Ovirt 
Virualization Manager and something is wrong with MOM service.

[root@ovirt-04 ~]# service vdsmd status
Redirecting to /bin/systemctl status vdsmd.service
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Tue 2019-02-19 17:13:31 MSK; 16h ago
 Main PID: 17676 (vdsmd)
Tasks: 63
   CGroup: /system.slice/vdsmd.service
   ├─17676 /usr/bin/python2 /usr/share/vdsm/vdsmd
   ├─26249 /usr/libexec/ioprocess --read-pipe-fd 77 --write-pipe-fd 76 
--max-threads 10 --max-queued-requests 10
   └─26269 /usr/libexec/ioprocess --read-pipe-fd 82 --write-pipe-fd 81 
--max-threads 10 --max-queued-requests 10

Feb 20 09:11:14 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
Feb 20 09:11:14 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available, KSM 
stats will be missing.
Feb 20 09:23:47 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
Feb 20 09:23:47 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available, KSM 
stats will be missing.
Feb 20 09:36:20 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
Feb 20 09:36:20 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available, KSM 
stats will be missing.
Feb 20 09:48:53 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
Feb 20 09:48:53 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available, KSM 
stats will be missing.
Feb 20 10:01:25 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available.
Feb 20 10:01:25 ovirt-04.scanru.local vdsm[17676]: WARN MOM not available, KSM 
stats will be missing.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CWUZHHGBTF7FYPDZX5N5MPNEBUNU7T7R/