invalid spf record for ovirt.org
by Jorick Astrego
Hi,
During routine maintenance on our mailserver I noticed the following in
the log:
[22/Jul/2020 14:33:33] Error when parsing SPF TXT record for domain:
ovirt.org, envelope-from=users-bounces(a)ovirt.org, message: Invalid
character found near "" in "66.187.233.88"
A check on MXtoolbox also gives an invalid systax error:
v=spf1 a:mail.ovirt.org a:gerrit.ovirt.org 66.187.233.88 ~all
Prefix Type Value PrefixDesc Description Error
v spf1
The SPF record version
+ a mail.ovirt.org Pass Match if IP has a DNS 'A' record in
given domain.
+ a gerrit.ovirt.org Pass Match if IP has a DNS 'A' record in
given domain.
+ 66.187.233.88
Pass Unknown Unknown mechanisms are not allowed
~ all
SoftFail Always matches. It goes at the end of your record.
Test Result
<https://mxtoolbox.com/problem/spf/spf-syntax-check?page=prob_spf&action=s...>
SPF Syntax Check Invalid syntax found
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
----------------
Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
----------------
3 years, 9 months
4.4: Export as OVA always fails w/ ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER
by Gilboa Davara
Hello all,
I'm trying to export a VM as OVA on a single host hyper converged (over
NFS) 4.4 installation, and no matter which host destination directory I
set, with or without a trailing '/' (per bugzilla #1780424) the export
fails with the same error (see below).
Export into the export domain (on the same path) seems to work just fine.
$ cat engine.log | grep WARN
2020-07-22 14:51:50,155+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-158) [57c42e68-155e-4bd2-9dcd-bbc620088943] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory
/exports/export/kvm/gilboa-vmh-probe64
2020-07-22 14:52:22,077+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-160) [092fb51d-1054-43ff-9161-69943c677512] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory /tmp
2020-07-22 14:52:45,504+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-160) [3c8ae09d-3d03-42dd-b2e8-b488052674f1] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory /tmp
2020-07-22 15:04:32,393+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-159) [7a234e5a-be10-4b0b-b817-eb682b846272] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory /exports/export/kvm/temp
2020-07-22 15:10:07,066+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-159) [75e66244-aa1c-4d40-8f9f-578cccb265a3] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory
/exports/export/kvm/temp/gilboa-vmh-probe64.ova
2020-07-22 15:10:46,480+03 WARN
[org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default
task-163) [6a6e9cae-b111-4f89-8dad-41a45a57c96c] Validation of action
'ExportVmToOva' failed for user gilboa@internal-authz. Reasons:
VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName
gilboa-home-srv.localdomain,$directory /exports/export/kvm/temp
- Gilboa
3 years, 9 months
Hosted Engine | Ovirt 4.4.1
by Vijay Sachdeva
Hi Everyone
Getting below error when deploying hosted engine:
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "msg": "The Python 2 yum module is needed for this module. If you require Python 3 support use the `dnf` Ansible module instead."}
Any idea how to fix it?
Thanks
Vijay Sachdeva
3 years, 9 months
Reinstall failed on 4.4.1.1 with custom kernel settings
by mmarino＠extraordy.com
Hi, after the upgrade from 4.4.1 to 4.4.1.1, it seems that I cannot reinstall adding custom kernel settings. In my case, I'm trying to add "ixgbe.allow_unsupported_sfp=1" to cmdline but reinstall process fails without showing any relevant error in /var/log/vdsm/vdsm.log. I did the same test on version 4.4.1 and it works without problems. On version 4.4.1 I tried to (1) add a parameter with reinstall, (2) add a second parameter and reinstall, (3) remove all params and reinstall and (4) finally add only one custom param with reinstall. All tests are ok on version 4.4.1 and the problem happens only on version 4.4.1.1.
Please, have you some idea on how to solve the issue? Is this a bug?
Thank you,
Marco
3 years, 9 months
OVA import does not upload disks
by Paolo Airaldi
Hello,
I'm running 4.3.5.4-1.el7. I've exported a VM as OVA and now I'm trying to
import it in another Data Center (it's like a DR Data Center)
Import runs successfully both from GUI and from Ansible, but imported VM
disks are empty and the VM fails to boot.
How can I import disks content too?
Thanks in advance for any help.
Paolo
3 years, 9 months
Re: ovirt 4.4.1.1 hci and problems with ansible 2.9.10 and/or missing python2
by Holger Petrick
Hello Gianluca,
thanks for opening the bug. I have also reported my test scenario below.
(One thing more in my case, the standalone Manager needs to be installed on EL8 and not like documents says on EL7.
With EL7 load is gives an error that Engine for EL7 is not avaiable. Document needs to be updated.)
---
The same error occurs when trying to add a node to a standalone Engine Manager.
Steps to Reproduce:
1. install a standalone Engine Manager on EL8 step by step with this documentation
https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_mana...
2. install a node using ovirt-node-ng-installer-4.4.1-2020071311.el8.iso
3. try to add the node inside the Engine Manager
Log output:
2020-07-21 10:14:17 CEST - included: /usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml for ovirtnode1.example.net
2020-07-21 10:14:17 CEST - included: /usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/vdsmid.yml for ovirtnode1.example.net
2020-07-21 10:14:17 CEST - included: /usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/pki.yml for ovirtnode1.example.net
2020-07-21 10:14:17 CEST - included: /usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/restart_services.yml for ovirtnode1.example.net
2020-07-21 10:14:17 CEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-host package] *********************
2020-07-21 10:14:17 CEST -
2020-07-21 10:14:17 CEST - fatal: [ovirtnode1.example.net]: FAILED! => {"changed": false, "module_stderr": "/bin/sh: /usr/bin/python2: No such file or directory\n", "module_stdout": "", "msg": "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error", "rc": 127}
2020-07-21 10:14:17 CEST - {
"status" : "OK",
"msg" : "",
"data" : {
"uuid" : "bfb59a41-6672-4115-ba93-1755556b3d11",
"counter" : 61,
"stdout" : "fatal: [ovirtnode1.example.net]: FAILED! => {\"changed\": false, \"module_stderr\": \"/bin/sh: /usr/bin/python2: No such file or directory\\n\", \"module_stdout\": \"\", \"msg\": \"The module failed to execute correctly, you probably need to set the interpreter.\\nSee stdout/stderr for the exact error\", \"rc\": 127}",
"start_line" : 54,
"end_line" : 55,
"runner_ident" : "230c108e-cb2a-11ea-97da-00155d120809",
"event" : "runner_on_failed",
"pid" : 28965,
"created" : "2020-07-21T08:14:16.528490",
"parent_uuid" : "00155d12-0809-c845-9450-0000000001a1",
"event_data" : {
"playbook" : "ovirt-host-deploy.yml",
"playbook_uuid" : "3a66c11c-02f9-492a-937d-21f1386e492d",
"play" : "all",
"play_uuid" : "00155d12-0809-c845-9450-000000000006",
"play_pattern" : "all",
"task" : "Install ovirt-host package",
"task_uuid" : "00155d12-0809-c845-9450-0000000001a1",
"task_action" : "yum",
"task_args" : "",
"task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:2",
"role" : "ovirt-host-deploy-vdsm",
"host" : "ovirtnode1.example.net",
"remote_addr" : "ovirtnode1.example.net",
"res" : {
"module_stdout" : "",
"module_stderr" : "/bin/sh: /usr/bin/python2: No such file or directory\n",
"msg" : "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error",
"rc" : 127,
"_ansible_no_log" : false,
"changed" : false
},
"start" : "2020-07-21T08:14:15.365609",
"end" : "2020-07-21T08:14:16.528185",
"duration" : 1.162576,
"ignore_errors" : null,
"event_loop" : null,a
"uuid" : "bfb59a41-6672-4115-ba93-1755556b3d11"
}
}
3 years, 9 months
ovirt 4.4 installation issues
by Markus Schaufler
Hi all,
in our environment, CentOS7 and RHEL7 for the most part (Ovirt 4.3 and RHV 4.3), we are able to set a proxy directly in /etc/yum.conf (or on the single repo) to momentarily bypass some network restrictions.
The proxy settings looks like this:
proxy=http://our-proxy.domain:8080
proxy_username=user
proxy_password=password
But is also works properly when it is set directly from CLI, and this is the one we use more often:
export http_proxy=http://user:password@our-proxy.domain:8080
export https_proxy=https://user:password@our-proxy.domain:8080
We are having difficulties to set the same proxy on CentOS8 / Ovirt 4.4.x.
There is no way the proxy settings allows us to run "yum update".
Extra Packages for Enterprise Linux 8 - x86_64 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'ovirt-4.4-epel':
- Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=x86_64&infra=... [Received HTTP code 407 from proxy after CONNECT]
Error: Failed to download metadata for repo 'ovirt-4.4-epel': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=x86_64&infra=... [Received HTTP code 407 from proxy after CONNECT]
Can somebody maybe point us to a solution? The above command is extracted by 'yum update' after a clean installation of Ovirt 4.4.1-2020070811 (but the same issue happened on previous versions and Nightly versions too).
Thank you,
Markus
3 years, 9 months
Need Help in setting up oVirt, Looking for some help (From India)
by Dhanasekar Mani
Hello,
We are setting up oVirt and we are having some issues in setting up.
Are there any oVirt members who can assist us from India ?
We are from Bangalore.
Thanks & Regards,
Mani
*i prefer "i did this & i have done this", rather than "i will do it"*
3 years, 9 months
Ovirt Hosted Engine Setup
by Vijay Sachdeva
Hi All,
I am trying to deploy hosted engine setup, the setup got stuck at below for hours:
Is this is a known bug?
Thanks
Vijay Sachdeva
3 years, 9 months
