[ovirt-users] Deploying Self-Hosted Engine Using Cockpit 4.3 not working

[kiv]

Hi all.

Fresh install host node 4.3. Install ok.
Open web ui, and start deploying Self-Hosted Engine.
When i add ISCSI storage - i get error:

Retrieval of iSCSI targets failed.

My iscsi target up and work.

___
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/JQCAR3DXAUUZRV35VKNKQ6KZ334ECRZR/

[ovirt-users] Re: Node losing management network address?

[Dominik Holler]

On Wed, 27 Feb 2019 13:24:14 +0200
Juhani Rautiainen  wrote:

> On Wed, Feb 27, 2019 at 10:49 AM Dominik Holler  wrote:
> >
> 
> > > I just copied that ifcfg-ovirtmgmt file from second node and fixed
> > > IP-address to correct one before doing ifdown/ifup. That file had
> > > changed to DHCP so my instinct was trying to correct that one.
> > >
> >
> > Please let oVirt doing the work for you. If you interface to oVirt is
> > the web UI, please use the dialog "Edit Managment Network: ovirtmgmt"
> > which opens by clicking on the pencil symbol next to ovirtmgmt in
> > Compute > Hosts > xxx > Network Interfaces > Setup Host Networks
> > This will enable oVirt to recognize this change as intended.
> 
> Problem was that oVirt couldn't do the work anymore. It had for some
> reason switched that node to using DHCP addresses. DHCP gave totally
> different address to the node which was not known by ovirt engine.
> This is why I tried above change because I had lost connections to
> node after the resync. I had to use HP ILO console to see what's going
> on and found out that it had switched to DHCP and had wrong. And it
> used ILO fencing to boot the server because it couldn't reach it
> (which took many aftive vm's down). After the boot it still couldn't
> connect because address was still given by DHCP.

You did the right thing to establish a temporary connection of host and
engine. As soon as the engine is able to communicate with the host,
oVirt's web ui (or REST-API) should be used to configure the management
network address and to ensure, that the host is in sync with oVirt's config.

> What I'm wondering
> why it switched to DHCP when it had had static since first minute?
> 

This is a valid question.

> > > I noticed that one node had ovirtmgmt network unsynchronized. I tried

oVirt detected a difference between the expected configuration and applied
configuration. This might happen if the interface configuration is change
directly on the host instead of using oVirt Engine.

> > > to resynchronize it.

If you have the vdsm.log, the relevant lines start at the pattern
Calling 'Host.setupNetworks'
and ends at the pattern
FINISH getCapabilities


> > > This led the node being rebooted by HP ILO. After
> > > reboot the node came up with DHCP address. 

I have no idea why this happened, maybe there is a trace
in /var/log/messages ?

VDSM would revert a change in management networking configuration,
if after the change communication to engine is broken.
But if the host is rebooted during the change, there might be a
problem.
If you think you triggered
Bug 1664106 - [Network] Host reboot while setup networks leads to host stuck on 
status 'connecting'
you logfiles would be very helpful, if they are attached to the bug.
Thanks!



> >
> > Maybe no required anymore, since you described very precise what you
> > did.
> 
> Or not clearly enough.
> 
> Thanks,
> -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/DYJ76YVMW2W5MOR43XSAEUOMELZ7MUOK/

[ovirt-users] Re: unable to put ovirt host in maintenance

[stephane laurencelle]

Hello Vaibhav,


i check in the database and there is no job with status different of finished, 
it's return me 0 row


regards,


stephane


De : Vaibhav Pagar 
Envoyé : 26 février 2019 08:45:49
À : slaurence...@hotmail.com
Cc : users@ovirt.org
Objet : Re: [ovirt-users] Re: unable to put ovirt host in maintenance

Hello Stephane,

There might be unfinished jobs in the database.
Can you check from the job table and see if there is any unfinished job

#Engine > select * from job where status!=‘FINISHED’;

If yes, then clear that job and restart ovirt-engine service.

After that try to put host into maintenance mode and see if it works for you.

Thanks,

Vaibhav

On Sun, 24 Feb 2019 at 9:36 PM, 
mailto:slaurence...@hotmail.com>> wrote:
Hello Vaibhav,

i check with the vdsm-client and not task seem to be running for him.

any other idea ?

Stephane
___
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/CV7PISSR42S3ZYOVORJH3ENG3O6QP36D/
___
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/3B4HFMDUGJJFQVDHXYIRGPIGSTCTWT7I/

[ovirt-users] Re: Cannot start VM: Bad volume specification

[Alan]

Is it as simple as doing: lvchange ---activate     




 On Tue, 26 Feb 2019 16:15:32 + Alan G  wrote 





I tried that initially but I'm not sure how to access the image on block 
storage? The lv is marked as NOT available in lvdisplay.



--- Logical volume --- 

  LV Path    
/dev/70205101-c6b1-4034-a9a2-e559897273bc/74d27dd2-3887-4833-9ce3-5925dbd551cc

  LV Name    74d27dd2-3887-4833-9ce3-5925dbd551cc

  VG Name    70205101-c6b1-4034-a9a2-e559897273bc

  LV UUID    svAB48-Rgnd-0V2A-2O07-Z2Ic-4zfO-XyJiFo

  LV Write Access    read/write

  LV Creation host, time nyc-ovirt-01.redacted.com, 2018-05-15 12:02:41 +

  LV Status  NOT available

  LV Size    14.00 GiB

  Current LE 112

  Segments   9

  Allocation inherit

  Read ahead sectors auto





 On Tue, 26 Feb 2019 15:57:47 + Benny Zlotnik 
 wrote 











I haven't found anything other the leaks issue, you can try to run

$ qemu-img check -r leaks  

(make sure to have it backed up)




On Tue, Feb 26, 2019 at 5:40 PM Alan G  wrote:




___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto: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/JCTVJ4K7QNA653MA7YZZSYNU5OG2SNQE/




Logs are attached. The first error from snapshot deletion is at 2019-02-26 
13:27:11,877Z in the engine log.





 On Tue, 26 Feb 2019 15:11:39 + Benny Zlotnik 
 wrote 




Can you provide full vdsm & engine logs?



On Tue, Feb 26, 2019 at 5:10 PM Alan G  wrote:




___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto: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/XKTHCAZENAB2WLPJGDLGDDUWKPCOJCFV/




Hi,





I performed the following: -



1. Shutdown VM.

2. Take a snapshot

3. Create a clone from snapshot.

4. Start the clone. Clone starts fine.

5. Attempt to delete snapshot from original VM, fails.

6. Attempt to start original VM, fails with "Bad volume specification".



This was logged in VDSM during the snapshot deletion attempt.



2019-02-26 13:27:10,907+ ERROR (tasks/3) [storage.TaskManager.Task] 
(Task='67577e64-f29d-4c47-a38f-e54b905cae03') Unexpected error (task:872) 

Traceback (most recent call last):

  File "/usr/share/vdsm/storage/task.py", line 879, in _run

    return fn(*args, **kargs)

  File "/usr/share/vdsm/storage/task.py", line 333, 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/share/vdsm/storage/sp.py", line 1892, in finalizeMerge

    merge.finalize(subchainInfo)

  File "/usr/share/vdsm/storage/merge.py", line 271, in finalize

    optimal_size = subchain.base_vol.optimal_size()

  File "/usr/share/vdsm/storage/blockVolume.py", line 440, in optimal_size

    check = qemuimg.check(self.getVolumePath(), qemuimg.FORMAT.QCOW2)

  File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 157, in check

    out = _run_cmd(cmd)

  File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 426, in _run_cmd

    raise QImgError(cmd, rc, out, err)

QImgError: cmd=['/usr/bin/qemu-img', 'check', '--output', 'json', '-f', 
'qcow2', 
'/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-04

6c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f'], ecode=3, 
stdout={

    "image-end-offset": 52210892800,

    "total-clusters": 1638400,

    "check-errors": 0,

    "leaks": 323,

    "leaks-fixed": 0,

    "allocated-clusters": 795890,

    "filename": 
"/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-046c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f",

    "format": "qcow2",

    "fragmented-clusters": 692941

}

, stderr=Leaked cluster 81919 refcount=1 reference=0

Leaked cluster 81920 refcount=1 reference=0

Leaked cluster 81921 refcount=1 reference=0

etc..



Is there any way to fix these leaked clusters? 



Running oVirt 4.1.9 with FC block storage.



Thanks,



Alan





___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto:users-le...@ovirt.org

Privacy Statement: 

[ovirt-users] Re: Deploying Self-Hosted Engine Using Cockpit 4.3 not working

[Simone Tiraboschi]

On Wed, Feb 27, 2019 at 1:02 PM  wrote:

> Hi all.
>
> Fresh install host node 4.3. Install ok.
> Open web ui, and start deploying Self-Hosted Engine.
> When i add ISCSI storage - i get error:
>
> Retrieval of iSCSI targets failed.
>

Yes, we have an open bug here:
https://bugzilla.redhat.com/1683366

I'd suggest to deploy from CLI in the mean time.


>
> My iscsi target up and work.
>
> ___
> 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/JQCAR3DXAUUZRV35VKNKQ6KZ334ECRZR/
>
___
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/BI6BF3GXAGWJMMYXOQJZ62KRSPHJ2XRO/

[ovirt-users] Re: Cannot start VM: Bad volume specification

[Alan G]

Still cannot remove snapshot.



2019-02-27 08:56:58,781+ ERROR (tasks/6) [storage.TaskManager.Task] 
(Task='72570267-d86a-4a14-a8bb-fc925a717753') Unexpected error (task:872) 

Traceback (most recent call last):

  File "/usr/share/vdsm/storage/task.py", line 879, in _run

    return fn(*args, **kargs)

  File "/usr/share/vdsm/storage/task.py", line 333, 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/share/vdsm/storage/sp.py", line 1884, in prepareMerge

    merge.prepare(subchainInfo)

  File "/usr/share/vdsm/storage/merge.py", line 181, in prepare

    with subchain.prepare():

  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__

    return self.gen.next()

  File "/usr/share/vdsm/storage/merge.py", line 160, in prepare

    vol.prepare(rw=rw, justme=True)

  File "/usr/share/vdsm/storage/volume.py", line 562, in prepare

    raise se.prepareIllegalVolumeError(self.volUUID)

prepareIllegalVolumeError: Cannot prepare illegal volume: 
('5f5b436d-6c48-4b9f-a68c-f67d666741ab',)





 On Tue, 26 Feb 2019 18:28:02 + Benny Zlotnik  
wrote 




Can you remove the snapshot now?



On Tue, Feb 26, 2019 at 7:06 PM Alan G  wrote:




___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto: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/FFRIVWZACG2E6WJ224A6DLBR6G6RPUN4/




That cleaned up the qcow image and qemu-img now reports it's ok, but I still 
cannot start the VM, get "Cannot prepare illegal volume".



Is there some metadata somewhere that needs to be cleaned/reset?





 On Tue, 26 Feb 2019 16:25:22 + Benny Zlotnik 
 wrote 




it's because the VM is down, you can manually activate using

$ lvchange -a y vgname/lvname



remember to deactivate after






On Tue, Feb 26, 2019 at 6:15 PM Alan G  wrote:







I tried that initially but I'm not sure how to access the image on block 
storage? The lv is marked as NOT available in lvdisplay.



--- Logical volume --- 

  LV Path    
/dev/70205101-c6b1-4034-a9a2-e559897273bc/74d27dd2-3887-4833-9ce3-5925dbd551cc

  LV Name    74d27dd2-3887-4833-9ce3-5925dbd551cc

  VG Name    70205101-c6b1-4034-a9a2-e559897273bc

  LV UUID    svAB48-Rgnd-0V2A-2O07-Z2Ic-4zfO-XyJiFo

  LV Write Access    read/write

  LV Creation host, time http://nyc-ovirt-01.redacted.com, 2018-05-15 12:02:41 
+

  LV Status  NOT available

  LV Size    14.00 GiB

  Current LE 112

  Segments   9

  Allocation inherit

  Read ahead sectors auto





 On Tue, 26 Feb 2019 15:57:47 + Benny Zlotnik 
 wrote 




I haven't found anything other the leaks issue, you can try to run

$ qemu-img check -r leaks  

(make sure to have it backed up)




On Tue, Feb 26, 2019 at 5:40 PM Alan G  wrote:




___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto: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/JCTVJ4K7QNA653MA7YZZSYNU5OG2SNQE/




Logs are attached. The first error from snapshot deletion is at 2019-02-26 
13:27:11,877Z in the engine log.





 On Tue, 26 Feb 2019 15:11:39 + Benny Zlotnik 
 wrote 




Can you provide full vdsm & engine logs?



On Tue, Feb 26, 2019 at 5:10 PM Alan G  wrote:




___

Users mailing list -- mailto:users@ovirt.org

To unsubscribe send an email to mailto: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/XKTHCAZENAB2WLPJGDLGDDUWKPCOJCFV/




Hi,





I performed the following: -



1. Shutdown VM.

2. Take a snapshot

3. Create a clone from snapshot.

4. Start the clone. Clone starts fine.

5. Attempt to delete snapshot from original VM, fails.

6. Attempt to start original VM, fails with "Bad volume specification".



This was logged in VDSM during the snapshot deletion attempt.



2019-02-26 13:27:10,907+ ERROR (tasks/3) 

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

[Sandro Bonazzola]

Il giorno lun 25 feb 2019 alle ore 11:10 Niels de Vos 
ha scritto:

> On Mon, Feb 25, 2019 at 10:05:52AM +0100, Sandro Bonazzola wrote:
> > Il giorno gio 21 feb 2019 alle ore 08:48 Sandro Bonazzola <
> > sbona...@redhat.com> ha scritto:
> >
> > >
> > >
> > > 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?
> > >
> >
> > Update for users: a fix has been merged for Gluster 6 and the backport to
> > Gluster 5 has been verified, reviewed and pending merge (
> > https://review.gluster.org/#/c/glusterfs/+/22258/).
>
> I plan to push an update with only this change later today. That means
> the updated glusterfs-5 version is expected to hit the CentOS mirrors
> tomorrow.
>

Niels, I see glusterfs-5.4-1.el7 being tagged for testing, not yet for
release (https://cbs.centos.org/koji/buildinfo?buildID=25227).
Sahina did your team test this build to see if it solves the upgrade path
for glusterfs-gnfs?
Users: your help testing this would be very useful. You can find test repo
here: https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-5/

Thanks,


>
> Niels
>
>
> >
> >
> >
> > >
> > >
> > >
> > >
> > >>
> > >> [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-users] Changing Ovirt hosted engine memory

[Dionysis K]

Hello! i am new user to ovirt and i was trying to increase the memory of the 
hosted engine from 5120 MB to 10240 MB and the reports on the events are those 
bellow, the environment the hosted engine runs is on 3 ovirt nodes with version 
4.2.8 and the hosted engine is updates with the latest version, any ideas how 
to set up things 


Failed to hot set memory to VM HostedEngine. Underlying error message: 
unsupported configuration: Attaching memory device with size '5242880' would 
exceed domain's maxMemory config


VDSM  command SetAmountOfMemoryVDS failed: unsupported configuration: Attaching 
memory device with size '5242880' would exceed domain's maxMemory config
___
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/SKNBMNJ2LRLS7PK3CX2JTQHAXTXCBLHT/

[ovirt-users] [oVirt 4.3.1-RC2 Test Day] Hyperconverged HE Deployment

[Guillaume Pavese]

Hi, I tried again today to deploy HE on Gluster with oVirt 4.3.1 RC2 on a
clean Nested environment (no precedent deploy attempts to clean before...).

Gluster was deployed without problem from cockpit.
I then snapshoted my vms before trying to deploy HE both from cockpit, then
from cmdline.
Both attempts failed at the same spot :

[ INFO ] Creating Storage Domain
[ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of
steps]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using
username/password credentials]
[ ERROR ] ConnectionError: Error while sending HTTP request: (7, 'Failed
connect to vs-inf-int-ovt-fr-301-210.hostics.fr:443; No route to host')
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false,
"msg": "Error while sending HTTP request: (7, 'Failed connect to
vs-inf-int-ovt-fr-301-210.hostics.fr:443; No route to host')"}
Please specify the storage you would like to use (glusterfs, iscsi, fc,
nfs)[nfs]:



[root@vs-inf-int-kvm-fr-301-210 ~]# traceroute
vs-inf-int-ovt-fr-301-210.hostics.fr
traceroute to vs-inf-int-ovt-fr-301-210.hostics.fr (192.168.122.147), 30
hops max, 60 byte packets
1 vs-inf-int-kvm-fr-301-210.hostics.fr (192.168.122.1) 3006.344 ms !H
3006.290 ms !H 3006.275 ms !H




Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group
___
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/5JEA5726OHI2MTOHEBV3VYAKDNDNSNMJ/

[ovirt-users] Re: Node losing management network address?

[Juhani Rautiainen]

On Wed, Feb 27, 2019 at 10:49 AM Dominik Holler  wrote:
>

> > I just copied that ifcfg-ovirtmgmt file from second node and fixed
> > IP-address to correct one before doing ifdown/ifup. That file had
> > changed to DHCP so my instinct was trying to correct that one.
> >
>
> Please let oVirt doing the work for you. If you interface to oVirt is
> the web UI, please use the dialog "Edit Managment Network: ovirtmgmt"
> which opens by clicking on the pencil symbol next to ovirtmgmt in
> Compute > Hosts > xxx > Network Interfaces > Setup Host Networks
> This will enable oVirt to recognize this change as intended.

Problem was that oVirt couldn't do the work anymore. It had for some
reason switched that node to using DHCP addresses. DHCP gave totally
different address to the node which was not known by ovirt engine.
This is why I tried above change because I had lost connections to
node after the resync. I had to use HP ILO console to see what's going
on and found out that it had switched to DHCP and had wrong. And it
used ILO fencing to boot the server because it couldn't reach it
(which took many aftive vm's down). After the boot it still couldn't
connect because address was still given by DHCP. What I'm wondering
why it switched to DHCP when it had had static since first minute?

>
> Maybe no required anymore, since you described very precise what you
> did.

Or not clearly enough.

Thanks,
-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/2ZVLCGNK4U2F4TQOKAV3E4G5GJ5VMJQU/

[ovirt-users] Re: Changing Ovirt hosted engine memory

[Sandro Bonazzola]

Il giorno mer 27 feb 2019 alle ore 13:59 Dionysis K  ha
scritto:

> Hello! i am new user to ovirt and i was trying to increase the memory of
> the hosted engine from 5120 MB to 10240 MB and the reports on the events
> are those bellow, the environment the hosted engine runs is on 3 ovirt
> nodes with version 4.2.8 and the hosted engine is updates with the latest
> version, any ideas how to set up things
>
>
Welcome to oVirt community!



>
> Failed to hot set memory to VM HostedEngine. Underlying error message:
> unsupported configuration: Attaching memory device with size '5242880'
> would exceed domain's maxMemory config
>
>
> VDSM  command SetAmountOfMemoryVDS failed: unsupported configuration:
> Attaching memory device with size '5242880' would exceed domain's maxMemory
> config
>

Ryan, can you help here?




> ___
> 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/SKNBMNJ2LRLS7PK3CX2JTQHAXTXCBLHT/
>


-- 

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/ZATX6E52AYISSXXTFD27MT25EMXRI7QJ/

[ovirt-users] Re: Cannot start VM: Bad volume specification

[Benny Zlotnik]

Can you provide the output of vdsm-tool dump-volume-chains ?

On Wed, Feb 27, 2019 at 11:45 AM Alan G  wrote:

> Still cannot remove snapshot.
>
> 2019-02-27 08:56:58,781+ ERROR (tasks/6) [storage.TaskManager.Task]
> (Task='72570267-d86a-4a14-a8bb-fc925a717753') Unexpected error (task:872)
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 879, in _run
> return fn(*args, **kargs)
>   File "/usr/share/vdsm/storage/task.py", line 333, 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/share/vdsm/storage/sp.py", line 1884, in prepareMerge
> merge.prepare(subchainInfo)
>   File "/usr/share/vdsm/storage/merge.py", line 181, in prepare
> with subchain.prepare():
>   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
> return self.gen.next()
>   File "/usr/share/vdsm/storage/merge.py", line 160, in prepare
> vol.prepare(rw=rw, justme=True)
>   File "/usr/share/vdsm/storage/volume.py", line 562, in prepare
> raise se.prepareIllegalVolumeError(self.volUUID)
> prepareIllegalVolumeError: Cannot prepare illegal volume:
> ('5f5b436d-6c48-4b9f-a68c-f67d666741ab',)
>
>
>  On Tue, 26 Feb 2019 18:28:02 + *Benny Zlotnik
> >* wrote 
>
> Can you remove the snapshot now?
>
> On Tue, Feb 26, 2019 at 7:06 PM Alan G  wrote:
>
> ___
> 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/FFRIVWZACG2E6WJ224A6DLBR6G6RPUN4/
>
>>
>> That cleaned up the qcow image and qemu-img now reports it's ok, but I
>> still cannot start the VM, get "Cannot prepare illegal volume".
>>
>> Is there some metadata somewhere that needs to be cleaned/reset?
>>
>>
>>  On Tue, 26 Feb 2019 16:25:22 + *Benny Zlotnik
>> >* wrote 
>>
>> it's because the VM is down, you can manually activate using
>> $ lvchange -a y vgname/lvname
>>
>> remember to deactivate after
>>
>>
>> On Tue, Feb 26, 2019 at 6:15 PM Alan G  wrote:
>>
>>
>>> I tried that initially but I'm not sure how to access the image on block
>>> storage? The lv is marked as NOT available in lvdisplay.
>>>
>>> --- Logical volume ---
>>>   LV Path
>>> /dev/70205101-c6b1-4034-a9a2-e559897273bc/74d27dd2-3887-4833-9ce3-5925dbd551cc
>>>   LV Name74d27dd2-3887-4833-9ce3-5925dbd551cc
>>>   VG Name70205101-c6b1-4034-a9a2-e559897273bc
>>>   LV UUIDsvAB48-Rgnd-0V2A-2O07-Z2Ic-4zfO-XyJiFo
>>>   LV Write Accessread/write
>>>   LV Creation host, time nyc-ovirt-01.redacted.com, 2018-05-15 12:02:41
>>> +
>>>   LV Status  NOT available
>>>   LV Size14.00 GiB
>>>   Current LE 112
>>>   Segments   9
>>>   Allocation inherit
>>>   Read ahead sectors auto
>>>
>>>
>>>  On Tue, 26 Feb 2019 15:57:47 + *Benny Zlotnik
>>> >* wrote 
>>>
>>> I haven't found anything other the leaks issue, you can try to run
>>> $ qemu-img check -r leaks 
>>> (make sure to have it backed up)
>>>
>>> On Tue, Feb 26, 2019 at 5:40 PM Alan G  wrote:
>>>
>>> ___
>>> 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/JCTVJ4K7QNA653MA7YZZSYNU5OG2SNQE/
>>>

 Logs are attached. The first error from snapshot deletion is
 at 2019-02-26 13:27:11,877Z in the engine log.


  On Tue, 26 Feb 2019 15:11:39 + *Benny Zlotnik
 >* wrote 

 Can you provide full vdsm & engine logs?

 On Tue, Feb 26, 2019 at 5:10 PM Alan G  wrote:

 ___
 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/XKTHCAZENAB2WLPJGDLGDDUWKPCOJCFV/

>
> Hi,
>
>
> I performed the following: -
>
> 1. Shutdown VM.
> 2. Take a snapshot
> 3. Create a clone from snapshot.
> 4. Start the clone. Clone starts fine.
> 5. Attempt to delete snapshot from original VM, fails.
> 6. Attempt to start original VM, fails with "Bad volume 

[ovirt-users] Re: non-redhat version of ovirt-host-deploy

[ivan . kabaivanov]

Hey, thanks again for taking the time to answer my questions.  I really 
appreciate it!

You are right about first running ovirt in its native distribution 
(RHEL/Fedora/Centos) so I can familiarize myself with its proper functioning 
state.  Even though I did not mention it, I am doing just that -- I have a 
CentOS VM with ovirt-engine running and another one with ovirt-node.  However, 
sometimes I still run into issues I am uncertain the root cause of.

I will do some more testing and reading of READMEs and the code and check how 
ovirt works on CentOS.

Perhaps I'll start another thread, titled Porting oVirt to LFS where I will 
post my questions as I run into issues I can't resolve on my own, instead of 
starting a new thread for each one?

One thing I would like to raise now is that various packages or even different 
scripts within the same package depend on either python2 or python3 and some 
use the very ambiguous #!/usr/bin/python.  Trouble is, I recently switched to 
python3 by default, so /usr/bin/python is actually python3, not as the script 
assumes, python2.  So I'm patching those to #!/usr/bin/python2.  But it would 
be very useful, now that I read somewhere that Fedora is about to default to 
python3, to not assume python2 is default and explicitly specify the 
interpreter #!/usr/bin/env python2 or #!/usr/bin/env python3.

Thanks,
IvanK.
___
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/KJOLZA2KVU3QHKLEKCYRQQLQBMMRU3MB/

[ovirt-users] Re: Can't manually migrate VM's (4.3.0)

[Greg Sheremeta]

Hi Ron,

Please attach your browser console log and engine.log snippet when you have
the problem.
If you could dive into the console and grab the actual REST API response,
that would be great.
The request will be something like
/api/hosts?migration_target_of=...

Greg

On Tue, Feb 26, 2019 at 6:32 PM Greg Sheremeta  wrote:

> It sounds like a bug. I'll talk with Michal about reverting this dialog to
> the 4.2 version.
>
> Greg
>
> On Tue, Feb 26, 2019 at 1:47 PM Ron Jerome  wrote:
>
>> Hi Sharon,
>> This happens with all the VM's, regardless of uptime.  I've never tried
>> to migrate a VM if it's not completely up.
>>
>> When I select a VM and push the "Migrate" button, I never get to the
>> "Migrate" dialog box, I just presents the error show in the attached
>> image.
>>
>> I know for a fact that manual migration did work on this cluster,
>> unfortunately, I don't know if it ever worked in 4.3.0 or if I was still at
>> 4.2.8 when I last used it.
>>
>> Ron.
>>
>> On Tue, 26 Feb 2019 at 11:59, Sharon Gratch  wrote:
>>
>>> Hi Ron,
>>>
>>> What is the VM state when you try to manually migrate it? Is the VM in
>>> the beginning of the "powering up" state?
>>> If so then please wait 1-2 seconds and then try to migrate again and see
>>> if it is reproduced.
>>> You can't migrate a VM on "Wait for Launch" state and once the VM enters
>>> the "powering up" state then it sometimes takes time for UI to be refreshed
>>> with state and data. It was reproduced to me too.
>>>
>>> Greg, does it sound reasonable?
>>>
>>> Thanks,
>>> Sharon
>>>
>>>
>>>
>>> Can you please send a screenshot of the "Migrate VM(s)" dialog with th
>>>
>>> On Tue, Feb 26, 2019 at 5:33 PM Ron Jerome  wrote:
>>>
 I've toggled all the hosts into and out of maintenance, and VM's
 migrate off of each as expected, but I still can't manually initiate a VM
 migration from the UI.  Do you have any hints as to where to look for error
 messages?

 Thanks in advance,

 Ron.

 On Mon, 25 Feb 2019 at 19:56, Ron Jerome  wrote:

>
> It's a 3 node cluster, each node has 84G RAM, and there are only two
> two other VM's running, so there should be plenty of capacity.
>
> Automatic migration works, if I put a host into Maintenance, the VM's
> will migrate.
>
> Ron
>
> On Mon, Feb 25, 2019, 6:46 PM Greg Sheremeta, 
> wrote:
>
>> Turns out it's a bad error message. It just means there are no hosts
>> available to migrate to.
>>
>> Do you have other hosts up with capacity?
>>
>> Greg
>>
>>
>> On Mon, Feb 25, 2019 at 3:01 PM Ron Jerome  wrote:
>>
>>> I've been running 4.3.0 for a few weeks now and just discovered that
>>> I can't manually migrate VM's from the UI.  I get an error message 
>>> saying: "Could
>>> not fetch data needed for VM migrate operation"
>>>
>>> Sounds like
>>> https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1670701
>>>
>>> Ron.
>>> ___
>>> 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/5OBUNZHUPVEDZ5YLTXI2CQEPBQGBZ2JT/
>>>
>>
>>
>> --
>>
>> 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/VVSXK3WO4AA5B7T6LGEYWRBNAO56G46V/

>>>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>


-- 

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/2MGCE5WJIQC3S3A6JMWQB4W6CF25RKTF/

[ovirt-users] McAfee.com/Activate

[jeff root]

I am working as an IT professional and holds a very good experience in the same 
field.
at Miami, USA
https://activate-mcafee.net
___
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/R4FDW3AT2DWSQ3FTBCMMT3IZZP6JNUFH/

[ovirt-users] Re: Node losing management network address?

[Dominik Holler]

On Wed, 27 Feb 2019 08:52:24 +0200
Juhani Rautiainen  wrote:

> On Tue, Feb 26, 2019 at 12:05 PM Dominik Holler  wrote:
> >
> > On Mon, 25 Feb 2019 13:46:59 +0200
> > Juhani Rautiainen  wrote:
> >
> > > Hi!
> > >
> > > I had weird occurence in my two node ovirt cluster today (I have HE).
> > > I noticed that one node had ovirtmgmt network unsynchronized. I tried
> > > to resynchronize it. This led the node being rebooted by HP ILO. After
> > > reboot the node came up with DHCP address. Tried to change it back by
> > > fixing ifcfg-ovirtmgmt to original static address.
> >
> > How did you fix? By ovirt-engine's web UI, REST-API or by modifying a
> > config file on the host, or cockpit?
> 
> I just copied that ifcfg-ovirtmgmt file from second node and fixed
> IP-address to correct one before doing ifdown/ifup. That file had
> changed to DHCP so my instinct was trying to correct that one.
> 

Please let oVirt doing the work for you. If you interface to oVirt is
the web UI, please use the dialog "Edit Managment Network: ovirtmgmt"
which opens by clicking on the pencil symbol next to ovirtmgmt in
Compute > Hosts > xxx > Network Interfaces > Setup Host Networks
This will enable oVirt to recognize this change as intended.

> >
> > If you would share the vdsm.log files containing the relevant flow, this
> > would help to understand what happened.
> 
> Can I upload these somewhere? I can find the vdsm logs from the
> failure time frame. From engine logs I can see that EVENT_ID:
> VDS_NETWORKS_OUT_OF_SYNC(1,110) started weeks earlier (February 6th).
> The problem really just flared when I noticed it and tried to resync.
> There are not old enough vdsm logs to see what happened back then.
> This event continues daily so is there anything on vdsm logs which is
> connected to that event that I could dig for? Just noticed that this
> is pretty much the date I upgraded cluster from 4.2.8 to 4.3.
> 

Maybe no required anymore, since you described very precise what you
did.

> Thanks,
> 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/75HVUDC4BTRDLGJLPH4AFEKPSTGZ7C5W/

[ovirt-users] Re: non-redhat version of ovirt-host-deploy

[Yedidyah Bar David]

On Thu, Feb 28, 2019 at 12:06 AM  wrote:
>
> Hey, thanks again for taking the time to answer my questions.  I really 
> appreciate it!
>
> You are right about first running ovirt in its native distribution 
> (RHEL/Fedora/Centos) so I can familiarize myself with its proper functioning 
> state.  Even though I did not mention it, I am doing just that -- I have a 
> CentOS VM with ovirt-engine running and another one with ovirt-node.  
> However, sometimes I still run into issues I am uncertain the root cause of.
>
> I will do some more testing and reading of READMEs and the code and check how 
> ovirt works on CentOS.
>
> Perhaps I'll start another thread, titled Porting oVirt to LFS where I will 
> post my questions as I run into issues I can't resolve on my own, instead of 
> starting a new thread for each one?

I think a thread per issue is much more likely to attract people that
know the answer to actually respond...

Perhaps add 'Port-To-LFS' in the subject.

Perhaps write a series of blog posts about your work, sounds like it
will be quite an interesting read :-)

Check also all of the developer pages on the site.

At least for the engine we have a notion called 'dev env' - where
everything runs as non-root and does not rely on anything
distribution-specific. This is described in the README, and also:

https://www.ovirt.org/develop/developer-guide/engine/engine-development-environment.html

Obviously there are some differences between this and LFS:

1. In LFS you might actually want to do run things as root and have
them manage your env. I guess from LFS's POV this should be optional,
for the user to choose :-)

2. You do have to somehow provide all the dependencies. The engine's
README does detail them, but it's not easy to actually provide them if
not using a supported distro. Since you said you already have a
working engine inside LFS, I guess you are now past this point anyway.

Also, it's not fully clear what you want to achieve on the hosts side.
Do you want them to be fully-LFS too? Do you then also want the engine
to do package management (e.g. upgrades) on them? You'll have to first
clearly define what you want to do.

>
> One thing I would like to raise now is that various packages or even 
> different scripts within the same package depend on either python2 or python3 
> and some use the very ambiguous #!/usr/bin/python.  Trouble is, I recently 
> switched to python3 by default, so /usr/bin/python is actually python3, not 
> as the script assumes, python2.  So I'm patching those to #!/usr/bin/python2. 
>  But it would be very useful, now that I read somewhere that Fedora is about 
> to default to python3, to not assume python2 is default and explicitly 
> specify the interpreter #!/usr/bin/env python2 or #!/usr/bin/env python3.

Python3 support is work in progress. Some parts already ported, others
not yet. The biggest part IIUC is vdsm, and you might want to check a
recent thread on the devel list "[ovirt-devel] Running Vdsm on Python
3".

Thanks, good luck and best regards,


>
> Thanks,
> IvanK.
> ___
> 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/KJOLZA2KVU3QHKLEKCYRQQLQBMMRU3MB/



--
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/KDYBHIG5NIHMN2JXZ6SUMYAERYVLNZBZ/

[ovirt-users] Re: Node losing management network address?

[Juhani Rautiainen]

On Wed, Feb 27, 2019 at 6:26 PM Dominik Holler  wrote:
>

>
> This is a valid question.
>
> > > > I noticed that one node had ovirtmgmt network unsynchronized. I tried
>
> oVirt detected a difference between the expected configuration and applied
> configuration. This might happen if the interface configuration is change
> directly on the host instead of using oVirt Engine.
>
> > > > to resynchronize it.
>
> If you have the vdsm.log, the relevant lines start at the pattern
> Calling 'Host.setupNetworks'
> and ends at the pattern
> FINISH getCapabilities

This gave some clues. See the log below. IMHO it points engine getting
something wrong because it seems to ask for DHCP setup in query.
Probably fails because it succeeds in address change and network
connection is torn down.

2019-02-25 12:41:38,478+0200 WARN  (vdsm.Scheduler) [Executor] Worker
blocked: 
timeout=60, duration=60.01 at 0x7fc9c961e090> task#=230106 at
0x7fc9a43a1fd0>, traceback:
File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap
  self.__bootstrap_inner()
File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner
  self.run()
File: "/usr/lib64/python2.7/threading.py", line 765, in run
  self.__target(*self.__args, **self.__kwargs)
File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py",
line 195, in run
  ret = func(*args, **kwargs)
File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run
  self._execute_task()
File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315,
in _execute_task
  task()
File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__
  self._callable()
File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line
262, in __call__
  self._handler(self._ctx, self._req)
File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line
305, in _serveRequest
  response = self._handle_request(req, ctx)
File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line
345, in _handle_request
  res = method(**params)
File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194,
in _dynamicMethod
  result = fn(*methodArgs)
File: "", line 2, in setupNetworks
File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method
  ret = func(*args, **kwargs)
File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1562, in
setupNetworks
  supervdsm.getProxy().setupNetworks(networks, bondings, options)
File: "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py",
line 56, in __call__
  return callMethod()
File: "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py",
line 54, in 
  **kwargs)
File: "", line 2, in setupNetworks
File: "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in
_callmethod
  kind, result = conn.recv() (executor:363)
2019-02-25 12:41:38,532+0200 INFO  (jsonrpc/0) [jsonrpc.JsonRpcServer]
RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312)
2019-02-25 12:41:38,538+0200 INFO  (jsonrpc/5) [api.host] START
getCapabilities() from=::1,41016 (api:48)
2019-02-25 12:41:38,834+0200 INFO  (jsonrpc/7) [api.host] START
getAllVmStats() from=::1,41018 (api:48)
2019-02-25 12:41:38,845+0200 WARN  (jsonrpc/7) [virt.vm]
(vmId='66394fff-6207-4277-ab47-bffd39075eef') monitor became
unresponsive (command timeout, age=70.070003) (vm:6014)
2019-02-25 12:41:38,850+0200 INFO  (jsonrpc/7) [api.host] FINISH
getAllVmStats return={'status': {'message': 'Done', 'code': 0},
'statsList': (suppressed)} from=::1,41018 (api:54)
2019-02-25 12:41:38,854+0200 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer]
RPC call Host.getAllVmStats succeeded in 0.02 seconds (__init__:312)
2019-02-25 12:41:38,867+0200 INFO  (jsonrpc/2) [api.host] START
getAllVmIoTunePolicies() from=::1,41018 (api:48)
2019-02-25 12:41:38,868+0200 INFO  (jsonrpc/2) [api.host] FINISH
getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code':
0}, 'io_tune_policies_dict': {'5cb297ee-81c0-4fc6-a2ba-87192723e6ab':
{'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L,
'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L,
'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path':
'/rhev/data-center/mnt/blockSD/5106a440-3a0a-4a79-a8ee-0ffc5fa8e3a2/images/a4b8b705-d999-4578-99eb-c80aa1cbbec6/19e9b0b0-6485-43ed-93e5-c2ef40d2e388',
'name': 'vda'}]}, '16a6d21b-3d69-4967-982b-dfe05534f153': {'policy':
[], 'current_values': [{'ioTune': {'write_bytes_sec': 0L,
'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L,
'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path':
'/rhev/data-center/mnt/blockSD/5106a440-3a0a-4a79-a8ee-0ffc5fa8e3a2/images/67c41187-6510-429e-b88d-93a907bbbf38/b1f627d3-13c2-4800-8f29-4504d35bba5f',
'name': 'sda'}]}, '59103e4b-863c-4c16-8f45-226712a9ab08': {'policy':
[], 'current_values': [{'ioTune': {'write_bytes_sec': 0L,
'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L,
'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path':

[ovirt-users] reinstall centos node (ovirt 4.2.7) fails due missing dependency on librbd1

[Mike Lykov]

Hi All!


I'm using ovirt-release42-4.2.7.1-1.el7.noarch
centos-release-7-5.1804.5.el7.centos.x86_64
And HCI glusterfs deployment (no ceph).

And yesterday I wanted an add hosted engine deploy on some node. 
It requires to enable maintenance mode, reinstall node with "hosted engine = 
deploy" config (in webui).

I made it, but reinstall fails. In logs I see (not full list):
...
Feb 27 16:35:39 Updated: libvirt-daemon-4.5.0-10.el7_6.4.x86_64
Feb 27 16:35:39 Updated: 
libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.4.x86_64
Feb 27 16:36:04 Updated: 
libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.4.x86_64
Feb 27 16:36:04 Updated: 
libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.4.x86_64
Feb 27 16:36:04 Updated: libvirt-daemon-driver-storage-4.5.0-10.el7_6.4.x86_64

After it 
# rpm -q librbd1
librbd1-0.94.5-2.el7.x86_64

фев 27 16:36:51 ovirtnode5.miac systemd[1]: Starting Virtualization daemon...
фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+: 
537: info : libvirt version: 4.5.0, package: 10.el7_6.4 (CentOS BuildSystem 
, 2019-01-29-17:31:22, x86-01.bsys.centos.org)
фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+: 
537: info : hostname: ovirtnode5.miac
фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+: 
537: error : virModuleLoadFile:53 : внутренняя ошибка: Failed to load module 
'/usr/lib64/libvirt/storage-backend/libvirt_storage_backend_rbd.so': 
/usr/lib64/libv
irt/storage-backend/libvirt_storage_backend_rbd.so: undefined symbol: 
rbd_diff_iterate2
фев 27 16:36:51 ovirtnode5.miac systemd[1]: libvirtd.service: main process 
exited, code=exited, status=3/NOTIMPLEMENTED
фев 27 16:36:51 ovirtnode5.miac systemd[1]: Failed to start Virtualization 
daemon.

There is a old bugs like
https://bugzilla.redhat.com/show_bug.cgi?id=1316911
or new posts like 
http://dreamcloud.artark.ca/libvirtd-failure-after-latest-upgrade-in-rhel-centos7/

Obviously, the libvirt* rpms are updated, but librbd* not. But why? Why libvirt 
packages are not strictly dependenced on all required package/lib versions?

libvirt-daemon-driver-storage-rbd must require exactly that librbd version that 
can work with, i think.

--
Mike
___
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/A4X6PPFT7RKCETV4OTR7YARDDRGFBZ2Y/