[ovirt-users] oVirt Node 4.5.5 web login

[Aditya Prasad]

Hi 

I am new to oVirt so apologies for ignorance. 

I have installed oVirt Node 4.5.5 and how to login to Web-Interface 
(https://:9090) what is the default user and password. 
___
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/BF33AWKGNBBM667X676VKXYNKRKIA2MC/

[ovirt-users] ovirt node ng 4.5.5 fresh install fails

[Levi Wilbert]

I'm attempting to update our oVirt cluster to 4.5.5 from 4.5.4, running oVirt 
Node NG on the hosts.
When I tried updating a host through the oVirt Manager GUI, after the host 
reboots, it fails to start up and goes into emergency recovery mode:
[4.534872] localhost systemd[1]: Reached target Local File Systems.
[4.535119] localhost systemd[1]: Reached target System Initialization.
[4.535343] localhost systemd[1]: Reached target Basic System.
[4.536759] localhost systemd[1]: Started Hardware RNG Entropy Gatherer 
Daemon.
[4.541801] localhost rngd[1512]: Disabling 7: PKCS11 Entropy generator 
(pkcs11)
[4.541801] localhost rngd[1512]: Disabling 5: NIST Network Entropy Beacon 
(nist)
[4.541801] localhost rngd[1512]: Disabling 9: Qrypt quantum entropy beacon 
(qrypt)
[4.541801] localhost rngd[1512]: Initializing available sources
[4.542073] localhost rngd[1512]: [hwrng ]: Initialization Failed
[4.542073] localhost rngd[1512]: [rdrand]: Enabling RDSEED rng support
[4.542073] localhost rngd[1512]: [rdrand]: Initialized
[4.542073] localhost rngd[1512]: [jitter]: JITTER timeout set to 5 sec
[4.582381] localhost rngd[1512]: [jitter]: Initializing AES buffer
[8.309063] localhost rngd[1512]: [jitter]: Enabling JITTER rng support
[8.309063] localhost rngd[1512]: [jitter]: Initialized
[  133.884355] localhost dracut-initqueue[1095]: Warning: dracut-initqueue: 
timeout, still waiting for following initqueue hooks:
[  133.885349] localhost dracut-initqueue[1095]: Warning: 
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-id\x2fmd-uuid-3f47cad8:fecb96ea:0ea37615:4e5dec4e.sh:
 "[ -e "/dev/disk/by-id/md-uuid-3f47cad8:fecb96ea:0ea37615:4e5dec4e" ]"
[  133.886485] localhost dracut-initqueue[1095]: Warning: 
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-id\x2fmd-uuid-d446b801:d515c112:116ff07f:9ae52466.sh:
 "[ -e "/dev/disk/by-id/md-uuid-d446b801:d515c112:116ff07f:9ae52466" ]"
[  133.887619] localhost dracut-initqueue[1095]: Warning: 
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fonn\x2fovirt-node-ng-4.5.5-0.20231130.0+1.sh:
 "if ! grep -q After=remote-fs-pre.target 
/run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[  133.887619] localhost dracut-initqueue[1095]: [ -e 
"/dev/onn/ovirt-node-ng-4.5.5-0.20231130.0+1" ]
[  133.887619] localhost dracut-initqueue[1095]: fi"
[  133.888667] localhost dracut-initqueue[1095]: Warning: 
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fonn\x2fswap.sh: "[ -e 
"/dev/onn/swap" ]"
[  133.890050] localhost dracut-initqueue[1095]: Warning: dracut-initqueue: 
starting timeout scripts
[  133.969228] localhost dracut-initqueue[7366]: Scanning devices md126p2  for 
LVM logical volumes onn/ovirt-node-ng-4.5.5-0.20231130.0+1
[  133.969228] localhost dracut-initqueue[7366]: onn/swap
[  134.001560] localhost dracut-initqueue[7366]:   
onn/ovirt-node-ng-4.5.5-0.20231130.0+1 thin
[  134.001560] localhost dracut-initqueue[7366]:   onn/swap 
  linear
[  134.014259] localhost dracut-initqueue[7381]: 
/etc/lvm/profile/imgbased-pool.profile: stat failed: No such file or directory
[  134.532608] localhost dracut-initqueue[7381]: Check of pool onn/pool00 
failed (status:64). Manual repair required!


I then attempted installing the oVirt Node NG 4.5.5 iso to a USB stick and 
tried installing that way, however, after going through the GUI and setting up 
storage, network, hostname, etc, the install fails shortly after clicking 
"Begin".

22:11:32,671 WARNING 
org.fedoraproject.Anaconda.Modules.Storage:INFO:blivet:executing action: [468] 
destroy device lvmthinlv onn-var_log_audit (id 216)
22:11:32,672 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
LVMLogicalVolumeDevice.destroy: onn-var_log_audit ; status: 
False ;
22:11:32,673 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
 LVMLogicalVolumeDevice.teardown: onn-var_log_audit ; 
status: False ; controllable: False ;
22:11:32,674 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
LVMVolumeGroupDevice.setup_parents: name: onn ; orig: True ;
22:11:32,674 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
  PartitionDevice.setup: Volume0_0p2 ; orig: True ; status: 
True ; controllable: True ;
22:11:32,675 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
  LVMPhysicalVolume.setup: device: /dev/md/Volume0_0p2 ; 
type: lvmpv ; status: False ;
22:11:32,676 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet:   
   LVMLogicalVolumeDevice._destroy: onn-var_log_audit ; status: 
False ;
22:11:32,676 WARNING 
org.fedoraproject.Anaconda.Modules.Storage:INFO:program:Running [97] lvm 
lvremove --yes onn/var_log_audit --config= log {level=7 file=/tmp/lvm.log 
syslog=0} 

[ovirt-users] ovirt node NonResponsive

[carlos . mendes]

Hello,

I have ovirt with two nodes and one that are NonResponsive and and cant manage 
them
because they are in Unknown state.
It seems that nodes lost connection for a while with their gateway.

The node (ovirt2) however is having consistent problems. The follow sequence of 
events is
reproducible and is causing the host to enter a "NonOperational" state on the
cluster:

What is the proper way of restoring management?

I have a two-node cluster with the ovirt manager running standlone on the 
virtual maachine
CentOS-Stream-9 and the ovirt node running the most recent oVirt Node 4.5.4 
software.

I can then re-activate ovirt2, which appears as green for approximately 5 
minutes and then
repeats all of the above issues.

What can I do to troubleshoot this?
___
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/NC22FEYOTUNVPSUWHYKAQ37ZZRXNDEMH/

[ovirt-users] ovirt node NonResponsive

[carlos . mendes]

Hello,

I have ovirt with two nodes and one that are NonResponsive and and cant manage 
them because they are in Unknown state.
It seems that nodes lost connection for a while with their gateway.

The node (ovirt2) however is having consistent problems. The follow sequence of 
events is reproducible and is causing the host to enter a "NonOperational" 
state on the cluster:

What is the proper way of restoring management?

I have a two-node cluster with the ovirt manager running standlone on the 
virtual maachine CentOS-Stream-9 and the ovirt node running the most recent 
oVirt Node 4.5.4  software.

I can then re-activate ovirt2, which appears as green for approximately 5 
minutes and then repeats all of the above issues.

What can I do to troubleshoot this?
___
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/R25AFAZWTAJA4QLKXMVBELWMBUQSG7FA/

[ovirt-users] ovirt node 4.5 is not working on esxi8 on my lab

[poper]

Hello there,

May I ask why I have installed ovirt node 4.5 latest from iso on my esxi8 after 
I logged in to the web interface to manage this host I cannot find menu 
virtualization but when I tested on 4.4.6 everything is work. Do you have any 
idea?

Thanks.
___
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/WLICKYZLJON2BYBPYHFPGSDDZF7VWEIP/

[ovirt-users] ovirt node

[skhurtsilava]

Hello Guys
I installed oVirt Node 4.4 and I want to deploy Hosted Engine  but i get this 
error

[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Ensure the resolved address 
resolves only on the selected interface]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 
'ovirt.bee.moitel.local' doesn't uniquely match the interface 'ens192' selected 
for the management bridge; it matches also interface with IP 
['fe80::9a5b:2039:fe49:5252', '192.168.222.1', 'fd00:1234:5678:900::1']. Please 
make sure that the hostname got from the interface for the management network 
resolves only there.\n"}

How can i fix this error?
___
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/MFW6ESTNTQPRL4Y6WWZ4EZHSEITQ334B/

[ovirt-users] Ovirt node disk broken

[marcel d'heureuse]

Hi all,

On a single Server the node disk is broken and I have to replace it. 

The glusterfs configuration is also gone but the glusterfs directorys are 
existing on a separate available disk. 

Did I have a Chance to install the ovirt Node on a New disk and make the old 
glusterfs running and also the 7 vms included the hosted engine? 

I can also deploy a New hosted engine but can I than import the existing 
gluster disk from the old Installation?

I have installed the node and also mount the gluster_bricks but to make the 
volumes available I have not found any command. 

It is an ovirt 4.3.10 Installation. 

Is there any chance to save some time. The data inside the vms are good to 
have. 

Br
Marcel

___
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/355KIW6ZVWU2R4UMJIZAP3C4HZYMT5P3/

[ovirt-users] oVirt node 4.5 now load QLogic 10gb interface.

[kalilac]

Hello all.
Again, here, asking for help. I just installed a oVirt node 4.5.4 in a new 
server but I can't use our 10gb interface becouse even though the module been 
loaded we can´t see the interface. I tryed install 4.4 oVirt node in the same 
server and I can see and use the same interface. I tryed with the 4.5.2, el9, 
el8 and has the same issu. 

Operating System: oVirt Node 4.5.4
Kernel: Linux 5.14.0-202.el9.x86_6
module: bnx2i
filename:   
/lib/modules/5.14.0-202.el9.x86_64/kernel/drivers/scsi/bnx2i/bnx2i.ko.xz
version:2.7.10.1
license:GPL
description:QLogic NetXtreme II 
BCM5706/5708/5709/57710/57711/57712/57800/57810/57840 iSCSI Driver
author: Anil Veerabhadrappa  and Eddie Wai 

rhelversion:9.2

A tryed remove and reload the module but nothing happened. 

Anyone has any ideia what is going wrong? 

Best regards
___
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/QUF46UA7IDRB4TXSF2ZYZKJEFL5Y6RG2/

[ovirt-users] Ovirt-node don't communicate with qemu-agent

[Fernando Hallberg]

Hi all,

I reinstalled one of the ovirt-nodes, with ovirt-4.5.4, and after the
reinstallation the agents of the vms connected to this node cannot
communicate with the ovirt-engine.

ovirt-engine 4.5.4

any idea?

VMs work perfectly, but the agent doesn't communicate.

Best regards,

Fernando Hallberg
___
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/KCCPQWTYU4D2EZFNRO77FNAKVFKWKFDA/

[ovirt-users] ovirt node Emulex network

[parallax]

ovirt-node-ng-installer-4.4.10-2022030308.el8

ovirt-node-ng-installer-4.4.10-2022030308

can't recognize network intefaces:

06:00.0 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.1 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.4 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.5 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)

anyone know howto fix it ?
___
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/X2QWLS5ZXGDUYYWXMZREQG7PLP4MGTZP/

[ovirt-users] ovirt-node 4.5 and engine 4.4

[Nathanaël Blanchet via Users]

Hello,

I'm planning to upgrade ovirt engine to 4.5, but I need now to install 
additionnal hosts. Is it safe to directly install my new hosts with 
ovirt-node 4.5 and attach them to 4.4 engine?

Thank you

-- 
Nathanaël Blanchet

Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

[ovirt-users] oVirt Node 4.5.3.1 Async update

[Sandro Bonazzola]

oVirt Node 4.5.3.1 Async update

On October 20th 2022 the oVirt project released an async update of oVirt
Node (4.5.3.1) delivering a fix for OVS/OVN package conflict issue.

The update is already available on resources.ovirt.org and should land on
oVirt mirrors within 24 hours.


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R PERFORMANCE & SCALE

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/LXCTQGKBF2UBENE2I27TVJSEZFNBUSGC/

[ovirt-users] oVirt node 4.4 repository missing package

[kenneth . hau]

Hi there, I saw that there has new package of 
ovirt-node-ng-image-update-placeholder-4.4.10.3-1.el8.noarch.rpm has released 
on 2022-06-24. However, I would like to know if there has any plan to release 
new package of ovirt-node-ng-image-update-4.4.10.3-1.el8.noarch.rpm as the the 
package is still retain at 4.4.10.2-1. Many thanks.
___
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/QLQ535C2DZ32WAQG3VYBCPTG7BNNQIVO/

[ovirt-users] ovirt node 4.5.1 fails to boot cleanly with selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'

[p . staniforth]

Hello we have some nodes that don't boot cleanly, CTRL-D or logging into the 
node allows the system to finish the startup properly.

selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start 
failed with result 'dependency'
systemd[1]: Timed out waiting for device 
dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device.
systemd[1]: Dependency failed for /gluster_bricks/extra.
systemd[1]: Dependency failed for Local File Systems.
systemd[1]: Dependency failed for Mark the need to relabel after reboot.
systemd[1]: selinux-autorelabel-mark.service: Job 
selinux-autorelabel-mark.service/start failed with result 'dependency'.
systemd[1]: local-fs.target: Job local-fs.target/start failed with result 
'dependency'.
systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
systemd[1]: gluster_bricks-extra.mount: Job gluster_bricks-extra.mount/start 
failed with result 'dependency'.
systemd[1]: 
dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device: 
Job 
dev-disk-by\x2duuid-3839035f\x2db3be\x2d4b8b\x2db711\x2df19bee4785f2.device/start
 failed with result 'timeout'.

The other gluster bricks created at install time don't have this problem.

Thanks,
 Paul S.
___
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/KFH6BIG2ABHIWCUPGHVCJH5VWUXGZLOZ/

[ovirt-users] Ovirt node Virus scan

[marcel d'heureuse]

Hi,

I have to scan our 18 nodes with a virus scanner and I have to provide the 
report to our ito. 

This nodes have no internet connection and they will not get it. 

Which software I should use? Clamav? 

I can shutdown each single node and can scan but I would prefer to have it as 
cmd running and generate monthly or weekly reports. I don't want to have the 
daemon running.

How did you do this?

Br
Marcel
___
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/BS3LF3JXNA5I4GV6YW3L22V4JVRW426A/

[ovirt-users] oVirt Node 4.5 - Installing gluster single node stops immediately

[Patrick Lomakin]

Hi guys! I've tried to deploy ovirt single node with gluster via GUI but have a 
problem immediately. A log file that shows after installation was empty. But in 
journalctl I found that:

Apr 23 20:06:45 host1 cockpit-ws[22948]: ERROR! couldn't resolve module/action 
'vdo'. This often indicates a misspelling, missing collection, or incorrect 
module path.
Apr 23 20:06:45 host1 cockpit-ws[22948]: The error appears to be in 
'/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml': 
line 53, column 3, but may
Apr 23 20:06:45 host1 cockpit-ws[22948]: be elsewhere in the file depending on 
the exact syntax problem.
Apr 23 20:06:45 host1 cockpit-ws[22948]: The offending line appears to be:
Apr 23 20:06:45 host1 cockpit-ws[22948]: - name: Create VDO with specified size
Apr 23 20:06:45 host1 cockpit-ws[22948]:   ^ here
___
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/27TOMN4KBWECMYV4QQ6XFVX5ALFWZELH/

[ovirt-users] ovirt-node-ng state "Bond status: NONE"

[Renaud RAKOTOMALALA]

Hello,

I am trying to add a new ovirt-node-ng 4.4.10 node to my cluster managed by an 
ovirt-engine version 4.4.10.

My cluster is composed of other ovirt-node-ng which have been successively 
updated from version 4.4.4 to version 4.4.10 without any problem.

This new node is integrated normally in the cluster, however when I look at the 
status of the network part in the tab "Network interface" I see that all 
interfaces are "down".

I have a paperclip at the "bond0" interface that says: "Bond state; NONE"

I compared the content of "/etc/sysconfig/network-script" between an hypervisor 
which works and the one which has the problem and I notice that a whole bunch 
of files are missing and in particular the "ifup/ifdown" files. The folder 
contains only the cluster specific files + the "ovirtmgmt" interface.

The hypervisor which has the problem seems to be perfectly functional, 
ovirt-engine does not raise any problem.

Have you already encountered this type of problem?

Cheers,
Renaud
___
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/XGOKO22HWF6OMLDCJW6XAWLE2DNPTQCB/

[ovirt-users] OVIRT-Node Engine Deployment Failure due to no URLs in mirrorlist

[aellahib]

I am running OVIRT-Node and although I updated my mirror list and the hosts are 
fine. It seems my engine deployment (deploying hyperconverged gluster) is 
trying to use a different set of mirrors during Engine VM Prep.

SO this is the error I see, should I be running a newer RPM on these nodes or 
something, I am not aware if there is a newer one I should be using for this.

[ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package]
[ ERROR ] fatal: [localhost -> 192.168.222.193]: FAILED! => {"changed": false, 
"msg": "Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': 
Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": 
[]}
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine]
[ INFO ] changed: [localhost -> 192.168.222.193]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path]
[ INFO ] ok: [localhost -> localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory]
[ INFO ] changed: [localhost -> localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image]
[ INFO ] ok: [localhost -> localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path]
[ INFO ] ok: [localhost -> localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush 
dirty buffers]
[ INFO ] ok: [localhost -> localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a 
failure]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a 
failure deploying the engine on the local engine VM. The system may not be 
provisioned according to the playbook results: please check the logs for the 
issue, fix accordingly or re-deploy from scratch.\n"}



It does let me click PrepareVM despite Deployment Failed -- but at that point 
/var/tmp is filled to more than 67% so it fails due to no space for engine 
install despite the good minimum requirements set lol
___
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/4EBNIFJ3ANERON47E2XX75T3IOQ52AYD/

[ovirt-users] oVirt Node - master - CentOS Stream 9 based ISO available for testing

[Sandro Bonazzola]

Hi,
I'm still working on it but I have a first ISO ready for giving a first run
at
https://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-node-ng-installer/4.5.0-2021091610/el9/ovirt-node-ng-installer-4.5.0-2021091610.el9.iso

Known limitations:
- No hosted engine setup available
- No ansible available
- No collectd support
- No cinderlib support

Everything else should be there but it's totally untested.

Help giving it a try and providing feedback is appreciated.

Thanks
-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/X3PDXUXTIGOF4MBVZZCNZ25DUB3IQYBT/

[ovirt-users] oVirt Node 4.4.8.3 Async update

[Sandro Bonazzola]

oVirt Node 4.4.8.3 Async update

On September 3rd 2021 the oVirt project released an async update for oVirt
Node consuming the following packages:

   -

   ovirt-release44 4.4.8.3
   -

   ovirt-node-ng-image-update 4.4.8.3

oVirt Node respin also consumed most recent CentOS Stream and Advanced
Virtualization content.

It also includes fixes for:

   -

   Bug 1996602  - VM
   remains in paused state when trying to write on a resized disk resides on
   iscsi
   -

  Via qemu-kvm-6.0.0-29.el8s which shipped live.



Here’s the full list of changes:

--- ovirt-node-ng-image-4.4.8.2.manifest-rpm 2021-09-01 12:59:05.195037688
+0200

+++ ovirt-node-ng-image-4.4.8.3.manifest-rpm 2021-09-03 13:27:52.006368887
+0200

@@ -47 +46,0 @@

-boost-iostreams-1.66.0-10.el8.x86_64

@@ -112 +111 @@

-device-mapper-persistent-data-0.9.0-1.el8.x86_64

+device-mapper-persistent-data-0.9.0-4.el8.x86_64

@@ -355 +354 @@

-libcap-2.26-4.el8.x86_64

+libcap-2.26-5.el8.x86_64

@@ -637 +636 @@

-osinfo-db-20210215-1.el8.noarch

+osinfo-db-20210809-1.el8.noarch

@@ -648 +647 @@

-ovirt-node-ng-image-update-placeholder-4.4.8.2-1.el8.noarch

+ovirt-node-ng-image-update-placeholder-4.4.8.3-1.el8.noarch

@@ -656,2 +655,2 @@

-ovirt-release-host-node-4.4.8.2-1.el8.noarch

-ovirt-release44-4.4.8.2-1.el8.noarch

+ovirt-release-host-node-4.4.8.3-1.el8.noarch

+ovirt-release44-4.4.8.3-1.el8.noarch

@@ -768 +767 @@

-python3-eventlet-0.25.2-3.el8.noarch

+python3-eventlet-0.25.2-3.1.el8.noarch

@@ -814 +813 @@

-python3-os-brick-4.0.3-1.el8.noarch

+python3-os-brick-4.0.3-2.el8.noarch

@@ -890,14 +889,14 @@

-qemu-guest-agent-6.0.0-27.el8s.x86_64

-qemu-img-6.0.0-27.el8s.x86_64

-qemu-kvm-6.0.0-27.el8s.x86_64

-qemu-kvm-block-curl-6.0.0-27.el8s.x86_64

-qemu-kvm-block-gluster-6.0.0-27.el8s.x86_64

-qemu-kvm-block-iscsi-6.0.0-27.el8s.x86_64

-qemu-kvm-block-rbd-6.0.0-27.el8s.x86_64

-qemu-kvm-block-ssh-6.0.0-27.el8s.x86_64

-qemu-kvm-common-6.0.0-27.el8s.x86_64

-qemu-kvm-core-6.0.0-27.el8s.x86_64

-qemu-kvm-docs-6.0.0-27.el8s.x86_64

-qemu-kvm-hw-usbredir-6.0.0-27.el8s.x86_64

-qemu-kvm-ui-opengl-6.0.0-27.el8s.x86_64

-qemu-kvm-ui-spice-6.0.0-27.el8s.x86_64

+qemu-guest-agent-6.0.0-29.el8s.x86_64

+qemu-img-6.0.0-29.el8s.x86_64

+qemu-kvm-6.0.0-29.el8s.x86_64

+qemu-kvm-block-curl-6.0.0-29.el8s.x86_64

+qemu-kvm-block-gluster-6.0.0-29.el8s.x86_64

+qemu-kvm-block-iscsi-6.0.0-29.el8s.x86_64

+qemu-kvm-block-rbd-6.0.0-29.el8s.x86_64

+qemu-kvm-block-ssh-6.0.0-29.el8s.x86_64

+qemu-kvm-common-6.0.0-29.el8s.x86_64

+qemu-kvm-core-6.0.0-29.el8s.x86_64

+qemu-kvm-docs-6.0.0-29.el8s.x86_64

+qemu-kvm-hw-usbredir-6.0.0-29.el8s.x86_64

+qemu-kvm-ui-opengl-6.0.0-29.el8s.x86_64

+qemu-kvm-ui-spice-6.0.0-29.el8s.x86_64

@@ -934,2 +933,2 @@

-selinux-policy-3.14.3-78.el8.noarch

-selinux-policy-targeted-3.14.3-78.el8.noarch

+selinux-policy-3.14.3-79.el8.noarch

+selinux-policy-targeted-3.14.3-79.el8.noarch

@@ -1007 +1006 @@

-virt-v2v-1.42.0-14.el8s.x86_64

+virt-v2v-1.42.0-15.el8s.x86_64



-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/N4PJ5WXMNJQU5YQY776WVE6QBDS7D7K3/

[ovirt-users] Ovirt node 4.4.5 failure to upgrade to 4.4.6

[Guillaume Pavese]

Maybe my problem is in part linked to an issue seen by Jayme earlier, but
then the resolution that worked for him did not succeed for me :

I first upgraded my Self Hosted Engine from 4.4.5 to 4.4.6 and then
upgraded it to Centos-Stream and rebooted

Then I tried to upgrade the cluster (3 ovirt-nodes on 4.4.5) but it failed
at the first host.
They are all ovir-node hosts, originally first installed in 4.4.5

In Host Event Logs I saw :

...
Update of host ps-inf-prd-kvm-fr-510.hostics.fr.
Upgrade packages
Update of host ps-inf-prd-kvm-fr-510.hostics.fr.
Check if image was updated.
Update of host ps-inf-prd-kvm-fr-510.hostics.fr.
Check if image was updated.
Update of host ps-inf-prd-kvm-fr-510.hostics.fr.
Check if image-updated file exists.
Failed to upgrade Host ps-inf-prd-kvm-fr-510.hostics.fr (User:
g...@hostics.fr).



ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch was installed according to
yum,
I tried reinstalling it but got errors: "Error in POSTIN scriptlet" :

Downloading Packages:
[SKIPPED] ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch.rpm: Already
downloaded
...
  Running scriptlet: ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch

  Reinstalling : ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch

  Running scriptlet: ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch

warning: %post(ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch) scriptlet
failed, exit status 1

Error in POSTIN scriptlet in rpm package ovirt-node-ng-image-update
---
Reinstalled:
  ovirt-node-ng-image-update-4.4.6.3-1.el8.noarch



nodectl still showed it was on 4.4.5 :

[root@ps-inf-prd-kvm-fr-510 ~]# nodectl info
bootloader:
  default: ovirt-node-ng-4.4.5.1-0.20210323.0 (4.18.0-240.15.1.el8_3.x86_64)
 ...
  current_layer: ovirt-node-ng-4.4.5.1-0.20210323.0+1



I tried to upgrade the Host again from oVirt and this time there was no
error, and the host rebooted.
However, it did not pass active after rebooting and nodectl still shows
that it's 4.4.5 installed. Similar symptoms as OP

So I removed ovirt-node-ng-image-update, then reinstalled it and got no
error this time.
nodectl info seemed to show that it was installed :


[root@ps-inf-prd-kvm-fr-510 yum.repos.d]# nodectl info
bootloader:
  default: ovirt-node-ng-4.4.6.3-0.20210518.0 (4.18.0-301.1.el8.x86_64)
...
  current_layer: ovirt-node-ng-4.4.5.1-0.20210323.0+1


However, after reboot the Host was still shown as "unresponsive"
After Marking it as "Manually rebooted", passing it in maintenance mode and
trying to activate it, the Host was automatically fenced. And still
unresponsive after this new reboot.

I passed it in maintenance mode again, And tried to reinstall it with
"Deploy Hosted Engine" selected
However if failed : "Task Stop services failed to execute."

In
/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20210602082519-ps-inf-prd-kvm-fr-510.hostics.fr-0565d681-9406-4fa7-a444-7ee34804579c.log
:

"msg" : "Unable to stop service vdsmd.service: Job for vdsmd.service
canceled.\n", "failed" : true,

"msg" : "Unable to stop service supervdsmd.service: Job for
supervdsmd.service canceled.\n", failed" : true,

"stderr" : "Error:  ServiceOperationError: _systemctlStop failed\nb'Job for
vdsmd.service canceled.\\n' ",

"stderr_lines" : [ "Error:  ServiceOperationError: _systemctlStop failed",
"b'Job for vdsmd.service canceled.\\n' " ],


If I try on the Host I get :

[root@ps-inf-prd-kvm-fr-510 ~]# systemctl stop vdsmd
Job for vdsmd.service canceled.

[root@ps-inf-prd-kvm-fr-510 ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
preset: disabled)
   Active: deactivating (stop-sigterm) since Wed 2021-06-02 08:49:21 CEST;
7s ago
  Process: 54037 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
--pre-start (code=exited, status=0/SUCCESS)
...

Jun 02 08:47:34 ps-inf-prd-kvm-fr-510.hostics.fr vdsm[54100]: WARN Failed
to retrieve Hosted Engine HA info, is Hosted Engine setup finished?
...
Jun 02 08:48:31 ps-inf-prd-kvm-fr-510.hostics.fr vdsm[54100]: WARN Worker
blocked: 
  File:
"/usr/lib64/python3.6/threading.py", line 884, in _bootstrap

self._bootstrap_inner()



Retrying to manually stop vdsmd a second time then seems to work...
I tried rebooting again, restarting the install always fail at the the same
spot

What should I try to get this host back up?



Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group

-- 


Ce message et toutes les pièces jointes (ci-après le “message”) sont 
établis à l’intention exclusive de ses destinataires et sont confidentiels. 
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir 
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a 
sa destination, toute diffusion ou toute publication, totale ou partielle, 
est interdite, sauf autorisation expresse. L’internet ne permettant pas 
d’assurer l’intégrité de ce message . 

[ovirt-users] oVirt Node

[KSNull Zero]

Hello!
We want to switch OS based oVirt instalation to oVirt-Node based.
Is it safe to have OS based hosts and oVirt-Node hosts in the same cluster 
(with FC shared storage) during transition ?
Thank you.
___
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/M3TCXZYIP6Q4KA6XBOHGO6OXMQGJAMBN/

[ovirt-users] Ovirt node - 4.4.4 -> 4.4.5 upgrade failed - do i need a reinstall ? tried removing /dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 to reinstall rpm..

[morgan cox]

Hi.

I have a 2 node cluster (both installed from the Ovirt-node iso) , 1 server is 
100% fine, but one server I tried to update when there were issues with the 
ovirtmgmt network (I wasn't aware of at the time) - as a result the server 
update failed, and was still on ovirt-node 4.4.4  after - I could see the LVM 
layer for 4.4.5 though.

The network is fine now (hence the other server being ok) - I tried 
reinstalling the package ovirt-node-ng-image-update-4.4.5.1-1.el8.noarch.rpm 
but it failed due to LVM lv for 4.4.5 already existing ...

So I tried removing the LV - i.e 

# lvremove /dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 


however now I'm sure I have less 4.4.4 lvs ..

i.e

--
[root@ng2-ovirt-kvm3 mcox]# lvs
  LV   VG  Attr   LSize   Pool   Origin 
Data%  Meta%  Move Log Cpy%Sync Convert
  home onn Vwi-aotz--   1.00g pool00
10.05  
  ovirt-node-ng-4.4.4.1-0.20210208.0+1 onn Vwi-aotz-- 191.00g pool00
2.27   
  pool00   onn twi-aotz-- 218.00g   
2.48   1.92
  swap onn -wi-ao   4.00g   
   
  tmp  onn Vwi-aotz--   1.00g pool00
2.24   
  var  onn Vwi-aotz--  15.00g pool00
2.80   
  var_crashonn Vwi-aotz--  10.00g pool00
0.21   
  var_log  onn Vwi-aotz--   8.00g pool00
5.97   
  var_log_auditonn Vwi-aotz--   2.00g pool00
1.14 


Where as on the working server I have these Ovirt Node LVs

  ovirt-node-ng-4.4.4.1-0.20210208.0   onn Vwi---tz-k 191.00g pool00 root   
   
  ovirt-node-ng-4.4.4.1-0.20210208.0+1 onn Vwi-a-tz-- 191.00g pool00 
ovirt-node-ng-4.4.4.1-0.20210208.0 1.86   
  ovirt-node-ng-4.4.5.1-0.20210323.0   onn Vri---tz-k 191.00g pool00
   
  ovirt-node-ng-4.4.5.1-0.20210323.0+1 onn Vwi-aotz-- 191.00g pool00 
ovirt-node-ng-4.4.5.1-0.20210323.0 1.58  

Anyway I tried to reinstall the 
ovirt-node-ng-image-update-4.4.5.1-1.el8.noarch.rpm package after removal of lv 
and files in /boot

But install still fails .. Is there anything I can do to update this node - or 
should I bite the bullet and reinstall ?

 this is from /var/log/imgbased.log -> 



--
2021-04-14 16:05:56,634 [INFO] (MainThread) Adding a new layer after 
2021-04-14 16:05:56,634 [INFO] (MainThread) Adding a new layer after 
2021-04-14 16:05:56,634 [DEBUG] (MainThread) Basing new layer on previous: 

2021-04-14 16:05:56,634 [DEBUG] (MainThread) Finding next layer based on 
2021-04-14 16:05:56,634 [DEBUG] (MainThread) Suggesting for layer for base 
ovirt-node-ng-4.4.5.1-0.20210323.0
2021-04-14 16:05:56,635 [DEBUG] (MainThread) ... without layers
2021-04-14 16:05:56,635 [INFO] (MainThread) New layer will be: 
2021-04-14 16:05:56,635 [DEBUG] (MainThread) Calling: (['vgs', '--noheadings', 
'--ignoreskippedcluster', '--select', 'vg_tags = imgbased:vg', '-o', 
'vg_name'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' 
encoding='UTF-8'>, 'close_fds': True}
2021-04-14 16:05:56,697 [DEBUG] (MainThread) Returned: b'onn'
2021-04-14 16:05:56,698 [DEBUG] (MainThread) Calling: (['vgs', '--noheadings', 
'--ignoreskippedcluster', '@imgbased:pool', '-o', 'lv_full_name'],) {'stderr': 
<_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': 
True}
2021-04-14 16:05:56,757 [DEBUG] (MainThread) Returned: b'onn/pool00'
2021-04-14 16:05:56,758 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', 
'--ignoreskippedcluster', '--nosuffix', '--units', 'm', '-o', 
'metadata_percent,lv_metadata_size', 'onn/pool00'],) {'stderr': 
<_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': 
True}
2021-04-14 16:05:56,829 [DEBUG] (MainThread) Returned: b'2.05   1024.00'
2021-04-14 16:05:56,830 [DEBUG] (MainThread) Pool: onn/pool00, metadata 
size=1024.0M (2.05%)
2021-04-14 16:05:56,830 [DEBUG] (MainThread) Calling: (['lvchange', 
'--activate', 'y', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0', 
'--ignoreactivationskip'],) {'stderr': <_io.TextIOWrapper name='/dev/null' 
mode='w' encoding='UTF-8'>, 'close_fds': True}
2021-04-14 16:05:56,953 [DEBUG] (MainThread) Calling: (['lvcreate', 
'--snapshot', '--name', 'ovirt-node-ng-4.4.5.1-0.20210323.0+1', 
'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'close_fds': True, 'stderr': -2}
2021-04-14 16:05:57,111 [DEBUG] (MainThread) Returned: b'WARNING: 

[ovirt-users] Ovirt Node (iso) - OK to enable Centos-BaseOS/Centos-Appstream repos ?

[morgan cox]

Hi.

I have installed Ovirt nodes via the ovirt-node iso (centos8 based) - on a 
fresh install the standard CentOS repos are disabled (the ovirt 4-4  repo is 
enabled)

As part of our company hardening we need to install a few packages from the 
Centos repos.

Can I enable the CentOS-Linux-AppStream.repo + CentOS-Linux-BaseOS.repo repos 
or will this cause issues when we update the node ?

Thanks
___
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/JITF2KTDAE7V2FMEYRJZOMUDCNKBGL56/

[ovirt-users] oVirt Node install with Foreman VG issue

[simon]

Hi All,

I have a server with a RAID1 disk for sda and RAID 5 disk for sdb.

Following default install, prior to Cockpit Gluster and Engine wizards there is 
only a single Volume Group which doesn’t allow me to continue.

If I manually configure the install and deselect sdb it gives other issues with 
multipath but at least I can resolve those.

Is there a specific kickstart confuguration that should be used?

Kind Regards

Shimme
___
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/SO3UXYCQYCXICRFDBG6FOBVZZYGF46C4/

[ovirt-users] oVirt Node install with Foreman VG issue

[simon]

Hi All,

I have a server with a RAID1 disk for sda and RAID 5 disk for sdb.

Following default install, prior to Cockpit Gluster and Engine wizards there is 
only a single Volume Group which doesn’t allow me to continue.

If I manually configure the install and deselect sdb it gives other issues with 
multipath but at least I can resolve those.

Is there a specific kickstart confuguration that should be used?

Kind Regards

Shimme
___
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/OFZS3XVTVMP5GFT2ZHZNLZ4XUPXBNCZC/

[ovirt-users] ovirt node ng 4.4 crash in anaconda when setting ntp

[Gianluca Cecchi]

Hello,
when installing ovirt node ng 4.4 on a Dell M620 I remember I had a crash
in anaconda if I try to set up ntp.
Using ovirt-node-ng-installer-4.4.4-2020122111.el8.iso
As soon as I select it and try to type the hostname to use, all stops and
then anaconda aborts.
Just today I had the same with the latest RHVH 4.4 iso:
RHVH-4.4-20201210.0-RHVH-x86_64-dvd1.iso on an R630.
Quite disappointing because I also have to fight with iDRAC8 to install the
OS: it is slow to die.
In practice I waste about one hour

Is anyone aware of it or able to reproduce on another platform so that
eventually I'm going to open a bug/case for it?
My config is default one in anaconda accepting default and creating a
bonded connection (LACP).
Then as the last step I go into the set time/date and click on the ntp
button and I get the problem as soon as I try to type inside the text box.

Thanks,
Gianluca
___
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/KXJBJEK2V764ZQQB4LT4VD6MRGFLY6WQ/

[ovirt-users] ovirt node based on centos 8 stream

[Nathanaël Blanchet]

Hi all,

I project to upgrade from 4.3 to 4.4 hosts in the next few days, and I 
wonder if ovirt node based on centos 8.3 will be upgradable to ovirt 
node based on centos stream.


If not, I will wait to upgrade directly to ovirt node centos stream 
based when available.


--
Nathanaël Blanchet

Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr
___
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/R2FAFKH2Q7U23FUSNO6X2E2OIEO33BXD/

[ovirt-users] oVirt Node Crash

[Anton Louw via Users]

Hi Everybody,

I have built a new host which has been running fine for the last couple of 
days. I noticed today that the host crashed, but it is not giving me a reason 
as to why.

It happened at 13:45 today, but I have given time before that on the logs as 
well.

Is there something I am missing here?

Thanks


Anton Louw
Cloud Engineer: Storage and Virtualization
__
D: 087 805 1572 | M: N/A
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
anton.l...@voxtelecom.co.za

www.vox.co.za






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

[ovirt-users] Ovirt Node 4.4.2 install Odroid-H2 64GB eMMC

[franklin . shearer]

Hi All,

I'm trying to install node 4.4.2 on an eMMC card, but when I get to the storage 
configuration of the installer, it doesn't save the settings (which is 
automatic configuration) I have chosen and displays failed to save storage 
configuration. I have deleted all partitions on the card before trying to 
install and I still get the same error. The only way I can get it to go is 
select manual configuration with LVM thin provisioning and automatically 
create. Am I doing something wrong. I can install Centos 8 no issues on this, 
but not oVirt node 4.4.2.
___
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/XYCGL3TLQKKAUXXO7LRCSBK6QLCDJTRE/

[ovirt-users] oVirt-node

[Budur Nagaraju]

Hi

Is there a way to deploy  vms on the ovirt node without using the oVirt
engine?

Thanks,
Nagaraju
___
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/FEGDT6G6P3D4GEPXFKWECUVO33H73YH5/

[ovirt-users] ovirt-node-4.4.2 grub is not reading new grub.cfg at boot

[Mike Lindsay]

Hey Folks,

I've got a bit of a strange one here. I downloaded and installed
ovirt-node-ng-installer-4.4.2-2020091810.el8.iso today on an old dev
laptop and to get it to install I needed to add acpi=off to the kernel
boot param to get the installing to work (known issue with my old
laptop). After installation it was still booting with acpi=off, no
biggie (seen that happen with Centos 5,6,7 before on occasion) right,
just change the line in /etc/defaults/grub and run grub2-mkconfig (ran
for both efi and legacy for good measure even knowing EFI isn't used)
and reboot...done this hundreds of times without any problems.

But this time after rebooting if I hit 'e' to look at the kernel
params on boot, acpi=off is still there. Basically any changes to
/etc/default/grub are being ignored or over-ridden but I'll be damned
if I can't find where.

I know I'm missing something simple here, I do this all the time but
to be honest this is the first Centos 8 based install I've had time to
play with. Any suggestions would be greatly appreciated.

The drive layout is a bit weird but had no issues running fedora or
centos in the past. boot drive is a mSATA (/dev/sdb) and there is a
SSD data drive at /dev/sda...having sda installed or removed makes no
difference and /boot is mounted where it should /dev/sdb1very
strange

Cheers,
Mike

[root@ovirt-node01 ~]# cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX='crashkernel=auto resume=/dev/mapper/onn-swap
rd.lvm.lv=onn/ovirt-node-ng-4.4.2-0.20200918.0+1 rd.lvm.lv=onn/swap
noapic rhgb quiet'
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
GRUB_DISABLE_OS_PROBER='true'



[root@ovirt-node01 ~]# cat /boot/grub2/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set pager=1

if [ -f ${config_directory}/grubenv ]; then
  load_env -f ${config_directory}/grubenv
elif [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

terminal_output console
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/00_tuned ###
set tuned_params=""
set tuned_initrd=""
### END /etc/grub.d/00_tuned ###

### BEGIN /etc/grub.d/01_users ###
if [ -f ${prefix}/user.cfg ]; then
  source ${prefix}/user.cfg
  if [ -n "${GRUB2_PASSWORD}" ]; then
set superusers="root"
export superusers
password_pbkdf2 root ${GRUB2_PASSWORD}
  fi
fi
### END /etc/grub.d/01_users ###

### BEGIN /etc/grub.d/08_fallback_counting ###
insmod increment
# Check if boot_counter exists and boot_success=0 to activate this behaviour.
if [ -n "${boot_counter}" -a "${boot_success}" = "0" ]; then
  # if countdown has ended, choose to boot rollback deployment,
  # i.e. default=1 on OSTree-based systems.
  if  [ "${boot_counter}" = "0" -o "${boot_counter}" = "-1" ]; then
set default=1
set boot_counter=-1
  # otherwise decrement boot_counter
  else
decrement boot_counter
  fi
  save_env boot_counter
fi
### END /etc/grub.d/08_fallback_counting ###

### BEGIN /etc/grub.d/10_linux ###
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
b6557c59-e11f-471b-8cb1-70c47b0b4b29
else
  search --no-floppy --fs-uuid --set=root b6557c59-e11f-471b-8cb1-70c47b0b4b29
fi
insmod part_msdos
insmod ext2
set boot='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=boot --hint-bios=hd1,msdos1
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1
b6557c59-e11f-471b-8cb1-70c47b0b4b29
else
  search --no-floppy --fs-uuid --set=boot b6557c59-e11f-471b-8cb1-70c47b0b4b29
fi

# This section was generated by a script. Do not modify the generated
file - 

[ovirt-users] oVirt Node 4.4.2 is now generally available

[Sandro Bonazzola]

oVirt Node 4.4.2 is now generally available

The oVirt project is pleased to announce the general availability of oVirt
Node 4.4.2 , as of September 25th, 2020.

This release completes the oVirt 4.4.2 release published on September 17th
Important notes before you install / upgrade

Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
)

How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Due to Bug 1837864  -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.2 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

   1.

   Remove the current lvm filter while still on 4.4.1, or in emergency mode
   (if rebooted).
   2.

   Reboot.
   3.

   Upgrade to 4.4.2 (redeploy in case of already being on 4.4.2).
   4.

   Run vdsm-tool config-lvm-filter to confirm there is a new filter in
   place.
   5.

   Only if not using oVirt Node:
   - run "dracut --force --add multipath” to rebuild initramfs with the
   correct filter configuration
   6.

   Reboot.

Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download  page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation .
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   .
   -

   For a general overview of oVirt, see About oVirt
   .

What’s new in oVirt Node 4.4.2 Release?

oVirt Node has been updated, including:

   -

   oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/
   -

   Ansible 2.9.13:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-13

   -

   Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/
   -

   Advanced Virtualization 8.2.1


See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Additional resources:

   -

   Read more about the oVirt 4.4.2 release highlights:
   http://www.ovirt.org/release/4.4.2/
   -

   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] http://www.ovirt.org/release/4.4.2/
[2] http://resources.ovirt.org/pub/ovirt-4.4/iso/

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/2E6IOFCH5MJSPZ6MNSB5GIW7BGUZNXDS/

[ovirt-users] Ovirt Node 4.4.2 Engine Deployment - Notification Settings

[David White via Users]

I finally got oVirt node installed with gluster on a single node. 
So that's great progress!

Once that step was complete...
I noticed that the Engine Deployment wizard asks for SMTP settings for where to 
send notifications. I was kind of surprised that it doesn't allow one to enter 
any credentials. It looks like this requires an unauthenticated local relay. I 
don't like that. :) See attached screenshot.

Has there been any talk about adding this into the wizard deployment?

Sent with ProtonMail Secure Email.

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/4S5S6KNZOUA4WKPCFF6MYGXCFPP4AR7Z/

[ovirt-users] oVirt node 4.4.1 deploy FQDN not reachable

[Roberto Nunin]

Hi all

I have an issue while trying to deploy hyperconverged solution on three
ovirt node boxes.
ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.

When from cockpit I choose gluster deployment, I have a form where I can
insert both gluster fqdn names and public fqdn names (that is what I need,
due to distinct network cards & networks)

If I insert right names, that are resolved by nodes, I receive, anyway,
FQDN is not reachable below Host1 entries.

As already stated, these names are certainly resolved by DNS used.
Any hints about ?

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

[ovirt-users] oVirt Node 4.1.1 Hosted Engine Deployment Fibre Channel No LUNS found

[hkexdong--- via Users]

I've an external RAID subsystem connect to the host by SAS cable (SFF-8644).
I follow the instructions of the RAID card manufacture. Include the driver 
during host installation. And I can see the created RAID volumes (LUNs) 
available in "Installation Destination". Although I choose to install the 
engine in host local disk.
The installation success and I proceed to hosted engine deployment by Cockpit. 
And now I stuck at part 4 Storage.
I believe "Storage Type" select "Fibre Channel" is correct even I'm not using 
fibre cable. As NFS and iSCSI are utilize network.
I confirm there are 2 RAID volume (LUN0 & LUN1) created in the external RAID 
subsystem. Why oVirt cannot discover them. What could be wrong :(
___
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/IIMW6VBS4JBL5WJFTS7AWDS5ENQDB63Y/

[ovirt-users] ovirt-node-ng-image-update 4.4.1 to 4.4.1.1

[David M. Hornsby]

All,

I applied the recent update 4.4.1 -> 4.4.1.1 to a host in a cluster and it 
failed. After reboot it was hund at the emergency console. I reinstalled 4.4.1 
fresh on the host. Prior to adding it back to the cluster I applied the same 
update with the same result. Is this just a bad update or is the post install 
script bad.

Thanks,
David.
___
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/AY65GWXHPUTIET7DOTQZQJOKZ24CRG4L/

[ovirt-users] oVirt Node 4.4.1.1 Cockpit Hyperconverged Gluster deploy fails insufficient free space no matter how small the volume is set

[clam2718]

Hi,

Deploying oVirt 4.4.1.1 via Cockpit --> Hosted Engine --> Hyperconverged fails 
at Gluster deployment:

TASK [gluster.infra/roles/backend_setup : Create thick logical volume] *
failed: [fmov1n3.sn.dtcorp.com] (item={'vgname': 'gluster_vg_nvme0n1', 
'lvname': 'gluster_lv_engine', 'size': '100G'}) => {"ansible_index_var": 
"index", "ansible_loop_var": "item", "changed": false, "err": "  Volume group 
\"gluster_vg_nvme0n1\" has insufficient free space (25599 extents): 25600 
required.\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": 
"100G", "vgname": "gluster_vg_nvme0n1"}, "msg": "Creating logical volume 
'gluster_lv_engine' failed", "rc": 5}
failed: [fmov1n1.sn.dtcorp.com] (item={'vgname': 'gluster_vg_nvme0n1', 
'lvname': 'gluster_lv_engine', 'size': '100G'}) => {"ansible_index_var": 
"index", "ansible_loop_var": "item", "changed": false, "err": "  Volume group 
\"gluster_vg_nvme0n1\" has insufficient free space (25599 extents): 25600 
required.\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": 
"100G", "vgname": "gluster_vg_nvme0n1"}, "msg": "Creating logical volume 
'gluster_lv_engine' failed", "rc": 5}
failed: [fmov1n2.sn.dtcorp.com] (item={'vgname': 'gluster_vg_nvme0n1', 
'lvname': 'gluster_lv_engine', 'size': '100G'}) => {"ansible_index_var": 
"index", "ansible_loop_var": "item", "changed": false, "err": "  Volume group 
\"gluster_vg_nvme0n1\" has insufficient free space (25599 extents): 25600 
required.\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": 
"100G", "vgname": "gluster_vg_nvme0n1"}, "msg": "Creating logical volume 
'gluster_lv_engine' failed", "rc": 5}

Deployment is on 3 count Dell PowerEdge R740xd with 5 count 1.6TB NVMe drives 
per host.  Deployment is only to three as JBOD, 1 drive per node per volume 
(engine, data, vmstore) utilizing VDO. 
 Thus, deploying even a 100G volume to 1.6TB drive fails with "insufficient 
free space" error.

I suspect this might have to do with the Ansible playbook deploying Gluster 
mishandling the logical volume creation due to the rounding error as described 
here: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/logical_volume_manager_administration/nofreeext

If I can provide any additional information, logs, etc. please ask.  Also, if 
anyone has experience/suggestions with Gluster config for hyperconverged setup 
on NVMe drives I would greatly appreciate any pearls of wisdom.

Thank you so very much for any assistance!
Charles
___
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/3AARZD4VBNNHWNWRCVD2QNWQZJYY5AL5/

[ovirt-users] oVirt-node 4.4.0 - Hosted engine deployment fails when host is unable to download updates

[Marco Fais]

Hi,

fresh installation of oVirt-node 4.4.0 on a cluster -- the hosted-engine
--deploy command fails if DNF is unable to download updates.

This cluster is not connected to the public network at the moment.

If I use a proxy (setting the relevant env. variables) it fails at a later
stage (I think the engine VM is trying to download updates as well, but
encounters the same issue and doesn't seem to use the proxy).

With oVirt-node 4.3.x I didn't have this issue -- any suggestions?

[~]# hosted-engine --deploy
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  During customization use CTRL-D to abort.
  Continuing will configure this host for serving as hypervisor and
will create a local VM with a running engine.
  The locally running engine will be used to configure a new
storage domain and create a VM there.
  At the end the disk of the local VM will be moved to the shared
storage.
  Are you sure you want to continue? (Yes, No)[Yes]:
  Configuration files:
  Log file:
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200604214638-vae2wf.log
  Version: otopi-1.9.1 (otopi-1.9.1-1.el8)
[ INFO  ] DNF Downloading 1 files, 0.00KB
[ INFO  ] DNF Downloaded Extra Packages for Enterprise Linux 8 - x86_64
[

* ERROR ] DNF Failed to download metadata for repo 'ovirt-4.4-epel'[ ERROR
] DNF Failed to download metadata for repo 'ovirt-4.4-epel'[ ERROR ] Failed
to execute stage 'Environment setup': Failed to download metadata for repo
'ovirt-4.4-epel'*
[ INFO  ] Stage: Clean up
[...]

Thanks,
Marco
___
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/VKLN5RBYUHNCMISCNDDKI2FPLIXT34CC/

[ovirt-users] ovirt node 4.4 and infiniband

[Giulio Casella]

Hi all,
I have in production a 4.3.9 setup of ovirt, based on a standalone
engine, not HE.
I have 3 datacenters (an 3 clusters). One of these clusters is composed
of many tenth of HP blades, accessing storage via InfiniBand (used as
normal NICs, via ipoib). They're not the state of the art, but I cannot
renew the entire hardware.

After a setup of ovirt node 4.4 I cannot see ib0 nic.

I managed to see it installing CentOS 8, enabling Mellanox repo
(https://linux.mellanox.com/public/repo/mlnx_ofed/latest/rhel8.1/mellanox_mlnx_ofed.repo)
and installing package "mlnx-ofed-basic".

In Ovirt Node it's not possible, that package require dependencies from
CentOS 8 repos, not present in ovirt repo.

Is there any chances to have infiniband NICs working in ovirt?

TIA,
gc
___
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/DSB62G3CWZ5YE7DAMAUE72LMBZ24FNNG/

[ovirt-users] Ovirt Node 4.3.6 Logical Network Issue - Network Down

[jeremy_tourville]

I have built a new host and my setup is a single hyperconverged node..  I 
followed the directions to create a new logical network.  I see that the engine 
has marked the network as being down. (Hosts>Network Interfaces Tab>Setup Host 
Networks)

Here is my network config on the host-
[root@vmh ~]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp96s0f0:  mtu 1500 qdisc mq master 
ovirtmgmt state UP group default qlen 1000
link/ether 0c:c4:7a:f9:b9:88 brd ff:ff:ff:ff:ff:ff
3: enp96s0f1:  mtu 1500 qdisc mq state UP 
group default qlen 1000
link/ether 0c:c4:7a:f9:b9:89 brd ff:ff:ff:ff:ff:ff
inet 172.30.51.2/30 brd 172.30.51.3 scope global noprefixroute dynamic 
enp96s0f1
   valid_lft 82411sec preferred_lft 82411sec
inet6 fe80::d899:439c:5ee8:e292/64 scope link noprefixroute
   valid_lft forever preferred_lft forever
19: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
link/ether 96:e4:00:aa:71:f7 brd ff:ff:ff:ff:ff:ff
23: ovs-system:  mtu 1500 qdisc noop state DOWN group 
default qlen 1000
link/ether 36:0f:60:69:e1:2b brd ff:ff:ff:ff:ff:ff
24: br-int:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether f6:3b:14:e1:15:48 brd ff:ff:ff:ff:ff:ff
25: ovirtmgmt:  mtu 1500 qdisc noqueue state 
UP group default qlen 1000
link/ether 0c:c4:7a:f9:b9:88 brd ff:ff:ff:ff:ff:ff
inet 172.30.50.3/24 brd 172.30.50.255 scope global dynamic ovirtmgmt
   valid_lft 84156sec preferred_lft 84156sec
inet6 fe80::ec4:7aff:fef9:b988/64 scope link
   valid_lft forever preferred_lft forever
26: vnet0:  mtu 1500 qdisc mq master ovirtmgmt 
state UNKNOWN group default qlen 1000
link/ether fe:16:3e:50:53:cd brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe50:53cd/64 scope link
   valid_lft forever preferred_lft forever

VLAN 101 is attached to enp96s0f0 which is my ovirtmgmt interface.  -IP range 
172.30.50.x
VLAN 102 is attached to enp96s0f1 which is my storage NIC for gluster.  -IP 
range 172.30.51.x
VLAN 103 is attached to enp96s0f1 is intended for most of my VMs that are not 
infrastructure related.  -IP range 192.168.2.x

I am pretty confident my router/switch is setup correctly..  As a test, I can 
go to localhost>networking>add VLAN and assign enp96s0f1 to VLAN 103 and it 
does get an IP address in the 192.168.2.x range.  The host can also ping the 
192.168.2.1 gateway.

Why doesn't the engine think the VLAN is up?  Which logs do I need to review?

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

[ovirt-users] oVirt node - post-upgrade tasks

[dan . munteanu]

Dear oVirt community,

recently I've started to use oVirt as a replacement for KVM + VirtManager and 
I've decided to use the oVirt Node installed on Dell EMC servers with 
self-hosted engine.  So far, everything works fine, except that, each time I'm 
updating the nodes, I must reinstall Dell OMSA needed by the monitoring system 
(via SNMP). Is there any way to automatize the OMSA installation as a 
post-upgrade task/hook?


Thank you

Dan
___
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/3P54P45VI7HBP7XX4ZQNM53QNSS6QWAW/

[ovirt-users] ovirt node install

[Staniforth, Paul]

Hello,

on the latest version of the oVirt-node install running nodectl 
info gives the error



Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/site-packages/nodectl/__main__.py", line 42, in 

CliApplication()
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 200, in 
CliApplication
return cmdmap.command(args)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 118, in 
command
return self.commands[command](**kwargs)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line 76, in info
Info(self.imgbased, self.machine).write()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 46, in __init__
self._fetch_information()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 49, in 
_fetch_information
self._get_bootloader_info()
  File "/usr/lib/python2.7/site-packages/nodectl/info.py", line 62, in 
_get_bootloader_info
bootinfo["entries"][k] = v.__dict__
AttributeError: 'list' object has no attribute '__dict__'



Also what is the correct way to update from ovirt node 4.2 to 4.3?

I used

yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.4-1.el7.noarch.rpm

I then did yum erase ovirt-release42 and rm  /etc/yum.repos.d/ovirt-4.2*

Regards,
   Paul S.
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
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/GNXDVTU66ZUFIRTHTNB2RPBGVYIFYLF5/

[ovirt-users] oVirt node 4.3.4 stable can't deploy hosted engine to iscsi target all available LUNs used

[Mitja Pirih]

Hi,

I am new to oVirt, coming from XenServer platform, so please be patient with me.

After a successful install of latest stable oVirt node 
(ovirt-node-ng-installer-4.3.4-2019061016.el7.iso) I am having troubles 
deploying hosted engine to an iscsi target over Cockpit. I have a couple of 
iscsi targets available on two different storage platforms (Synology DS418, 
Lenovo DE2000H). After retrieving iscsi Target list all LUNs get automatically 
"connected" by "Target list scan" and shown as used on LUNs list. I can 
reproduce this every single time. On storage system I can also see, that all 
LUNs get connected by the initial scan. As a result I an unable to continue the 
deployment as there are no LUNs available.

Is this a normal behavior? What would you suggest me 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/C3P3IRR7GA7RKZZMJTBHOU7DAJU3ZT5Q/

[ovirt-users] oVirt Node Blocks VirtViewer/SPICE connections (Did Not Auto-Configure Firewall?)

[Zachary Winter]

I am unable to connect via SPICE (Windows VirtViewer) to VM's running on 
my compute node.  It appears the node did not auto-configure the 
firewall because the .vv files appear to point to the correct IP address 
and common ports.  Is there a way to re-run/re-execute the firewall 
auto-configuration now that the node has already been installed?


If not, does anyone happen to have firewall-cmd commands handy that I 
can run to resolve this quickly?  Which ports need to be opened?


The specs on the node are as follows:

OS Version:
RHEL - 7 - 6.1810.2.el7.centos
OS Description:
oVirt Node 4.3.3.1
Kernel Version:
3.10.0 - 957.10.1.el7.x86_64
KVM Version:
2.12.0 - 18.el7_6.3.1
LIBVIRT Version:
libvirt-4.5.0-10.el7_6.6
VDSM Version:
vdsm-4.30.13-1.el7
SPICE Version:
0.14.0 - 6.el7_6.1
GlusterFS Version:
glusterfs-5.5-1.el7
CEPH Version:
librbd1-10.2.5-4.el7
Open vSwitch Version:
openvswitch-2.10.1-3.el7
Kernel Features:
PTI: 1, IBRS: 0, RETP: 1, SSBD: 3
VNC Encryption:
Enabled
___
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/XIP6HNQVJXNW55YBXUL273CEH2YSHOA5/

[ovirt-users] oVirt Node 4.3.2 Activation/Deactivation Loop

[zachary . winter]

I have a two-node cluster with one host (ovirt1) running the oVirt engine and 
the other running the most recent oVirt Node (4.3.2 from March 2019) software.  
The engine host has the following information:

OS Version:
RHEL - 7 - 6.1810.2.el7.centos

OS Description:
CentOS Linux 7 (Core)
Kernel Version: 3.10.0 - 957.12.2.el7.x86_64
KVM Version: 2.12.0 - 18.el7_6.5.1
LIBVIRT Version: libvirt-4.5.0-10.el7_6.9
VDSM Version: vdsm-4.30.13-1.el7
SPICE Version: 0.14.0 - 6.el7_6.1
GlusterFS Version: [N/A]
CEPH Version: librbd1-10.2.5-4.el7
Open vSwitch Version: openvswitch-2.10.1-3.el7
Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3
VNC Encryption: Enabled

Aside from the other issue I raised of seeing the "Uncaught exception occurred. 
Please try reloading the page. Details: (TypeError) : Cannot read property 'a' 
of null
Please have your administrator check the UI logs" error on the main host, 
ovirt1 appears to functioning normally.

The node (ovirt2) however is having consistent problems.  The follow sequence 
of events is reproducible and is causing the host to enter a "NonOperational" 
state on the cluster:

* Host ovirt2 installed
* VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can 
be caused by communication issues
* Host ovirt2 is not responding. Host cannot be fenced automatically because 
power management for the host is disabled.
* Host ovirt2 cannot access the Storage Domain(s)  attached to the 
Data Center DataCenter1. Setting Host state to Non-Operational. 
(5/27/1912:43:22 PM)
* (Banner appears in GUI) Failed Activating Host ovirt2.witsconsult.com
* Failed to connect Host ovirt2 to Storage Pool DataCenter1 (5/27/1912:47:07 PM)
* Host ovirt2 cannot access the Storage Domain(s)  attached to the 
Data Center DataCenter1. Setting Host state to Non-Operational. 
(5/27/1912:47:07 PM)
* Host ovirt2 is not responding. Host cannot be fenced automatically because 
power management for the host is disabled. (5/27/1912:47:07 PM)
* VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can 
be caused by communication issues  (5/27/1912:47:07 PM)

I can then re-activate ovirt2, which appears as green for approximately 5 
minutes and then repeats all of the above issues.

What can I do to troubleshoot this?
___
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/TR5A2YGMX2KUX2PPAFY2F5BQCDO4CJ3D/

[ovirt-users] Ovirt Node transfer to New Engine (it is possible)

[IT INFRA]

Hi,

It is possible to transfer my node to other ovirt engine (new 4.3) here's the 
scenario.

Old Server: (no internet prod)
Engine (ovirt 4.1) - Hardware failure No possible recovery
Node1 (node 4.1)
Node2 (node 4.1)

New Server 
Engine (Ovirt 4.3)

*note have full backup of old engine 4.1 version\
* can't re install using yum install 
http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm (no more link 
available)

any possible solution on this..

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

[ovirt-users] oVirt node loses gluster volume UUID after reboot, goes to emergency mode every time I reboot.

[michael]

This only started to happen with oVirt node 4.3, 4.2 didn't have issue.  Since 
I updated to 4.3, every reboot the host goes into emergency mode.  First few 
times this happened I re-installed O/S from scratch, but after some digging I 
found out that the drives it mounts in /etc/fstab cause the problem, 
specifically these mounts.  All three are single drives, one is an SSD and the 
other 2 are individual NVME drives.

UUID=732f939c-f133-4e48-8dc8-c9d21dbc0853 /gluster_bricks/storage_nvme1 auto 
defaults 0 0
UUID=5bb67f61-9d14-4d0b-8aa4-ae3905276797 /gluster_bricks/storage_ssd auto 
defaults 0 0
UUID=f55082ca-1269-4477-9bf8-7190f1add9ef /gluster_bricks/storage_nvme2 auto 
defaults 0 0

In order to get the host to actually boot, I have to go to console, delete 
those mounts, reboot, and then re-add them, and they end up with new UUIDs.  
all of these hosts reliably rebooted in 4.2 and earlier, but all the versions 
of 4.3 have this same problem (I keep updating to hope issue is fixed).  
 
___
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/I4UKZAWPQDXWA47AKTQD43PAUCK2JBJN/

[ovirt-users] Ovirt Node 4.3 Gluster Install adding bricks

[pollard]

Sorry if this seems simple, but trial and error is how I learn. So the basics. 
I installed Node 4.3 on 3 hosts, and was following the setup for self-hosted 
engine. The setup fails when detecting peers and indicates that they are 
already part of a cluster. So i restart the install and choose the install 
engine on single node with Gluster. I now have all three nodes connected to 
ovirt engine, however my trouble is I am not understanding how to add the disk 
of the two nodes to the glusterFS. I also have some extra disks on my primary 
node I want to add. I believe it is as follows but I dont want to mess this up.

Under Compute >> Hosts >> $HOSTNAME
Select Storage Devices
Select Disk in my case sde
Then create brick?
 If this is the case Do I add it to a LV if so which one 
engine,data or vmstore?
 Do I repeat this for each hosts?

I can duplicate the engine, data and vmstore on each one, but that will still 
leave me with two disks on each node without assignment
If anyone can help that would be great.


Thank you.
Pollard

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

[ovirt-users] oVirt Node install failed

[kiv]

Hi all!

The following error occurs during installation oVirt Node 4.2.8:

 EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during 
installation of Host hostname_ovirt_node2: Yum Cannot queue package dmidecode: 
Cannot retrieve metalink for repository: ovirt-4.2-epel/x86_64. Please verify 
its path and try again

From shell ovirt node type command:

yum install dmidecode

Cannot retrieve metalink for repository: ovirt-4.2-epel/x86_64. Please verify 
its path and try again
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, product-id, subscription-manager
This system is not registered with an entitlement server. You can use 
subscription-manager to register.
Cannot upload enabled repos report, is this client registered?

Does anyone know how to fix this?
___
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/7D4DLDSZ6F2U4CCQC63GMFYR5EF6HYDB/

[ovirt-users] ovirt node installation and deploy...

[matteo fedeli]

Hi at all, during the deployment the system fail... 

http://oi63.tinypic.com/et9kd4.jpg
During installation it's corretct select all disks?
All disk must be without any partition table?

My target is on the first disk ovirt node, second vmstore/engine volume and 
third for data.

By watching this image,
https://access.redhat.com/webassets/avalon/d/Red_Hat_Hyperconverged_Infrastructure_for_Virtualization-1.5-Deploying_Red_Hat_Hyperconverged_Infrastructure_for_Virtualization-en-US/images/761a53cdd65305972eea0baf5bd56eba/cockpit-virt-gluster-deploy-bricks.png
How can I set the LV size correctly?
___
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/YQDDAHBRDIPD3VOSSKAOOBWYAEDF4SSO/

[ovirt-users] ovirt-node 4.3 hyperconverged - fails on VM deployment - all nodes broken

[feral]

Boring 3 vanilla node deployment. Default options except for gluster volume
size. All three nodes on static IP on LAN. All three have each other listed
in /etc/hosts as well as dns.
Gluster wizard complete successfully, deploy VM. VM deployment fails after
copying to the gluster storage. At that point, rebooting any node results
in node not coming back to life. No networking, so no other services.
Only error I can get is to check the engine.log, which I cannot do as the
engine fails to come up.

Anyone else seeing this with a vanilla install/deployment?

-- 
_
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
___
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/4QDZX5DK4VC6LPGS3SOM2NR6KFW7QUA6/

[ovirt-users] ovirt-node-4.3, deployment fails when moving hosted engine vm to gluster storage.

[feral]

I have no idea what's wrong at this point. Very vanilla install of 3 nodes.
Run the Hyperconverged wizard, completes fine. Run the engine deployment,
takes hours, eventually fails with :

[ INFO ] TASK [oVirt.hosted-engine-setup : Check engine VM health]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
"cmd": ["hosted-engine", "--vm-status", "--json"], "delta":
"0:00:00.340985", "end": "2019-02-06 11:44:48.836431", "rc": 0, "start":
"2019-02-06 11:44:48.495446", "stderr": "", "stderr_lines": [], "stdout":
"{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=12994
(Wed Feb 6 11:44:44
2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=12995 (Wed Feb 6
11:44:44
2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\n\",
\"hostname\": \"ovirt-431.localdomain\", \"host-id\": 1, \"engine-status\":
{\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
\"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
\"maintenance\": false, \"crc32\": \"5474927a\", \"local_conf_timestamp\":
12995, \"host-ts\": 12994}, \"global_maintenance\": false}",
"stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\":
true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=12994
(Wed Feb 6 11:44:44
2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=12995 (Wed Feb 6
11:44:44
2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStop\\nstopped=False\\n\",
\"hostname\": \"ovirt-431.localdomain\", \"host-id\": 1, \"engine-status\":
{\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
\"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
\"maintenance\": false, \"crc32\": \"5474927a\", \"local_conf_timestamp\":
12995, \"host-ts\": 12994}, \"global_maintenance\": false}"]}
[ INFO ] TASK [oVirt.hosted-engine-setup : Check VM status at virt level]
[ INFO ] changed: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Fail if engine VM is not running]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Get target engine VM IP address]
[ INFO ] changed: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Get VDSM's target engine VM
stats]
[ INFO ] changed: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Convert stats to JSON format]
[ INFO ] ok: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Get target engine VM IP address
from VDSM stats]
[ INFO ] ok: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Fail if Engine IP is different
from engine's he_fqdn resolved IP]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [oVirt.hosted-engine-setup : Fail is for any other reason the
engine didn't started]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
engine failed to start inside the engine VM; please check engine.log."}

---

I can't check the engine.log as I can't connect to the VM once this failure
occurs. I can ssh in prior to the VM being moved to gluster storage, but as
soon as it starts doing so, the VM never comes back online.


-- 
_
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
___
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/LAM3TX64UQOOO7A2WBMGZUEF4TVFHXJA/

[ovirt-users] ovirt-node 4.2 iso - hyperconverged wizard doesn't write gdeployConfig settings

[feral]

New install of ovirt-node 4.2 (from iso). Setup each node with networking
and ssh keys, and use the hyperconverged gluster deployment wizard. None of
the user specified settings are ever reflected in the gdeployConfig.conf.
Anyone running into this?

-- 
_
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
___
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/TF56FSFRNGCWEM4VJFOGKKAELJ3ID7NR/

[ovirt-users] ovirt node ng 4.3.0 rc1 and HCI single host problems

[Gianluca Cecchi]

Let's start a new thread more focused on the subject

I'm just testing deployment of HCI single host using oVirt Node NG CentOS 7
iso

I was able to complete the gluster setup via cockpit with these
modifications:

1) I wanted to check via ssh and found that files *key under /etc/ssh/ had
too weak config so that ssh daemon didn't started after installation of
node from iso
changing to 600 and restarting the service was ok

2) I used a single disk configured as jbod, so I choose that option instead
of the default proposed RAID6

But the playook failed with
. . .
PLAY [gluster_servers]
*

TASK [Create LVs with specified size for the VGs]
**
changed: [192.168.124.211] => (item={u'lv': u'gluster_thinpool_sdb',
u'size': u'50GB', u'extent': u'100%FREE', u'vg': u'gluster_vg_sdb'})

PLAY RECAP
*
192.168.124.211: ok=1changed=1unreachable=0
failed=0
Ignoring errors...
Error: Section diskcount not found in the configuration file

Reading inside the playbooks involved here:
/usr/share/gdeploy/playbooks/auto_lvcreate_for_gluster.yml
/usr/share/gdeploy/playbooks/vgcreate.yml

and the snippet

  - name: Convert the logical volume
lv: action=convert thinpool={{ item.vg }}/{{item.pool }}
poolmetadata={{ item.vg }}/'metadata' poolmetadataspare=n
vgname={{ item.vg }} disktype="{{disktype}}"
diskcount="{{ diskcount }}"
stripesize="{{stripesize}}"
chunksize="{{ chunksize | default('') }}"
snapshot_reserve="{{ snapshot_reserve }}"
with_items: "{{ lvpools }}"
ignore_errors: yes

I simply edited the gdeploy.conf from the gui button adding this section
under the [disktype] one
"

[diskcount]
1

"
then clean lv/vg/pv and the gdeploy step completed successfully

3) at first stage of ansible deploy I have this failed command that seems
not to prevent from completion but that I have not understood..

PLAY [gluster_servers]
*

TASK [Run a command in the shell]
**
failed: [192.168.124.211] (item=vdsm-tool configure --force) => {"changed":
true, "cmd": "vdsm-tool configure --force", "delta": "0:00:01.475528",
"end": "2019-01-11 10:59:55.147601", "item": "vdsm-tool configure --force",
"msg": "non-zero return code", "rc": 1, "start": "2019-01-11
10:59:53.672073", "stderr": "Traceback (most recent call last):\n  File
\"/usr/bin/vdsm-tool\", line 220, in main\nreturn
tool_command[cmd][\"command\"](*args)\n  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py\", line 40, in
wrapper\nfunc(*args, **kwargs)\n  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 143,
in configure\n_configure(c)\n  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 90, in
_configure\ngetattr(module, 'configure', lambda: None)()\n  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurators/bond_defaults.py\",
line 39, in configure\nsysfs_options_mapper.dump_bonding_options()\n
File
\"/usr/lib/python2.7/site-packages/vdsm/network/link/bond/sysfs_options_mapper.py\",
line 48, in dump_bonding_options\nwith
open(sysfs_options.BONDING_DEFAULTS, 'w') as f:\nIOError: [Errno 2] No such
file or directory: '/var/run/vdsm/bonding-defaults.json'", "stderr_lines":
["Traceback (most recent call last):", "  File \"/usr/bin/vdsm-tool\", line
220, in main", "return tool_command[cmd][\"command\"](*args)", "  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py\", line 40, in
wrapper", "func(*args, **kwargs)", "  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 143,
in configure", "_configure(c)", "  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 90, in
_configure", "getattr(module, 'configure', lambda: None)()", "  File
\"/usr/lib/python2.7/site-packages/vdsm/tool/configurators/bond_defaults.py\",
line 39, in configure", "sysfs_options_mapper.dump_bonding_options()",
"  File
\"/usr/lib/python2.7/site-packages/vdsm/network/link/bond/sysfs_options_mapper.py\",
line 48, in dump_bonding_options", "with
open(sysfs_options.BONDING_DEFAULTS, 'w') as f:", "IOError: [Errno 2] No
such file or directory: '/var/run/vdsm/bonding-defaults.json'"], "stdout":
"\nChecking configuration status...\n\nabrt is already configured for
vdsm\nlvm is configured for vdsm\nlibvirt is already configured for
vdsm\nSUCCESS: ssl configured to true. No conflicts\nManual override for
multipath.conf detected - preserving current configuration\nThis manual
override for multipath.conf was based on downrevved template. You are
strongly advised to contact your support representatives\n\nRunning
configure...\nReconfiguration of abrt is done.\nReconfiguration of passwd
is done.\nReconfiguration of libvirt is done.", 

[ovirt-users] ovirt node ng 4.3.0 rc1 upgrade fails

[Jorick Astrego]

Hi,

Trying to update oVirt Node 4.2.7.1 to 4.3.0, but it fails with the
following dependencies:

    "Loaded plugins: enabled_repos_upload, fastestmirror,
imgbased-persist,\n  : package_upload, product-id,
search-disabled-repos, subscription-\n  : manager,
vdsmupgrade\nThis system is not registered with an entitlement
server. You can use subscription-manager to register.\nLoading
mirror speeds from cached hostfile\n * ovirt-4.3-epel:
ftp.nluug.nl\nResolving Dependencies\n--> Running transaction
check\n---> Package ovirt-host.x86_64 0:4.2.3-1.el7 will be
updated\n---> Package ovirt-host.x86_64 0:4.3.0-1.el7 will be an
update\n--> Processing Dependency: ovirt-host-dependencies =
4.3.0-1.el7 for package: ovirt-host-4.3.0-1.el7.x86_64\n-->
Processing Dependency: aide for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: openscap
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: openscap-utils for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: pam_pkcs11
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: scap-security-guide for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Running transaction check\n--->
Package ovirt-host.x86_64 0:4.3.0-1.el7 will be an update\n-->
Processing Dependency: aide for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: openscap
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: openscap-utils for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: pam_pkcs11
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: scap-security-guide for package:
ovirt-host-4.3.0-1.el7.x86_64\n---> Package
ovirt-host-dependencies.x86_64 0:4.2.3-1.el7 will be updated\n--->
Package ovirt-host-dependencies.x86_64 0:4.3.0-1.el7 will be an
update\n--> Processing Dependency: vdsm >= 4.30.5 for package:
ovirt-host-dependencies-4.3.0-1.el7.x86_64\n--> Processing
Dependency: vdsm-client >= 4.30.5 for package:
ovirt-host-dependencies-4.3.0-1.el7.x86_64\n--> Running transaction
check\n---> Package ovirt-host.x86_64 0:4.3.0-1.el7 will be an
update\n--> Processing Dependency: aide for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: openscap
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: openscap-utils for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: pam_pkcs11
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: scap-security-guide for package:
ovirt-host-4.3.0-1.el7.x86_64\n---> Package vdsm.x86_64
0:4.20.43-1.el7 will be updated\n--> Processing Dependency: vdsm =
4.20.43-1.el7 for package:
vdsm-hook-ethtool-options-4.20.43-1.el7.noarch\n--> Processing
Dependency: vdsm = 4.20.43-1.el7 for package:
vdsm-gluster-4.20.43-1.el7.x86_64\n--> Processing Dependency: vdsm =
4.20.43-1.el7 for package:
vdsm-hook-vmfex-dev-4.20.43-1.el7.noarch\n--> Processing Dependency:
vdsm = 4.20.43-1.el7 for package:
vdsm-hook-fcoe-4.20.43-1.el7.noarch\n---> Package vdsm.x86_64
0:4.30.5-1.el7 will be an update\n--> Processing Dependency:
vdsm-http = 4.30.5-1.el7 for package: vdsm-4.30.5-1.el7.x86_64\n-->
Processing Dependency: vdsm-jsonrpc = 4.30.5-1.el7 for package:
vdsm-4.30.5-1.el7.x86_64\n--> Processing Dependency: vdsm-python =
4.30.5-1.el7 for package: vdsm-4.30.5-1.el7.x86_64\n--> Processing
Dependency: qemu-kvm-rhev >= 10:2.12.0-18.el7_6.1 for package:
vdsm-4.30.5-1.el7.x86_64\n---> Package vdsm-client.noarch
0:4.20.43-1.el7 will be updated\n---> Package vdsm-client.noarch
0:4.30.5-1.el7 will be an update\n--> Processing Dependency:
vdsm-api = 4.30.5-1.el7 for package:
vdsm-client-4.30.5-1.el7.noarch\n--> Processing Dependency:
vdsm-yajsonrpc = 4.30.5-1.el7 for package:
vdsm-client-4.30.5-1.el7.noarch\n--> Running transaction check\n--->
Package ovirt-host.x86_64 0:4.3.0-1.el7 will be an update\n-->
Processing Dependency: aide for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: openscap
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: openscap-utils for package:
ovirt-host-4.3.0-1.el7.x86_64\n--> Processing Dependency: pam_pkcs11
for package: ovirt-host-4.3.0-1.el7.x86_64\n--> Processing
Dependency: scap-security-guide for package:
ovirt-host-4.3.0-1.el7.x86_64\n---> Package qemu-kvm-ev.x86_64
10:2.10.0-21.el7_5.7.1 will be updated\n---> Package
qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.1.1 will be an update\n-->
Processing Dependency: qemu-kvm-common-ev = 10:2.12.0-18.el7_6.1.1
for package: 10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64\n-->
Processing Dependency: qemu-img-ev = 10:2.12.0-18.el7_6.1.1 for
package: 

[ovirt-users] oVirt Node install - kickstart postintall

[jeanbaptiste]

Hello everybody,

Since days, I'm trying to install oVirt (via Foreman) in network mode (TFTP net 
install).
All is great, but I want to make some actions in postinstall (%post).
Some actions are relatated to /etc/sysconfig/network-interfaces and another 
action is related to root authorized_keys.

When I try to add pub-key to a created  authorized_keys for root, I work 
(verified into anaconda. 
But after installation and anaconda reboot, I've noticed all my %post actions 
in /(root) are discared. After reboot, there is nothing in /root/.ssh for 
example.
Whereas, in /etc, all my modications are preserved.

I thought to a Selinux relative issue, but It is not relative to  Selinux 

I miss something. Please can you help to  understand how oVirt install / 
partition work ?

thanks for all
___
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/BCQEKHCPSFDEFDPI4OVSXRTJS3BSJH5R/

[ovirt-users] oVirt Node 4.2.5.1 vm stuck on "Powering Down"

[maoz zadok]

Hello,
vm  stuck (on two hosts)
I have MySQL VM guest that was stuck in a way that "kill -9" to the MySQL
server pid did nothing.
from the shell I execute "init 0", this did not shut down the VM.

from the ovirt-engine I'm trying to power off the machine, and it is not
doing anything.
the event shows:

> VDSM kvm5 command DestroyVDS failed: Virtual machine destroy error
>
and:

> Failed to power off VM mysql-production (Host: kvm5, User:
> admin@internal-authz).
>

Note,  when I list the VM s on the hosts view, I see that that same VM is
on two hosts (kvm7 and kvm5).
It looks like the VM is stuck on two hosts, in the status "Powering Down"

any ideas?
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/E2HKUJZYUNC3VCVI3SAL3ZNXV3TU5OO2/

[ovirt-users] Ovirt Node Installation issue on Ovirt 4.2

[Hemant Gupta]

Hi,
I have downloaded the ISO on physical server but I am unable to attach to my 
ovirt engine as it showing vdsm error but during update on CentosOS launched 
with ISO its giving below :
[root@r yum.repos.d]# sudo yum install 
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, 
package_upload, product-id, search-disabled-repos, vdsmupgrade
Examining /var/tmp/yum-root-fu0Y2g/ovirt-release42.rpm: 
ovirt-release42-4.2.7-1.el7.noarch
/var/tmp/yum-root-fu0Y2g/ovirt-release42.rpm: does not update installed package.
Error: Nothing to do
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, product-id
Cannot upload enabled repos report, is this client registered?
___
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/PJGVGBK43RUHZE6ITJ7J4U33EHONPPFF/

[ovirt-users] oVirt node LDAP auth

[Николаев Алексей]

Hi, community! What is best way for LDAP auth on oVirt Node? Is it possible to use realmd to integarate with domain?___
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/RHMSCULZUUXMBTQYCQI7Z6A5F2RPWNI3/

[ovirt-users] Ovirt Node Installtion

[aru_barani]

1. I install the ovirt node 4.2 in KVM on centos 7. when i try to install 
package or yum update it shows the message" Cannot retrieve metalink for 
repository:   ovirt-4.2-epel/x86_64. Please verify its path and try again 
Uploading Enabled Repositories Report Loaded plugins: fastestmirror, product-id 
Cannot upload enabled repos report, is this client registered?" this system 
have full internet access please give me the solution for this issue

2. We need to test ovirt node and ovirt engine for load balance in vm so please 
help me or have any unregister ovirt node

3. In Web GUI of Ovirt node console the "Domain Join option is disable" is 
possible to enable
___
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/IZXH7DFRXBBFUHKVBUKXL33HRNZY4L2O/

[ovirt-users] oVirt Node 4.2.7 upgrade fails with broken dependencies ?

[Rogério Ceni Coelho]

Hi all !

Broken dependencies ?

[root@nscovirtkvm41prdpoa ~]# yum update
Loaded plugins: enabled_repos_upload, fastestmirror, package_upload,
product-id, search-disabled-repos, subscription-manager, vdsmupgrade
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Loading mirror speeds from cached hostfile
 * base: mirror.ufscar.br
 * epel: mirror.ci.ifes.edu.br
 * extras: centos.brnet.net.br
 * ovirt-4.2: www.gtlib.gatech.edu
 * ovirt-4.2-epel: mirror.ci.ifes.edu.br
 * updates: mirror.ufscar.br
Resolving Dependencies
--> Running transaction check
---> Package collectd.x86_64 0:5.8.0-6.1.el7 will be updated
--> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package:
collectd-disk-5.8.0-6.1.el7.x86_64
--> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package:
collectd-write_http-5.8.0-6.1.el7.x86_64
---> Package collectd.x86_64 0:5.8.1-1.el7 will be an update
---> Package collectd-netlink.x86_64 0:5.8.0-6.1.el7 will be updated
---> Package collectd-netlink.x86_64 0:5.8.1-1.el7 will be an update
---> Package collectd-virt.x86_64 0:5.8.0-6.1.el7 will be updated
---> Package collectd-virt.x86_64 0:5.8.1-1.el7 will be an update
---> Package ovirt-hosted-engine-setup.noarch 0:2.2.30-1.el7 will be updated
---> Package ovirt-hosted-engine-setup.noarch 0:2.2.32-1.el7 will be an
update
--> Finished Dependency Resolution
Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64
(@ovirt-4.2-centos-opstools)
   Requires: collectd(x86-64) = 5.8.0-6.1.el7
   Removing: collectd-5.8.0-6.1.el7.x86_64
(@ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-6.1.el7
   Updated By: collectd-5.8.1-1.el7.x86_64 (epel)
   collectd(x86-64) = 5.8.1-1.el7
   Available: collectd-5.7.2-1.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.7.2-1.el7
   Available: collectd-5.7.2-3.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.7.2-3.el7
   Available: collectd-5.8.0-2.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-2.el7
   Available: collectd-5.8.0-3.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-3.el7
   Available: collectd-5.8.0-5.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-5.el7
Error: Package: collectd-disk-5.8.0-6.1.el7.x86_64
(@ovirt-4.2-centos-opstools)
   Requires: collectd(x86-64) = 5.8.0-6.1.el7
   Removing: collectd-5.8.0-6.1.el7.x86_64
(@ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-6.1.el7
   Updated By: collectd-5.8.1-1.el7.x86_64 (epel)
   collectd(x86-64) = 5.8.1-1.el7
   Available: collectd-5.7.2-1.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.7.2-1.el7
   Available: collectd-5.7.2-3.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.7.2-3.el7
   Available: collectd-5.8.0-2.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-2.el7
   Available: collectd-5.8.0-3.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-3.el7
   Available: collectd-5.8.0-5.el7.x86_64
(ovirt-4.2-centos-opstools)
   collectd(x86-64) = 5.8.0-5.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, product-id, subscription-manager
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Cannot upload enabled repos report, is this client registered?
[root@nscovirtkvm41prdpoa ~]# yum repolist
Loaded plugins: enabled_repos_upload, fastestmirror, package_upload,
product-id, search-disabled-repos, subscription-manager, vdsmupgrade
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Loading mirror speeds from cached hostfile
 * base: mirror.ufscar.br
 * epel: mirror.ci.ifes.edu.br
 * extras: centos.brnet.net.br
 * ovirt-4.2: www.gtlib.gatech.edu
 * ovirt-4.2-epel: mirror.ci.ifes.edu.br
 * updates: mirror.ufscar.br
repo id   repo
name
status
base/7/x86_64 CentOS-7
- Base
 9,911
centos-sclo-rh-release/x86_64 CentOS-7
- SCLo rh
  8,099
epel/x86_64   Extra
Packages for Enterprise Linux 7 - x86_64
   12,708
extras/7/x86_64   CentOS-7
- Extras
   434
ovirt-4.2/7   Latest
oVirt 4.2 Release
2,439

[ovirt-users] Ovirt Node issue with fqdn

[miquel . oliveros]

I'm trying to change the FQDN, I tried changing the /etc/hosts and also with 
hosted-engine --deploy... please can someone help me about what can I do to 
change the fqdn?

And I'm trying to do the Hosted Engine Deployment and I want to put for example 
ovirtNode.sec.com...

Any idea about how 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/UZSUDGC2QR7ZWVZA2LEJBINGDR5CA2PP/

[ovirt-users] ovirt-node-ng-image-update 4.2.4 to 4.2.5.1 fails

[Glenn Farmer]

yum update ends with:

warning: %post(ovirt-node-ng-image-update-4.2.5.1-1.el7.noarch) scriptlet 
failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package 
ovirt-node-ng-image-update-4.2.5.1-1.el7.noarch

It creates the layers:

ovirt-node-ng-4.2.5.1-0.20180731.0   onn Vri---tz-k  6.00g pool00
ovirt-node-ng-4.2.5.1-0.20180731.0+1 onn  Vwi-a-tz--  6.00g pool00 
ovirt-node-ng-4.2.5.1-0.20180731.0

But no grub2 boot entry.

nodectl info:

layers:
  ovirt-node-ng-4.2.4-0.20180626.0:
ovirt-node-ng-4.2.4-0.20180626.0+1
  ovirt-node-ng-4.2.5.1-0.20180731.0:
ovirt-node-ng-4.2.5.1-0.20180731.0+1
  ovirt-node-ng-4.2.2-0.20180405.0:
ovirt-node-ng-4.2.2-0.20180405.0+1
bootloader:
  default: ovirt-node-ng-4.2.4-0.20180626.0+1
  entries:
ovirt-node-ng-4.2.2-0.20180405.0+1:
  index: 1
  title: ovirt-node-ng-4.2.2-0.20180405.0+1
  kernel: 
/boot/ovirt-node-ng-4.2.2-0.20180405.0+1/vmlinuz-3.10.0-693.21.1.el7.x86_64
  args: "ro crashkernel=auto 
rd.lvm.lv=onn/ovirt-node-ng-4.2.2-0.20180405.0+1 
img.bootid=ovirt-node-ng-4.2.2-0.20180405.0+1"
  initrd: 
/boot/ovirt-node-ng-4.2.2-0.20180405.0+1/initramfs-3.10.0-693.21.1.el7.x86_64.img
  root: /dev/onn/ovirt-node-ng-4.2.2-0.20180405.0+1
ovirt-node-ng-4.2.4-0.20180626.0+1:
  index: 0
  title: ovirt-node-ng-4.2.4-0.20180626.0+1
  kernel: 
/boot/ovirt-node-ng-4.2.4-0.20180626.0+1/vmlinuz-3.10.0-862.3.3.el7.x86_64
  args: "ro crashkernel=auto 
rd.lvm.lv=onn/ovirt-node-ng-4.2.4-0.20180626.0+1 
img.bootid=ovirt-node-ng-4.2.4-0.20180626.0+1"
  initrd: 
/boot/ovirt-node-ng-4.2.4-0.20180626.0+1/initramfs-3.10.0-862.3.3.el7.x86_64.img
  root: /dev/onn/ovirt-node-ng-4.2.4-0.20180626.0+1
current_layer: ovirt-node-ng-4.2.4-0.20180626.0+1

Just posting for others that might have the same issue.
___
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/VOTNR3NH3EAEW6YDINIILFVGQB2BX544/

[ovirt-users] oVirt Node 4.2.3.1. to 4.2.5 upgrade trouble, log attached

[Matt Simonsen]

Hello all,

I've emailed about similar trouble with an oVirt Node upgrade using the 
ISO install. I've attached the /tmp/imgbased.log file in hopes it will 
help give a clue as to why the trouble.


Since these use NFS storage I can rebuild, but would like to know, 
ideally, what caused the upgrade to break.


Truthfully following the install, I don't think I have done *that* much 
to these systems, so I'm not sure what would have caused the problem.


I have done several successful upgrades in the past and most of my 
standalone systems have been working great.


I've been really happy with oVirt, so kudos to the team.

Thanks for any help,

Matt




imgbased.log.gz
Description: application/gzip
___
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/G6P7CHKTBD7ESE33MIXEDKV44QXITDJP/

[ovirt-users] ovirt-node-ng update to 4.2.5 failed

[p . staniforth]

Hello,
  I tried to update a ovirt-ng-node from 4.2.4 via the engine and it 
failed, I also tried using "yum update ovirt-node-ng-image-update".
What is the correct way to update a node and how do I delete old layers 

Thanks,
   Paul S.
The output from "nodectl info" is

layers: 
  ovirt-node-ng-4.2.4-0.20180626.0: 
ovirt-node-ng-4.2.4-0.20180626.0+1
  ovirt-node-ng-4.1.9-0.20180124.0: 
ovirt-node-ng-4.1.9-0.20180124.0+1
  ovirt-node-ng-4.2.5.1-0.20180731.0: 
ovirt-node-ng-4.2.5.1-0.20180731.0+1
bootloader: 
  default: ovirt-node-ng-4.2.4-0.20180626.0+1
  entries: 
ovirt-node-ng-4.2.4-0.20180626.0+1: 
  index: 0
  title: ovirt-node-ng-4.2.4-0.20180626.0
  kernel: 
/boot/ovirt-node-ng-4.2.4-0.20180626.0+1/vmlinuz-3.10.0-862.3.3.el7.x86_64
  args: "ro crashkernel=auto 
rd.lvm.lv=onn/ovirt-node-ng-4.2.4-0.20180626.0+1 rd.lvm.lv=onn/swap rhgb quiet 
LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.2.4-0.20180626.0+1"
  initrd: 
/boot/ovirt-node-ng-4.2.4-0.20180626.0+1/initramfs-3.10.0-862.3.3.el7.x86_64.img
  root: /dev/onn/ovirt-node-ng-4.2.4-0.20180626.0+1
ovirt-node-ng-4.1.9-0.20180124.0+1: 
  index: 1
  title: ovirt-node-ng-4.1.9-0.20180124.0
  kernel: 
/boot/ovirt-node-ng-4.1.9-0.20180124.0+1/vmlinuz-3.10.0-693.11.6.el7.x86_64
  args: "ro crashkernel=auto 
rd.lvm.lv=onn/ovirt-node-ng-4.1.9-0.20180124.0+1 rd.lvm.lv=onn/swap rhgb quiet 
LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.1.9-0.20180124.0+1"
  initrd: 
/boot/ovirt-node-ng-4.1.9-0.20180124.0+1/initramfs-3.10.0-693.11.6.el7.x86_64.img
  root: /dev/onn/ovirt-node-ng-4.1.9-0.20180124.0+1
current_layer: ovirt-node-ng-4.2.4-0.20180626.0+1
___
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/BGBYX6IFNCJTMIT344XV2U2QVV2CXYWF/

[ovirt-users] oVirt node 4.2.x - custom multipath.conf and external storage availability

[Roberto Nunin]

HI all

How can I provide to my oVirt hosts a custom multipath.conf, considering
that we are using shared/mirrored FC storage from HPE 3PAR with high
availability of provided LUNs, using peer-persistance feature ?

To configure correctly this require  a custom multipath.conf is required.
How I can avoid it will be overwritten during upgrades ?

Second topic:
Is ALUA feature supported also in oVirt nodes, like for standard RHEL 6/7
and/or CentOS 6/7 ?

I was digging  for a while into user's digest, but not able to find focused
informations.

This is the feature needed by peer-persistance, allowing two different
volumes to be masked toward a given host with the same WWN and LUN number.

Thanks in advance

-- 
Roberto
___
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/LCKGIS3C5D5JP5B4ELDFTLCSQMKMLILM/

[ovirt-users] oVirt node not installed

[Spickiy Nikita]

Hi, i try install oVirt node, but getting errors on step post-install script. 
Screen error in attachment.
 [cid:944CCD96-B8FF-4ABA-AF17-FA6A7DC184BB@digital-ecosystems.ru] 
[cid:8D77635B-AF62-4894-A9E2-F57E9F290DE5@digital-ecosystems.ru]
___
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/2NAYW6CR72YP6ADQMCID7ANH2D756WZT/

[ovirt-users] Ovirt Node NG (4.2.3.1-0.20180530) Boot fail ISCSI using ibft after installation

[Ralf Schenk]

Hello,

I successfully installed Ovirt Node NG from ISO to an ISCSI target
attached via first network interface by using following extensions to
the grub cmdline:

"rd.iscsi.ibft=1 ip=ibft ip=eno2:dhcp"

I want to use the server as diskless ovirt-node-ng Server.

After successful install the system reboots and starts up but it fails
later in dracut even having detected correctly the disk and all the LV's.

I think "iscsistart" is run multiple times even after already being
logged in to the ISCSI-Target and that fails finally like that:

*[  147.644872] localhost dracut-initqueue[1075]: iscsistart: initiator
reported error (15 - session exists)*
[  147.645588] localhost dracut-initqueue[1075]: iscsistart: Logging
into iqn.2018-01.de.databay.office:storage01.epycdphv02-disk1
172.16.1.3:3260,1
[  147.651027] localhost dracut-initqueue[1075]: Warning: 'iscsistart -b
' failed with return code 0
[  147.807510] localhost systemd[1]: Starting Login iSCSI Target...
[  147.809293] localhost iscsistart[6716]: iscsistart: TargetName not
set. Exiting iscsistart
[  147.813625] localhost systemd[1]: iscsistart_iscsi.service: main
process exited, code=exited, status=7/NOTRUNNING
[  147.824897] localhost systemd[1]: Failed to start Login iSCSI Target.
[  147.825050] localhost systemd[1]: Unit iscsistart_iscsi.service
entered failed state.
[  147.825185] localhost systemd[1]: iscsistart_iscsi.service failed.

-- 
Mit freundlichen Grüßen

Ralf Schenk

+ cat /lib/dracut/dracut-033-535.el7
dracut-033-535.el7
+ cat /proc/cmdline
BOOT_IMAGE=/ovirt-node-ng-4.2.3.1-0.20180530.0+1/vmlinuz-3.10.0-862.3.2.el7.x86_64
 root=/dev/onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 ro crashkernel=auto 
bootdev=ibft0 ip=ibft ip=eno2:dhcp netroot=iscsi rd.iscsi.ibft=1 
rd.iscsi.firmware=1 rd.auto rd.lvm.lv=onn/var_log rd.lvm.lv=onn/tmp 
rd.lvm.lv=onn/var_log_audit rd.lvm.lv=onn/swap 
rd.lvm.lv=onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 rd.lvm.lv=onn/home 
plymouth.enable=0 rd.lvm.lv=onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 
img.bootid=ovirt-node-ng-4.2.3.1-0.20180530.0+1
+ '[' -f /etc/cmdline ']'
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/40-ibft.conf ']'
+ echo /etc/cmdline.d/40-ibft.conf
/etc/cmdline.d/40-ibft.conf
+ cat /etc/cmdline.d/40-ibft.conf
ip=172.16.1.121:::255.255.255.0::ibft0:none
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/45-ifname.conf ']'
+ echo /etc/cmdline.d/45-ifname.conf
/etc/cmdline.d/45-ifname.conf
+ cat /etc/cmdline.d/45-ifname.conf
ifname=ibft0:0c:c4:7a:fa:23:92
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/dracut-neednet.conf ']'
+ echo /etc/cmdline.d/dracut-neednet.conf
/etc/cmdline.d/dracut-neednet.conf
+ cat /etc/cmdline.d/dracut-neednet.conf
rd.neednet=1
+ cat /proc/self/mountinfo
0 0 0:1 / / rw shared:1 - rootfs rootfs rw
18 0 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
19 0 0:3 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw
20 0 0:5 / /dev rw,nosuid shared:9 - devtmpfs devtmpfs 
rw,size=131896204k,nr_inodes=32974051,mode=755
21 18 0:17 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - 
securityfs securityfs rw
22 20 0:19 / /dev/shm rw,nosuid,nodev shared:10 - tmpfs tmpfs rw
23 20 0:12 / /dev/pts rw,nosuid,noexec,relatime shared:11 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
24 0 0:20 / /run rw,nosuid,nodev shared:12 - tmpfs tmpfs rw,mode=755
25 18 0:21 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs 
ro,mode=755
26 25 0:22 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - 
cgroup cgroup 
rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
27 18 0:23 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore 
pstore rw
28 18 0:24 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:7 
- efivarfs efivarfs rw
29 25 0:25 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:13 - 
cgroup cgroup rw,blkio
30 25 0:26 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:14 - 
cgroup cgroup rw,freezer
31 25 0:27 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:15 - cgroup cgroup rw,cpuacct,cpu
32 25 0:28 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,net_prio,net_cls
33 25 0:29 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup rw,devices
34 25 0:30 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:18 - cgroup cgroup rw,perf_event
35 25 0:31 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,hugetlb
36 25 0:32 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,memory
37 25 0:33 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,cpuset
38 25 0:34 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:22 - 
cgroup cgroup rw,pids
39 0 0:35 / /var/lib/nfs/rpc_pipefs rw,relatime shared:23 - rpc_pipefs 

[ovirt-users] oVirt Node 4.1 at www.ovirt.org/node/ is 404

[clam2718]

I am trying to download Node 4.1 from https://www.ovirt.org/node but am 
receiving a 404 error.  Is there an alternative link to try for the latest 
stable release?

Thanks,
Charles
___
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/XHR755UBG3O5TMGZES2PWSQZ4BOS6XGH/

[ovirt-users] Ovirt node 4.2.1.1 patch/upgrade?

[Jakov Sosic]

Hi guys,

how do you upgrade ovirt nodes? I can't figure out the best practice 
from documentation.


If I try `Check for upgrades` from oVirt Hosted engine interface, 
nothing happens.


If I run `yum update` on an ovirt node, I get offered the following:


```
Installing:
 ovirt-node-ng-image-update  noarch 
 4.2.3.1-1.el7ovirt-4.2 
 643 M
 replacing  ovirt-node-ng-image-update-placeholder.noarch 
4.2.1.1-1.el7.centos


```

I can access all the CentOS packages if I run `yum update 
--enablerepos=base,updates,extras`.



So, what is the proper way to do it?


Thanks,

Jakov
___
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/YEDECJWLDQ4VLTDP6DB3WNYHG2RETPIO/

[ovirt-users] Ovirt Node NG (4.2.3.1-0.20180530) Boot fail ISCSI using ibft after installation

[Ralf Schenk]

Hello,

I successfully installed Ovirt Node NG from ISO to an ISCSI target
attached via first network interface by using following extensions to
the grub cmdline:

"rd.iscsi.ibft=1 ip=ibft ip=eno2:dhcp"

I want to use the server as diskless ovirt-node-ng Server.

After successful install the system reboots and starts up but it fails
later in dracut even having detected correctly the disk and all the LV's.

I think "iscsistart" is run multiple times even after already being
logged in to the ISCSI-Target and that fails finally like that:

*[  147.644872] localhost dracut-initqueue[1075]: iscsistart: initiator
reported error (15 - session exists)*
[  147.645588] localhost dracut-initqueue[1075]: iscsistart: Logging
into iqn.2018-01.de.databay.office:storage01.epycdphv02-disk1
172.16.1.3:3260,1
[  147.651027] localhost dracut-initqueue[1075]: Warning: 'iscsistart -b
' failed with return code 0
[  147.807510] localhost systemd[1]: Starting Login iSCSI Target...
[  147.809293] localhost iscsistart[6716]: iscsistart: TargetName not
set. Exiting iscsistart
[  147.813625] localhost systemd[1]: iscsistart_iscsi.service: main
process exited, code=exited, status=7/NOTRUNNING
[  147.824897] localhost systemd[1]: Failed to start Login iSCSI Target.
[  147.825050] localhost systemd[1]: Unit iscsistart_iscsi.service
entered failed state.
[  147.825185] localhost systemd[1]: iscsistart_iscsi.service failed.

After a long timeout dracut drops to a shell.
I attach my shortended and cleaned rdsosreport.txt. Can someone help me
find a workaround ?

Bye


-- 


*Ralf Schenk*
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail *r...@databay.de* 
    
*Databay AG*
Jens-Otto-Krag-Straße 11
D-52146 Würselen
*www.databay.de* 

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
Philipp Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen


+ cat /lib/dracut/dracut-033-535.el7
dracut-033-535.el7
+ cat /proc/cmdline
BOOT_IMAGE=/ovirt-node-ng-4.2.3.1-0.20180530.0+1/vmlinuz-3.10.0-862.3.2.el7.x86_64
 root=/dev/onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 ro crashkernel=auto 
bootdev=ibft0 ip=ibft ip=eno2:dhcp netroot=iscsi rd.iscsi.ibft=1 
rd.iscsi.firmware=1 rd.auto rd.lvm.lv=onn/var_log rd.lvm.lv=onn/tmp 
rd.lvm.lv=onn/var_log_audit rd.lvm.lv=onn/swap 
rd.lvm.lv=onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 rd.lvm.lv=onn/home 
plymouth.enable=0 rd.lvm.lv=onn/ovirt-node-ng-4.2.3.1-0.20180530.0+1 
img.bootid=ovirt-node-ng-4.2.3.1-0.20180530.0+1
+ '[' -f /etc/cmdline ']'
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/40-ibft.conf ']'
+ echo /etc/cmdline.d/40-ibft.conf
/etc/cmdline.d/40-ibft.conf
+ cat /etc/cmdline.d/40-ibft.conf
ip=172.16.1.121:::255.255.255.0::ibft0:none
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/45-ifname.conf ']'
+ echo /etc/cmdline.d/45-ifname.conf
/etc/cmdline.d/45-ifname.conf
+ cat /etc/cmdline.d/45-ifname.conf
ifname=ibft0:0c:c4:7a:fa:23:92
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/dracut-neednet.conf ']'
+ echo /etc/cmdline.d/dracut-neednet.conf
/etc/cmdline.d/dracut-neednet.conf
+ cat /etc/cmdline.d/dracut-neednet.conf
rd.neednet=1
+ cat /proc/self/mountinfo
0 0 0:1 / / rw shared:1 - rootfs rootfs rw
18 0 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
19 0 0:3 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw
20 0 0:5 / /dev rw,nosuid shared:9 - devtmpfs devtmpfs 
rw,size=131896204k,nr_inodes=32974051,mode=755
21 18 0:17 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - 
securityfs securityfs rw
22 20 0:19 / /dev/shm rw,nosuid,nodev shared:10 - tmpfs tmpfs rw
23 20 0:12 / /dev/pts rw,nosuid,noexec,relatime shared:11 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
24 0 0:20 / /run rw,nosuid,nodev shared:12 - tmpfs tmpfs rw,mode=755
25 18 0:21 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs 
ro,mode=755
26 25 0:22 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - 
cgroup cgroup 
rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
27 18 0:23 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore 
pstore rw
28 18 0:24 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:7 
- efivarfs efivarfs rw
29 25 0:25 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:13 - 
cgroup cgroup rw,blkio
30 25 0:26 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:14 - 
cgroup cgroup rw,freezer
31 25 0:27 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:15 - cgroup cgroup rw,cpuacct,cpu
32 25 0:28 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,net_prio,net_cls
33 25 0:29 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup 

[ovirt-users] ovirt-node: freshly installed node: network interfaces not visible

[etienne . charlier]

Hello,

I'm deploying a test cluster to get used to the ovirt product.
My ovirt ( 4.2.2) engine is deployed in a vmware virtual machine.

I'm busy deploying 5 hosts using the ovirt-node iso.

I have issue with the additional physical network interface ( used for vm 
trafic and iSCSI)

In ovirt manager I can't see the physical network interfaces. It's thus not 
possible to assign logical network to physical interfaces and my hosts stays in 
"non operational" status.

How should  I configure the additional interfaces in the  ovirt-node installer 
to have them recognized ?

I somehow managed to configure one host and I can see a comment line in 
/etc/sysconfig/network-script/ifcfg-... saying vdsm has acquired the 
interface
No Such line in the ifcfg-* file in non operational hosts

Any idea ?
Etienne

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

[ovirt-users] oVirt Node on CentOS 7.5 and AMD EPYC Support

[Tobias Scheinert]

Hi,

I am currently building a new virtualization cluster with oVirt, using 
AMD EPYC processors (AMD EPYC 7351P). At the moment I'm running oVirt 
Node Version 4.2.3 @ CentOS 7.4.1708.


We have the situation that the processor type is recognized as "AMD 
Opteron G3". With this type of instruction set the VMs are not able to 
do AES in hardware, this results in poor performance in our case.


I found some information that tells me that this problem should be 
solved with CentOS 7.5


--> 

My actual questions:

- Are there any further information about the AMD EPYC support?
- Any information about an update of the oVirt node to CentOS 7.5?


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

Re: [ovirt-users] oVirt Node Resize tool for local storage

[Christopher Cox]

On 03/28/2018 01:37 AM, Pavol Brilla wrote:

Hi

AFAIK ext4 is not supporting online shrinking of filesystem,
to shrink storage you would need to unmount filesystem,
thus it is not possible to do with VM online.


Correct.  Just saying it's not possible at all with XFS, be that online or 
offline.

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

Re: [ovirt-users] oVirt Node Resize tool for local storage

[Pavol Brilla]

Hi

AFAIK ext4 is not supporting online shrinking of filesystem,
to shrink storage you would need to unmount filesystem,
thus it is not possible to do with VM online.

On Wed, Mar 28, 2018 at 2:30 AM, Matt Simonsen  wrote:

> Hello,
>
> We have a development box with local storage, running ovirt Node 4.1
>
> It appears that using the admin interface on port 9090 I can resize a live
> partition to a smaller size.
>
> Our storage is a seperate LVM partition, ext4 formated.
>
> My question is, both theoretically and practically, if anyone has feedback
> on:
>
>
> #1: Does this work (ie- will it shrink the filesystem then shrink the LV)?
>
> #2: May we do this with VMs running?
>
>
> Thanks
>
> Matt
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 

PAVOL BRILLA

RHV QUALITY ENGINEER, CLOUD

Red Hat Czech Republic, Brno 

TRIED. TESTED. TRUSTED. 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt Node Resize tool for local storage

[Matt Simonsen]

Hello,

We have a development box with local storage, running ovirt Node 4.1

It appears that using the admin interface on port 9090 I can resize a 
live partition to a smaller size.


Our storage is a seperate LVM partition, ext4 formated.

My question is, both theoretically and practically, if anyone has 
feedback on:



#1: Does this work (ie- will it shrink the filesystem then shrink the LV)?

#2: May we do this with VMs running?


Thanks

Matt

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

[ovirt-users] ovirt node pxe and thinpool errror in status

[Gianluca Cecchi]

Hello,
I'm experimenting to install ovirt ng node 4.2 via pxe and it seems all
went ok.
Only problem I have is that opening terminal session I get this traceback
that seems related to thinpool

Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in
_run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/site-packages/nodectl/__main__.py", line
42, in 
CliApplication()
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line
200, in CliApplication
return cmdmap.command(args)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line
118, in command
return self.commands[command](**kwargs)
  File "/usr/lib/python2.7/site-packages/nodectl/__init__.py", line
101, in motd
Motd(Status(Health(self.imgbased).status(),
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py",
line 358, in status
status.results.append(group().run())
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py",
line 385, in check_thin
pool = self.app.imgbase._thinpool()
  File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line
120, in _thinpool
return LVM.Thinpool.from_tag(self.thinpool_tag)
  File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 191,
in from_tag
assert len(lvs) == 1
AssertionError
Admin Console: https://192.168.122.196:9090/


[root@localhost ~]#

Current disk layout is

[root@localhost ~]# fdisk -l /dev/vda

Disk /dev/vda: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000a3595

   Device Boot  Start End  Blocks   Id  System
/dev/vda1   *2048 2099199 1048576   83  Linux
/dev/vda2 2099200   10485759951379200   8e  Linux LVM

[root@localhost ~]# pvs
  PV VG Fmt  Attr PSize   PFree
  /dev/vda2  centos lvm2 a--  <49.00g 9.80g

[root@localhost ~]# vgs
  VG #PV #LV #SN Attr   VSize   VFree
  centos   1   3   0 wz--n- <49.00g 9.80g

[root@localhost ~]# lvs
  LV VG Attr   LSize   Pool   Origin Data%  Meta%  Move Log
Cpy%Sync Convert
  pool00 centos twi-aotz-- <34.16g   10.28
9.18
  root   centos Vwi-aotz-- <34.16g pool00
10.28
  swap   centos -wi-ao
5.00g
[root@localhost ~]#

Any hint?

I installed from 4.2 iso and then applied the
ovirt-node-ng-image-update-4.2.1.1-1.el7.centos.noarch yum update
The problem remains

At the moment it is not linked with any engine, also installed.
I can go to the Admin Console web page and I see, clicking inside
"Virtualization" left tab, that on the right dashboard I have a yellow
triangle to the right of the "Health" word...
But I don't exactly understand the source of the warning...

Thanks for any hint related,

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

Re: [ovirt-users] ovirt Node 4.2.1 on 2 node : problem with ha broker and HE storage

[Simone Tiraboschi]

On Mon, Mar 5, 2018 at 10:56 PM, Nicolas Vaye 
wrote:

> Hello,
>
>
> I'd installed oVirt Node 4.2.1 on two host, i'd deployed HE on the first,
> via a storage NFS.
> The administration portal seem to be OK but i can't see the HE VM, the
> portal indicate there is one VM, but impossible to get it into the list of
> the VM.
> I can't see the storage that host the HE-VM too.
> Where is the problem ?
>

Did you deployed with the vintage --noansible flow?
In that case you explicitly have to add another SD before the auto import
process can be started.


>
> I'd added the second host into the cluster and i haven't the option to
> deploy the HE into it during the "add Host" operation.
> After added the second node, i can put into maintenance mode and then
> reinstall with the option DEPLOY for HE but the result is :
> "Cannot edit Host. You are using an unmanaged hosted engine VM. Please add
> the first storage domain in order to start the hosted engine import
> process."
>
>
>
> The logs for the first node indicate this error (very often, every ~
> 30sec) below :
>
> ovirt-ha-broker 
> ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update
> ERROR Failed to read state. Traceback (most recent call last): File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/status_broker.py",
> line 88, in run self._storage_broker.get_raw_stats() File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
> line 162, in get_raw_stats .format(str(e))) RequestError: failed to read
> metadata: [Errno 2] No such file or directory: '/var/run/vdsm/storage/
> e906ea1d-a5ee-4ea9-838c-bcb4a8b866ff/f1ccdaaf-4682-4d68-9c27-751d54f101a6/
> 13fb32ec-0463-45d4-925a-b557c1dc803f'
>
> With this problem, i can't move the HE vm on the second host. so there is
> no HA.
>
> Thanks.
>
>
> Nicolas VAYE
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt Node 4.2.1 on 2 node : problem with ha broker and HE storage

[Nicolas Vaye]

Hello,


I'd installed oVirt Node 4.2.1 on two host, i'd deployed HE on the first, via a 
storage NFS.
The administration portal seem to be OK but i can't see the HE VM, the portal 
indicate there is one VM, but impossible to get it into the list of the VM.
I can't see the storage that host the HE-VM too.
Where is the problem ?

I'd added the second host into the cluster and i haven't the option to deploy 
the HE into it during the "add Host" operation.
After added the second node, i can put into maintenance mode and then reinstall 
with the option DEPLOY for HE but the result is :
"Cannot edit Host. You are using an unmanaged hosted engine VM. Please add the 
first storage domain in order to start the hosted engine import process."



The logs for the first node indicate this error (very often, every ~ 30sec) 
below :

ovirt-ha-broker ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update 
ERROR Failed to read state. Traceback (most recent call last): File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/status_broker.py",
 line 88, in run self._storage_broker.get_raw_stats() File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
 line 162, in get_raw_stats .format(str(e))) RequestError: failed to read 
metadata: [Errno 2] No such file or directory: 
'/var/run/vdsm/storage/e906ea1d-a5ee-4ea9-838c-bcb4a8b866ff/f1ccdaaf-4682-4d68-9c27-751d54f101a6/13fb32ec-0463-45d4-925a-b557c1dc803f'

With this problem, i can't move the HE vm on the second host. so there is no HA.

Thanks.


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

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Luca 'remix_tj' Lorenzetto]

Hi Yuval,

interesting, thank you!

Luca

On Thu, Jan 18, 2018 at 1:26 PM, Yuval Turgeman  wrote:
> Hi Luca,
>
> We updated the FAQ [1] with a small script to help upgrade between major
> releases.
>
> [1] https://www.ovirt.org/node/faq/
>
> On Mon, Jan 15, 2018 at 10:21 AM, Luca 'remix_tj' Lorenzetto
>  wrote:
>>
>>
>>
>> On Thu, Jan 11, 2018 at 2:31 PM, Ryan Barry  wrote:
>>>
>>> Note that, in the case of Node, the ovirt-release RPM should not be
>>> installed. Mostly because it automatically enables a number of per-package
>>> updates (such as vdsm) instead of installing a single image.
>>>
>>> Trimming the repo files so they look like what is shipped in Node
>>> (IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm, which is
>>> the only package needing an update.
>>>
>>
>> Hi,
>>
>> i'm upgrading ovirt-node too. I found out that installing ovirt-release
>> file and running yum upgrade wants to upgrade everything. Instead, if i make
>>
>> yum upgrade ovirt-node-ng-image*
>>
>> I get the new image downloaded.
>>
>> So which is the right procedure to upgrade a node? Maybe providing a
>> single command alternative to yum (let's say ovirt-node-upgrade) for
>> upgrading would be better and avoid issues when doing such operation.
>>
>> Luca
>>
>> --
>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
>> calcoli che potrebbero essere affidati a chiunque se si usassero delle
>> macchine"
>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>>
>> "Internet è la più grande biblioteca del mondo.
>> Ma il problema è che i libri sono tutti sparsi sul pavimento"
>> John Allen Paulos, Matematico (1945-vivente)
>>
>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net ,
>> 
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>



-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Yuval Turgeman]

Hi Luca,

We updated the FAQ [1] with a small script to help upgrade between major
releases.

[1] https://www.ovirt.org/node/faq/

On Mon, Jan 15, 2018 at 10:21 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

>
>
> On Thu, Jan 11, 2018 at 2:31 PM, Ryan Barry  wrote:
>
>> Note that, in the case of Node, the ovirt-release RPM should not be
>> installed. Mostly because it automatically enables a number of per-package
>> updates (such as vdsm) instead of installing a single image.
>>
>> Trimming the repo files so they look like what is shipped in Node
>> (IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm,
>> which is the only package needing an update.
>>
>>
> Hi,
>
> i'm upgrading ovirt-node too. I found out that installing ovirt-release
> file and running yum upgrade wants to upgrade everything. Instead, if i
> make
>
> yum upgrade ovirt-node-ng-image*
>
> I get the new image downloaded.
>
> So which is the right procedure to upgrade a node? Maybe providing a
> single command alternative to yum (let's say ovirt-node-upgrade) for
> upgrading would be better and avoid issues when doing such operation.
>
> Luca
>
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Ryan Barry]

Next-gen node (since 4.0) doesn't have any strong notion of "persistence",
unlike previous versions of oVirt Node.

My guess would be that /exports was not moved across to the new system.

The update process for Node is essentially:

* create a new lv
* unpack the squashfs in the new RPM and put it on the LV
* Go through /var, /etc, and /root to see if any files were modified/added,
and copy those to the new layer
* Add a new bootloader entry
* Re-install any persistent RPMs

I would guess that /exports as not on its own partition, so it didn't carry
across. Mounting the LV for the old image somewhere (/tmp/...) will make
them visible again,


On Tue, Dec 19, 2017 at 9:26 AM, Kasturi Narra  wrote:

> Hello Matt,
>
>All the partitions will be persisted when gluster is installed on
> the ovirt node since gluster recommends user not to create bricks in root
> directory. If the gluster bricks are created in root partition then once
> the update of the node is done, you will not be able to see any of the
> bricks.
>
> Hope this helps !!!
>
> Thanks
> kasturi.
>
> On Tue, Dec 19, 2017 at 4:28 AM, Matt Simonsen  wrote:
>
>> On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
>>
>> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis 
>> wrote:
>>
>>> have you gotten an image update yet?
>>>
>>> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  wrote:
>>>
 Hello all,

 I read at https://www.ovirt.org/develop/projects/node/troubleshooting/
 that "Changes made from the command line are done at your own risk. Making
 changes has the potential to leave your system in an unusable state." It
 seems clear that RPMs should not be installed.

>>>
>> That document mainly refers to vintage node.
>> In Next Generation Node now we have rpm persistence; please check
>> https://www.ovirt.org/develop/release-management/features/no
>> de/node-next-persistence/
>>
>>
>>
>>
>> I'm sure glad we tested!
>>
>> On one Node image we had images locally stored in /exports and shared out
>> via NFS. After an upgrade & reboot, images are gone.
>>
>> If we "Convert to local storage" will the data persist?  I am planning to
>> test, but want to be sure how this is designed.
>>
>> I assume during a Gluster installation something is also updated in oVirt
>> Node to allow for the Gluster partition to persist?
>>
>> At this point I'm thinking I should manually install via CentOS7 to
>> ensure folders and partitions are persistent. Is there any downside to
>> installing over CentOS7?
>>
>> Thanks
>> Matt
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

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

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Ryan Barry]

Note that, in the case of Node, the ovirt-release RPM should not be
installed. Mostly because it automatically enables a number of per-package
updates (such as vdsm) instead of installing a single image.

Trimming the repo files so they look like what is shipped in Node
(IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm, which
is the only package needing an update.

On Fri, Dec 29, 2017 at 4:45 AM, Ed Stout  wrote:

> On 29 December 2017 at 09:11, Michal Skrivanek
>  wrote:
> >
> >
> >> On 29 Dec 2017, at 10:03, Ed Stout  wrote:
> >>
> >> On 29 December 2017 at 08:42, Michal Skrivanek
> >>  wrote:
> >>>
> >>>
>  On 29 Dec 2017, at 09:34, Ed Stout  wrote:
> 
>  Good Morning,
> 
>  Perhaps someone could clarify for me, please - to update oVirt Nodes
>  from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
>  release file, then yum update?
> >>>
> >>> Hi,
> >>> yes, that should be the right one
> >>>
>  Or, do I have to start with the 4.2
>  ISO then update from there?
> 
>  When I try the former it fails with dependency issues for the nodes, I
>  did however manage to update a self hosted appliance engine to 4.2.  I
>  had a read through the mailing list archive and couldn't find similar
>  issues, so perhaps I'm doing something wrong.
> 
>  --> Processing Dependency: lshw for package:
> vdsm-4.20.9.3-1.el7.centos.x86_64
>  --> Finished Dependency Resolution
>  Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
> (ovirt-4.2)
>   Requires: libvirt-daemon-config-network
>  Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
> (ovirt-4.2)
>   Requires: virt-install
>  Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
>  (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
>  Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
>   Requires: lshw
>  Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
>  (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles —nodigest
> >>>
> >>> can you list all your enabled repos? Seems you're missing the base
> CentOS
> >>>
> >>> Thanks,
> >>> michal
> >>
> >> Sure, thanks for the reply - I have 3 nodes, installed from the 4.1.x
> >> oVirt node ISOs, no custom packages/repos, that see the same (minus
> >> the 4.2 added here).
> >>
> >> [root@onode3 ~]# yum repolist enabled
> >> Loaded plugins: fastestmirror, imgbased-persist
> >> Loading mirror speeds from cached hostfile
> >> * ovirt-4.1-epel: mirrors.ukfast.co.uk
> >> * ovirt-4.2: ftp.snt.utwente.nl
> >> * ovirt-4.2-epel: mirrors.ukfast.co.uk
> >> repo id
> >> repo name
> >>
> >>   status
> >> centos-opstools-release/x86_64
> >> CentOS-7 - OpsTools - release
> >>
> >>  421
> >> centos-sclo-rh-release/x86_64
> >> CentOS-7 - SCLo rh
> >>
> >>6,534
> >> ovirt-4.1/7
> >> Latest oVirt 4.1 Release
> >>
> >>2,101
> >> ovirt-4.1-centos-gluster38/x86_64
> >> CentOS-7 - Gluster 3.8
> >>
> >>   31
> >> ovirt-4.1-epel/x86_64
> >> Extra Packages for Enterprise Linux 7
> >> - x86_64
> >>   12,184
> >> ovirt-4.1-patternfly1-noarch-epel/x86_64
> >> Copr repo for patternfly1 owned by
> >> patternfly
> >>   2
> >> ovirt-4.2/7
> >> Latest oVirt 4.2 Release
> >>
> >>  179
> >> ovirt-4.2-centos-gluster312/x86_64
> >> CentOS-7 - Gluster 3.12
> >>
> >>   93
> >> ovirt-4.2-centos-opstools/x86_64
> >> CentOS-7 - OpsTools - release
> >>
> >>  421
> >> ovirt-4.2-centos-ovirt42/x86_64
> >> CentOS-7 - oVirt 4.2
> >>
> >>  201
> >> ovirt-4.2-centos-qemu-ev/x86_64
> >> CentOS-7 - QEMU EV
> >>
> >>   39
> >> ovirt-4.2-epel/x86_64
> >> Extra Packages for Enterprise Linux 7
> >> - x86_64
> >>   12,184
> >> ovirt-4.2-virtio-win-latest
> >> virtio-win builds roughly matching
> >> what will be shipped in upcoming RHEL
> >>  35
> >> ovirt-centos-ovirt41/x86_64
> >> 

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Ed Stout]

On 29 December 2017 at 09:11, Michal Skrivanek
 wrote:
>
>
>> On 29 Dec 2017, at 10:03, Ed Stout  wrote:
>>
>> On 29 December 2017 at 08:42, Michal Skrivanek
>>  wrote:
>>>
>>>
 On 29 Dec 2017, at 09:34, Ed Stout  wrote:

 Good Morning,

 Perhaps someone could clarify for me, please - to update oVirt Nodes
 from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
 release file, then yum update?
>>>
>>> Hi,
>>> yes, that should be the right one
>>>
 Or, do I have to start with the 4.2
 ISO then update from there?

 When I try the former it fails with dependency issues for the nodes, I
 did however manage to update a self hosted appliance engine to 4.2.  I
 had a read through the mailing list archive and couldn't find similar
 issues, so perhaps I'm doing something wrong.

 --> Processing Dependency: lshw for package: 
 vdsm-4.20.9.3-1.el7.centos.x86_64
 --> Finished Dependency Resolution
 Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
 (ovirt-4.2)
  Requires: libvirt-daemon-config-network
 Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
 (ovirt-4.2)
  Requires: virt-install
 Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
 (ovirt-4.2-centos-gluster312)
  Requires: python-prettytable
 Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
  Requires: lshw
 Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
 (ovirt-4.2-centos-gluster312)
  Requires: python-prettytable
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles —nodigest
>>>
>>> can you list all your enabled repos? Seems you're missing the base CentOS
>>>
>>> Thanks,
>>> michal
>>
>> Sure, thanks for the reply - I have 3 nodes, installed from the 4.1.x
>> oVirt node ISOs, no custom packages/repos, that see the same (minus
>> the 4.2 added here).
>>
>> [root@onode3 ~]# yum repolist enabled
>> Loaded plugins: fastestmirror, imgbased-persist
>> Loading mirror speeds from cached hostfile
>> * ovirt-4.1-epel: mirrors.ukfast.co.uk
>> * ovirt-4.2: ftp.snt.utwente.nl
>> * ovirt-4.2-epel: mirrors.ukfast.co.uk
>> repo id
>> repo name
>>
>>   status
>> centos-opstools-release/x86_64
>> CentOS-7 - OpsTools - release
>>
>>  421
>> centos-sclo-rh-release/x86_64
>> CentOS-7 - SCLo rh
>>
>>6,534
>> ovirt-4.1/7
>> Latest oVirt 4.1 Release
>>
>>2,101
>> ovirt-4.1-centos-gluster38/x86_64
>> CentOS-7 - Gluster 3.8
>>
>>   31
>> ovirt-4.1-epel/x86_64
>> Extra Packages for Enterprise Linux 7
>> - x86_64
>>   12,184
>> ovirt-4.1-patternfly1-noarch-epel/x86_64
>> Copr repo for patternfly1 owned by
>> patternfly
>>   2
>> ovirt-4.2/7
>> Latest oVirt 4.2 Release
>>
>>  179
>> ovirt-4.2-centos-gluster312/x86_64
>> CentOS-7 - Gluster 3.12
>>
>>   93
>> ovirt-4.2-centos-opstools/x86_64
>> CentOS-7 - OpsTools - release
>>
>>  421
>> ovirt-4.2-centos-ovirt42/x86_64
>> CentOS-7 - oVirt 4.2
>>
>>  201
>> ovirt-4.2-centos-qemu-ev/x86_64
>> CentOS-7 - QEMU EV
>>
>>   39
>> ovirt-4.2-epel/x86_64
>> Extra Packages for Enterprise Linux 7
>> - x86_64
>>   12,184
>> ovirt-4.2-virtio-win-latest
>> virtio-win builds roughly matching
>> what will be shipped in upcoming RHEL
>>  35
>> ovirt-centos-ovirt41/x86_64
>> CentOS-7 - oVirt 4.1
>>
>>  456
>> sac-gdeploy/x86_64
>> Copr repo for gdeploy owned by sac
>>
>>4
>> virtio-win-stable
>> virtio-win builds roughly matching
>> what was shipped in latest RHEL
>>   5
>> repolist: 34,890
>
> I think it’s missing the base centos repos, maybe that is a bug in the 
> initial deployment.
> Try to add base CentOS 4.2 repo from CentOS site, all the above are supposed 
> to be “on top” of that one
>
> Thanks,
> michal

Much obliged - the CentOS-Base.repo is there, 

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Michal Skrivanek]

> On 29 Dec 2017, at 10:03, Ed Stout  wrote:
> 
> On 29 December 2017 at 08:42, Michal Skrivanek
>  wrote:
>> 
>> 
>>> On 29 Dec 2017, at 09:34, Ed Stout  wrote:
>>> 
>>> Good Morning,
>>> 
>>> Perhaps someone could clarify for me, please - to update oVirt Nodes
>>> from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
>>> release file, then yum update?
>> 
>> Hi,
>> yes, that should be the right one
>> 
>>> Or, do I have to start with the 4.2
>>> ISO then update from there?
>>> 
>>> When I try the former it fails with dependency issues for the nodes, I
>>> did however manage to update a self hosted appliance engine to 4.2.  I
>>> had a read through the mailing list archive and couldn't find similar
>>> issues, so perhaps I'm doing something wrong.
>>> 
>>> --> Processing Dependency: lshw for package: 
>>> vdsm-4.20.9.3-1.el7.centos.x86_64
>>> --> Finished Dependency Resolution
>>> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
>>> (ovirt-4.2)
>>>  Requires: libvirt-daemon-config-network
>>> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
>>> (ovirt-4.2)
>>>  Requires: virt-install
>>> Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
>>> (ovirt-4.2-centos-gluster312)
>>>  Requires: python-prettytable
>>> Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
>>>  Requires: lshw
>>> Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
>>> (ovirt-4.2-centos-gluster312)
>>>  Requires: python-prettytable
>>> You could try using --skip-broken to work around the problem
>>> You could try running: rpm -Va --nofiles —nodigest
>> 
>> can you list all your enabled repos? Seems you're missing the base CentOS
>> 
>> Thanks,
>> michal
> 
> Sure, thanks for the reply - I have 3 nodes, installed from the 4.1.x
> oVirt node ISOs, no custom packages/repos, that see the same (minus
> the 4.2 added here).
> 
> [root@onode3 ~]# yum repolist enabled
> Loaded plugins: fastestmirror, imgbased-persist
> Loading mirror speeds from cached hostfile
> * ovirt-4.1-epel: mirrors.ukfast.co.uk
> * ovirt-4.2: ftp.snt.utwente.nl
> * ovirt-4.2-epel: mirrors.ukfast.co.uk
> repo id
> repo name
> 
>   status
> centos-opstools-release/x86_64
> CentOS-7 - OpsTools - release
> 
>  421
> centos-sclo-rh-release/x86_64
> CentOS-7 - SCLo rh
> 
>6,534
> ovirt-4.1/7
> Latest oVirt 4.1 Release
> 
>2,101
> ovirt-4.1-centos-gluster38/x86_64
> CentOS-7 - Gluster 3.8
> 
>   31
> ovirt-4.1-epel/x86_64
> Extra Packages for Enterprise Linux 7
> - x86_64
>   12,184
> ovirt-4.1-patternfly1-noarch-epel/x86_64
> Copr repo for patternfly1 owned by
> patternfly
>   2
> ovirt-4.2/7
> Latest oVirt 4.2 Release
> 
>  179
> ovirt-4.2-centos-gluster312/x86_64
> CentOS-7 - Gluster 3.12
> 
>   93
> ovirt-4.2-centos-opstools/x86_64
> CentOS-7 - OpsTools - release
> 
>  421
> ovirt-4.2-centos-ovirt42/x86_64
> CentOS-7 - oVirt 4.2
> 
>  201
> ovirt-4.2-centos-qemu-ev/x86_64
> CentOS-7 - QEMU EV
> 
>   39
> ovirt-4.2-epel/x86_64
> Extra Packages for Enterprise Linux 7
> - x86_64
>   12,184
> ovirt-4.2-virtio-win-latest
> virtio-win builds roughly matching
> what will be shipped in upcoming RHEL
>  35
> ovirt-centos-ovirt41/x86_64
> CentOS-7 - oVirt 4.1
> 
>  456
> sac-gdeploy/x86_64
> Copr repo for gdeploy owned by sac
> 
>4
> virtio-win-stable
> virtio-win builds roughly matching
> what was shipped in latest RHEL
>   5
> repolist: 34,890

I think it’s missing the base centos repos, maybe that is a bug in the initial 
deployment. 
Try to add base CentOS 4.2 repo from CentOS site, all the above are supposed to 
be “on top” of that one

Thanks,
michal

> 
>> 
>>> 
>>> 
>>> OS Version:
>>> RHEL - 7 - 4.1708.el7.centos
>>> OS Description:
>>> oVirt Node 4.1.8
>>> Kernel Version:
>>> 3.10.0 - 693.11.1.el7.x86_64
>>> KVM Version:
>>> 2.9.0 - 16.el7_4.8.1
>>> LIBVIRT Version:
>>> 

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Ed Stout]

On 29 December 2017 at 08:42, Michal Skrivanek
 wrote:
>
>
>> On 29 Dec 2017, at 09:34, Ed Stout  wrote:
>>
>> Good Morning,
>>
>> Perhaps someone could clarify for me, please - to update oVirt Nodes
>> from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
>> release file, then yum update?
>
> Hi,
> yes, that should be the right one
>
>>  Or, do I have to start with the 4.2
>> ISO then update from there?
>>
>> When I try the former it fails with dependency issues for the nodes, I
>> did however manage to update a self hosted appliance engine to 4.2.  I
>> had a read through the mailing list archive and couldn't find similar
>> issues, so perhaps I'm doing something wrong.
>>
>> --> Processing Dependency: lshw for package: 
>> vdsm-4.20.9.3-1.el7.centos.x86_64
>> --> Finished Dependency Resolution
>> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
>> (ovirt-4.2)
>>   Requires: libvirt-daemon-config-network
>> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
>> (ovirt-4.2)
>>   Requires: virt-install
>> Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
>> (ovirt-4.2-centos-gluster312)
>>   Requires: python-prettytable
>> Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
>>   Requires: lshw
>> Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
>> (ovirt-4.2-centos-gluster312)
>>   Requires: python-prettytable
>> You could try using --skip-broken to work around the problem
>> You could try running: rpm -Va --nofiles —nodigest
>
> can you list all your enabled repos? Seems you're missing the base CentOS
>
> Thanks,
> michal

Sure, thanks for the reply - I have 3 nodes, installed from the 4.1.x
oVirt node ISOs, no custom packages/repos, that see the same (minus
the 4.2 added here).

[root@onode3 ~]# yum repolist enabled
Loaded plugins: fastestmirror, imgbased-persist
Loading mirror speeds from cached hostfile
 * ovirt-4.1-epel: mirrors.ukfast.co.uk
 * ovirt-4.2: ftp.snt.utwente.nl
 * ovirt-4.2-epel: mirrors.ukfast.co.uk
repo id
 repo name

   status
centos-opstools-release/x86_64
 CentOS-7 - OpsTools - release

  421
centos-sclo-rh-release/x86_64
 CentOS-7 - SCLo rh

6,534
ovirt-4.1/7
 Latest oVirt 4.1 Release

2,101
ovirt-4.1-centos-gluster38/x86_64
 CentOS-7 - Gluster 3.8

   31
ovirt-4.1-epel/x86_64
 Extra Packages for Enterprise Linux 7
- x86_64
   12,184
ovirt-4.1-patternfly1-noarch-epel/x86_64
 Copr repo for patternfly1 owned by
patternfly
   2
ovirt-4.2/7
 Latest oVirt 4.2 Release

  179
ovirt-4.2-centos-gluster312/x86_64
 CentOS-7 - Gluster 3.12

   93
ovirt-4.2-centos-opstools/x86_64
 CentOS-7 - OpsTools - release

  421
ovirt-4.2-centos-ovirt42/x86_64
 CentOS-7 - oVirt 4.2

  201
ovirt-4.2-centos-qemu-ev/x86_64
 CentOS-7 - QEMU EV

   39
ovirt-4.2-epel/x86_64
 Extra Packages for Enterprise Linux 7
- x86_64
   12,184
ovirt-4.2-virtio-win-latest
 virtio-win builds roughly matching
what will be shipped in upcoming RHEL
  35
ovirt-centos-ovirt41/x86_64
 CentOS-7 - oVirt 4.1

  456
sac-gdeploy/x86_64
 Copr repo for gdeploy owned by sac

4
virtio-win-stable
 virtio-win builds roughly matching
what was shipped in latest RHEL
   5
repolist: 34,890

>
>>
>>
>> OS Version:
>> RHEL - 7 - 4.1708.el7.centos
>> OS Description:
>> oVirt Node 4.1.8
>> Kernel Version:
>> 3.10.0 - 693.11.1.el7.x86_64
>> KVM Version:
>> 2.9.0 - 16.el7_4.8.1
>> LIBVIRT Version:
>> libvirt-3.2.0-14.el7_4.5
>> VDSM Version:
>> vdsm-4.19.43-1.el7.centos
>> SPICE Version:
>> 0.12.8 - 2.el7.1
>> GlusterFS Version:
>> glusterfs-3.8.15-2.el7
>> CEPH Version:
>> librbd1-0.94.5-2.el7
>>
>> Cheers,
>>
>> Ed
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Michal Skrivanek]

> On 29 Dec 2017, at 09:34, Ed Stout  wrote:
> 
> Good Morning,
> 
> Perhaps someone could clarify for me, please - to update oVirt Nodes
> from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
> release file, then yum update?

Hi,
yes, that should be the right one

>  Or, do I have to start with the 4.2
> ISO then update from there?
> 
> When I try the former it fails with dependency issues for the nodes, I
> did however manage to update a self hosted appliance engine to 4.2.  I
> had a read through the mailing list archive and couldn't find similar
> issues, so perhaps I'm doing something wrong.
> 
> --> Processing Dependency: lshw for package: vdsm-4.20.9.3-1.el7.centos.x86_64
> --> Finished Dependency Resolution
> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
> (ovirt-4.2)
>   Requires: libvirt-daemon-config-network
> Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch 
> (ovirt-4.2)
>   Requires: virt-install
> Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
> Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
>   Requires: lshw
> Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
> (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles —nodigest

can you list all your enabled repos? Seems you're missing the base CentOS

Thanks,
michal

> 
> 
> OS Version:
> RHEL - 7 - 4.1708.el7.centos
> OS Description:
> oVirt Node 4.1.8
> Kernel Version:
> 3.10.0 - 693.11.1.el7.x86_64
> KVM Version:
> 2.9.0 - 16.el7_4.8.1
> LIBVIRT Version:
> libvirt-3.2.0-14.el7_4.5
> VDSM Version:
> vdsm-4.19.43-1.el7.centos
> SPICE Version:
> 0.12.8 - 2.el7.1
> GlusterFS Version:
> glusterfs-3.8.15-2.el7
> CEPH Version:
> librbd1-0.94.5-2.el7
> 
> Cheers,
> 
> Ed
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

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

[ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Ed Stout]

Good Morning,

Perhaps someone could clarify for me, please - to update oVirt Nodes
from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
release file, then yum update?  Or, do I have to start with the 4.2
ISO then update from there?

When I try the former it fails with dependency issues for the nodes, I
did however manage to update a self hosted appliance engine to 4.2.  I
had a read through the mailing list archive and couldn't find similar
issues, so perhaps I'm doing something wrong.

--> Processing Dependency: lshw for package: vdsm-4.20.9.3-1.el7.centos.x86_64
--> Finished Dependency Resolution
Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch (ovirt-4.2)
   Requires: libvirt-daemon-config-network
Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch (ovirt-4.2)
   Requires: virt-install
Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   Requires: python-prettytable
Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
   Requires: lshw
Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   Requires: python-prettytable
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


OS Version:
RHEL - 7 - 4.1708.el7.centos
OS Description:
oVirt Node 4.1.8
Kernel Version:
3.10.0 - 693.11.1.el7.x86_64
KVM Version:
2.9.0 - 16.el7_4.8.1
LIBVIRT Version:
libvirt-3.2.0-14.el7_4.5
VDSM Version:
vdsm-4.19.43-1.el7.centos
SPICE Version:
0.12.8 - 2.el7.1
GlusterFS Version:
glusterfs-3.8.15-2.el7
CEPH Version:
librbd1-0.94.5-2.el7

Cheers,

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

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Kasturi Narra]

Hello Matt,

   All the partitions will be persisted when gluster is installed on
the ovirt node since gluster recommends user not to create bricks in root
directory. If the gluster bricks are created in root partition then once
the update of the node is done, you will not be able to see any of the
bricks.

Hope this helps !!!

Thanks
kasturi.

On Tue, Dec 19, 2017 at 4:28 AM, Matt Simonsen  wrote:

> On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
>
> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis  wrote:
>
>> have you gotten an image update yet?
>>
>> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  wrote:
>>
>>> Hello all,
>>>
>>> I read at https://www.ovirt.org/develop/projects/node/troubleshooting/
>>> that "Changes made from the command line are done at your own risk. Making
>>> changes has the potential to leave your system in an unusable state." It
>>> seems clear that RPMs should not be installed.
>>>
>>
> That document mainly refers to vintage node.
> In Next Generation Node now we have rpm persistence; please check
> https://www.ovirt.org/develop/release-management/features/
> node/node-next-persistence/
>
>
>
>
> I'm sure glad we tested!
>
> On one Node image we had images locally stored in /exports and shared out
> via NFS. After an upgrade & reboot, images are gone.
>
> If we "Convert to local storage" will the data persist?  I am planning to
> test, but want to be sure how this is designed.
>
> I assume during a Gluster installation something is also updated in oVirt
> Node to allow for the Gluster partition to persist?
>
> At this point I'm thinking I should manually install via CentOS7 to ensure
> folders and partitions are persistent. Is there any downside to installing
> over CentOS7?
>
> Thanks
> Matt
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Matt Simonsen]

On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis > wrote:


have you gotten an image update yet?

On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen > wrote:

Hello all,

I read at
https://www.ovirt.org/develop/projects/node/troubleshooting/

that "Changes made from the command line are done at your own
risk. Making changes has the potential to leave your system in
an unusable state." It seems clear that RPMs should not be
installed.


That document mainly refers to vintage node.
In Next Generation Node now we have rpm persistence; please check
https://www.ovirt.org/develop/release-management/features/node/node-next-persistence/





I'm sure glad we tested!

On one Node image we had images locally stored in /exports and shared 
out via NFS. After an upgrade & reboot, images are gone.


If we "Convert to local storage" will the data persist?  I am planning 
to test, but want to be sure how this is designed.


I assume during a Gluster installation something is also updated in 
oVirt Node to allow for the Gluster partition to persist?


At this point I'm thinking I should manually install via CentOS7 to 
ensure folders and partitions are persistent. Is there any downside to 
installing over CentOS7?


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

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Simone Tiraboschi]

On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis  wrote:

> have you gotten an image update yet?
>
> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  wrote:
>
>> Hello all,
>>
>> I read at https://www.ovirt.org/develop/projects/node/troubleshooting/
>> that "Changes made from the command line are done at your own risk. Making
>> changes has the potential to leave your system in an unusable state." It
>> seems clear that RPMs should not be installed.
>>
>
That document mainly refers to vintage node.
In Next Generation Node now we have rpm persistence; please check
https://www.ovirt.org/develop/release-management/features/node/node-next-persistence/



>
>> Is this accurate for https://www.ovirt.org/node/ ?
>>
>> We have added smartctl and hpacucli in order to do disk and RAID
>> monitoring. So far our node servers have retained changes across reboots,
>> which is the primary reason I'm wondering if perhaps this applies to an
>> older version of oVirt Node.
>>
>> If what we have been doing is not supported, what is the suggested method
>> to do do hardware monitoring (in particular disks)?
>>
>> Thanks
>> Matt
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Donny Davis]

have you gotten an image update yet?

On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  wrote:

> Hello all,
>
> I read at https://www.ovirt.org/develop/projects/node/troubleshooting/
> that "Changes made from the command line are done at your own risk. Making
> changes has the potential to leave your system in an unusable state." It
> seems clear that RPMs should not be installed.
>
> Is this accurate for https://www.ovirt.org/node/ ?
>
> We have added smartctl and hpacucli in order to do disk and RAID
> monitoring. So far our node servers have retained changes across reboots,
> which is the primary reason I'm wondering if perhaps this applies to an
> older version of oVirt Node.
>
> If what we have been doing is not supported, what is the suggested method
> to do do hardware monitoring (in particular disks)?
>
> Thanks
> Matt
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Matt Simonsen]

Hello all,

I read at https://www.ovirt.org/develop/projects/node/troubleshooting/ 
that "Changes made from the command line are done at your own risk. 
Making changes has the potential to leave your system in an unusable 
state." It seems clear that RPMs should not be installed.


Is this accurate for https://www.ovirt.org/node/ ?

We have added smartctl and hpacucli in order to do disk and RAID 
monitoring. So far our node servers have retained changes across 
reboots, which is the primary reason I'm wondering if perhaps this 
applies to an older version of oVirt Node.


If what we have been doing is not supported, what is the suggested 
method to do do hardware monitoring (in particular disks)?


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

Re: [ovirt-users] oVirt Node ng upgrade failed

[Yuval Turgeman]

Great, thanks! we already have a patch in POST ready here:
https://gerrit.ovirt.org/#/c/84957/

Thanks,
Yuval

On Dec 1, 2017 15:04, "Kilian Ries" <m...@kilian-ries.de> wrote:

Bug is opened:


https://bugzilla.redhat.com/show_bug.cgi?id=1519784



Ok, i try to fix my host next week. Thanks for your help ;)
--
*Von:* Yuval Turgeman <yuv...@redhat.com>
*Gesendet:* Donnerstag, 30. November 2017 09:22:39

*An:* Kilian Ries
*Cc:* users
*Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed

Looks like it, yes - we try to add setfiles_t to permissive, because we
assume selinux is on, and if it's disabled, semanage fails with the error
you mentioned.  Can you open a bug on this ?

If you would like to fix the system, you will need to clean the unused LVs,
remove the relevant boot entries from grub (if they exist) and
/boot/ovirt-node-ng-4.1.7-0.20171108.0+1 (if it exists), then reinstall the
rpm.


On Thu, Nov 30, 2017 at 10:16 AM, Kilian Ries <m...@kilian-ries.de> wrote:

> Yes, selinux is disabled via /etc/selinux/config; Is that the problem? :/
> --
> *Von:* Yuval Turgeman <yuv...@redhat.com>
> *Gesendet:* Donnerstag, 30. November 2017 09:13:34
> *An:* Kilian Ries
> *Cc:* users
>
> *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed
>
> Kilian, did you disable selinux by any chance ? (selinux=0 on boot) ?
>
> On Thu, Nov 30, 2017 at 9:57 AM, Yuval Turgeman <yuv...@redhat.com> wrote:
>
>> Looks like selinux is broken on your machine for some reason, can you
>> share /etc/selinux ?
>>
>> Thanks,
>> Yuval.
>>
>> On Tue, Nov 28, 2017 at 6:31 PM, Kilian Ries <m...@kilian-ries.de> wrote:
>>
>>> @Yuval Turgeman
>>>
>>>
>>> ###
>>>
>>>
>>> [17:27:10][root@vm5:~]$semanage permissive -a setfiles_t
>>>
>>> SELinux:  Could not downgrade policy file 
>>> /etc/selinux/targeted/policy/policy.30,
>>> searching for an older version.
>>>
>>> SELinux:  Could not open policy file <= 
>>> /etc/selinux/targeted/policy/policy.30:
>>>  No such file or directory
>>>
>>> /sbin/load_policy:  Can't load policy:  No such file or directory
>>>
>>> libsemanage.semanage_reload_policy: load_policy returned error code 2.
>>> (No such file or directory).
>>>
>>> SELinux:  Could not downgrade policy file 
>>> /etc/selinux/targeted/policy/policy.30,
>>> searching for an older version.
>>>
>>> SELinux:  Could not open policy file <= 
>>> /etc/selinux/targeted/policy/policy.30:
>>>  No such file or directory
>>>
>>> /sbin/load_policy:  Can't load policy:  No such file or directory
>>>
>>> libsemanage.semanage_reload_policy: load_policy returned error code 2.
>>> (No such file or directory).
>>>
>>> OSError: No such file or directory
>>>
>>>
>>> ###
>>>
>>>
>>> @Ryan Barry
>>>
>>>
>>> Manual yum upgrade finished without any error but imgbased.log still
>>> shows me the following:
>>>
>>>
>>> ###
>>>
>>>
>>> 2017-11-28 17:25:28,372 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Creating /home as
>>> {'attach': True, 'size': '1G'}
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling binary: (['vgs',
>>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'stderr':
>>> }
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling: (['vgs',
>>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'close_fds':
>>> True, 'stderr': }
>>>
>>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Returned: onn/home
>>>
>>>   onn/tmp
>>>
>>>   onn/var_log
>>>
>>>   onn/var_log_audit
>>>
>>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', '/etc'],) {}
>>>
>>> 2017-11-28 17:25:28,534 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> '/etc'],) {'close_fds': True, 'stderr': -2}
>>>
>>> 2017-11-28 17:25:28,539 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', u'/tmp/mnt.tuHU8'],) {}
>>>
>>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2}
>>>
>>> 2017-11-28

Re: [ovirt-users] oVirt Node ng upgrade failed

[Kilian Ries]

Bug is opened:


https://bugzilla.redhat.com/show_bug.cgi?id=1519784



Ok, i try to fix my host next week. Thanks for your help ;)


Von: Yuval Turgeman <yuv...@redhat.com>
Gesendet: Donnerstag, 30. November 2017 09:22:39
An: Kilian Ries
Cc: users
Betreff: Re: [ovirt-users] oVirt Node ng upgrade failed

Looks like it, yes - we try to add setfiles_t to permissive, because we assume 
selinux is on, and if it's disabled, semanage fails with the error you 
mentioned.  Can you open a bug on this ?

If you would like to fix the system, you will need to clean the unused LVs, 
remove the relevant boot entries from grub (if they exist) and 
/boot/ovirt-node-ng-4.1.7-0.20171108.0+1 (if it exists), then reinstall the rpm.


On Thu, Nov 30, 2017 at 10:16 AM, Kilian Ries 
<m...@kilian-ries.de<mailto:m...@kilian-ries.de>> wrote:

Yes, selinux is disabled via /etc/selinux/config; Is that the problem? :/


Von: Yuval Turgeman <yuv...@redhat.com<mailto:yuv...@redhat.com>>
Gesendet: Donnerstag, 30. November 2017 09:13:34
An: Kilian Ries
Cc: users

Betreff: Re: [ovirt-users] oVirt Node ng upgrade failed

Kilian, did you disable selinux by any chance ? (selinux=0 on boot) ?

On Thu, Nov 30, 2017 at 9:57 AM, Yuval Turgeman 
<yuv...@redhat.com<mailto:yuv...@redhat.com>> wrote:
Looks like selinux is broken on your machine for some reason, can you share 
/etc/selinux ?

Thanks,
Yuval.

On Tue, Nov 28, 2017 at 6:31 PM, Kilian Ries 
<m...@kilian-ries.de<mailto:m...@kilian-ries.de>> wrote:

@Yuval Turgeman


###


[17:27:10][root@vm5:~]$semanage permissive -a setfiles_t

SELinux:  Could not downgrade policy file 
/etc/selinux/targeted/policy/policy.30, searching for an older version.

SELinux:  Could not open policy file <= /etc/selinux/targeted/policy/policy.30: 
 No such file or directory

/sbin/load_policy:  Can't load policy:  No such file or directory

libsemanage.semanage_reload_policy: load_policy returned error code 2. (No such 
file or directory).

SELinux:  Could not downgrade policy file 
/etc/selinux/targeted/policy/policy.30, searching for an older version.

SELinux:  Could not open policy file <= /etc/selinux/targeted/policy/policy.30: 
 No such file or directory

/sbin/load_policy:  Can't load policy:  No such file or directory

libsemanage.semanage_reload_policy: load_policy returned error code 2. (No such 
file or directory).

OSError: No such file or directory


###


@Ryan Barry


Manual yum upgrade finished without any error but imgbased.log still shows me 
the following:


###


2017-11-28 17:25:28,372 [DEBUG] (MainThread) Returned:

2017-11-28 17:25:28,434 [DEBUG] (MainThread) Creating /home as {'attach': True, 
'size': '1G'}

2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling binary: (['vgs', 
'--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'stderr': }

2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling: (['vgs', '--noheadings', 
'@imgbased:volume', '-o', 'lv_full_name'],) {'close_fds': True, 'stderr': }

2017-11-28 17:25:28,533 [DEBUG] (MainThread) Returned: onn/home

  onn/tmp

  onn/var_log

  onn/var_log_audit

2017-11-28 17:25:28,533 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
'/etc'],) {}

2017-11-28 17:25:28,534 [DEBUG] (MainThread) Calling: (['umount', '-l', 
'/etc'],) {'close_fds': True, 'stderr': -2}

2017-11-28 17:25:28,539 [DEBUG] (MainThread) Returned:

2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.tuHU8'],) {}

2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2}

2017-11-28 17:25:28,635 [DEBUG] (MainThread) Returned:

2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling binary: (['rmdir', 
u'/tmp/mnt.tuHU8'],) {}

2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling: (['rmdir', 
u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2}

2017-11-28 17:25:28,640 [DEBUG] (MainThread) Returned:

2017-11-28 17:25:28,641 [ERROR] (MainThread) Failed to migrate etc

Traceback (most recent call last):

  File 
"/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 109, in on_new_layer

check_nist_layout(imgbase, new_lv)

  File 
"/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 179, in check_nist_layout

v.create(t, paths[t]["size"], paths[t]["attach"])

  File 
"/tmp/tmp.ipxGZrbQEi/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create

"Path is already a volume: %s" % where

AssertionError: Path is already a volume: /home

2017-11-28 17:25:28,642 [DEBUG] (MainThread) Calling binary: (['umount', '-l', 
u'/tmp/mnt.bEW2k'],) {}

2017-11-28 17:25:28,642 [DEBUG] (MainThread) Calling: (['umount', '-l', 
u'/tmp/mnt.bEW2k'],) {'close_fds': True, 'stderr': -2}

2017-11-28 17:2

Re: [ovirt-users] ovirt-node-ng-update

[Nathanaël Blanchet]

thanx for replying


Le 30/11/2017 à 10:19, Yuval Turgeman a écrit :

2 more questions -

1.  Which ovirt repos are enabled on your node ?
centos-opstools-release/x86_64   CentOS-7 - OpsTools - 
release  263
ovirt-4.1/7  Latest oVirt 4.1 
Release 1 997
ovirt-4.1-centos-gluster38/x86_64    CentOS-7 - Gluster 
3.8  30
ovirt-4.1-epel/x86_64    Extra Packages for Enterprise 
Linux 7 - x86_64  12 131
ovirt-4.1-patternfly1-noarch-epel/x86_64 Copr repo for patternfly1 owned 
by patternfly    2
ovirt-centos-ovirt41/x86_64  CentOS-7 - oVirt 
4.1   405
sac-gdeploy/x86_64   Copr repo for gdeploy owned by 
sac   4
virtio-win-stable    virtio-win builds roughly 
matching what was shipped in



2.  Can you share the output from `rpm -qa | grep ovirt-node-ng` ?

[root@mascota ~]# rpm -qva | grep ovirt-node
ovirt-node-ng-nodectl-4.1.5-0.20171107.0.el7.noarch
ovirt-node-ng-image-update-placeholder-4.1.7-1.el7.centos.noarch



Thanks,
Yuval.

On Thu, Nov 30, 2017 at 11:02 AM, Nathanaël Blanchet > wrote:




Le 30/11/2017 à 08:58, Yuval Turgeman a écrit :

Hi,

Which version are you using ?

4.1.7



Thanks,
Yuval.

On Wed, Nov 29, 2017 at 4:17 PM, Nathanaël Blanchet
> wrote:

Hi all,

I didn't find any explicit howto about upgrade of ovirt-node,
but I may mistake...

However, here is what I guess: after installing a fresh
ovirt-node-ng  iso, the engine check upgrade finds an
available update "ovirt-node-ng-image-update"

But, the available update is the same as the current one.  If
I choose installing it succeeds, but after rebooting,
ovirt-node-ng-image-update is not still part of installed
rpms so that engine tells me an update of ovirt-node is still
available.

-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr 

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





-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr   



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





--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

Re: [ovirt-users] ovirt-node-ng-update

[Yuval Turgeman]

2 more questions -

1.  Which ovirt repos are enabled on your node ?
2.  Can you share the output from `rpm -qa | grep ovirt-node-ng` ?

Thanks,
Yuval.

On Thu, Nov 30, 2017 at 11:02 AM, Nathanaël Blanchet 
wrote:

>
>
> Le 30/11/2017 à 08:58, Yuval Turgeman a écrit :
>
> Hi,
>
> Which version are you using ?
>
> 4.1.7
>
>
> Thanks,
> Yuval.
>
> On Wed, Nov 29, 2017 at 4:17 PM, Nathanaël Blanchet 
> wrote:
>
>> Hi all,
>>
>> I didn't find any explicit howto about upgrade of ovirt-node, but I may
>> mistake...
>>
>> However, here is what I guess: after installing a fresh ovirt-node-ng
>> iso, the engine check upgrade finds an available update
>> "ovirt-node-ng-image-update"
>>
>> But, the available update is the same as the current one.  If I choose
>> installing it succeeds, but after rebooting, ovirt-node-ng-image-update is
>> not still part of installed rpms so that engine tells me an update of
>> ovirt-node is still available.
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques
>> 227 avenue Professeur-Jean-Louis-Viala
>> 
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt-node-ng-update

[Nathanaël Blanchet]

Le 30/11/2017 à 08:58, Yuval Turgeman a écrit :

Hi,

Which version are you using ?

4.1.7


Thanks,
Yuval.

On Wed, Nov 29, 2017 at 4:17 PM, Nathanaël Blanchet > wrote:


Hi all,

I didn't find any explicit howto about upgrade of ovirt-node, but
I may mistake...

However, here is what I guess: after installing a fresh
ovirt-node-ng  iso, the engine check upgrade finds an available
update "ovirt-node-ng-image-update"

But, the available update is the same as the current one. If I
choose installing it succeeds, but after rebooting,
ovirt-node-ng-image-update is not still part of installed rpms so
that engine tells me an update of ovirt-node is still available.

-- 
Nathanaël Blanchet


Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala


34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr 

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





--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

Re: [ovirt-users] oVirt Node ng upgrade failed

[Yuval Turgeman]

Looks like it, yes - we try to add setfiles_t to permissive, because we
assume selinux is on, and if it's disabled, semanage fails with the error
you mentioned.  Can you open a bug on this ?

If you would like to fix the system, you will need to clean the unused LVs,
remove the relevant boot entries from grub (if they exist) and
/boot/ovirt-node-ng-4.1.7-0.20171108.0+1 (if it exists), then reinstall the
rpm.


On Thu, Nov 30, 2017 at 10:16 AM, Kilian Ries <m...@kilian-ries.de> wrote:

> Yes, selinux is disabled via /etc/selinux/config; Is that the problem? :/
> --
> *Von:* Yuval Turgeman <yuv...@redhat.com>
> *Gesendet:* Donnerstag, 30. November 2017 09:13:34
> *An:* Kilian Ries
> *Cc:* users
>
> *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed
>
> Kilian, did you disable selinux by any chance ? (selinux=0 on boot) ?
>
> On Thu, Nov 30, 2017 at 9:57 AM, Yuval Turgeman <yuv...@redhat.com> wrote:
>
>> Looks like selinux is broken on your machine for some reason, can you
>> share /etc/selinux ?
>>
>> Thanks,
>> Yuval.
>>
>> On Tue, Nov 28, 2017 at 6:31 PM, Kilian Ries <m...@kilian-ries.de> wrote:
>>
>>> @Yuval Turgeman
>>>
>>>
>>> ###
>>>
>>>
>>> [17:27:10][root@vm5:~]$semanage permissive -a setfiles_t
>>>
>>> SELinux:  Could not downgrade policy file 
>>> /etc/selinux/targeted/policy/policy.30,
>>> searching for an older version.
>>>
>>> SELinux:  Could not open policy file <= 
>>> /etc/selinux/targeted/policy/policy.30:
>>>  No such file or directory
>>>
>>> /sbin/load_policy:  Can't load policy:  No such file or directory
>>>
>>> libsemanage.semanage_reload_policy: load_policy returned error code 2.
>>> (No such file or directory).
>>>
>>> SELinux:  Could not downgrade policy file 
>>> /etc/selinux/targeted/policy/policy.30,
>>> searching for an older version.
>>>
>>> SELinux:  Could not open policy file <= 
>>> /etc/selinux/targeted/policy/policy.30:
>>>  No such file or directory
>>>
>>> /sbin/load_policy:  Can't load policy:  No such file or directory
>>>
>>> libsemanage.semanage_reload_policy: load_policy returned error code 2.
>>> (No such file or directory).
>>>
>>> OSError: No such file or directory
>>>
>>>
>>> ###
>>>
>>>
>>> @Ryan Barry
>>>
>>>
>>> Manual yum upgrade finished without any error but imgbased.log still
>>> shows me the following:
>>>
>>>
>>> ###
>>>
>>>
>>> 2017-11-28 17:25:28,372 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Creating /home as
>>> {'attach': True, 'size': '1G'}
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling binary: (['vgs',
>>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'stderr':
>>> }
>>>
>>> 2017-11-28 17:25:28,434 [DEBUG] (MainThread) Calling: (['vgs',
>>> '--noheadings', '@imgbased:volume', '-o', 'lv_full_name'],) {'close_fds':
>>> True, 'stderr': }
>>>
>>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Returned: onn/home
>>>
>>>   onn/tmp
>>>
>>>   onn/var_log
>>>
>>>   onn/var_log_audit
>>>
>>> 2017-11-28 17:25:28,533 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', '/etc'],) {}
>>>
>>> 2017-11-28 17:25:28,534 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> '/etc'],) {'close_fds': True, 'stderr': -2}
>>>
>>> 2017-11-28 17:25:28,539 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling binary: (['umount',
>>> '-l', u'/tmp/mnt.tuHU8'],) {}
>>>
>>> 2017-11-28 17:25:28,540 [DEBUG] (MainThread) Calling: (['umount', '-l',
>>> u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2}
>>>
>>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling binary: (['rmdir',
>>> u'/tmp/mnt.tuHU8'],) {}
>>>
>>> 2017-11-28 17:25:28,635 [DEBUG] (MainThread) Calling: (['rmdir',
>>> u'/tmp/mnt.tuHU8'],) {'close_fds': True, 'stderr': -2}
>>>
>>> 2017-11-28 17:25:28,640 [DEBUG] (MainThread) Returned:
>>>
>>> 2017-11-28 17:25:28,641 [ERROR] (MainThread) Failed to migrate etc
>>>
>>> Traceback (m