[ovirt-users] oVirt Metrics Store installation

2018-09-30 Thread Markus Schaufler
Hi!

I'm having trouble installing the oVirt Metrics Store following this 
https://www.ovirt.org/develop/release-management/features/metrics/metrics-store-installation/
 respectively this guide 
https://www.ovirt.org/develop/release-management/features/metrics/setting-up-viaq-logging/

When executing the test script
ANSIBLE_LOG_PATH=/tmp/ansible-prereq.log ansible-playbook -vvv -e 
@/root/vars.yaml -i /root/ansible-inventory-origin-39-aio 
playbooks/prerequisites.yml

following error occurs:


Using module file 
/usr/lib/python2.7/site-packages/ansible/modules/packaging/os/yum.py
 EXEC /bin/sh -c '/usr/bin/python && sleep 0'
fatal: [localhost]: FAILED! => {
"attempts": 3,
"changed": false,
"invocation": {
"module_args": {
"allow_downgrade": false,
"bugfix": false,
"conf_file": null,
"disable_gpg_check": false,
"disable_plugin": [],
"disablerepo": null,
"enable_plugin": [],
"enablerepo": null,
"exclude": null,
"install_repoquery": true,
"installroot": "/",
"list": null,
"name": [
"docker",
"atomic",
"skopeo"
],
"security": false,
"skip_broken": false,
"state": "present",
"update_cache": false,
"update_only": false,
"validate_certs": true
}
},
"msg": "Error: Package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64 
(centosplus)\n   Requires: python-docker-py >= 1.7.2-1\n   
Available: docker-python-1.4.0-115.el7.x86_64 (centosplus)\n   
python-docker-py = 1.4.0-115.el7\n   Available: 
python-docker-py-1.10.6-3.el7.noarch (centosplus)\n   
python-docker-py = 1.10.6-3.el7\n   Available: 
python-docker-py-1.10.6-4.el7.noarch (centosplus)\n   
python-docker-py = 1.10.6-4.el7\n   Available: 
python2-docker-2.4.2-1.2.el7.noarch (centos-openshift-origin-testing-cbs)\n 
  python-docker-py = 2.4.2-1.2.el7\n   Installed: 
python2-docker-3.3.0-1.el7.noarch (@centos-openshift-origin-testing)\n  
 Not found\n",
"rc": 1,
"results": [
"2:docker-1.13.1-74.git6e3bb8e.el7.centos.x86_64 providing docker is 
already installed",
"Loaded plugins: fastestmirror\nLoading mirror speeds from cached 
hostfile\nResolving Dependencies\n--> Running transaction check\n---> Package 
atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing 
Dependency: python-docker-py >= 1.7.2-1 for package: 
1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage 
python-docker-py-1.10.6-4.el7.noarch is obsoleted by 
python2-docker-3.3.0-1.el7.noarch which is already installed\n--> Processing 
Dependency: runc for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> 
Processing Dependency: python-dateutil for package: 
1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: ostree for 
package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: 
gomtree for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n---> Package 
skopeo.x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos will be installed\n--> 
Running transaction check\n---> Package atomic.x86_64 
1:1.22.1-22.git5a342e3.el7 will be installed\n--
 > Processing Dependency: python-docker-py >= 1.7.2-1 for package: 
 > 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage 
 > python-docker-py-1.10.6-4.el7.noarch is obsoleted by 
 > python2-docker-3.3.0-1.el7.noarch which is already installed\n---> Package 
 > gomtree.x86_64 0:0.5.0-0.2.git16da0f8.el7 will be installed\n---> Package 
 > ostree.x86_64 0:2018.5-1.el7 will be installed\n--> Processing Dependency: 
 > libarchive.so.13()(64bit) for package: ostree-2018.5-1.el7.x86_64\n---> 
 > Package python-dateutil.noarch 0:1.5-7.el7 will be installed\n---> Package 
 > runc.x86_64 0:1.0.0-37.rc5.dev.gitad0f525.el7 will be installed\n--> 
 > Processing Dependency: criu for package: 
 > runc-1.0.0-37.rc5.dev.gitad0f525.el7.x86_64\n--> Running transaction 
 > check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be 
 > installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for 
 > package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage 
 > python-docker-py-1.10.6-4.el7.noarch is obsoleted by 
 > python2-docker-3.3.0-1.el7.
 noarch which is already installed\n---> Package criu.x86_64 0:3.5-4.el7 will 
be installed\n--> Processing Dependency: 
libprotobuf-c.so.1(LIBPROTOBUF_C_1.0.0)(64bit) for package: 
criu-3.5-4.el7.x86_64\n--> Processing Dependency: libprotobuf-c.so.1()(64bit) 
for package: criu-3.5-4.el7.x86_64\n--> Processing Dependency: 
libnet.so.1()(64bit) for package: criu-3.5-4.el7.x86_64\n---> Package 
libarchive.x86_64 0:3.1.2-10.el7_2 will be installed\n--> Running transaction 
check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be 

[ovirt-users] Re: Suggestion: Addition of a one-off PXE boot option in the "Edit Virtual Machine > Boot Options" section

2018-09-30 Thread Maton, Brett
As suggested may be run once will suit, there's a checkbox at the bottom of
the option panel to roll-back options after reboot.

On Sat, 29 Sep 2018 at 22:06, Zach Dzielinski 
wrote:

> My current usage of oVirt requires me to switch the boot priorities for
> virtual machines from hard disk to pxe fairly often.
>
> It would be nice to see an option added in that would set a one-off pxe
> boot for virtual machines, reverting back to the original boot priorities
> after restart.
>
> This would save some time when dealing with multiple machines, by
> eliminating the need to switch them to pxe and then back to their previous
> boot options in the middle of their boot process.
> ___
> 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/KQOMOM2J6VXOHR6EL6DYGBPLEHSN2RM7/
>
___
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/KBVYZXEKSTOB4HOGP7NIQCSXW4Y555KM/


[ovirt-users] liveliness check fails on one host

2018-09-30 Thread g . vasilopoulos
I have an ovirt installation (4.2.6), and I have come accross this issue: 
Hosted engine can migrate to a certain host say host5. Admin portal is working 
fine, everything is working fine AFAIK but hosted-engne --vm-status shows 
"failed livelines check", when engine is on that host, so after a while the 
engine migrates somewhere else, it not a terrible problem, but it is annoying 
and I would like to know why is this happening, and if there is a way to fix it
On every other host in the cluster this problem does not exists. firewall rules 
are exactly the same on hosts (in fact they are copied) . Any places to look at?
Thank you
___
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/YO5IP3P4FGXVWFRL7HKCE72JFCW73FF5/


[ovirt-users] Re: Networking in oVirt

2018-09-30 Thread g . vasilopoulos
I'm not an expert but as far as I can tell, if your router supports a secondary 
ip in that network and routes these packets to the internet it should work. If 
not you should do NAT/Masquerade the vm network to the internet. But that is 
something that is not in ovirt configuration to handle, you have to do it with 
other means.
___
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/74AL53ZO2PZBRU3G7FAJRLMGQUEM42S6/