Re: [ovirt-users] routing

2018-05-06 Thread Justin Zygmont
Thanks for the reply,

Ok I see what you’re saying, its just confusing because there are several 
places that mention the gateways and none of them are clear on what they’re 
doing.
For example, under Cluster > Networks > Manage Networks,  default route is only 
selectable for 1 network, yet in each network you create there is still the 
option of choosing a IP address and gateway.

Even if I don’t put in any IP or gateway for a tagged vlan, it still depends of 
the management gateway to forward to the router.  I thought I should be able to 
lose the management network and still have all the tagged vlans working?



From: Edward Haas [mailto:eh...@redhat.com]
Sent: Sunday, May 6, 2018 7:34 AM
To: Justin Zygmont 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] routing

Not sure if I understand what you are asking here, but the need for a gateway 
per network has emerged from the need to support other host networks (not VM 
networks) beside the management one.
As an example, migration and storage networks can be defined, each passing 
dedicated traffic (one for storage communication and another for VM migration 
traffic), they may need to pass through different gateways.
So the management network can be accessed using gateway A, storage using B and 
migration using C. A will usually be set on a host level as the host default 
gateway, and the others will be set for the individual networks.
Otherwise, how would you expect storage to use a different router (than the 
management one) in the network?
Thanks,
Edy.

On Thu, May 3, 2018 at 1:08 AM, Justin Zygmont 
> wrote:
I don’t understand why you would want this unless the ovirtnode itself was 
actually the router, wouldn’t you want to only have an IP on the management 
network, and leave the rest of the VLANS blank so they depend on the router to 
route the traffic:

NIC1  -> ovirt-mgmt  - gateway set
NIC2  -> VLAN3, VLAN4, etc…


https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/

Viewing or Editing the Gateway for a Logical Network
Users can define the gateway, along with the IP address and subnet mask, for a 
logical network. This is necessary when multiple networks exist on a host and 
traffic should be routed through the specified network, rather than the default 
gateway.
If multiple networks exist on a host and the gateways are not defined, return 
traffic will be routed through the default gateway, which may not reach the 
intended destination. This would result in users being unable to ping the host.
oVirt handles multiple gateways automatically whenever an interface goes up or 
down.



___
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] Re-attaching ISOs and moving ISOs storage

2018-05-06 Thread Fred Rolland
I am trying to reproduce this on my setup, with no success for now.
Can you share the engine log corresponding to the time you tried to detach?

What are the options available currently?
I understand that "Activate" does not work, what about "Detach"?

Can your hosts access the ISO domain?


On Fri, May 4, 2018 at 2:09 PM, Callum Smith  wrote:

> Is there any sensible way to either clean up the existing ISOs storage or
> re-attach it? I'm struggling to even export VMs and migrate them elsewhere
> with this and need to recover them asap.
>
> Regards,
> Callum
>
> --
>
> Callum Smith
> Research Computing Core
> Wellcome Trust Centre for Human Genetics
> University of Oxford
> e. cal...@well.ox.ac.uk
>
> On 2 May 2018, at 15:09, Callum Smith  wrote:
>
> Attached, thank you for looking into this
>
>
> https://*HOSTNAME*/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae
>
>  href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae"
>  id="f5914df0-f46c-4cc0-b666-c929aa0225ae"> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/isattached"
>  rel="isattached"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/reduceluns"
>  rel="reduceluns"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/refreshluns"
>  rel="refreshluns"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/updateovfstore"
>  rel="updateovfstore"/>VMISOs href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/disksnapshots"
>  rel="disksnapshots"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/files"
>  rel="files"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/diskprofiles"
>  rel="diskprofiles"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/storageconnections"
>  rel="storageconnections"/> href="/ovirt-engine/api/v4/storagedomains/f5914df0-f46c-4cc0-b666-c929aa0225ae/permissions"
>  rel="permissions"/>11770357874688
> false0
> 5
> false
> okfalse  
>   backoffice01.cluster/vm-iso 
>nfsv1
> false
> false
> iso38654705664
> 10
> false
>  href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304" 
> id="5a54bf81-0228-02bc-0358-0304"/>
> 
>
>
> https://*HOSTNAME*/ovirt-engine/api/v4/datacenters/5a54bf81-
> 0228-02bc-0358-0304/storagedomains
>
> 
>  href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/d9f8093b-71cd-423d-9b7d-91a613ef98ba"
>  id="d9f8093b-71cd-423d-9b7d-91a613ef98ba"> href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/d9f8093b-71cd-423d-9b7d-91a613ef98ba/activate"
>  rel="activate"/> href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/d9f8093b-71cd-423d-9b7d-91a613ef98ba/deactivate"
>  rel="deactivate"/>
> tegile-virtman-backup href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/d9f8093b-71cd-423d-9b7d-91a613ef98ba/disks"
>  rel="disks"/>17519171600384
> false0
> 5
> false
> okfalse
> maintenance
> 192.168.64.248auto  
>   /export/virtman/backupnfs 
>v1
> false
> false
> export8589934592
> 10
> false href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304" 
> id="5a54bf81-0228-02bc-0358-0304"/>
>  href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304" 
> id="5a54bf81-0228-02bc-0358-0304"/>
>  href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/017dd620-65ec-4fa4-8d46-67737dedd7a1"
>  id="017dd620-65ec-4fa4-8d46-67737dedd7a1"> href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/017dd620-65ec-4fa4-8d46-67737dedd7a1/activate"
>  rel="activate"/> href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/017dd620-65ec-4fa4-8d46-67737dedd7a1/deactivate"
>  rel="deactivate"/>VMStorage
>  href="/ovirt-engine/api/v4/datacenters/5a54bf81-0228-02bc-0358-0304/storagedomains/017dd620-65ec-4fa4-8d46-67737dedd7a1/disks"
>  rel="disks"/>11770357874688
> false118111600640
> 5
> false
> oktrue
> active
> backoffice01.cluster/vm-storage2  
>   nfs
> v4

Re: [ovirt-users] routing

2018-05-06 Thread Edward Haas
Not sure if I understand what you are asking here, but the need for a
gateway per network has emerged from the need to support other host
networks (not VM networks) beside the management one.
As an example, migration and storage networks can be defined, each passing
dedicated traffic (one for storage communication and another for VM
migration traffic), they may need to pass through different gateways.
So the management network can be accessed using gateway A, storage using B
and migration using C. A will usually be set on a host level as the host
default gateway, and the others will be set for the individual networks.

Otherwise, how would you expect storage to use a different router (than the
management one) in the network?

Thanks,
Edy.


On Thu, May 3, 2018 at 1:08 AM, Justin Zygmont 
wrote:

> I don’t understand why you would want this unless the ovirtnode itself was
> actually the router, wouldn’t you want to only have an IP on the management
> network, and leave the rest of the VLANS blank so they depend on the router
> to route the traffic:
>
>
>
> NIC1  -> ovirt-mgmt  - gateway set
>
> NIC2  -> VLAN3, VLAN4, etc…
>
>
>
>
>
> https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/
>
>
>
> *Viewing or Editing the Gateway for a Logical Network*
>
> Users can define the gateway, along with the IP address and subnet mask,
> for a logical network. This is necessary when multiple networks exist on a
> host and traffic should be routed through the specified network, rather
> than the default gateway.
>
> If multiple networks exist on a host and the gateways are not defined,
> return traffic will be routed through the default gateway, which may not
> reach the intended destination. This would result in users being unable to
> ping the host.
>
> oVirt handles multiple gateways automatically whenever an interface goes
> up or down.
>
>
>
>
>
> ___
> 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] adding a host

2018-05-06 Thread Alona Kaplan
There was a bug when adding a host to a cluster that contains a required
network. It was fixed in 4.2.3.4.

Bug-Url- https://bugzilla.redhat.com/1570388

Thanks,
Alona.

On Sun, May 6, 2018 at 3:49 PM, Yanir Quinn  wrote:

> For removing the non operational host :
> 1.Right click on the host name
> 2.Click on  "Confirm host has been rebooted"
> 3.Remove the host
>
>
> For the issue you are experiencing with host addition, according to the
> engine logs you have sent, you might need to perform a few steps ,  see:
> https://bugzilla.redhat.com/show_bug.cgi?id=1516256#c2
>
> I would also recommend to check the the host's network is not down.
> Also, during installation of the host,observe the messages in the Events
> section (UI)
>
> Hope this helps.
>
>
>
>
> On Thu, May 3, 2018 at 10:07 PM, Justin Zygmont 
> wrote:
>
>> I can’t seem to do anything to control the host from the engine, when I
>> select it for Maint, the engine log shows:
>>
>>
>>
>> [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default
>> task-50) [90ba81ef-21e4-4272-8c59-84786e969ff7] Running command:
>> MaintenanceNumberOfVdssCommand internal: false. Entities affected :  ID:
>> 74dfe965-cb11-495a-96a0-3dae6b3cbd75 Type: VDSAction group
>> MANIPULATE_HOST with role type ADMIN
>>
>> 2018-05-03 12:00:37,918-07 INFO  
>> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
>> (default task-50) [90ba81ef-21e4-4272-8c59-84786e969ff7] START,
>> SetVdsStatusVDSCommand(HostName = ovnode102,
>> SetVdsStatusVDSCommandParameters:{hostId='74dfe965-cb11-495a-96a0-3dae6b3cbd75',
>> status='PreparingForMaintenance', nonOperationalReason='NONE',
>> stopSpmFailureLogged='true', maintenanceReason='null'}), log id: 647d5f78
>>
>>
>>
>>
>>
>> I have only 1 host in the DC, status is Up, the cluster says host count
>> is 2 even though the second host stays Non Operational.  I don’t know how
>> to remove it.
>>
>> I just installed and tried to join the DC, this is a fresh installation,
>> the engine was launched through cockpit.
>>
>>
>>
>> Heres what nodectl shows from the host:
>>
>>
>>
>> ovnode102 ~]# nodectl check
>>
>> Status: OK
>>
>> Bootloader ... OK
>>
>>   Layer boot entries ... OK
>>
>>   Valid boot entries ... OK
>>
>> Mount points ... OK
>>
>>   Separate /var ... OK
>>
>>   Discard is used ... OK
>>
>> Basic storage ... OK
>>
>>   Initialized VG ... OK
>>
>>   Initialized Thin Pool ... OK
>>
>>   Initialized LVs ... OK
>>
>> Thin storage ... OK
>>
>>   Checking available space in thinpool ... OK
>>
>>   Checking thinpool auto-extend ... OK
>>
>> vdsmd ... OK
>>
>>
>>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>>
>>
>> *From:* Yanir Quinn [mailto:yqu...@redhat.com]
>> *Sent:* Thursday, May 3, 2018 1:19 AM
>>
>> *To:* Justin Zygmont 
>> *Cc:* users@ovirt.org
>> *Subject:* Re: [ovirt-users] adding a host
>>
>>
>>
>> Did you try switching the host to maintenance mode first ?
>>
>> What is the state of the data center and how many active hosts do you
>> have now?
>>
>> And did you perform any updates recently or just run a fresh installation
>> ?  if so , did you run engine-setup before launching engine ?
>>
>>
>>
>> On Thu, May 3, 2018 at 12:47 AM, Justin Zygmont 
>> wrote:
>>
>> I read this page and it doesn’t help since this is a host that can’t be
>> removed, the “remove” button is dimmed out.
>>
>>
>>
>> This is 4.22 ovirt node, but the host stays in a “non operational”
>> state.  I notice the logs have a lot of errors, for example:
>>
>>
>>
>>
>>
>> the SERVER log:
>>
>>
>>
>> 2018-05-02 14:40:23,847-07 WARN  
>> [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
>> (ForkJoinPool-1-worker-14) IJ000609: Attempt to return connection twice:
>> org.jboss.jca.core.connectionmanager.listener.TxConnectionLi
>> stener@1fab84d7[state=NORMAL managed connection=org.jboss.jca.adapt
>> ers.jdbc.local.LocalManagedConnection@3f37cf10 connection handles=0
>> lastReturned=1525297223847 lastValidated=1525290267811
>> lastCheckedOut=1525296923770 trackByTx=false
>> pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@20550f35
>> mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@5baa90f[pool=ENGINEDataSource]
>> xaResource=LocalXAResourceImpl@24a7fc0b[connectionListener=1fab84d7
>> connectionManager=5bec70d2 warned=false currentXid=null
>> productName=PostgreSQL productVersion=9.5.9 jndiName=java:/ENGINEDataSource]
>> txSync=null]: java.lang.Throwable: STACKTRACE
>>
>> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcu
>> rrentLinkedDequeManagedConnectionPool.returnConnection(Semap
>> horeConcurrentLinkedDequeManagedConnectionPool.java:722)
>>
>> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcu
>> rrentLinkedDequeManagedConnectionPool.returnConnection(Semap
>> horeConcurrentLinkedDequeManagedConnectionPool.java:611)
>>
>> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.
>> 

Re: [ovirt-users] problem to create snapshot

2018-05-06 Thread Ala Hino
[Please always CC ovirt-users so other engineer can provide help]

It seems that the storage domain is corrupted.
Can you please run the following command and send the output?

vdsm-client StorageDomain getInfo storagedomainID=

You may need to move the storage to maintenance and re-initialize it.

On Thu, May 3, 2018 at 10:10 PM, Marcelo Leandro 
wrote:

> Hello,
>
> Thank you for reply:
>
> oVirt Version -  4.1.9
> Vdsm Versoin - 4.20.23
>
> attached logs,
>
> Very Thanks.
>
> Marcelo Leandro
>
> 2018-05-03 15:59 GMT-03:00 Ala Hino :
>
>> Can you please share more info?
>> - The version you are using
>> - Full log of vdsm and the engine
>>
>> Is the VM running or down while creating the snapshot?
>>
>> On Thu, May 3, 2018 at 8:32 PM, Marcelo Leandro 
>> wrote:
>>
>>> Anyone help me?
>>>
>>> 2018-05-02 17:55 GMT-03:00 Marcelo Leandro :
>>>
 Hello ,

 I am geting error when try do a snapshot:

 Error msg in SPM log.

 2018-05-02 17:46:11,235-0300 WARN  (tasks/2) [storage.ResourceManager]
 Resource factory failed to create resource '01_img_6e5cce71-3438-4045-9d5
 4-607123e0557e.ed7f1c0f-5986-4979-b783-5c465b0854c6'. Canceling
 request. (resourceManager:543)
 Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py",
 line 539, in registerResource
 obj = namespaceObj.factory.createResource(name, lockType)
   File 
 "/usr/lib/python2.7/site-packages/vdsm/storage/resourceFactories.py",
 line 193, in createResource
 lockType)
   File 
 "/usr/lib/python2.7/site-packages/vdsm/storage/resourceFactories.py",
 line 122, in __getResourceCandidatesList
 imgUUID=resourceName)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line
 213, in getChain
 if srcVol.isLeaf():
   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line
 1430, in isLeaf
 return self._manifest.isLeaf()
   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line
 138, in isLeaf
 return self.getVolType() == sc.type2name(sc.LEAF_VOL)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line
 134, in getVolType
 self.voltype = self.getMetaParam(sc.VOLTYPE)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line
 118, in getMetaParam
 meta = self.getMetadata()
   File "/usr/lib/python2.7/site-packages/vdsm/storage/blockVolume.py",
 line 112, in getMetadata
 md = VolumeMetadata.from_lines(lines)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/volumemetadata.py",
 line 103, in from_lines
 "Missing metadata key: %s: found: %s" % (e, md))
 MetaDataKeyNotFoundError: Meta Data key not found error: ("Missing
 metadata key: 'DOMAIN': found: {'NONE': '#
 
 
 
 
 
 
 
 #'}",)
 2018-05-02 17:46:11,286-0300 WARN  (tasks/2)
 [storage.ResourceManager.Request] (ResName='01_img_6e5cce71-3438
 -4045-9d54-607123e0557e.ed7f1c0f-5986-4979-b783-5c465b0854c6',
 ReqID='a3cd9388-977b-45b9-9aa0-e431aeff8750') Tried to cancel a
 processed request (resourceManager:187)
 2018-05-02 17:46:11,286-0300 ERROR (tasks/2) [storage.TaskManager.Task]
 (Task='ba0766ca-08a1-4d65-a4e9-1e0171939037') Unexpected error
 (task:875)
 Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line
 882, in _run
 return fn(*args, **kargs)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line
 336, in run
 return self.cmd(*self.argslist, **self.argsdict)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py",
 line 79, in wrapper
 return method(self, *args, **kwargs)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line
 1938, in createVolume
 with rm.acquireResource(img_ns, imgUUID, rm.EXCLUSIVE):
   File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py",
 line 1025, in acquireResource
 return _manager.acquireResource(namespace, name, lockType,
 timeout=timeout)
   File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py",
 line 475, in acquireResource
 raise se.ResourceAcqusitionFailed()
 

Re: [ovirt-users] managing local users in 4.2 ?

2018-05-06 Thread Alex K
Indeed the behaviour has not changed.
When adding users at 4.1 with ovirt-aaa-jdbc-tool i still need to add them
through gui for users to be listed in gui.

Alex


On Sun, May 6, 2018, 12:58 Martin Perina  wrote:

>
>
> On Fri, 4 May 2018, 15:59 Matthias Leopold, <
> matthias.leop...@meduniwien.ac.at> wrote:
>
>> Am 2018-05-04 um 12:36 schrieb Matthias Leopold:
>> > Hi,
>> >
>> > i tried to create a local user in oVirt 4.2 with "ovirt-aaa-jdbc-tool
>> > user add" (like i did in oVirt 4.1.9). the command worked ok, but the
>> > created user wasn't visible in the web gui. i then used the "add"
>> button
>> > in admin portal to add the already existing user and after that the
>> user
>> > was visible. i didn't have to do that in 4.1.9, the "add" button was
>> > already there the, but i didn't know what to do with it. how did
>> > managing local users change in 4.2?
>> >
>>
>> ok, i got it: only after setting actual permissions for a user he/she
>> appears automatically in Admin Portal - Administration - Users. this was
>> different in 4.1.9 IIRC
>>
>
> Sorry, but that behavior didn't change since 3.5/3.6. Only users which has
> directly assigned a permission are listed there. But those users are
> visible in all Add Permission tabs right after creating by aaa-jdbc tool.
>
>
>> matthias
>> ___
>> 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] adding a host

2018-05-06 Thread Yanir Quinn
For removing the non operational host :
1.Right click on the host name
2.Click on  "Confirm host has been rebooted"
3.Remove the host


For the issue you are experiencing with host addition, according to the
engine logs you have sent, you might need to perform a few steps ,  see:
https://bugzilla.redhat.com/show_bug.cgi?id=1516256#c2

I would also recommend to check the the host's network is not down.
Also, during installation of the host,observe the messages in the Events
section (UI)

Hope this helps.




On Thu, May 3, 2018 at 10:07 PM, Justin Zygmont 
wrote:

> I can’t seem to do anything to control the host from the engine, when I
> select it for Maint, the engine log shows:
>
>
>
> [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default
> task-50) [90ba81ef-21e4-4272-8c59-84786e969ff7] Running command:
> MaintenanceNumberOfVdssCommand internal: false. Entities affected :  ID:
> 74dfe965-cb11-495a-96a0-3dae6b3cbd75 Type: VDSAction group
> MANIPULATE_HOST with role type ADMIN
>
> 2018-05-03 12:00:37,918-07 INFO  
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (default task-50) [90ba81ef-21e4-4272-8c59-84786e969ff7] START,
> SetVdsStatusVDSCommand(HostName = ovnode102,
> SetVdsStatusVDSCommandParameters:{hostId='74dfe965-cb11-495a-96a0-3dae6b3cbd75',
> status='PreparingForMaintenance', nonOperationalReason='NONE',
> stopSpmFailureLogged='true', maintenanceReason='null'}), log id: 647d5f78
>
>
>
>
>
> I have only 1 host in the DC, status is Up, the cluster says host count is
> 2 even though the second host stays Non Operational.  I don’t know how to
> remove it.
>
> I just installed and tried to join the DC, this is a fresh installation,
> the engine was launched through cockpit.
>
>
>
> Heres what nodectl shows from the host:
>
>
>
> ovnode102 ~]# nodectl check
>
> Status: OK
>
> Bootloader ... OK
>
>   Layer boot entries ... OK
>
>   Valid boot entries ... OK
>
> Mount points ... OK
>
>   Separate /var ... OK
>
>   Discard is used ... OK
>
> Basic storage ... OK
>
>   Initialized VG ... OK
>
>   Initialized Thin Pool ... OK
>
>   Initialized LVs ... OK
>
> Thin storage ... OK
>
>   Checking available space in thinpool ... OK
>
>   Checking thinpool auto-extend ... OK
>
> vdsmd ... OK
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> *From:* Yanir Quinn [mailto:yqu...@redhat.com]
> *Sent:* Thursday, May 3, 2018 1:19 AM
>
> *To:* Justin Zygmont 
> *Cc:* users@ovirt.org
> *Subject:* Re: [ovirt-users] adding a host
>
>
>
> Did you try switching the host to maintenance mode first ?
>
> What is the state of the data center and how many active hosts do you have
> now?
>
> And did you perform any updates recently or just run a fresh installation
> ?  if so , did you run engine-setup before launching engine ?
>
>
>
> On Thu, May 3, 2018 at 12:47 AM, Justin Zygmont 
> wrote:
>
> I read this page and it doesn’t help since this is a host that can’t be
> removed, the “remove” button is dimmed out.
>
>
>
> This is 4.22 ovirt node, but the host stays in a “non operational” state.
> I notice the logs have a lot of errors, for example:
>
>
>
>
>
> the SERVER log:
>
>
>
> 2018-05-02 14:40:23,847-07 WARN  [org.jboss.jca.core.
> connectionmanager.pool.strategy.OnePool] (ForkJoinPool-1-worker-14)
> IJ000609: Attempt to return connection twice: org.jboss.jca.core.
> connectionmanager.listener.TxConnectionListener@1fab84d7[state=NORMAL
> managed connection=org.jboss.jca.adapters.jdbc.local.
> LocalManagedConnection@3f37cf10 connection handles=0
> lastReturned=1525297223847 lastValidated=1525290267811
> lastCheckedOut=1525296923770 trackByTx=false pool=org.jboss.jca.core.
> connectionmanager.pool.strategy.OnePool@20550f35 mcp=
> SemaphoreConcurrentLinkedQueueManagedConnectionPool@5baa90f[pool=ENGINEDataSource]
> xaResource=LocalXAResourceImpl@24a7fc0b[connectionListener=1fab84d7
> connectionManager=5bec70d2 warned=false currentXid=null
> productName=PostgreSQL productVersion=9.5.9 jndiName=java:/ENGINEDataSource]
> txSync=null]: java.lang.Throwable: STACKTRACE
>
> at org.jboss.jca.core.connectionmanager.pool.mcp.
> SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection(
> SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:722)
>
> at org.jboss.jca.core.connectionmanager.pool.mcp.
> SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection(
> SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:611)
>
> at org.jboss.jca.core.connectionmanager.pool.
> AbstractPool.returnConnection(AbstractPool.java:847)
>
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.
> returnManagedConnection(AbstractConnectionManager.java:725)
>
> at org.jboss.jca.core.connectionmanager.tx.
> TxConnectionManagerImpl.managedConnectionDisconnected(
> TxConnectionManagerImpl.java:585)
>
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.
> 

Re: [ovirt-users] managing local users in 4.2 ?

2018-05-06 Thread Martin Perina
On Fri, 4 May 2018, 15:59 Matthias Leopold, <
matthias.leop...@meduniwien.ac.at> wrote:

> Am 2018-05-04 um 12:36 schrieb Matthias Leopold:
> > Hi,
> >
> > i tried to create a local user in oVirt 4.2 with "ovirt-aaa-jdbc-tool
> > user add" (like i did in oVirt 4.1.9). the command worked ok, but the
> > created user wasn't visible in the web gui. i then used the "add" button
> > in admin portal to add the already existing user and after that the user
> > was visible. i didn't have to do that in 4.1.9, the "add" button was
> > already there the, but i didn't know what to do with it. how did
> > managing local users change in 4.2?
> >
>
> ok, i got it: only after setting actual permissions for a user he/she
> appears automatically in Admin Portal - Administration - Users. this was
> different in 4.1.9 IIRC
>

Sorry, but that behavior didn't change since 3.5/3.6. Only users which has
directly assigned a permission are listed there. But those users are
visible in all Add Permission tabs right after creating by aaa-jdbc tool.


> matthias
> ___
> 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] ansible failure during host install

2018-05-06 Thread Shirly Radco
--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Sun, May 6, 2018 at 12:47 PM, Shirly Radco  wrote:

> If you did not install the Openshift based metrics store you need to
> remove the /etc/ovirt-engine-metrics-config.yml file.
>

Sorry. Remove  /etc/ovirt-engine-metrics/config.yml

It is only required while setting up the metrics store.
>
> This should fix you host install issue, ansible will skip the roles
> related to the metrics configuration on the host.
> If you are interested in setting up the metrics store you can have a look
> at https://www.ovirt.org/develop/release-management/
> features/metrics/metrics-store/
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 
>
> On Fri, May 4, 2018 at 1:20 AM, Young, Matthew (Numerical Algorithms
> Group)  wrote:
>
>> I’ve gotten past that error with “oc delete route/docker-registry” before
>> restart the playbook
>>
>>
>>
>> Matt
>>
>>
>>
>> *From:* Young, Matthew (Numerical Algorithms Group)
>> *Sent:* Thursday, May 3, 2018 4:02 PM
>> *To:* 'Shirly Radco' 
>> *Cc:* users 
>> *Subject:* RE: [ovirt-users] ansible failure during host install
>>
>>
>>
>> Ovirt-engine-metrics v1.1.3.4
>>
>>
>>
>> /etc/ovirt-engine-metrics/config.yml:
>>
>>   ovirt_env_name: data-science-sandbox
>>
>>   fluentd_elasticsearch_host: ovirt-metrics.datasci.bp.com
>>
>>   ovirt_elasticsearch_mounted_storage_path: /data
>>
>>
>>
>> I have not gotten the openshift based metrics store running.  It is
>> consistently timing out while performing “TASK [openshift_hosted :
>> Configure a passthrough route for docker-registry].”
>>
>> Failure summary:
>>
>>   1. Hosts:localhost
>>
>>  Play: Create Hosted Resources - registry
>>
>>  Task: Configure a passthrough route for docker-registry
>>
>>  Message:  {u'cmd': u'/usr/bin/oc replace -f
>> /tmp/docker-registry-DtGZqz --force -n default', u'returncode': 1,
>> u'results': {}, u'stderr': u'error: timed out waiting for the condition\n',
>> u'stdout': u'route "docker-registry" deleted\n'}
>>
>>
>>
>> Matt Young
>>
>>
>>
>> *From:* Shirly Radco 
>> *Sent:* Thursday, April 12, 2018 4:04 PM
>> *To:* Young, Matthew (Numerical Algorithms Group) 
>> *Cc:* users 
>> *Subject:* Re: [ovirt-users] ansible failure during host install
>>
>>
>>
>> Hi,
>>
>>
>>
>> What version of ovirt-engine-metrics are you using?
>>
>>
>>
>> Did you already setup the OpenShift based metrics store to connect to?
>>
>>
>>
>> Have you configured /etc/ovirt-engine-metrics/config.yml?
>>
>>
>>
>> --
>>
>> SHIRLY RADCO
>>
>> BI SENIOR SOFTWARE ENGINEER
>>
>> Red Hat Israel
>>
>>
>> TRIED. TESTED. TRUSTED.
>>
>>
>>
>>
>>
>> On Thu, Apr 12, 2018, 21:35 Young, Matthew (Numerical Algorithms Group) <
>> matthew.you...@bp.com> wrote:
>>
>> Hello all,
>>
>>
>>
>> I have been working on adding a new host to an oVirt cluster.  The
>> installation is failing in the ansible portion, specifically installing the
>> ansible elasticsearch ca cert.  I have no experience with ansible.  Does
>> anyone know what is causing this issue?  Or how to create this ca cert?
>>
>>
>>
>>  from ansible log
>>
>> …
>>
>> 2018-04-12 09:32:18,114 p=56616 u=ovirt |  TASK
>> [oVirt.ovirt-fluentd/fluentd-setup : Create fluentd.conf]
>> *
>>
>> 2018-04-12 09:32:18,730 p=56616 u=ovirt |  ok: [10.222.10.156] => {
>>
>> "changed": false,
>>
>> "checksum": "c9f88b60cd12ab8e3f3ffce1ae07654c89b06ef6",
>>
>> "gid": 0,
>>
>> "group": "root",
>>
>> "mode": "0640",
>>
>> "owner": "root",
>>
>> "path": "/etc/fluentd/fluent.conf",
>>
>> "secontext": "system_u:object_r:etc_t:s0",
>>
>> "size": 58,
>>
>> "state": "file",
>>
>> "uid": 0
>>
>> }
>>
>> 2018-04-12 09:32:18,739 p=56616 u=ovirt |  TASK
>> [oVirt.ovirt-fluentd/fluentd-setup : Install fluentd certificate]
>> *
>>
>> 2018-04-12 09:32:18,759 p=56616 u=ovirt |  skipping: [10.222.10.156] => {
>>
>> "changed": false,
>>
>> "skip_reason": "Conditional result was False"
>>
>> }
>>
>> 2018-04-12 09:32:18,768 p=56616 u=ovirt |  TASK
>> [oVirt.ovirt-fluentd/fluentd-setup : Install fluentd elasticsearch CA
>> certificate] ***
>>
>> 2018-04-12 09:32:18,810 p=56616 u=ovirt |  fatal: [10.222.10.156]:
>> FAILED! => {
>>
>> "changed": false
>>
>> }
>>
>>
>>
>> MSG:
>>
>>
>>
>> src (or content) is required
>>
>>
>>
>> 2018-04-12 09:32:18,812 p=56616 u=ovirt |  PLAY RECAP
>> *
>>
>> 2018-04-12 09:32:18,812 p=56616 u=ovirt |  10.222.10.156  :
>> ok=33   changed=4unreachable=0failed=1
>>
>>
>>
>> 
>>
>> 

Re: [ovirt-users] ansible failure during host install

2018-05-06 Thread Shirly Radco
If you did not install the Openshift based metrics store you need to remove
the /etc/ovirt-engine-metrics-config.yml file.
It is only required while setting up the metrics store.

This should fix you host install issue, ansible will skip the roles related
to the metrics configuration on the host.
If you are interested in setting up the metrics store you can have a look
at
https://www.ovirt.org/develop/release-management/features/metrics/metrics-store/

--

SHIRLY RADCO

BI SeNIOR SOFTWARE ENGINEER

Red Hat Israel 

TRIED. TESTED. TRUSTED. 

On Fri, May 4, 2018 at 1:20 AM, Young, Matthew (Numerical Algorithms Group)
 wrote:

> I’ve gotten past that error with “oc delete route/docker-registry” before
> restart the playbook
>
>
>
> Matt
>
>
>
> *From:* Young, Matthew (Numerical Algorithms Group)
> *Sent:* Thursday, May 3, 2018 4:02 PM
> *To:* 'Shirly Radco' 
> *Cc:* users 
> *Subject:* RE: [ovirt-users] ansible failure during host install
>
>
>
> Ovirt-engine-metrics v1.1.3.4
>
>
>
> /etc/ovirt-engine-metrics/config.yml:
>
>   ovirt_env_name: data-science-sandbox
>
>   fluentd_elasticsearch_host: ovirt-metrics.datasci.bp.com
>
>   ovirt_elasticsearch_mounted_storage_path: /data
>
>
>
> I have not gotten the openshift based metrics store running.  It is
> consistently timing out while performing “TASK [openshift_hosted :
> Configure a passthrough route for docker-registry].”
>
> Failure summary:
>
>   1. Hosts:localhost
>
>  Play: Create Hosted Resources - registry
>
>  Task: Configure a passthrough route for docker-registry
>
>  Message:  {u'cmd': u'/usr/bin/oc replace -f
> /tmp/docker-registry-DtGZqz --force -n default', u'returncode': 1,
> u'results': {}, u'stderr': u'error: timed out waiting for the condition\n',
> u'stdout': u'route "docker-registry" deleted\n'}
>
>
>
> Matt Young
>
>
>
> *From:* Shirly Radco 
> *Sent:* Thursday, April 12, 2018 4:04 PM
> *To:* Young, Matthew (Numerical Algorithms Group) 
> *Cc:* users 
> *Subject:* Re: [ovirt-users] ansible failure during host install
>
>
>
> Hi,
>
>
>
> What version of ovirt-engine-metrics are you using?
>
>
>
> Did you already setup the OpenShift based metrics store to connect to?
>
>
>
> Have you configured /etc/ovirt-engine-metrics/config.yml?
>
>
>
> --
>
> SHIRLY RADCO
>
> BI SENIOR SOFTWARE ENGINEER
>
> Red Hat Israel
>
>
> TRIED. TESTED. TRUSTED.
>
>
>
>
>
> On Thu, Apr 12, 2018, 21:35 Young, Matthew (Numerical Algorithms Group) <
> matthew.you...@bp.com> wrote:
>
> Hello all,
>
>
>
> I have been working on adding a new host to an oVirt cluster.  The
> installation is failing in the ansible portion, specifically installing the
> ansible elasticsearch ca cert.  I have no experience with ansible.  Does
> anyone know what is causing this issue?  Or how to create this ca cert?
>
>
>
>  from ansible log
>
> …
>
> 2018-04-12 09:32:18,114 p=56616 u=ovirt |  TASK
> [oVirt.ovirt-fluentd/fluentd-setup : Create fluentd.conf]
> *
>
> 2018-04-12 09:32:18,730 p=56616 u=ovirt |  ok: [10.222.10.156] => {
>
> "changed": false,
>
> "checksum": "c9f88b60cd12ab8e3f3ffce1ae07654c89b06ef6",
>
> "gid": 0,
>
> "group": "root",
>
> "mode": "0640",
>
> "owner": "root",
>
> "path": "/etc/fluentd/fluent.conf",
>
> "secontext": "system_u:object_r:etc_t:s0",
>
> "size": 58,
>
> "state": "file",
>
> "uid": 0
>
> }
>
> 2018-04-12 09:32:18,739 p=56616 u=ovirt |  TASK
> [oVirt.ovirt-fluentd/fluentd-setup : Install fluentd certificate]
> *
>
> 2018-04-12 09:32:18,759 p=56616 u=ovirt |  skipping: [10.222.10.156] => {
>
> "changed": false,
>
> "skip_reason": "Conditional result was False"
>
> }
>
> 2018-04-12 09:32:18,768 p=56616 u=ovirt |  TASK
> [oVirt.ovirt-fluentd/fluentd-setup : Install fluentd elasticsearch CA
> certificate] ***
>
> 2018-04-12 09:32:18,810 p=56616 u=ovirt |  fatal: [10.222.10.156]: FAILED!
> => {
>
> "changed": false
>
> }
>
>
>
> MSG:
>
>
>
> src (or content) is required
>
>
>
> 2018-04-12 09:32:18,812 p=56616 u=ovirt |  PLAY RECAP
> *
>
> 2018-04-12 09:32:18,812 p=56616 u=ovirt |  10.222.10.156  :
> ok=33   changed=4unreachable=0failed=1
>
>
>
> 
>
> ___
> 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


[ovirt-users] Problems with OVN

2018-05-06 Thread Samuli Heinonen

Hi all,

I'm building a home lab using oVirt+GlusterFS in hyperconverged(ish) setup.

My setup consists of 2x nodes with ASRock H110M-STX motherboard, Intel 
Pentium G4560 3,5 GHz CPU and 16 GB RAM. Motherboard has integrated 
Intel Gigabit I219V LAN. At the moment I'm using RaspberryPi as Gluster 
arbiter node. Nodes are connected to basic "desktop switch" without any 
management available.


Hardware is nowhere near perfect, but it get its job done and is enough 
for playing around. However I'm having problems getting OVN to work 
properly and I'm clueless where to look next.


oVirt is setup like this:
oVirt engine host oe / 10.0.1.101
oVirt hypervisor host o2 / 10.0.1.18
oVirt hypervisor host o3 / 10.0.1.21
OVN network 10.0.200.0/24

When I spin up a VM in o2 and o3 with IP address in network 10.0.1.0/24 
everything works fine. VMs can interact between each other without any 
problems.


Problems show up when I try to use OVN based network between virtual 
machines. If virtual machines are on same hypervisor then everything 
seems to work ok. But if I have virtual machine on hypervisor o2 and 
another one on hypervisor o3 then TCP connections doesn't work very 
well. UDP seems to be ok and it's possible to ping hosts, do dns & ntp 
queries and so on.


Problem with TCP is that for example when taking SSH connection to 
another host at some point connection just hangs and most of the time 
it's not even possible to even log in before connectiong hangs. If I 
look into tcpdump at that point it looks like packets never reach 
destination. Also, if I have multiple connections, then all of them hang 
at the same time.


I have tried switching off tx checksum and other similar settings, but 
it didn't make any difference.


I'm suspecting that hardware is not good enough. Before investigating 
into new hardware I'd like to get some confirmation that everything is 
setup correctly.


When setting up oVirt/OVN I had to run following undocumented command to 
get it working at all: vdsm-tool ovn-config 10.0.1.101 10.0.1.21 (oVirt 
engine IP, hypervisor IP). Especially this makes me think that I have 
missed some crucial part in configuration.


On oVirt engine in /var/log/openvswitch/ovsdb-server-nb.log there are 
error messages:
2018-05-06T08:30:05.418Z|00913|stream_ssl|WARN|SSL_read: unexpected SSL 
connection close
2018-05-06T08:30:05.418Z|00914|jsonrpc|WARN|ssl:127.0.0.1:53152: receive 
error: Protocol error
2018-05-06T08:30:05.419Z|00915|reconnect|WARN|ssl:127.0.0.1:53152: 
connection dropped (Protocol error)


To be honest, I'm not sure what's causing those error messages or are 
they related. I found out some bug reports stating that they are not 
critical.


Any ideas what to do next or should I just get better hardware? :)

Best regards,
Samuli Heinonen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users