[ovirt-users] Varying degree of failures after updating from 4.4.8 to 4.4.9

2021-12-11 Thread Paul-Erik Törrönen

I have a server running the engine on CentOS Stream.

2 hosts running likewise  CentOS 8 Stream (C8S) and 2 hosts running 
Rocky Linux 8.5 (RL8.5).


I had several VMs running on the 8S without any issue. After the oVirt 
upgrade, which partially fails* on the C8S-machines, the VMs on the 
C8S-hosts appear to be running, according to the oVirt GUI, but I can 
neither ping, ssh or even open a virt-viewer console to the VM. The 
console shows just a black screen.


The only thing shown in the GUI is a note that the guest agent should be 
updated on the VM, so there appears to be some kind of communication 
between the engine/host and the VM.


If I create a new VM on the C8S, I get the same result: No access to it, 
console is black despite the fact that oVirt GUI shows the VM as running 
and green.


If I create a VM on one of the RL8.5 hosts, the console does work, I can 
eg. complete the GUI-installation (from CD) there. But after the boot, 
despite having configured the network correctly in the oVirt-GUI and in 
the installation process, the VM (using the console) is unable to raise 
the network.


No error is displayed in the oVirt GUI neither for the cluster, DC, host 
nor VM.


No apparent log-error neither in the engine-server nor the hosts.

Stopped the firewalld on both in the engine-server as well as the hosts, 
but this did not change anything.


It seems that the 4.4.9-upgrade somehow broke the oVirt logical 
networking, completely on C8S-hosts.


* The C8S hosts fail on update WRT the following packages:

Error:
 Problem 1: package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires 
rsyslog = 8.2102.0-5.el8, but none of the providers can be installed
  - cannot install both rsyslog-8.2102.0-6.el8.x86_64 and 
rsyslog-8.2102.0-5.el8.x86_64
  - cannot install the best update candidate for package 
rsyslog-openssl-8.2102.0-5.el8.x86_64
  - cannot install the best update candidate for package 
rsyslog-8.2102.0-5.el8.x86_64
 Problem 2: package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires 
rsyslog-openssl, but none of the providers can be installed
  - package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 
8.2102.0-5.el8, but none of the providers can be installed
  - cannot install both rsyslog-8.2102.0-6.el8.x86_64 and 
rsyslog-8.2102.0-5.el8.x86_64
  - package rsyslog-elasticsearch-8.2102.0-6.el8.x86_64 requires rsyslog 
= 8.2102.0-6.el8, but none of the providers can be installed
  - cannot install the best update candidate for package 
rsyslog-elasticsearch-8.2102.0-5.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-host-dependencies-4.4.9-2.el8.x86_64
 Problem 3: problem with installed package 
rsyslog-openssl-8.2102.0-5.el8.x86_64
  - package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 
8.2102.0-5.el8, but none of the providers can be installed
  - cannot install both rsyslog-8.2102.0-6.el8.x86_64 and 
rsyslog-8.2102.0-5.el8.x86_64
  - package rsyslog-mmjsonparse-8.2102.0-6.el8.x86_64 requires rsyslog = 
8.2102.0-6.el8, but none of the providers can be installed
  - cannot install the best update candidate for package 
rsyslog-mmjsonparse-8.2102.0-5.el8.x86_64
 Problem 4: package ovirt-host-4.4.9-2.el8.x86_64 requires 
ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be 
installed
  - package ovirt-host-dependencies-4.4.9-2.el8.x86_64 requires 
rsyslog-openssl, but none of the providers can be installed
  - package rsyslog-openssl-8.2102.0-5.el8.x86_64 requires rsyslog = 
8.2102.0-5.el8, but none of the providers can be installed
  - cannot install both rsyslog-8.2102.0-6.el8.x86_64 and 
rsyslog-8.2102.0-5.el8.x86_64
  - package rsyslog-mmnormalize-8.2102.0-6.el8.x86_64 requires rsyslog = 
8.2102.0-6.el8, but none of the providers can be installed
  - cannot install the best update candidate for package 
rsyslog-mmnormalize-8.2102.0-5.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-host-4.4.9-2.el8.x86_64


The RL8.5 have no issues with the rsyslog-* packages which are:
rsyslog-8.2102.0-5.el8.x86_64
rsyslog-elasticsearch-8.2102.0-5.el8.x86_64
rsyslog-mmjsonparse-8.2102.0-5.el8.x86_64
rsyslog-mmnormalize-8.2102.0-5.el8.x86_64
rsyslog-openssl-8.2102.0-5.el8.x86_64

What can I still check at this point?

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


[ovirt-users] Re: Update to 4.4.8 leaves cluster in a circular error-state

2021-09-03 Thread Paul-Erik Törrönen

On 9/2/21 9:16 AM, Lucia Jelinkova wrote:
Could you please share more details about the CPU problem you're facing? 
There shouldn't be any breaking change in that CPU definition in 4.4+ 
compatibility version.


Unfortunately not, I've already made irreversible changes to the cluster 
so that I can no longer reproduce the error which I got when I tried to 
activate one of the Dell hosts and which resulted in an error about the 
CPU family.


After having wiped out most of the configurations I still do get a 
related error:


"The host CPU does not match the Cluster CPU Type and is running in a 
degraded mode. It is missing the following CPU flags: vmx, nx, 
model_Westmere, aes. Please update the host CPU microcode or change the 
Cluster CPU Type."


This error is not quite accurate since lscpu does list all of the flags 
mentioned above, except for the model_Westmere.


IIRC there were some comments in the mailing list earlier this year WRT 
this flag-mismatch and being related to incompatible linux-firmware 
package. Currently the host that generates this error has this package 
installed:


Name: linux-firmware
Version : 20210702
Release : 103.gitd79c2677.el8

Will need to dig through the mailing list archives.

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


[ovirt-users] Update to 4.4.8 leaves cluster in a circular error-state

2021-09-01 Thread Paul-Erik Törrönen
Having updated rpm-packages for a DC with a cluster containing 2 hosts 
(and executed the engine-setup on the engine machine), I now face the 
following issue:


One of the VMs had a couple of snapshots and apparently this interferes 
with the upgrade of the cluster version, which currently is 4.4.


The 4.4 has become incompatible with the chosen CPU architecture (Intel 
Westmere Family, the hosts are both Dell x10-series with Xeon X56xx 
CPUs) and requires an upgrade to newer compatibility version, 4.6 
presumably, so the DC/Cluster state is "unknown". However I can't do 
this because the snapshots exists. I get the "Cannot change cluster 
version since following VMs are previewing snapshots:" listing a VM with 
snapshots. The snapshots in turn can not be Commit/Undo because: "Cannot 
revert to Snapshot. Unknown Data Center status.".


So how do I break this circular error? The VM itself is not essential, 
it can be removed if that solves the case. However this can not be 
completed from the UI because: "Cannot remove VM. Unknown Data Center 
status.".


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


[ovirt-users] Re: Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup

2021-09-01 Thread Paul-Erik Törrönen

On 8/31/21 4:19 PM, Sandro Bonazzola wrote:
Please "yum update ovirt-release44" so it will pull in the new 
repositories needed to satisfy the dependencies.


Yup, this seems to have fixed it. Strange that a regular 'dnf update' 
would not update also the ovirt-release44 package.


Anyhow, the new issue is now a circular one, I'll write a separate email 
about that.


Thank you,

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


[ovirt-users] Re: Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup

2021-08-31 Thread Paul-Erik Törrönen

On 2021-08-17 11:12, Dana Elfassy wrote:

The execution of the task itself is fine - we're always installing this
package because of dependencies.
As for its failure- looks like an issue with the repositories.
Please run $ yum repolist
on the host and copy the output


Sorry for replying so late, was on a 2-week road-trip.

$ yum repolist
repo id  
   repo name
appstream
   CentOS Stream 8 - AppStream
baseos   
   CentOS Stream 8 - BaseOS
elasticsearch-7.x
   Elasticsearch repository for 7.x 
packages
epel-next
   Extra Packages for Enterprise 
Linux 8 - Next - x86_64
extras   
   CentOS Stream 8 - Extras
ovirt-4.4
   Latest oVirt 4.4 Release
ovirt-4.4-centos-ceph-pacific
   Ceph packages for x86_64
ovirt-4.4-centos-gluster8
   CentOS-8 - Gluster 8
ovirt-4.4-centos-opstools
   CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-stream-advanced-virtualization  
   Advanced Virtualization CentOS 
Stream packages for x86_64
ovirt-4.4-centos-stream-nfv-openvswitch  
   CentOS-8 - NFV OpenvSwitch
ovirt-4.4-centos-stream-ovirt44  
   CentOS-8 Stream - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp  
   Copr repo for ovsdbapp owned by 
mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible 
   Copr repo for gluster-ansible 
owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection 
   Copr repo for EL8_collection 
owned by sbonazzo
ovirt-4.4-epel   
   Extra Packages for Enterprise 
Linux 8 - x86_64
ovirt-4.4-openstack-train
   OpenStack Train Repository
ovirt-4.4-virtio-win-latest  
   virtio-win builds roughly 
matching what will be shipped in upcoming RHEL
powertools   
   CentOS Stream 8 - PowerTools


Then there's also this:

$ dnf update
Last metadata expiration check: 0:28:17 ago on Tue 31 Aug 2021 12:45:32 
PM EEST.

Error:
 Problem 1: cannot install the best update candidate for package 
ovirt-host-dependencies-4.4.7-1.el8.x86_64
  - nothing provides python3-os-brick needed by 
ovirt-host-dependencies-4.4.8-1.el8.x86_64
 Problem 2: package ovirt-host-4.4.8-1.el8.x86_64 requires 
ovirt-host-dependencies = 4.4.8-1.el8, but none of the providers can be 
installed
  - cannot install the best update candidate for package 
ovirt-host-4.4.7-1.el8.x86_64
  - nothing provides python3-os-brick needed by 
ovirt-host-dependencies-4.4.8-1.el8.x86_64



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


[ovirt-users] Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup

2021-08-15 Thread Paul-Erik Törrönen
I have an existing oVirt-installation to which I want to add a new host 
(from the UI).


However the adding fails because oVirt tries to then install the 
ovirt-hosted-engine-setup despite the fact that in the New host-dialog I 
left the Choose hosted engine deployment action as None.


As a result the installation then aborts:

2021-08-15 13:17:37 EEST - TASK [ovirt-host-deploy-vdsm : Install 
ovirt-hosted-engine-setup package] **

2021-08-15 13:17:37 EEST -
2021-08-15 13:17:37 EEST - fatal: [new.host]: FAILED! => {"changed": 
false, "failures": ["No package ovirt-hosted-engine-setup available."], 
"msg": "Failed to install some of the specified packages", "rc": 1, 
"results": []}

2021-08-15 13:17:37 EEST - {
  "status" : "OK",
  "msg" : "",
  "data" : {
"uuid" : "98a244fb-15da-4192-a8fc-b23a5e5b7594",
"counter" : 55,
"stdout" : "fatal: [new.host]: FAILED! => {\"changed\": false, 
\"failures\": [\"No package ovirt-hosted-engine-setup available.\"], 
\"msg\": \"Failed to install some of the specified packages\", \"rc\": 
1, \"results\": []}",

"start_line" : 47,
"end_line" : 48,
"runner_ident" : "fe710372-fdb1-11eb-81f0-ecf4bb63099f",
"event" : "runner_on_failed",
"pid" : 24931,
"created" : "2021-08-15T10:17:35.963320",
"parent_uuid" : "ecf4bb63-099f-2448-1b83-01a7",
"event_data" : {
  "playbook" : "ovirt-host-deploy.yml",
  "playbook_uuid" : "8f70f945-4008-4159-b469-7ff04c9c242b",
  "play" : "all",
  "play_uuid" : "ecf4bb63-099f-2448-1b83-0006",
  "play_pattern" : "all",
  "task" : "Install ovirt-hosted-engine-setup package",
  "task_uuid" : "ecf4bb63-099f-2448-1b83-01a7",
  "task_action" : "yum",
  "task_args" : "",
  "task_path" : 
"/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6",

  "role" : "ovirt-host-deploy-vdsm",
  "host" : "new.host",
  "remote_addr" : "new.host",
  "res" : {
"msg" : "Failed to install some of the specified packages",
"failures" : [ "No package ovirt-hosted-engine-setup available." ],
"results" : [ ],
"rc" : 1,
"invocation" : {
  "module_args" : {
"name" : [ "ovirt-hosted-engine-setup" ],
"state" : "present",
"allow_downgrade" : false,
"autoremove" : false,
"bugfix" : false,
"disable_gpg_check" : false,
"disable_plugin" : [ ],
"disablerepo" : [ ],
"download_only" : false,
"enable_plugin" : [ ],
"enablerepo" : [ ],
...

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


[ovirt-users] Ansible ovirt.hosts has no port setting

2020-06-13 Thread Paul-Erik Törrönen

Running oVirt 4.4.

While setting up ovirt with ansible, I noticed that there is no 
parameter for setting the ssh port of the hosts (which is present if one 
adds an host on the GUI).


I tried adding the port as a part of the address, but that field is 
apparently evaluated as FQDN only.


I did circumvent this by adding FQDN-labeled sections with 
Port-definition  ~/.ssh/config for ovirt-user on the engine-machine (not 
hosted), but this only got me a step further since the configuration in 
the engine still is without a port definition and falls back to 22 as a 
result.


Running the ansible playbook with -vvv I can see the following:

Using module file 
/usr/lib/python3.6/site-packages/ansible/modules/cloud/ovirt/ovirt_host.py
<127.0.0.1> PUT 
/root/.ansible/tmp/ansible-local-3041af74sxb1/tmpjlyq4ic8 TO 
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py
<127.0.0.1> EXEC /bin/sh -c 'chmod u+x 
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/ 
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py 
&& sleep 0'
<127.0.0.1> EXEC /bin/sh -c '/usr/bin/python3.6 
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py 
&& sleep 0'
<127.0.0.1> EXEC /bin/sh -c 'rm -f -r 
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/ 
> /dev/null 2>&1 && sleep 0'

The full traceback is:
Traceback (most recent call last):
  File 
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/modules/cloud/ovirt/ovirt_host.py", 
line 639, in main
  File 
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/module_utils/ovirt.py", 
line 785, in action

poll_interval=self._module.params['poll_interval'],
  File 
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/module_utils/ovirt.py", 
line 359, in wait

raise Exception("Error while waiting on result state of the entity.")
Exception: Error while waiting on result state of the entity.
failed: [localhost] (item=myHost) => {
"ansible_loop_var": "item",
"changed": false,
"invocation": {
"module_args": {
"activate": true,
"address": null,
"check_upgrade": true,
"cluster": null,
"comment": null,
"fetch_nested": false,
"force": false,
"hosted_engine": null,
"id": null,
"iscsi": null,
"kdump_integration": null,
"kernel_params": null,
"name": "myHost",
"nested_attributes": [],
"override_display": null,
"override_iptables": null,
"password": null,
"poll_interval": 3,
"power_management_enabled": null,
"public_key": true,
"reboot_after_upgrade": true,
"spm_priority": null,
"state": "reinstalled",
"timeout": 600,
"vgpu_placement": null,
"wait": true
}
},
"item": {
"address": "myHost.myDomain",
"affinity_labels": [],
"auto_numa_status": "unknown",
"certificate": {
"organization": "myDomain",
"subject": "O=myDomain,CN=myHost.myDomain"
},
"cluster": {
"href": 
"/ovirt-engine/api/clusters/3642e08b-1311-4f8a-803b-897321513b0b",

"id": "3642e08b-1311-4f8a-803b-897321513b0b"
},
"comment": "",
"cpu": {
"speed": 0.0,
"topology": {}
},
"device_passthrough": {
"enabled": false
},
"devices": [],
"external_network_provider_configurations": [],
"external_status": "ok",
"hardware_information": {
"supported_rng_sources": []
},
"hooks": [],
"href": 
"/ovirt-engine/api/hosts/22623d77-069e-4feb-86db-03b08bc67c1a",

"id": "22623d77-069e-4feb-86db-03b08bc67c1a",
"katello_errata": [],
"kdump_status": "unknown",
"ksm": {
"enabled": false
},
"max_scheduling_memory": 0,
"memory": 0,
"name": "myHost",
"network_attachments": [],
"nics": [],
"numa_nodes": [],
"numa_supported": false,
"os": {
"custom_kernel_cmdline": ""
},
"permissions": [],
"port": 54321,
"power_management": {
"automatic_pm_enabled": true,
"enabled": false,
"kdump_detection": true,
"pm_proxies": []
},
"protocol": "stomp",
"se_linux": {},
"spm": {
"priority": 5,
"status": "none"
},
"ssh": {
"fingerprint": "SHA256:abc...",
"port": 22
},
"statistics": [],
"status": "install_failed",

[ovirt-users] Re: First ovirt 4.4 installation failing

2020-06-09 Thread Paul-Erik Törrönen

On 2020-06-09 11:26, Yedidyah Bar David wrote:
On Tue, Jun 9, 2020 at 10:23 AM Paul-Erik Törrönen  
wrote:
You can't eg. have a ed25519-only setup as the installation tries to 
use

RSA.



Thanks for this comment. Added a note for you on Wart's bug 1845271.


Thank you.


Do you think this is a significant limitation?


No, unless you get others requesting this particular support. I only 
stumbled across this as I am setting up my home network from scratch 
with a minimal ansible script collection which includes hardening the 
ssh.


Nonetheless it would be a good to mention it in documentation.

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


[ovirt-users] Re: First ovirt 4.4 installation failing

2020-06-09 Thread Paul-Erik Törrönen

On 2020-06-08 08:58, Yedidyah Bar David wrote:

I agree it's not detailed enough.
We have it briefly mentioned e.g. here:
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#host-firewall-requirements_SHE_cockpit_deploy
For some reason it's marked "Optional", not sure why.


I think it should also be pointed out that only certain keys are 
supported.


You can't eg. have a ed25519-only setup as the installation tries to use 
RSA.


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


Re: [ovirt-users] Confused by logical networks

2018-02-24 Thread Paul-Erik Törrönen

On 2018-02-23 08:41, Yaniv Kaul wrote:

There's no reason really to assign IPs to hosts on the logical network.


Ah yes, you're correct.

I was using the physical host as a GW so that the VMs on the logical 
network would have an access point to outside (like the CentOS 
repositories).


Anyways, I found the cause of my confusion in the end. The switch was 
not properly set up (*ahemm* forgot to save configuration).


3 thumbs up for oVirt showing the LLDP-info of the switch :-)

And the fact that despite having to reinstall essentially everything 
oVirt from scratch (due to failed upgrade), the VMs were just a matter 
if import. Splendid work!


Poltsi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Confused by logical networks

2018-02-22 Thread Paul-Erik Törrönen

On 2018-02-22 22:56, Vincent Royer wrote:

Hope some part of this helps you!


Thanks for your answer, I need to digest it more in detail, but it seems 
like I indeed have missed some essential parts.


I'll come back with a more detailed result later, but for the record, I 
do have a DNS server that I can manage completely in this case, and the 
switch management is also accessible to me.


Poltsi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Confused by logical networks

2018-02-22 Thread Paul-Erik Törrönen
I'm not sure how the logical networks should work and would appreciate 
if someone could shed some light into the matter, I've tried reading the 
documentation¹ but have not become any wiser :-/


For the sake of argument, I have two hosts in the same cluster/DC, They 
both have 2 network devices each (let's call them eth0 and eth1). On 
both hosts the ovirtmgmgt is connected to eth0 and uses the 
10.0.0.0/8-network. Host 1 is 10.0.0.1 and host 2 is 10.0.0.2. All four 
network devices are connected to one switch.


Then I create a logical network, mylogic which should be 192.168.1.0/24, 
which I assign to eth1 on each host, but define only for host 1 an 
ip-address, 192.168.1.1, host 2 has also the network assigned to eth1, 
but withouth an ip address.


Next I create vm1 on host 1, give it a single virtual network connection 
to mylogic, and configure the guest to use 192.168.1.2 with gw 
192.168.1.1. Obviously I can from the guest ping 192.168.1.1 which is 
the host address on the logical network as the guest is running on the 
same hardware where the host ip address is defined.


However, and this is where my confusion lies, if I now create another 
vm, vm2, on host 2, attach its network device to the mylogic network and 
configure it to use 192.168.1.3 with gw 192.168.1.1, I can not ping 
neither 192.168.1.1 nor 192.168.1.2.


My understanding is that vm2 should be able to ping the wm1 as well as 
the gateway address defined on host 1. However this does not seem to be 
the case.


What have I missed here?

TIA,

Poltsi

¹ https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Addition of hosts fail at network setup

2017-09-25 Thread Paul-Erik Törrönen

Hello,

I'm attempting to add another host to the cluster, and I'm getting the 
following error when I add the ovirtmgmt network to the physical network 
device:


Error while executing action HostSetupNetworks: Unexpected exception

In the host vdsm.log I have the following:

2017-09-25 19:58:35,060+0300 ERROR (jsonrpc/4) [jsonrpc.JsonRpcServer] 
Internal server error (__init__:577)

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 
572, in _handle_request

res = method(**params)
  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 202, 
in _dynamicMethod

result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 1575, in setupNetworks
supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in 
__call__

return callMethod()
  File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in 


**kwargs)
  File "", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in 
_callmethod

raise convert_to_error(kind, result)
IOError: [Errno 2] No such file or directory: 
u'/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt'
2017-09-25 19:58:35,061+0300 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] 
RPC call Host.setupNetworks failed (error -32603) in 0.18 seconds 
(__init__:539)


I thought the ifcfg-ovirtmgmt-file was supposed to be created by the 
ovirt setup?


I'm running the latest ovirt 4.1.6 on CentOS7.4 x86_64 
(ovirt-release41-4.1.6-1.el7.centos.noarch).


Poltsi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Lost disk image on guest

2017-08-03 Thread Paul-Erik Törrönen
Updated the ovirt to latest stable and after the host reboot (hardware 
was relocated) all of the VMs on the host are ok except one which has 
lost it's disk image (it still exists physically on the storage device).


Uploading this image to the storage fails (I get the usual initiating - 
0/XXXMB uploaded - Paused by system, the ovirt-imageio-proxy is running 
on the engine and has nothing in it's log), and I'm also unable to 
create any new disks when editing the problematic VM (the 
Attach/Create/+/--buttons are all grayed out).


The question is: Is the only course to 'fix' this situation to delete 
the whole VM and install it from scratch?


Poltsi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-11-20 Thread Paul-Erik Törrönen

On 2016-11-19 11:28, Joop wrote:

I have never setup such a server but if you create the ovirtmgmt bridge
first then the deploy will leave it alone and you won't lose network
connectivity.


I've set up almost the described combination (I do run the vm-engine on 
a separate laptop), and found that running the commandline stuff in a 
screen helps a lot, the setup commands can then complete instead of 
being interrupted as your (ssh-)session is killed.


I also enountered the same issue of network connection loss as the 
ovirtmgmt-interface took over my primary connection, but I was able to 
continue as I  had several network devices on my hardware which I had 
already configured, and was able to access the server through them.


If you only have one network interface, then I would recommend running 
the commands in a screen, and in the case of losing the connection, 
reconnect to the screen through the KVM.


My 0.02€

Poltsi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users