How to add hosted-engine deployment in oVIrt 4.2.3 after host has already been added to cluster ?
by Balg, Andreas
Hello everybody,
how am I supposed to add an additional hosted-engine deployment to a
cluster to a host that has already been added - "hosted-engine --
deploy" in the hosts terminal tells me to do it using the webUI ( oVirt
4.2.3 ) but in WebUI I haven't found a way to do so - also in Cockpit
it offers me to "Redeploy" the Hosted-engine setup is that the way to
go? It would really hurt if this would break the whole stuff.
Usually I'd just try that before bothering you guys here - but this
deployment is currently in use so this would really hurt.
Thanks in advance for any help
Cheers
Andreas
--
Andreas Balg
Senior Site Reliability Engineer DevOps
------------------------------------------------------------------
Haufe-umantis AG
Ein Unternehmen der Haufe Gruppe
Unterstrasse 11, CH-9001 St.Gallen
Tel. +41 71 224 01 52, Fax +41 71 224 01 02
E-Mail: andreas.balg(a)haufe.com
5 years, 11 months
VM import and manage custom property missing on new env
by Gianluca Cecchi
Hello,
I have a VM exported in 4.1 and imported in 4.1 into a different env
On original env where I exported I had the VM configured with custom
property hugepages.
On new env where I have imported it, I have not (yet) configured this
custom property.
In "Edit VM" I don't see anything related, so I cannot "diable" it, but if
I try to power on the VM I get:
Error while executing action:
vm1_import:
- Cannot run VM if some of the specified custom properties are not
configured by the system. The keys are: hugepages
Is it possible to choose during import phase if one wants to preserve or
not custom properties in general?
What can I do to workaround if I don't mind to use huge pages on the
imported VM?
Thanks,
Gianluca
5 years, 11 months
Upgrade host to 4.2 - 10gbe connection does not work anymore
by Demeter Tibor
Hi All,
I did successfully upgraded my 4.1 hosted engine and the first node to 4.2.3. Since upgrade, the node's 10Gbe connection does not work. It was the connection between host and storage. That is why, now I can't activate my node.
I have IP and I have all of bonding, and it seems to fine. All other networks and bonds (1gbe) is working fine, I can communicate with other hosts.
I had a mode-1 (active/passive) bonding on that interfaces. I can ping from other nodes, but not from this.
Also, I did a full OS upgrade (yum update) on node.
Somebody could me help?
Thanks in advance,
R
Tibor
5 years, 11 months
Cluster compatibility 4.1 to 4.2 upgrade
by Demeter Tibor
Dear Listmember,
I've just upgrade to my ovirt-hosted-engine from 4.1 to 4.2.3. It was successful, but it saw " Data Center XYZ compatibility version is 4.1, which is lower than latest engine version 4.2. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup."
My first question is that, it need to do BEFORE or AFTER the node upgrades?
I haven't upgrade my nodes yet, because after upgrade the live migration does not work with some VMs. It seems only affected those VMs that's have big (>8GB ) memory. It counting to 99 percent and after a while just stopped.
At this moment I can't stop my affected, productive VMs, so I can't do the upgrade of nodes.
I just wondering, if i do the upgrade to 4.2 , that's maybe repair my the live migration function?
What can I do?
Centos 7.4, NFS storage, 4 nodes, Hyperconverged hosted engine.
Thanks in advance,
Tibor
5 years, 11 months
How to update "quota_cluster_limit" settings of a quota object through REST API?
by Shao-Da Huang
Hi,
I can update the vCPU and memory quota by editing a Quota object of a
datacenter through webadmin portal, but it seems that I cannot update
through REST API...
For example, I have a quota object with a global quota_cluster_limit object:
GET https://192.168.80.168/ovirt-engine/api/datacenters/
5ad4fafe-0253-0015-0215-000000000378/quotas/8a6b3336-
2dfc-4e40-a58e-9bdcb45d228a/quotaclusterlimits/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<quota_cluster_limits> <quota_cluster_limit href="/ovirt-engine/api/
datacenters/5ad4fafe-0253-0015-0215-000000000378/quotas/
8a6b3336-2dfc-4e40-a58e-9bdcb45d228a/quotaclusterlimits/8a6b3336-2dfc-4e40-a58e-9bdcb45d228a"
id="8a6b3336-2dfc-4e40-a58e-9bdcb45d228a"> <memory_limit>16.0</memory_limit>
<memory_usage>0.0</memory_usage> <vcpu_limit>6</vcpu_limit>
<vcpu_usage>0</vcpu_usage> <quota href="/ovirt-engine/api/
datacenters/5ad4fafe-0253-0015-0215-000000000378/quotas/
8a6b3336-2dfc-4e40-a58e-9bdcb45d228a"
id="8a6b3336-2dfc-4e40-a58e-9bdcb45d228a"/>
</quota_cluster_limit> </quota_cluster_limits>
But when I try to do
PUT
https://192.168.80.168/ovirt-engine/api/datacenters/5ad4fafe-0253-0015-0215-
000000000378/quotas/8a6b3336-2dfc-4e40-a58e-9bdcb45d228a/
quotaclusterlimits/8a6b3336-2dfc-4e40-a58e-9bdcb45d228a
with request body like:
<quota_cluster_limit>
<vcpu_limit>8</vcpu_limit>
</quota_cluster_limit>
I got *405 Method Not Allowed.*
Could anyone give me some advices?
5 years, 11 months
Work-Around for Access Problem to resources.ovirt.org and jenkins.ovirt.org
by Anton Marchukov
Hello All.
Please note that ovirt.org got HSTS setting enabled. The way this
change was rolled was not authorised by us. The setting contains
“includeSubDomains” parameter that ask browser to access all resources
inside *.ovirt.org using https://.
The problem is that not all resources on *.ovirt.org are
https-enabled. And this will prevent you from being able to access
http://resources.ovirt.org
http://jenkins.ovirt.org
This setting is cached in your browser and then applied with no
exceptions even if you explicitly specify http:// the browser will
rewrite to https and then connection to above mentioned resources will
fail.
The only immediate work-around for you is to clear the HSTS flag in
your browser, please find the instructions for Firefox and Chrome [1].
Please note that you will get that setting back by visiting ovirt.org
website until we clear it from there.
We are currently working on this setting to be soften or disabled till
all resources are https enabled that is also in progress.
This is only related to access via the web browser. Accessing using
yum or automated scripts should work fine as they usually do not
observe and cache HSTS.
Anton.
[1] https://www.thesslstore.com/blog/clear-hsts-settings-chrome-firefox/
5 years, 11 months
sun.security.validator.ValidatorException after update to 4.2.3
by Jiří Sléžka
This is a cryptographically signed message in MIME format.
--------------ms020800040402030301010200
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Hi,
after upgrade ovirt from 4.2.2 to 4.2.3.5-1.el7.centos I cannot login
into admin portal because
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
I am using custom 3rd party certificate
Any hints how to resolve this issue?
Thanks in advance,
Jiri Slezka
--------------ms020800040402030301010200
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
Cn8wggUJMIID8aADAgECAhACt8ndrdK9CetZxFyQDGB4MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0xNDExMTgx
MjAwMDBaFw0yNDExMTgxMjAwMDBaMHIxCzAJBgNVBAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1I
b2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzANBgNVBAoTBlRFUkVOQTEmMCQGA1UEAxMd
VEVSRU5BIGVTY2llbmNlIFBlcnNvbmFsIENBIDMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
ggEKAoIBAQCwp9Jj5Aej1xPkS1GV3LvBdemFmkUR//nSzBodqsU3dv2BCRD30r4gt5oRsYty
qDGF2nnItxV1SkwVoDxFeRzOIHYNYvBRHaiGvCQjEXzPRTocOSVfWpmq/zAL/QOEqpJogeM+
0IBGiJcAENJshl7UcfjYbBnN5qStk74f52VWFf/aiF7MVJnsUr3oriQvXYOzs8N/NXyyQyim
atBbumJVCNszF1X+XHCGfPNvxlNFW9ktv7azK0baminfLcsh6ubCdINZc+Nof2lU387NCDgg
oh3KsYVcZTSuhh7qp6MjxE5VqOZod1hpXXzDOkjK+DAMC57iZXssncp24eaN08VlAgMBAAGj
ggGmMIIBojASBgNVHRMBAf8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBhjB5BggrBgEFBQcB
AQRtMGswJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcw
AoY3aHR0cDovL2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENB
LmNydDCBgQYDVR0fBHoweDA6oDigNoY0aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lD
ZXJ0QXNzdXJlZElEUm9vdENBLmNybDA6oDigNoY0aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNybDA9BgNVHSAENjA0MDIGBFUdIAAwKjAoBggr
BgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzAdBgNVHQ4EFgQUjJ8RLubj
egSlHlWLRggEpu2XcKYwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZI
hvcNAQELBQADggEBAI5HEV91Oen8WHFCoJkeu2Av+b/kWTV2qH/YNI1Xsbou2hHKhh4IyNkF
OxA/TUiuK2qQnQ5hAS0TIrs9SJ1Ke+DjXd/cTBiw7lCYSW5hkzigFV+iSivninpItafWqYBS
WxITl1KHBS9YBskhEqO5GLliDMPiAgjqUBQ/H1qZMlZNQIuFu0UaFUQuZUpJFr4+0zpzPxsB
iWU2muAoGItwbaP55EYshM7+v/J+x6kIhAJt5Dng8fOmOvR9F6Vw2/E0EZ6oQ8g1fdhwM101
S1OI6J1tUil1r7ES/svNqVWVb7YkUEBcPo8ppfHnTI/uxsn2tslsWefsOGJxNYUUSMAb9Eow
ggVuMIIEVqADAgECAhAKebGg8bOvnIyfOWAn4bpzMA0GCSqGSIb3DQEBCwUAMHIxCzAJBgNV
BAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzAN
BgNVBAoTBlRFUkVOQTEmMCQGA1UEAxMdVEVSRU5BIGVTY2llbmNlIFBlcnNvbmFsIENBIDMw
HhcNMTcxMTE2MDAwMDAwWhcNMTgxMjE1MTIwMDAwWjCBlDETMBEGCgmSJomT8ixkARkWA29y
ZzEWMBQGCgmSJomT8ixkARkWBnRlcmVuYTETMBEGCgmSJomT8ixkARkWA3RjczELMAkGA1UE
BhMCQ1oxJTAjBgNVBAoTHFNpbGVzaWFuIFVuaXZlcnNpdHkgaW4gT3BhdmExHDAaBgNVBAMT
E0ppcmkgU2xlemthIHNsZTAwMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC/
VwOD1hlYL6l7GzxNqV1ne7/iMF/gHvPfTwejsC2s9sby7It82qXPRBVA2s1Cjb1A3ucpdlDN
MXM83Lvh881XfkxhS2YLLyiZDmlSzAqfoMLxQ2/E0m1UugttzGJF7/10pEwj0FJFhnIVwA/E
8svCcbhxwO9BBpUz8JG1C6fTd0qyzJtNXVyH+WuHQbU2jgu2JJ7miiEKE1Fis0hFf1rKxTzX
aVGyXiQLOn7TZDfPtXrJEG7eWYlFUP58edyuJELpWHTPHn8xJKYTy8Qq5BgFNyCRQT/6imsh
tZlDBZSEeqyoSNtLsC57ZrjqgtLCEQFK9EX27dOy0/u95zS0OIWdAgMBAAGjggHbMIIB1zAf
BgNVHSMEGDAWgBSMnxEu5uN6BKUeVYtGCASm7ZdwpjAdBgNVHQ4EFgQUF1mSlcyDz9wWit9V
jCz+zJ9CrpswDAYDVR0TAQH/BAIwADAdBgNVHREEFjAUgRJqaXJpLnNsZXprYUBzbHUuY3ow
DgYDVR0PAQH/BAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDA0BgNVHSAE
LTArMAwGCiqGSIb3TAUCAgEwDAYKYIZIAYb9bAQfATANBgsqhkiG90wFAgMDAzCBhQYDVR0f
BH4wfDA8oDqgOIY2aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL1RFUkVOQWVTY2llbmNlUGVy
c29uYWxDQTMuY3JsMDygOqA4hjZodHRwOi8vY3JsNC5kaWdpY2VydC5jb20vVEVSRU5BZVNj
aWVuY2VQZXJzb25hbENBMy5jcmwwewYIKwYBBQUHAQEEbzBtMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5kaWdpY2VydC5jb20wRQYIKwYBBQUHMAKGOWh0dHA6Ly9jYWNlcnRzLmRpZ2lj
ZXJ0LmNvbS9URVJFTkFlU2NpZW5jZVBlcnNvbmFsQ0EzLmNydDANBgkqhkiG9w0BAQsFAAOC
AQEADtFRxKphkcHVdWjR/+i1+cdHfkbicraHlU5Mpw8EX6nemKu4GGAWfzH+Y7p6ImZwUHWf
/SSbrX+57xaFUBOr3jktQm1GRmGUZESEmsUDB8UZXzdQC79/tO9MzRhvEBXuQhdxdoO64Efx
VqtYAB2ydqz7yWh56ioSwaQZEXo5rO1kZuAcmVz8Smd1r/Mur/h8Y+qbrsJng1GS25aMhFts
UV6z9zXuHFkT9Ck8SLdCEDzjzYNjXIDB5n+QOmPXnXrZMlGiI/aOqa5k5Sv6xCIPdH2kbpyd
M1YiH/ChmU9gWJvy0Jq42KGLvWBvuHEzcb3f473Fvn4GWsXu0zDS2oh2/TGCA8MwggO/AgEB
MIGGMHIxCzAJBgNVBAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHEwlB
bXN0ZXJkYW0xDzANBgNVBAoTBlRFUkVOQTEmMCQGA1UEAxMdVEVSRU5BIGVTY2llbmNlIFBl
cnNvbmFsIENBIDMCEAp5saDxs6+cjJ85YCfhunMwDQYJYIZIAWUDBAIBBQCgggINMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE4MDUwNzE1NDEwM1owLwYJ
KoZIhvcNAQkEMSIEICVXkIyGY0Vn2bfo9/HNUIM1ozaasiIOr8tqAebw1DwvMGwGCSqGSIb3
DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG
9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgZcGCSsG
AQQBgjcQBDGBiTCBhjByMQswCQYDVQQGEwJOTDEWMBQGA1UECBMNTm9vcmQtSG9sbGFuZDES
MBAGA1UEBxMJQW1zdGVyZGFtMQ8wDQYDVQQKEwZURVJFTkExJjAkBgNVBAMTHVRFUkVOQSBl
U2NpZW5jZSBQZXJzb25hbCBDQSAzAhAKebGg8bOvnIyfOWAn4bpzMIGZBgsqhkiG9w0BCRAC
CzGBiaCBhjByMQswCQYDVQQGEwJOTDEWMBQGA1UECBMNTm9vcmQtSG9sbGFuZDESMBAGA1UE
BxMJQW1zdGVyZGFtMQ8wDQYDVQQKEwZURVJFTkExJjAkBgNVBAMTHVRFUkVOQSBlU2NpZW5j
ZSBQZXJzb25hbCBDQSAzAhAKebGg8bOvnIyfOWAn4bpzMA0GCSqGSIb3DQEBAQUABIIBAAlh
wZpUkIK/kEuHl6+ThVIcWni+413g80Z4nA2kizLn67bGYqLNPzkEXWT37geWbAgw3GZx7lHu
rmfqvxUZC3d3RIVubvLKQKZf/4N0PzMOxpdZlnYuWPpGydQ1FOv+jgJwxXcfnyJPuinBueuZ
nTI8aB/TnlrbsS6UgD1K7VmhJgr2q/ClXp41OgyVXiPi7v2nRa9eOmUnQ/MdhceDtjtH3h7y
SPBdKnz+CU8Ziu2dx9gB417x9khCvNaZHEFSdoniCWT6fypFRPODXxF/dGkUCZsMiK4W35k3
mKkfNhFdsFtJJTO4Daj1eP7zMbe+UNVb2E7GvoPlPSWhyWDX3z0AAAAAAAA=
--------------ms020800040402030301010200--
5 years, 11 months
Error : Cannot locate ovirt-host package, possible cause is incorrect channels
by Aziz
Hi All,
I'm trying to add a second Host to my controller but it fails for some
reason, from the events log in the webUI I got the following message :
*Host HV2 installation failed. Command returned failure code 1 during SSH
session *
The engine logs are showing the following messages :
*2018-05-09 05:50:28,315-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage:
Initializing.2018-05-09 05:50:28,398-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Environment
setup.2018-05-09 05:50:28,440-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Environment
packages setup.2018-05-09 05:50:29,924-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Programs
detection.2018-05-09 05:50:29,932-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Environment
customization.2018-05-09 05:50:30,457-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Kdump
supported.2018-05-09 05:50:30,541-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Logs at host located at:
'/tmp/ovirt-host-deploy-20180509105027-896hy7.log'.2018-05-09
05:50:30,595-04 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployVdsmUnit] (VdsDeploy)
[359b2b82-9cca-4910-8a74-4d90819702b0] Host hv2.vdi-lab.ma
<http://hv2.vdi-lab.ma> reports unique id
4C4C4544-0053-5A10-8048-C2C04F59344A2018-05-09 05:50:30,618-04 INFO
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployVdsmUnit] (VdsDeploy)
[359b2b82-9cca-4910-8a74-4d90819702b0] Assigning unique id
4C4C4544-0053-5A10-8048-C2C04F59344A to Host hv2.vdi-lab.ma
<http://hv2.vdi-lab.ma>2018-05-09 05:50:30,674-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Disabling Kdump
integration.2018-05-09 05:50:30,774-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Setup
validation.2018-05-09 05:50:31,232-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during
installation of Host HV2: Failed to execute stage 'Setup validation':
Cannot locate ovirt-host package, possible cause is incorrect
channels.2018-05-09 05:50:31,241-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage: Clean
up.2018-05-09 05:50:31,249-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage:
Pre-termination.2018-05-09 05:50:31,265-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Retrieving installation
logs to:
'/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20180509055031-hv2.vdi-lab.ma-359b2b82-9cca-4910-8a74-4d90819702b0.log'.2018-05-09
05:50:31,591-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) [359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID:
VDS_INSTALL_IN_PROGRESS(509), Installing Host HV2. Stage:
Termination.2018-05-09 05:50:31,592-04 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] SSH error running command
root(a)hv2.vdi-lab.ma:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp
-d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null
2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp
-C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy
DIALOG/dialect=str:machine DIALOG/customization=bool:True': IOException:
Command returned failure code 1 during SSH session 'root(a)hv2.vdi-lab.ma
<root(a)hv2.vdi-lab.ma>'2018-05-09 05:50:31,592-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] Error during host hv2.vdi-lab.ma
<http://hv2.vdi-lab.ma> install2018-05-09 05:50:31,593-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] Host installation failed for host
'fa86070d-61a3-40b5-85ec-bae7a2056210', 'HV2': Command returned failure
code 1 during SSH session 'root(a)hv2.vdi-lab.ma
<root(a)hv2.vdi-lab.ma>'2018-05-09 05:50:31,597-04 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] START,
SetVdsStatusVDSCommand(HostName = HV2,
SetVdsStatusVDSCommandParameters:{hostId='fa86070d-61a3-40b5-85ec-bae7a2056210',
status='InstallFailed', nonOperationalReason='NONE',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id:
1a83e92b2018-05-09 05:50:31,608-04 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] FINISH, SetVdsStatusVDSCommand, log
id: 1a83e92b2018-05-09 05:50:31,649-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] EVENT_ID: VDS_INSTALL_FAILED(505),
Host HV2 installation failed. Command returned failure code 1 during SSH
session 'root(a)hv2.vdi-lab.ma <root(a)hv2.vdi-lab.ma>'.2018-05-09
05:50:31,658-04 INFO
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-115)
[359b2b82-9cca-4910-8a74-4d90819702b0] Lock freed to object
'EngineLock:{exclusiveLocks='[fa86070d-61a3-40b5-85ec-bae7a2056210=VDS]',
sharedLocks=''}'*
Does anyone have a hint on how to fix this ?
Thank you in advance.
5 years, 11 months
Self Hosted Engine and iSCSI doubt
by Gianluca Cecchi
Hello,
a doubt for 4.1 related to LUNs / storage domains to dedicate to hosted
engine storage and normal data domain storage.
In oVirt docs here:
https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_En...
doesn't say anything special to differentiate iSCSI based and FC-SAN based
storage for hosted engine.
Inside the docs of Self-Hosted Engine Guide for RHV (bot 4.1 final and
4.2beta ones) there is this general statement:
"
You must have prepared storage for your self-hosted engine environment. At
least two storage domains are required:
- A shared storage domain dedicated to the Manager virtual machine. This
domain is created
during the self-hosted engine deployment, and must be at least 60 GB.
- A data storage domain for regular virtual machine data. This domain must
be added to the
self-hosted engine environment after the deployment is complete.
"
So far so good. But a bit below there is a particular note for iSCSI that I
don't understand quite well
"
IMPORTANT
If you are using iSCSI storage, do not use the same iSCSI target for the
shared
storage domain and data storage domain.
"
Does it simply remark that the LUN for the hosted engine storage (shared
storage domain) should be different from the LUN(s) used then for normal
VMs (data storage domain), or what?
I think it doesn't refer to the portal that for some reason needs to be
different, correct?
Any clarification about this restrictions?
Thanks,
Gianluca
5 years, 11 months
