Hosted-engine inaccessible
by Tau Makgaile
Hi,
I am currently experiencing a problem with my Hosted-engine. Hosted-engine
disconnected after increasing / partition. The increase went well but after
some time the hosted-enigine VM disconnected and has since been giving
alerts such as* re-initializingFSM*.
Though VMs underneth are running, Hosted-engine --vm-status:
*"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail"*
There is no backup to restore at the moment. I am looking for a way to
bring it up without redeploying the hosted engine.
Thanks in advance for your help.
Kind regards,
Tau
5 years, 4 months
oVirt 3.6: Node went into Error state while migrations happening
by Christopher Cox
On the node in question, the metadata isn't coming across (state) wise.
It shows VMs being in an unknown state (some are up and some are down),
some show as migrating and there are 9 forever hung migrating tasks. We
tried to bring up some of the down VMs that had a state of Down, but
that ended up getting them the state of "Wait for Lauch", though those
VMs are actually started.
Right now, my plan is attempt a restart of vdsmd on the node in
question. Just trying to get the node to a working state again. There
a total of 9 nodes in our cluster, but we can't manage any VMs on the
affected node right now.
Is there a way in 3.6 to cancel the hung tasks? I'm worried that if
vdsmd is restarted on the node, the tasks might be "attempted"... I
really need them to be forgotten if possible.
Ideally want all "Unknown" to return to either an "up" or "down" state
(depending if the VM is up or down) and for "Wait for Launch" for those,
to go to "up" and for all the "Migrating" to go to "up" or "down" (I
think only one is actually down).
I'm concerned that any attempt manually maniplate the state in the ovirt
mgmt head db will be moot because the node will be queried for state and
that state will be taken and override anything I attempt to do.
Thoughts??
5 years, 4 months
port_security in external networks-API
by ada per
Hello everyone,
I have the following python script that creates an external network, but now after updating ovirt a new option "network port security" exists that is set as enabled by default.
How can i disable the network port security?
thanks!! :)
networks_service = connection.system_service().networks_service()
# Use the "add" method to create new VM logical network in data center
network = networks_service.add(
network=types.Network(
name= ext_net_name,
description='Network for testing API',
data_center=types.DataCenter(
name='Default'
),
usages=[types.NetworkUsage.VM],
external_provider=types.OpenStackNetworkProvider(
id=provider.id
)
),
5 years, 5 months
hosted engine installation / multipath / iscsi
by Michael Frank
Hi,
since several days i try to install the hosted engine initially to an iscsi multipath device without success.
Some information on the environment:
- Version 4.3.3
- using two 10gbe interfaces as single bond for the ovirtmgmt interface
- using two 10gbe storage interfaces on each hypervisor for iscsi storage
-- each storage interface is configured without any bonding, etc
-- each storage interface lives in a separate vlan were also the iscsi Portals/target are available, the iscsi portals have 4x10ge interfaces each, (2 in vlan xx and 2 interfaces in vlan yy )
-- so; each storage interface is connected to two iscsi Portals via 4 interfaces
The documentation here is for me unclear:
https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_En...
>Note: To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. There is also a Multipath >Helper tool that generates a script to install and configure multipath with different options.
This indicates for me that it should be possbile to install the HE directly on the /dev/mapper/mpath device which is availibale when I have prepared the host accordingly before installing the HE (log in to multiple iscsi targets, create proper multipath,conf, etc) - right ?
I login to the two iscsi portals and get in sum 8 pathes, 4 from each interface and iscsi target.
Basically I have then the mpath device on the hypervisor available and i can mount the mpath device and put data on it.
In the cockpit interface the mount can also be activated and is recognized correctly.
multipathd -ll and lsblk looks good. Everything seems to be fine.
But when I run the "hosted-engine" --deploy, the last option while running the assistant is to enter the iscsi data.
So, basically i just want to define my mpath device - when entering the data (ip, port)for the iscsi Portal I can see the 4 pathes of the single hosted Engine target,
and when i choose the path where the "lun" is finally available it fails. I think in general this option is not that what i want to have
here for using the multipath device.
I' m lost - what is the usual way to install the HE on a multipath device ?
Do i have to change the configuration of the storage interfaces or the iscsi network design?
Did I missed something obvious ?
Can I put in my multipath data into the answerfile to get rid of the last step of the assistant ?
Can I use the related ansible role for specify the Mpath device which is available when activating the multipath service ?
Is it not possible in general ?? :
https://bugzilla.redhat.com/show_bug.cgi?id=1193961
Sorry in advance for the long mail .... 1!^^
br,
michael
Sent from a mobile device
5 years, 5 months
bond for vm interfaces
by Edoardo Mazza
Hello everyone,
I need to create a bond for vm interfaces but I don't kown what is the best
solution, you can help me?
Thanks
Edoardo
5 years, 5 months
Data Center Compatibility version
by Rick A
So I updated our environment a bit ago during a scheduled down time from 4.2 to 4.3. Everything went smoothly, but it looks like I forgot to update the Data Center Compatibility (See alert message below). My question is, can I just change the Data Center compatibility to 4.3 while the environment is running without causing issues, or do i need to shutdown all my VM's and put the hosts into maintenance mode? The compatibility version for everything else is already set to 4.3.
Thanks
Alert Message:
"Data Center compatibility version is 4.2, which is lower than latest engine version 4.3. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup"
5 years, 5 months
[ANN] oVirt 4.3.5 Fifth Release Candidate is now available for testing
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.3.5 Fifth Release Candidate for testing, as of July 11th, 2019.
While testing this release candidate please consider deeper testing on
gluster upgrade since with this release we are switching from Gluster 5 to
Gluster 6.
This update is a release candidate of the fifth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in
production.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.
Notes:
- oVirt Appliance is laready available
- oVirt Node is already available[2]
Additional Resources:
* Read more about the oVirt 4.3.5 release highlights:
http://www.ovirt.org/release/4.3.5/
* 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.3.5/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
5 years, 5 months
ovirt-release43-pre-4.3.6-0.1 - python-ioprocess RPM version
by Maton, Brett
Hi,
I just ran yum update on my test cluster and ran into the following issue:
I did notice that the python2-ioprocess is currently installed from the
ovirt-4.2 repo...
Any suggestions?
Thanks,
Brett
Repo RPM: ovirt-release43-pre-4.3.6-0.1.rc1.el7.noarch
yum -y upgrade
...
Error: Package: vdsm-python-4.30.25-1.el7.noarch (ovirt-4.3-pre)
Requires: python-ioprocess >= 1.2.1
Installed: python2-ioprocess-1.1.2-1.el7.x86_64 (@ovirt-4.2)
python-ioprocess = 1.1.2
Available: python-ioprocess-0.16.1-1.el7.noarch
(ovirt-4.3-centos-ovirt43)
python-ioprocess = 0.16.1-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
5 years, 5 months
4.3.5 update error
by Kapetanakis Giannis
Hi,
Trying today engine-setup to update from 4.3.3 -> 4.3.5 I got this error:
[ ERROR ] Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment
In log file I see:
2019-07-31 10:43:00,375+0300 DEBUG otopi.context context._executeMethod:145 method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod
method['method']()
File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _validation
self._checkSnapshotCompatibilityVersion()
File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 212, in _checkSnapshotCompatibilityVersion
'v': snapshot_cl,
UnboundLocalError: local variable 'snapshot_cl' referenced before assignment
2019-07-31 10:43:00,381+0300 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment
Any hints?
thanks
Giannis
5 years, 5 months
