[ovirt-users] Re: Cloud-init reset network configuration to default dhcp after reboot and regular run

[Mike Lykov]

05.12.2018 13:04, Eitan Raviv пишет:
After further investigation I would like to share one more important 
piece of information that explains the "reset" behaviour of the network 
configuration:


Thanks for that detailed clarification.

When a VM is started in 'Run once' mode, the initialization parameters 
supplied for that run are always passed by engine to cloud-init in the 
guest for application.


It's clear and work as intended.

But if a VM is started in 'Run' mode, the initialization parameters are 
passed to cloud-init on the guest only if this is the first run (be it 
'Run' or 'Run once'). On every consecutive run in 'Run' mode no 
parameters are passed to the guest, and therefore (as I quoted from the 
cloud-init documentation earlier in this thread) cloud-init falls back 
to DHCP configuration on the guest.



When this behaviour was introduced into engine the reasoning was that 
after the initial configuration of the VM, there is no reason to resend 
the configuration on every 'Run' but only on 'Run once'.


Yes, there is no reason, but for new user it looks very confusing:
 - create VM
 - configure cloud-init parameters (like IP addr)
 - Run VM (not once), parameters applied (all OK? as it seems)
 - work with/in VM
 - Stop VM (maybe after period of time when VM counts as 'configured 
successfully') for some maintetance
 - Run VM and try to access it (it is 'configured successfully' some 
time ago, isn't it?)

 - NO ACCESS to VM and configurаtion is LOST
 - try to access via console with 'WTF?' exclamation 

Why cloud-init in this scenario after successful configuration is not 
turn off/disable himself (by touch that file, for example) ?


Instead of it cloud-init+ovirt force user to:
 - try to figure why configuration is lost, learn "custom script" format
 - write "custom script" for touch /etc/cloud/cloud-init.disabled and 
reboot

 - run once VM to apply parameters
 - run VM as usual ?


Due to the behaviour of the current cloud-init package, this causes an 
unexpected side effect that should be dealt with by disabling cloud-init 
in one of the methods I described earlier in this thread.


Are there use cases when cloud-init (as a service) may require to start 
repeatedly on consecutive usual VM runs?
If will need to change parameters user may use "Run Once" start with new 
parameters - in this case a 'disabled' file may be ignored.

But what reason to finding a configuration while usual run at all?

--
BR, Mike




On Wed, Nov 28, 2018 at 10:12 AM Eitan Raviv > wrote:


On Wed, Nov 28, 2018 at 7:29 AM Mike Lykov mailto:co...@ya.ru>> wrote:
 >
 > 27.11.2018 16:15, Eitan Raviv пишет:
 > > According to cloud-init 0.7.9 documentation cloud-init is
configured
 > > to run by default on each boot [1] and to render the user-selected
 > > network configuration on first boot [2]. Also, in absence of a data
 > > source to configure the network, it will fall back to
configuring DHCP
 > > on eth0 [2].
 > >
 > > As you noted, if you run a VM once, and then in the next
regular run
 > > the cloud-init flag is not selected in the VM configuration in
engine,
 > > there is no data-source and cloud-init falls back to dhcp as
 > > documented.
 >
 > Thanks for the explanation. What intended use of this
subsystem/feature
 > are supposed to?
 >
 > My setup is not in cloud, it's local and use static IP adresses
for VM.
 > I do not want to configure each VM network in console by hand.
 > I create VM from template (template have installed cloud-init
package),
 > configure cloud-init hostname/eth0 network in engine, and as "custom
 > script" (at the same moment) I set a "touch
 > /etc/cloud/cloud-init.disabled" ?

Either that or add custom script to disable just cloud-init network
re-config as you did manually.
Please consult the documentation for the custom script syntax and format
(e.g. search for 'runcmd' in
https://cloudinit.readthedocs.io/en/0.7.9/topics/examples.html)

 > Then I "Run once" a VM, stop it, and run as usual without data source
 > and fallback.
 > Or I name network interface not "eth0" and therefore without need for
 > custom script?

I did not test the outcome of assigning the static IP to another NIC.
Just sharing a thought...

 >
 >
 > > The 'marker' file you refer to are also documented as follows:
 > >
 > > * disabling cloud-init altogether [1] with: touch
/etc/cloud/cloud-init.disabled
 > > * preventing cloud-init from configuring the network [2] with: echo
 > > ‘network: {config: disabled}‘ >> /etc/cloud/cloud.cfg
 > > whichever scenario is used to run a VM, this can be accomplished by
 > > adding the above commands to the custom_script that cloud-init
runs at
 > > the last stage of its operation [3].
 > >
 > > There is possibly a third 'hack' 

[ovirt-users] Re: Additional routes on Interface

[Gianluca Cecchi]

On Thu, Dec 6, 2018 at 8:46 AM Sandro Emma  wrote:

> Hi,
>
> we are running a RHV 4.1 installation which is working fine except one
> issue:
>
> We have a Network which is only used for fencing(power Management via
> ilo), each host has an interface with this network and a custom ip, for
> this to work we need a few custom routes.
> At the moment we add the new routes via a plain route file under
> /etc/sysconfig/network-scripts/, but the engine flags this interface then
> as out-of-sync.
>
> How can we persist those changes across reboots and still be able to add
> new devices via the UI ?
>
> This looked promising but isnt working:
> https://ovirt.org/develop/release-management/features/network/networkreloaded/
>
> Thanks for any Help :)
> 
>

I never used this feature, but I remember that you can specify in vdsm.conf
a list of interfaces that you want vdsm not to manage so that you can
configure them manually for your specific targets
Eg. on my 4.2.7 host I see this in the plain vdsm.conf.rpmnew
"
# Comma-separated list of fnmatch-patterns for host nics to be hidden
# from vdsm.
# hidden_nics = w*,usb*

# Comma-separated list of fnmatch-patterns for host bonds to be hidden
# from vdsm.
# hidden_bonds =

# Comma-separated list of fnmatch-patterns for host vlans to be hidden
# from vdsm. vlan names must be in the format "dev.VLANID" (e.g.
# eth0.100, em1.20, eth2.200). vlans with alternative names must be
# hidden from vdsm (e.g. eth0.10-fcoe, em1.myvlan100, vlan200)
# hidden_vlans =
"
In case you apply anything, I think you had better create a file in
/etc/vdsm/vdsm.conf.d, such as 50_unmanaged_nics.conf containing

hidden_nics = eth3

to be preserved across updates.
With this parameter you shouldn't see the interface listed in setup host
networks of the host gui.
The concept came out last year when I posted a question related to OVN and
Marcin Mirecki kindly answered about it.
See here and the whole thread:
https://lists.ovirt.org/pipermail/users/2017-February/079772.html

Marcin, possibly you can add something for this particular need?

HIH,
Gianluca
___
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/WMYTLPXDDEVKJFKCXRLBUUE5MM24WERP/

[ovirt-users] Centos7.6

[Demeter Tibor]

Dear All, 

I just wondering I would like to make an upgrade from 4.2.5 to latest stable 
release of ovirt. 
Meanwhile centos7.6 was released. 
Will that compatible with the current release of ovirt? 
How is safe an upgrade now? 

Thanks in advance, 

Regards, 
Tibor 



___
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/5KMICT3FR4CHD4DEW5JLCRXMQVG77JWY/

[ovirt-users] vGPU

[董青龙]

Hi all,
I am testing vGPU in ovirt4.2. I have a nvidia p100 GPU installed in 
the host and I have installed the correct dirver. I followed this 
page(https://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Host_for_vGPU_Installation/)
 but I failed. In the "Host Devices tab" I got an device called "GP100GL [Tesla 
P100 PCIe 16GB]". I could not find any device of "mdev type". Anyone can help 
me? Thanks a lot!___
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/NIWMUM5QFZMTAXZJ7LZ5HX3ZB3B3UPFW/

[ovirt-users] Re: Centos7.6

[Pavol Brilla]

Hi

my testing setup is working flawlessly with CentOS 7.6, I did not encounter
any hiccups during operation.

On Thu, Dec 6, 2018 at 10:39 AM Demeter Tibor  wrote:

> Dear All,
>
> I just wondering I would like to make an upgrade from 4.2.5 to latest
> stable release of ovirt.
> Meanwhile centos7.6 was released.
> Will that compatible with the current release of ovirt?
> How is safe an upgrade now?
>
> Thanks in advance,
>
> Regards,
> Tibor
>
> ___
> 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/5KMICT3FR4CHD4DEW5JLCRXMQVG77JWY/
>


-- 

PAVOL BRILLA

RHV QUALITY ENGINEER, CLOUD

Red Hat Czech Republic, Brno 

TRIED. TESTED. TRUSTED. 
___
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/QCDJGXKKE4H27SRCGWBWPDEPEYLFR7NC/

[ovirt-users] Re: Centos7.6

[Sandro Bonazzola]

Il giorno gio 6 dic 2018 alle ore 10:39 Demeter Tibor 
ha scritto:

> Dear All,
>
> I just wondering I would like to make an upgrade from 4.2.5 to latest
> stable release of ovirt.
> Meanwhile centos7.6 was released.
> Will that compatible with the current release of ovirt?
> How is safe an upgrade now?
>

oVirt 4.2.7 is already compatible with CentOS 7.6.
I think that right now it's the best time to upgrade both oVirt and CentOS.



>
> Thanks in advance,
>
> Regards,
> Tibor
>
> ___
> 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/5KMICT3FR4CHD4DEW5JLCRXMQVG77JWY/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D 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/2YMENWMVRWAREZT4DD7LC5BBT2ZGA4IW/

[ovirt-users] Re: Repository ovirt-4.2 is listed more than once in the configuration

[Pavol Brilla]

Hi

from Quickstart Guide of ovirt[1], source of those repo files is
http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm

you are installing release rpm which will create needed repo files for
successful oVirt installation.  ( ovirt-4.2-dependencies.repo
ovirt-4.2.repo )

as for -pre repo files are coming from pre-release version, they are coming
from: https://resources.ovirt.org/pub/yum-repo/ovirt-release42-pre.rpm,
which should be not used in production environment, maybe some time ago you
needed some fix which was already merged to -pre but still not in stable
release?

Try to check if you have more than 1 release package installed:
yum list \*release\*

[1] https://ovirt.org/documentation/quickstart/quickstart-guide/

On Mon, Nov 26, 2018 at 1:14 PM Markus Frei  wrote:

> Hello everybody
>
> I am frequently receiving the following messages from ovirt:
>
> Repository ovirt-4.2-epel is listed more than once in the configuration
> Repository ovirt-4.2-centos-gluster312 is listed more than once in the
> configuration
> Repository ovirt-4.2-virtio-win-latest is listed more than once in the
> configuration
> Repository ovirt-4.2-centos-qemu-ev is listed more than once in the
> configuration
> Repository ovirt-4.2-centos-opstools is listed more than once in the
> configuration
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Repository ovirt-4.2-centos-ovirt42 is listed more than once in the
> configuration
> Repository ovirt-4.2 is listed more than once in the configuration
>
> I`ve got following repos configured in directory /etc/yum.repos.d:
>
> ovirt-4.2-dependencies.repo
> ovirt-4.2-pre-dependencies.repo
> ovirt-4.2-pre.repo
> ovirt-4.2.repo
>
> I deleted the 'pre' repos several times but apparently they are being
> recreated somehow.
>
> Can anybody explain this behaviour please and eventually the meaning of
> these 'pre' repos in generell as well?
>
> Thank you in advance.
>
> Kind regards,
>
> Chris
> ___
> 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/YNPMP7W6DAFOZHVGFU2X7OO3RZTPSYCL/
>


-- 

PAVOL BRILLA

RHV QUALITY ENGINEER, CLOUD

Red Hat Czech Republic, Brno 

TRIED. TESTED. TRUSTED. 
___
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/LT73Z55M5XR5RTGI6UPOSJEGY7MHHB6D/

[ovirt-users] Re: Additional routes on Interface

[Sandro Emma]

Wow that was quick :) 

The option hidden_vlans did exactly what i wanted :) ! 
___
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/TPHOVCTEKKCLKJCV3IRE2LLCHAGXC6CE/

[ovirt-users] Re: Cloud-init reset network configuration to default dhcp after reboot and regular run

[Eitan Raviv]

We will consider changing the behaviour. This is indeed not intuitive.

On Thu, Dec 6, 2018 at 10:24 AM Mike Lykov  wrote:

> 05.12.2018 13:04, Eitan Raviv пишет:
> > After further investigation I would like to share one more important
> > piece of information that explains the "reset" behaviour of the network
> > configuration:
>
> Thanks for that detailed clarification.
>
> > When a VM is started in 'Run once' mode, the initialization parameters
> > supplied for that run are always passed by engine to cloud-init in the
> > guest for application.
>
> It's clear and work as intended.
>
> > But if a VM is started in 'Run' mode, the initialization parameters are
> > passed to cloud-init on the guest only if this is the first run (be it
> > 'Run' or 'Run once'). On every consecutive run in 'Run' mode no
> > parameters are passed to the guest, and therefore (as I quoted from the
> > cloud-init documentation earlier in this thread) cloud-init falls back
> > to DHCP configuration on the guest.
>
>
> > When this behaviour was introduced into engine the reasoning was that
> > after the initial configuration of the VM, there is no reason to resend
> > the configuration on every 'Run' but only on 'Run once'.
>
> Yes, there is no reason, but for new user it looks very confusing:
>   - create VM
>   - configure cloud-init parameters (like IP addr)
>   - Run VM (not once), parameters applied (all OK? as it seems)
>   - work with/in VM
>   - Stop VM (maybe after period of time when VM counts as 'configured
> successfully') for some maintetance
>   - Run VM and try to access it (it is 'configured successfully' some
> time ago, isn't it?)
>   - NO ACCESS to VM and configurаtion is LOST
>   - try to access via console with 'WTF?' exclamation 
>
> Why cloud-init in this scenario after successful configuration is not
> turn off/disable himself (by touch that file, for example) ?
>
> Instead of it cloud-init+ovirt force user to:
>   - try to figure why configuration is lost, learn "custom script" format
>   - write "custom script" for touch /etc/cloud/cloud-init.disabled and
> reboot
>   - run once VM to apply parameters
>   - run VM as usual ?
>
>
> > Due to the behaviour of the current cloud-init package, this causes an
> > unexpected side effect that should be dealt with by disabling cloud-init
> > in one of the methods I described earlier in this thread.
>
> Are there use cases when cloud-init (as a service) may require to start
> repeatedly on consecutive usual VM runs?
> If will need to change parameters user may use "Run Once" start with new
> parameters - in this case a 'disabled' file may be ignored.
> But what reason to finding a configuration while usual run at all?
>
> --
> BR, Mike
>
>
> >
> > On Wed, Nov 28, 2018 at 10:12 AM Eitan Raviv  > > wrote:
> >
> > On Wed, Nov 28, 2018 at 7:29 AM Mike Lykov  > > wrote:
> >  >
> >  > 27.11.2018 16:15, Eitan Raviv пишет:
> >  > > According to cloud-init 0.7.9 documentation cloud-init is
> > configured
> >  > > to run by default on each boot [1] and to render the
> user-selected
> >  > > network configuration on first boot [2]. Also, in absence of a
> data
> >  > > source to configure the network, it will fall back to
> > configuring DHCP
> >  > > on eth0 [2].
> >  > >
> >  > > As you noted, if you run a VM once, and then in the next
> > regular run
> >  > > the cloud-init flag is not selected in the VM configuration in
> > engine,
> >  > > there is no data-source and cloud-init falls back to dhcp as
> >  > > documented.
> >  >
> >  > Thanks for the explanation. What intended use of this
> > subsystem/feature
> >  > are supposed to?
> >  >
> >  > My setup is not in cloud, it's local and use static IP adresses
> > for VM.
> >  > I do not want to configure each VM network in console by hand.
> >  > I create VM from template (template have installed cloud-init
> > package),
> >  > configure cloud-init hostname/eth0 network in engine, and as
> "custom
> >  > script" (at the same moment) I set a "touch
> >  > /etc/cloud/cloud-init.disabled" ?
> >
> > Either that or add custom script to disable just cloud-init network
> > re-config as you did manually.
> > Please consult the documentation for the custom script syntax and
> format
> > (e.g. search for 'runcmd' in
> > https://cloudinit.readthedocs.io/en/0.7.9/topics/examples.html)
> >
> >  > Then I "Run once" a VM, stop it, and run as usual without data
> source
> >  > and fallback.
> >  > Or I name network interface not "eth0" and therefore without need
> for
> >  > custom script?
> >
> > I did not test the outcome of assigning the static IP to another NIC.
> > Just sharing a thought...
> >
> >  >
> >  >
> >  > > The 'marker' file you refer to are also documented as follows:
> >  > >
> >  > > * di

[ovirt-users] Re: start vm without engine

[Michal Skrivanek]

> On 6 Dec 2018, at 12:30, David David  wrote:
> 
> > > On 29 May 2018, at 16:08, David David  > > > wrote:
> > > 
> > > hi.
> > > 
> > > How to start VM directly in hypervisor? ovirt-engine was crashed.
> 
> > that is not supported yet
> 
> > > 
> > > VM's id is known.
> > > 
> > > vdsclient VM, hasn't argumets for starting vm. 
> 
> 
> Hello again
> 
> > it does, but you need to connect storage and then supply the whole VM 
> > configuration which is not simple to do. 
> 
> Ok. How to do this ?
> 
> I have access to FC storage, where VM placed

you can use the persisted libvirt definition on host where it was running last 
if the host just crashed (it’s removed on clean guest shutdown though). If you 
have it you can connect the appropriate storage domain using vdsm-client, and 
then start the VM using that libvirt definition.
again, it’s not very easy to do.
In all other cases it would have to be generated by the engine again as the 
OVF_STORE OVF backup is an OVF and you need libvirt’s XML so you would have to 
convert it first anyway, so again nothing simple to do.

In disaster recovery scenrio you can just take the whole storage domain and 
import it into the new clean engine installation and you’ll get all the VMs

it depends what you really want to do

Thanks,
michal

> 
> вт, 29 мая 2018 г. в 18:53, Michal Skrivanek  >:
> 
> 
> > On 29 May 2018, at 16:08, David David  > > wrote:
> > 
> > hi.
> > 
> > How to start VM directly in hypervisor? ovirt-engine was crashed.
> 
> that is not supported yet
> 
> > 
> > VM's id is known.
> > 
> > vdsclient VM, hasn't argumets for starting vm. 
> 
> it does, but you need to connect storage and then supply the whole VM 
> configuration which is not simple to do.
> 
> > 
> > Thanks.
> > ___
> > 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/SDTALWD2CHOEE5LMYXK6PTDFORBM2UUN/
> >  
> > 
> 

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

[ovirt-users] Re: Centos7.6

[Demeter Tibor]

Ok, thank you for all! 
Regards, 

Tibor 

- 2018. dec.. 6., 11:06, Sandro Bonazzola  írta: 

> Il giorno gio 6 dic 2018 alle ore 10:39 Demeter Tibor < [
> mailto:tdeme...@itsmart.hu | tdeme...@itsmart.hu ] > ha scritto:

>> Dear All,

>> I just wondering I would like to make an upgrade from 4.2.5 to latest stable
>> release of ovirt.
>> Meanwhile centos7.6 was released.
>> Will that compatible with the current release of ovirt?
>> How is safe an upgrade now?

> oVirt 4.2.7 is already compatible with CentOS 7.6.
> I think that right now it's the best time to upgrade both oVirt and CentOS.

>> Thanks in advance,

>> Regards,
>> Tibor

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

> --

> SANDRO BONAZZOLA

> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

> [ https://www.redhat.com/ | Red Hat EMEA ]

> [ mailto:sbona...@redhat.com | sbona...@redhat.com ] [ https://red.ht/sig ]
___
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/2ZMM6QGOLK2JAXKJPIVHRCK6KE774TXW/

[ovirt-users] Hypconverged Gluster Setup hangs after TLS/SSL

[matthias . barmeier]

Hi,

tried to setup hyperconverged with glusterfs. I used three i7 with two 1TB 
Disks and two NICs. Everythin worked fine till:

[ INFO ] TASK [Set Engine public key as authorized key without validating the 
TLS/SSL certificates]

appears in the wizards window. Does anyone has a hint on what to do?
___
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/BI6Z576SKSTNQZRBCWLYMVFYTRZVZOCE/

[ovirt-users] Re: VMs import over slow 1gig interface instead of fast 10gig interface?

[johnmartin7042]

This had to be the most valuable piece of information I received from this 
article: " Even though points modify each of the time, consider adding an 
updated url to old articles or blog posts. If website visitors discover 
previous posts initially with outdated information and facts, they are able to 
find the existing version effortlessly as a result of your applied website 
link." 

When I put in articles and some of my posts end up getting older, they may 
still be relevant to the current market. In addition to that, if the 
information may need some new content, which I put in a new post, then I am 
able to do so by adding a link to the newer content. I appreciate that tip. 
Thanks.

Here in Atlanta, we appreciate it:
https://manage-offiice.com
https://notronsupport.com
https://offiice-setup.net
https://help-norton.me  
___
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/AGPNCMFJJNZOXTYBVWWQF65VLESJG36F/

[ovirt-users] Re: Centos7.6

[Derek Atkins]

Sandro Bonazzola  writes:

> oVirt 4.2.7 is already compatible with CentOS 7.6.
> I think that right now it's the best time to upgrade both oVirt and CentOS.

Is it safe to upgrade straight from 4.1.9 on 7.4 to 4.2.7 on 7.6?

-derek
-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
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/M5BKGNLWKKU2WXDIVGNNDBODUJXVRUTI/

[ovirt-users] [ANN] oVirt 4.3.0 Second Alpha Release is now available for testing

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the Second
Alpha Release of oVirt 4.3.0, as of December 6th, 2018

This is pre-release software. This pre-release should not to be used in
production.

Please take a look at our community page[1] to learn how to ask questions
and interact with developers and users.

All issues or bugs should be reported via oVirt Bugzilla[2].

This update is the second alpha release of the 4.3.0 version.

This release brings more than 80 enhancements and more than 330 bug fixes
on top of oVirt 4.2 series.

What's new in oVirt 4.3.0?

* Q35 chipset, support booting using UEFI and Secure Boot

* Skylake-server and AMD EPYC support

* New smbus driver in windows guest tools

* Improved support for v2v

* Tech preview for oVirt on Fedora 28

* Hundreds of bug fixes on top of oVirt 4.2 series

* New VM portal details page (see a preview here:
https://imgur.com/a/ExINpci)

* New Cluster upgrade UI

* OVN security groups

* IPv6 (static host addresses)

* LLDP Labeler

* Support for 3.6 and 4.0 data centers, clusters and hosts were removed

* Now using PostgreSQL 10


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 draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:

- oVirt Appliance is already available for both CentOS 7 and Fedora 28
(tech preview).

- oVirt Node NG  is already available for both CentOS 7

- oVirt Node NG for Fedora 28 (tech preview) is facing build issues on
Jenkins and will be released as soon as possible

Additional Resources:

* Read more about the oVirt 4.3.0 release highlights:
http://www.ovirt.org/release/4.3.0/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] https://www.ovirt.org/community/

[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt

[3] http://www.ovirt.org/release/4.3.0/

[4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D 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/LFIP22NNOCYOQBRFLD7346ERTDD4YN4T/

[ovirt-users] Strange migration issue

[Demeter Tibor]

Dear All, 

I've using ovirt from 3.4 and we have a strange, rarely problem with live 
migrations. 

- In most of case impossible to do a live migrate of VMs that have a lot of 
memory (16 gigs and more up to 40 GB) . 
- Those are need to try and try until the migration will be successful 
- impossible to understand why does working in a case and doesn't in another 
- it is happening always if there bigger load on vms, but only on big memory 
VM-s 
- The small VMs (2-4-8 gigs) can migrate without problems 
- In very rarely cases possible to migrate on first try. 
- We using the memory ballooning function on all of VMs. 

We using dedicated migration network with separated vlans, but on same physical 
lan (1gbe) with ovirtmgmt. 
At this moment, we don't use QoS for dedicate bandwidth. 

What can I do ? 

Thanks in advance, 
Regards, 

Tibor 




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

[ovirt-users] Re: Centos7.6

[Sandro Bonazzola]

Il giorno gio 6 dic 2018, 16:33 Derek Atkins  ha scritto:

> Sandro Bonazzola  writes:
>
> > oVirt 4.2.7 is already compatible with CentOS 7.6.
> > I think that right now it's the best time to upgrade both oVirt and
> CentOS.
>
> Is it safe to upgrade straight from 4.1.9 on 7.4 to 4.2.7 on 7.6?
>

did not test this personally but should work. I would recommend to update
ovirt engine first and rest of centos in second step





> -derek
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
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/UXLCQMYLYVT3BPOS3T6UQA4QVGWKVU4P/

[ovirt-users] Network Setup after ovirt node Install and before add node to cluster

[Stefan Wolf]

Hello,

 

I ve downloaded an installed OVIRT NODE 4.2.7.1.

During the installation I ‘ve setup a static ip (I ‘ve also tried dhcp, both 
work)

The installation passes and after the reboot ovirt node starts without any 
problems.

BUT the network is not configured.

I know https://www.ovirt.org/documentation/install-guide/chap-oVirt_Nodes/ and  
I know

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

 

and now I am between these two documents

oVirt is installed but network is not configured to add it to datacenter

 

of course I know the scripts under /etc/sysconfig/network-scripts

do I really have do edit it manuel?

 

if I change ip in command line

ip a add … dev..

and ip route add …

it fails to add node to datacenter

 

- with one of the last version I ‘ve added the IP address in bash

- added the host to datacenter,

- after reboot readd the ip address in bash after reboot

- an then I could change network settings in oVirt Manger

 

What is best practices for adding a node to datacenter when the ip address is 
not assigned after installation

 

Thx shb

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

[ovirt-users] 4.2.7 & centos 7.6 dependency problems

[Demeter Tibor]

Dear All, 
I would like to upgrade my ovirt 4.2.5 to 4.2.7. 

The hosted engine upgrade was success, but on the nodes i've got an dependency 
error: 

---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed 
--> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package: 
mesa-libgbm-18.0.5-3.el7.x86_64 
--> Processing Dependency: libwayland-server.so.0()(64bit) for package: 
mesa-libgbm-18.0.5-3.el7.x86_64 
---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed 
---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed 
--> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for 
package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64 
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed 
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 
---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed 
---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed 
--> Running transaction check 
---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed 
---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed 
---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be installed 
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed 
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 
--> Finished Dependency Resolution 
--> Running transaction check 
---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased 
---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed 
--> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 
--> Finished Dependency Resolution 
Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates) 
Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2 
Available: nbdkit-1.2.6-1.el7.x86_64 (base) 
nbdkit(x86-64) = 1.2.6-1.el7 
Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates) 
nbdkit(x86-64) = 1.2.6-1.el7_6.2 
Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel) 
nbdkit(x86-64) = 1.2.7-2.el7 
You could try using --skip-broken to work around the problem 
You could try running: rpm -Va --nofiles --nodigest 


How can I solve this? 

Thanks in advance, 

Regards, 

Tibor 




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

[ovirt-users] Re: 4.2.7 & centos 7.6 dependency problems

[Roberto Nunin]

Hi

I had a similar problem just yesterday.
I've disabled all three sources within CentOS-Base.repo.

My nodes are still 7.5, but hope that this can help anyway.
My update process, done from hested-engine gui, has completed after the
change.

BR



Il giorno gio 6 dic 2018 alle 20:19 Demeter Tibor  ha
scritto:

> Dear All,
> I would like to upgrade my ovirt 4.2.5 to 4.2.7.
>
> The hosted engine upgrade was success, but on the nodes i've got an
> dependency error:
>
> ---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed
> --> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package:
> mesa-libgbm-18.0.5-3.el7.x86_64
> --> Processing Dependency: libwayland-server.so.0()(64bit) for package:
> mesa-libgbm-18.0.5-3.el7.x86_64
> ---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed
> ---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed
> --> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for
> package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> ---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed
> ---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed
> --> Running transaction check
> ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed
> ---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed
> ---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be
> installed
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> --> Running transaction check
> ---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates)
>Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Available: nbdkit-1.2.6-1.el7.x86_64 (base)
>nbdkit(x86-64) = 1.2.6-1.el7
>Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates)
>nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel)
>nbdkit(x86-64) = 1.2.7-2.el7
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
>
>
> How can I solve this?
>
> Thanks in advance,
>
> Regards,
>
> Tibor
>
> ___
> 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/AUAO3LNG2LY56K37ARWH6ORSC6MZL5CA/
>
-- 
Roberto Nunin
___
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/AHPXAMQPTLTHTNZLBAYZROT3NIXA67VS/

[ovirt-users] Re: 4.2.7 & centos 7.6 dependency problems

[Demeter Tibor]

Dear Roberto, 

Thank you for your reply. 
I would like to upgrade the node os (not just ovirt) to latest (7.6) version. 
Thanks 

Regards, 

Tibor 

- 2018. dec.. 6., 21:39, Roberto Nunin  írta: 

> Hi

> I had a similar problem just yesterday.
> I've disabled all three sources within CentOS-Base.repo.

> My nodes are still 7.5, but hope that this can help anyway.
> My update process, done from hested-engine gui, has completed after the 
> change.

> BR

> Il giorno gio 6 dic 2018 alle 20:19 Demeter Tibor < [ 
> mailto:tdeme...@itsmart.hu
> | tdeme...@itsmart.hu ] > ha scritto:

>> Dear All,
>> I would like to upgrade my ovirt 4.2.5 to 4.2.7.

>> The hosted engine upgrade was success, but on the nodes i've got an 
>> dependency
>> error:

>> ---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed
>> --> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package:
>> mesa-libgbm-18.0.5-3.el7.x86_64
>> --> Processing Dependency: libwayland-server.so.0()(64bit) for package:
>> mesa-libgbm-18.0.5-3.el7.x86_64
>> ---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed
>> ---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed
>> --> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for
>> package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64
>> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
>> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
>> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
>> ---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed
>> ---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed
>> --> Running transaction check
>> ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed
>> ---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed
>> ---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be 
>> installed
>> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
>> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
>> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
>> --> Finished Dependency Resolution
>> --> Running transaction check
>> ---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased
>> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
>> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
>> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
>> --> Finished Dependency Resolution
>> Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates)
>> Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2
>> Available: nbdkit-1.2.6-1.el7.x86_64 (base)
>> nbdkit(x86-64) = 1.2.6-1.el7
>> Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates)
>> nbdkit(x86-64) = 1.2.6-1.el7_6.2
>> Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel)
>> nbdkit(x86-64) = 1.2.7-2.el7
>> You could try using --skip-broken to work around the problem
>> You could try running: rpm -Va --nofiles --nodigest

>> How can I solve this?

>> Thanks in advance,

>> Regards,

>> Tibor

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

> --
> Roberto Nunin
___
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/BH6UKVHFNACOQV7Y7YWCV2YP54SUQJJQ/

[ovirt-users] Re: 4.2.7 & centos 7.6 dependency problems

[Simon Coter]

Hi Tibor,

the update is trying to install:

nbdkit(x86-64) = 1.2.7-2.el7

while you only have:

nbdkit(x86-64) = 1.2.6-1.el7_6.2

1.2.7 release is available on ovirt-4.2-epel repository while 1.2.6 is part of 
CentOS “Base” and “Updates”.
The problem is that "nbdkit-plugin-vddk” has only 1.2.6 release and this 
depends on “ndbkit”.
Possible workaround that should work:

Edit the .repo containing “ovirt-4.2-epel” and add the following line to 
the “ovirt-4.2-epel” entry:

exclude=ndbkit*

then, rerun the update.

Simon

> On Dec 6, 2018, at 10:27 PM, Demeter Tibor  wrote:
> 
> Dear Roberto,
> 
> Thank you for your reply.
> I would like to upgrade the node os (not just ovirt) to latest (7.6) version. 
> Thanks
> 
> Regards,
> 
> Tibor
> 
> 
> 
> - 2018. dec.. 6., 21:39, Roberto Nunin  írta:
> Hi
> 
> I had a similar problem just yesterday.
> I've disabled all three sources within CentOS-Base.repo.
> 
> My nodes are still 7.5, but hope that this can help anyway.
> My update process, done from hested-engine gui, has completed after the 
> change.
> 
> BR
> 
> 
> 
> Il giorno gio 6 dic 2018 alle 20:19 Demeter Tibor  > ha scritto:
> Dear All,
> I would like to upgrade my ovirt 4.2.5 to 4.2.7.
> 
> The hosted engine upgrade was success, but on the nodes i've got an 
> dependency error:
> 
> ---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed
> --> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package: 
> mesa-libgbm-18.0.5-3.el7.x86_64
> --> Processing Dependency: libwayland-server.so.0()(64bit) for package: 
> mesa-libgbm-18.0.5-3.el7.x86_64
> ---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed
> ---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed
> --> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for 
> package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> ---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed
> ---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed
> --> Running transaction check
> ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed
> ---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed
> ---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be 
> installed
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> --> Running transaction check
> ---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: 
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates)
>Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Available: nbdkit-1.2.6-1.el7.x86_64 (base)
>nbdkit(x86-64) = 1.2.6-1.el7
>Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates)
>nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel)
>nbdkit(x86-64) = 1.2.7-2.el7
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> 
> 
> How can I solve this?
> 
> Thanks in advance,
> 
> Regards,
> 
> Tibor
> 
> 
> ___
> 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/AUAO3LNG2LY56K37ARWH6ORSC6MZL5CA/
>  
> 
> -- 
> Roberto Nunin
> 
> 
> 
> 
> ___
> 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/BH6UKVHFNACOQV7Y7YWCV2YP54SUQJJQ/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statem

[ovirt-users] Re: Interface issue when using a macOS workstation

[Vineet Khandpur]

Anyone from RedHat care to chime in?

vk

Vineet Khandpur
UNIX System Administrator
Information Technology Services
University of Alberta Libraries
+1-780-492-4718


On Tue, 4 Dec 2018 at 16:20, Vineet Khandpur  wrote:

> * iTerm2 is a far superior alternative to ...
> vk
> 
> Vineet Khandpur
> UNIX System Administrator
> Information Technology Services
> University of Alberta Libraries
> +1-780-492-4718
>
>
> On Tue, 4 Dec 2018 at 16:19, Vineet Khandpur  wrote:
>
>> for spice terminal this worked like a charm for me:
>> https://rizvir.com/articles/ovirt-mac-console/
>> iTerm2 is a far superior to Terminal.
>>
>> But as far as the web interface, it looks to me like the way the GUI
>> (javascript?) is handling, or rather not handling CMD key press from Apple
>> keyboards .. I think.
>>
>> CNTL click is understood, but to Apple CNTL+click is a right click
>> equivalent, and I'm getting the pop up menu for oVirt VM guests: (New,
>> Edit, Remove, Run, Suspend .. etc)
>>
>> vk
>> 
>> Vineet Khandpur
>> UNIX System Administrator
>> Information Technology Services
>> University of Alberta Libraries
>> +1-780-492-4718
>>
>>
>> On Tue, 4 Dec 2018 at 15:52, Andrei Verovski 
>> wrote:
>>
>>> Hi,
>>>
>>> Its not a single quirk with a Mac - spice console also don't work.
>>> Terminal application is a trash.
>>>
>>> Install any Linux desktop under VirtualBox and forget that nightmare.
>>>
>>>
>>> On 12/5/18 12:45 AM, Vineet Khandpur wrote:
>>> > Hello.
>>> > Apologies if this has been asked before, but Google came up empty for
>>> me.
>>> >
>>> > Recently converted to a Macbook, I've noticed an issue with the oVirt
>>> > interface. When in the Compute > Virtual Machines screen, when I'm
>>> > trying to select multiple VMs, CMD+click doesn't work. I cannot select
>>> > multiple machines at the same time. CNTL+click in macOS sends a right
>>> > click to the interface, and no combination of OPTION/CONTROL/CMD
>>> > works. Tried on Chrome, Firefox and Safari.
>>> >
>>> > SHIFT+click works on selecting multiple hosts when they are all in a
>>> > row, but random select via CMD+click doesn't.
>>> >
>>> > A nudge in the right direction would be greatly appreciated.
>>> >
>>> > Thanks.
>>> > vk
>>> > 
>>> > Vineet Khandpur
>>> > UNIX System Administrator
>>> > Information Technology Services
>>> > University of Alberta Libraries
>>> > +1-780-492-4718
>>> >
>>> > ___
>>> > 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/DZUNBITT3GODDWYJ7VDWUP7APPBFGLJI/
>>>
>>>
___
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/WU76U7QMQ5SKFXLMVX2323K7UH54IKWB/

[ovirt-users] Re: Hypconverged Gluster Setup hangs after TLS/SSL

[Sahina Bose]

I think you may be running into
https://bugzilla.redhat.com/show_bug.cgi?id=1651516

On Thu, Dec 6, 2018 at 7:30 PM  wrote:
>
> Hi,
>
> tried to setup hyperconverged with glusterfs. I used three i7 with two 1TB 
> Disks and two NICs. Everythin worked fine till:
>
> [ INFO ] TASK [Set Engine public key as authorized key without validating the 
> TLS/SSL certificates]
>
> appears in the wizards window. Does anyone has a hint on what to do?
> ___
> 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/BI6Z576SKSTNQZRBCWLYMVFYTRZVZOCE/
___
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/4X2RXB5GIH4GBRU6FXMQFGRBBQIQKL5A/

[ovirt-users] DATA Domain with 1GB limit

[mohamedbehbity]

Once the attached the domain to a data center, the real size of the DAT domain 
is displayed as 1 GB
___
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/ZX6TXHUYW52SXALQBO6J563SE7GXK2EE/