4.4 regression: engine-setup fails if admin password in answerfile contains a "%"
I encountered this error when deploying the Hosted Engine via Cockpit: [ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]} The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'" Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated. OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3. Once I changed the admin password, installation progressed normally.
Hi Stephen, I think it's a regression. Could you open an issue/bug . Best Regards, Strahil Nikolov На 24 май 2020 г. 2:28:41 GMT+03:00, Stephen Panicho <s.panicho@gmail.com> написа:
I encountered this error when deploying the Hosted Engine via Cockpit:
[ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]}
The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'"
Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated.
OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj
Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3.
Once I changed the admin password, installation progressed normally.
-- Изпратено от моето Андроид у-во чрез K-9 Mail. Моля да ме извините за краткият ми изказ.
On Sun, May 24, 2020 at 9:51 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
Hi Stephen,
I think it's a regression. Could you open an issue/bug .
It is. Thanks for the report. Here is a fix: https://gerrit.ovirt.org/109244 Did any of you open a bug? If not, I'll open one. Thanks. Best regards,
Best Regards, Strahil Nikolov
На 24 май 2020 г. 2:28:41 GMT+03:00, Stephen Panicho <s.panicho@gmail.com> написа:
I encountered this error when deploying the Hosted Engine via Cockpit:
[ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]}
The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'"
Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated.
OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj
Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3.
Once I changed the admin password, installation progressed normally.
-- Изпратено от моето Андроид у-во чрез K-9 Mail. Моля да ме извините за краткият ми изказ. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/OHDBPINYMOJVS3...
-- Didi
On Sun, May 24, 2020 at 12:08 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 9:51 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
Hi Stephen,
I think it's a regression. Could you open an issue/bug .
It is. Thanks for the report. Here is a fix:
https://gerrit.ovirt.org/109244
Did any of you open a bug? If not, I'll open one. Thanks.
Best regards,
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem": On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the only "strange" character I used for the admin password was the @ Donna if it related with what you reported for the % character
Did you open a bug? In any case, my above patch is not supposed to fix '@', only '%' (I think). Thanks and best regards,
Best Regards, Strahil Nikolov
На 24 май 2020 г. 2:28:41 GMT+03:00, Stephen Panicho <s.panicho@gmail.com> написа:
I encountered this error when deploying the Hosted Engine via Cockpit:
[ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]}
The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'"
Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated.
OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj
Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3.
Once I changed the admin password, installation progressed normally.
-- Изпратено от моето Андроид у-во чрез K-9 Mail. Моля да ме извините за краткият ми изказ. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/OHDBPINYMOJVS3...
-- Didi
-- Didi
Created a bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1839533 (forgive me if this is improperly categorized...) On Sun, May 24, 2020 at 5:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 12:08 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 9:51 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
Hi Stephen,
I think it's a regression. Could you open an issue/bug .
It is. Thanks for the report. Here is a fix:
https://gerrit.ovirt.org/109244
Did any of you open a bug? If not, I'll open one. Thanks.
Best regards,
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the
only "strange" character I used for the admin password was the @
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
Best Regards, Strahil Nikolov
На 24 май 2020 г. 2:28:41 GMT+03:00, Stephen Panicho <
I encountered this error when deploying the Hosted Engine via Cockpit:
[ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED!
=> {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]}
The important bit is this: Failed to execute stage 'Initializing':
'%' must be followed by '%' or '(', found: '%JUUj'"
Hey! Those are the last few characters of the admin password. Note
s.panicho@gmail.com> написа: that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated.
OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj
Apparently engine-setup can no longer handle an answerfile with a "%"
character in it. This same password worked in 4.3.
Once I changed the admin password, installation progressed normally.
-- Изпратено от моето Андроид у-во чрез K-9 Mail. Моля да ме извините за краткият ми изказ. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/OHDBPINYMOJVS3...
-- Didi
-- Didi
On Sun, May 24, 2020 at 5:44 PM Stephen Panicho <s.panicho@gmail.com> wrote:
Created a bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1839533 (forgive me if this is improperly categorized...)
Thanks! A note, also to everyone: The most important part of a bug report is an accurate and complete reproduction description. The second most important is enough relevant logs. Metadata is not important in the report. It's important later on, but someone will manage to fix it later on... Well, metadata might be important for making sure the bug won't be forgotten somewhere. But sending the link like you did now is also enough for that. That's, obviously, IMHO :-) There are several articles on the net about "how to submit a good bug report" or stuff like that. It's been many years since I read one, but I think they'll agree with the above. Best regards,
On Sun, May 24, 2020 at 5:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 12:08 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 9:51 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
Hi Stephen,
I think it's a regression. Could you open an issue/bug .
It is. Thanks for the report. Here is a fix:
https://gerrit.ovirt.org/109244
Did any of you open a bug? If not, I'll open one. Thanks.
Best regards,
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the only "strange" character I used for the admin password was the @ Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
Best Regards, Strahil Nikolov
На 24 май 2020 г. 2:28:41 GMT+03:00, Stephen Panicho <s.panicho@gmail.com> написа:
I encountered this error when deploying the Hosted Engine via Cockpit:
[ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]}
The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'"
Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated.
OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj
Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3.
Once I changed the admin password, installation progressed normally.
-- Изпратено от моето Андроид у-во чрез K-9 Mail. Моля да ме извините за краткият ми изказ. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/OHDBPINYMOJVS3...
-- Didi
-- Didi
-- Didi
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the
only "strange" character I used for the admin password was the @
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... I will put attention in case of future 4.4 new installations Gianluca
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the only "strange" character I used for the admin password was the @ Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... I will put attention in case of future 4.4 new installations
Very well, thanks :-) -- Didi
Hey Didi, usually I fill in the bugzilla template . If it's possible , maybe we can change the oVirt bugzilla template to cover everything necessary ? Best Regards, Strahil Nikolov На 25 май 2020 г. 9:50:11 GMT+03:00, Yedidyah Bar David <didi@redhat.com> написа:
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com>
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I
wrote: the only "strange" character I used for the admin password was the @ think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... I will put attention in case of future 4.4 new installations
Very well, thanks :-)
On Tue, May 26, 2020 at 2:05 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Hey Didi,
usually I fill in the bugzilla template . If it's possible , maybe we can change the oVirt bugzilla template to cover everything necessary ?
Do you refer to this: ================================================================================ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: ================================================================================ ? I think we can change it, no idea about details. That said, I think it's already detailed enough. You have in the form also a way to upload logs, etc. I think it's enough for every open-source-software-user to spend at least one time in his career the time needed to read one of the "how to report bugs" howtos on the net, no need to repeat it in the form. Also, like everything else, some experience in doing this helps a lot... Best regards,
Best Regards, Strahil Nikolov
На 25 май 2020 г. 9:50:11 GMT+03:00, Yedidyah Bar David <didi@redhat.com> написа:
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com>
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I
wrote: the only "strange" character I used for the admin password was the @ think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... I will put attention in case of future 4.4 new installations
Very well, thanks :-)
-- Didi
Hey Didi, yes this one. The user has spent some time to fill in the template, so we shouldn't expect that this user should also dedicate extra time to search for articles :) Best Regards, Strahil Nikolov На 26 май 2020 г. 14:29:57 GMT+03:00, Yedidyah Bar David <didi@redhat.com> написа:
On Tue, May 26, 2020 at 2:05 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Hey Didi,
usually I fill in the bugzilla template . If it's possible , maybe
we can change the oVirt bugzilla template to cover everything necessary ?
Do you refer to this: ================================================================================ Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: ================================================================================ ?
I think we can change it, no idea about details.
That said, I think it's already detailed enough. You have in the form also a way to upload logs, etc.
I think it's enough for every open-source-software-user to spend at least one time in his career the time needed to read one of the "how to report bugs" howtos on the net, no need to repeat it in the form.
Also, like everything else, some experience in doing this helps a lot...
Best regards,
Best Regards, Strahil Nikolov
На 25 май 2020 г. 9:50:11 GMT+03:00, Yedidyah Bar David
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David
<didi@redhat.com> wrote:
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure
Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle
and the only "strange" character I used for the admin password was the @
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used
<didi@redhat.com> написа: - the
same password with the @ character or not....
I will put attention in case of future 4.4 new installations
Very well, thanks :-)
On Mon, May 25, 2020 at 8:50 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com>
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and
Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same
wrote: the only "strange" character I used for the admin password was the @ think). password with the @ character or not....
I will put attention in case of future 4.4 new installations
Very well, thanks :-) -- Didi
Just to avoid opening a bug for a different thing, today I tried a single host HCI setup with the wizard and it failed. Installed from ovirt-node-ng final 4.4 iso. I see I have no /etc/pki/CA directory on the host at the moment, but I don't know if the install workflow had not arrived there yet or what. Last lines in my wizard window are these ones below. Password used contains only letters, numbers and the "_" character in this attempt I'm in the "Prepare VM" stage. [ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt default network configuration] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n"} Status of libvirtd service is this one: [root@ovirt01 g.cecchi]# systemctl status libvirtd -l --no-pager ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─unlimited-core.conf Active: failed (Result: exit-code) since Wed 2020-06-03 15:13:35 CEST; 7min ago Docs: man:libvirtd(8) https://libvirt.org Process: 20001 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=6) Main PID: 20001 (code=exited, status=6) Tasks: 2 (limit: 32768) Memory: 70.1M CGroup: /system.slice/libvirtd.service ├─3926 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─3927 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Stopped Virtualization daemon. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Start request repeated too quickly. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Failed with result 'exit-code'. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Failed to start Virtualization daemon. [root@ovirt01 g.cecchi]# Let me know what files do you want to analyze the problem Under /var/log/ovirt-hosted-engine-setup I have: [root@ovirt01 ovirt-hosted-engine-setup]# ls -lrt total 632 -rw-r--r--. 1 root root 123814 Jun 3 15:07 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20205315737-ooohyb.log -rw-r--r--. 1 root root 126674 Jun 3 15:08 ovirt-hosted-engine-setup-ansible-validate_hostnames-20205315737-oqixuw.log -rw-r--r--. 1 root root 127548 Jun 3 15:10 ovirt-hosted-engine-setup-ansible-validate_hostnames-202053151022-yls4qo.log -rw-r--r--. 1 root root 261482 Jun 3 15:13 ovirt-hosted-engine-setup-ansible-initial_clean-20205315123-7x25zv.log [root@ovirt01 ovirt-hosted-engine-setup]# In this environment no dns but entry in /etc/hosts of the server. Host is on 192.168.1.x on eno1 and a vlan 100 on the same interface, used for "simulated" storage network 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:ae:ed:7f:17:11 brd ff:ff:ff:ff:ff:ff inet 192.168.1.211/24 brd 192.168.1.255 scope global noprefixroute eno1 valid_lft forever preferred_lft forever inet6 fe80::315c:2e9f:d009:8c0c/64 scope link noprefixroute valid_lft forever preferred_lft forever 7: eno1.100@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b8:ae:ed:7f:17:11 brd ff:ff:ff:ff:ff:ff inet 192.168.100.211/24 brd 192.168.100.255 scope global noprefixroute eno1.100 valid_lft forever preferred_lft forever inet6 fe80::be0f:c4be:cf7a:9da5/64 scope link noprefixroute valid_lft forever preferred_lft forever Thanks, Gianluca
On Wed, Jun 3, 2020 at 4:30 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Mon, May 25, 2020 at 8:50 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com> wrote:
Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem":
On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
I I remember correctly it happened to me during the beta cycle and the only "strange" character I used for the admin password was the @ Donna if it related with what you reported for the % character
Did you open a bug?
In any case, my above patch is not supposed to fix '@', only '%' (I think).
Thanks and best regards,
No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... I will put attention in case of future 4.4 new installations
Very well, thanks :-) -- Didi
Just to avoid opening a bug for a different thing, today I tried a single host HCI setup with the wizard and it failed. Installed from ovirt-node-ng final 4.4 iso. I see I have no /etc/pki/CA directory on the host at the moment, but I don't know if the install workflow had not arrived there yet or what. Last lines in my wizard window are these ones below. Password used contains only letters, numbers and the "_" character in this attempt I'm in the "Prepare VM" stage.
[ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt default network configuration] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n"}
Status of libvirtd service is this one:
[root@ovirt01 g.cecchi]# systemctl status libvirtd -l --no-pager ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─unlimited-core.conf Active: failed (Result: exit-code) since Wed 2020-06-03 15:13:35 CEST; 7min ago Docs: man:libvirtd(8) https://libvirt.org Process: 20001 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=6) Main PID: 20001 (code=exited, status=6) Tasks: 2 (limit: 32768) Memory: 70.1M CGroup: /system.slice/libvirtd.service ├─3926 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─3927 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Stopped Virtualization daemon. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Start request repeated too quickly.
This looks simply like libvirt was restarted too much too quickly. Did you restart it yourself before deploy? If not, and it's only due to the deploy process restarting it, then either: 1. That's ok, and we should simply configure systemd to allow that, 2. or there is some other problem, and restarting libvirt is just a symptom.
Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Failed with result 'exit-code'. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Failed to start Virtualization daemon. [root@ovirt01 g.cecchi]#
Let me know what files do you want to analyze the problem Under /var/log/ovirt-hosted-engine-setup I have:
[root@ovirt01 ovirt-hosted-engine-setup]# ls -lrt total 632 -rw-r--r--. 1 root root 123814 Jun 3 15:07 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20205315737-ooohyb.log -rw-r--r--. 1 root root 126674 Jun 3 15:08 ovirt-hosted-engine-setup-ansible-validate_hostnames-20205315737-oqixuw.log -rw-r--r--. 1 root root 127548 Jun 3 15:10 ovirt-hosted-engine-setup-ansible-validate_hostnames-202053151022-yls4qo.log -rw-r--r--. 1 root root 261482 Jun 3 15:13 ovirt-hosted-engine-setup-ansible-initial_clean-20205315123-7x25zv.log [root@ovirt01 ovirt-hosted-engine-setup]#
Perhaps check these for libvirt restarts, also /var/log/messages (or journalctl). Do you see there other errors?
In this environment no dns but entry in /etc/hosts of the server. Host is on 192.168.1.x on eno1 and a vlan 100 on the same interface, used for "simulated" storage network
For now, I'd assume that's not related, but can't be sure. Thanks and best regards, -- Didi
On Wed, Jun 3, 2020 at 4:15 PM Yedidyah Bar David <didi@redhat.com> wrote: [snip]
This looks simply like libvirt was restarted too much too quickly. Did you restart it yourself before deploy?
No. I installed from iso and after restart I connected to cockpit and run the gluster wizard for single host
If not, and it's only due to the deploy process restarting it, then either: 1. That's ok, and we should simply configure systemd to allow that, 2. or there is some other problem, and restarting libvirt is just a symptom.
Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Failed with result 'exit-code'. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Failed to start Virtualization daemon. [root@ovirt01 g.cecchi]#
Let me know what files do you want to analyze the problem Under /var/log/ovirt-hosted-engine-setup I have:
[root@ovirt01 ovirt-hosted-engine-setup]# ls -lrt total 632 -rw-r--r--. 1 root root 123814 Jun 3 15:07 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20205315737-ooohyb.log -rw-r--r--. 1 root root 126674 Jun 3 15:08 ovirt-hosted-engine-setup-ansible-validate_hostnames-20205315737-oqixuw.log -rw-r--r--. 1 root root 127548 Jun 3 15:10 ovirt-hosted-engine-setup-ansible-validate_hostnames-202053151022-yls4qo.log -rw-r--r--. 1 root root 261482 Jun 3 15:13 ovirt-hosted-engine-setup-ansible-initial_clean-20205315123-7x25zv.log [root@ovirt01 ovirt-hosted-engine-setup]#
Perhaps check these for libvirt restarts, also /var/log/messages (or journalctl). Do you see there other errors?
The latest file contains these last lines with the summary: 2020-06-03 15:13:34,567+0200 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:01 ] Install oVirt Hosted Engine packages [ < 1 sec ] System configuration validations [ 00:01 ] Get all active network interfaces [ < 1 sec ] Filter bonds with bad naming [ < 1 sec ] Generate output list [ 00:01 ] Collect interface types [ < 1 sec ] Get list of Team devices [ < 1 sec ] Filter unsupported interface types [ < 1 sec ] Prepare getent key [ < 1 sec ] Get full hostname [ < 1 sec ] Set hostname variable if not defined [ < 1 sec ] Define host address variable if not defined [ < 1 sec ] Get host address resolution [ < 1 sec ] Parse host address resolution [ < 1 sec ] Get target address from selected interface (IPv4) [ < 1 sec ] Get target address from selected interface (IPv6) [ < 1 sec ] Check for alias [ < 1 sec ] Filter resolved address list [ < 1 sec ] Get engine FQDN resolution [ < 1 sec ] Parse engine he_fqdn resolution [ < 1 sec ] Define he_cloud_init_host_name [ < 1 sec ] Get uuid [ < 1 sec ] Set he_vm_uuid [ < 1 sec ] Get uuid [ < 1 sec ] Set he_nic_uuid [ < 1 sec ] Get uuid [ < 1 sec ] Set he_cdrom_uuid [ < 1 sec ] get timezone [ < 1 sec ] Set he_time_zone [ 00:01 ] Check firewalld status [ < 1 sec ] Get default gateway IPv4 [ < 1 sec ] Get default gateway IPv6 [ < 1 sec ] Set he_gateway [ < 1 sec ] Generate unicast MAC address [ < 1 sec ] Set he_vm_mac_addr [ < 1 sec ] Get free memory [ < 1 sec ] Get cached memory [ < 1 sec ] Set Max memory [ < 1 sec ] set he_mem_size_MB to max available if not defined [ < 1 sec ] Populate service facts [ < 1 sec ] get max cpus [ < 1 sec ] Set he_maxvcpus [ < 1 sec ] Set he_vcpus to maximum amount if not defined [ < 1 sec ] Stop libvirt service [ 00:01 ] Drop vdsm config statements [ 00:01 ] Restore initial abrt config files [ 00:01 ] Restart abrtd service [ 00:01 ] Drop libvirt sasl2 configuration by vdsm [ 00:01 ] Stop and disable services [ < 1 sec ] Restore initial libvirt default network configuration [ FAILED ] Start libvirt 2020-06-03 15:13:34,567+0200 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7f7156a11b70> kwargs Previous lines of the same file contain: ... 2020-06-03 15:13:23,336+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Check number of chosen CPUs kwargs 2020-06-03 15:13:23,631+0200 INFO ansible skipped {'status': 'SKIPPED', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt- hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'Check number of chosen CPUs', 'ansible_host': 'localhost'} 2020-06-03 15:13:23,632+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f7154057748> kwargs 2020-06-03 15:13:23,944+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Stop libvirt service'} 2020-06-03 15:13:23,945+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Stop libvirt service kwargs is_conditional:False 2020-06-03 15:13:23,945+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Stop libvirt service kwargs 2020-06-03 15:13:24,625+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Stop libvirt service', 'task_duration': 0} 2020-06-03 15:13:24,626+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71541c4f98> kwargs 2020-06-03 15:13:24,930+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Drop vdsm config statements'} 2020-06-03 15:13:24,930+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Drop vdsm config statements kwargs is_conditional:False 2020-06-03 15:13:24,930+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Drop vdsm config statements kwargs 2020-06-03 15:13:25,166+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715412fbe0> kwargs 2020-06-03 15:13:25,385+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715412f198> kwargs 2020-06-03 15:13:25,600+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71540e8668> kwargs 2020-06-03 15:13:25,815+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715412fb38> kwargs 2020-06-03 15:13:26,096+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Drop vdsm config statements', 'task_duration': 1} 2020-06-03 15:13:26,096+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715402c780> kwargs 2020-06-03 15:13:26,417+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Restore initial abrt config files'} 2020-06-03 15:13:26,417+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Restore initial abrt config files kwargs is_conditional:False 2020-06-03 15:13:26,417+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Restore initial abrt config files kwargs 2020-06-03 15:13:26,878+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715404ba20> kwargs 2020-06-03 15:13:27,138+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f7154138320> kwargs 2020-06-03 15:13:27,391+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f7154061588> kwargs 2020-06-03 15:13:27,643+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715404b278> kwargs 2020-06-03 15:13:27,945+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Restore initial abrt config files', 'task_duration': 1} 2020-06-03 15:13:27,945+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f7154061ac8> kwargs 2020-06-03 15:13:28,268+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Restart abrtd service'} 2020-06-03 15:13:28,268+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Restart abrtd service kwargs is_conditional:False 2020-06-03 15:13:28,268+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Restart abrtd service kwargs 2020-06-03 15:13:29,045+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Restart abrtd service', 'task_duration': 1} 2020-06-03 15:13:29,046+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f715413e860> kwargs 2020-06-03 15:13:29,358+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm'} 2020-06-03 15:13:29,358+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm kwargs is_conditional:False 2020-06-03 15:13:29,358+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm kwargs 2020-06-03 15:13:30,873+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Drop libvirt sasl2 configuration by vdsm', 'task_duration': 1} 2020-06-03 15:13:30,873+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71541f2d30> kwargs 2020-06-03 15:13:31,212+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Stop and disable services'} 2020-06-03 15:13:31,212+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Stop and disable services kwargs is_conditional:False 2020-06-03 15:13:31,212+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Stop and disable services kwargs 2020-06-03 15:13:31,614+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71541c4518> kwargs 2020-06-03 15:13:31,978+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f714ffc0c88> kwargs 2020-06-03 15:13:32,353+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f714ffc0128> kwargs 2020-06-03 15:13:32,644+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Stop and disable services', 'task_duration': 1} 2020-06-03 15:13:32,644+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f7154199240> kwargs 2020-06-03 15:13:32,955+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Restore initial libvirt default network configuration'} 2020-06-03 15:13:32,956+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Restore initial libvirt default network configuration kwargs is_conditional:False 2020-06-03 15:13:32,956+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Restore initial libvirt default network configuration kwargs 2020-06-03 15:13:33,475+0200 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Restore initial libvirt default network configuration', 'task_duration': 0} 2020-06-03 15:13:33,476+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71541380f0> kwargs 2020-06-03 15:13:33,785+0200 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Start libvirt'} 2020-06-03 15:13:33,786+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Start libvirt kwargs is_conditional:False 2020-06-03 15:13:33,786+0200 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Start libvirt kwargs 2020-06-03 15:13:34,564+0200 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2020-06-03 15:13:34,565+0200 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2020-06-03 15:13:34,565+0200 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2020-06-03 15:13:34,565+0200 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "invocation": { "module_args": { "daemon_reexec": false, "daemon_reload": false, "enabled": true, "force": null, "masked": null, "name": "libvirtd", "no_block": false, "scope": null, "state": "started", "user": null } }, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n" }, "ansible_task": "Start libvirt", "ansible_type": "task", "status": "FAILED", "task_duration": 1 } 2020-06-03 15:13:34,565+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f71541c4240> kwargs ignore_errors:None 2020-06-03 15:13:34,567+0200 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "01:29 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 96, 'failures': 1, 'unreachable': 0, 'changed': 23, 'skipped': 37, 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" I confirm that what suggested by Joop worked for me too: " I have had this too and saw that during the test week it was also reported. The 'solution' was to run /usr/sbin/ovirt-hosted-engine-cleanup and let the wizard stay where it is and afterwards click Redeploy VM and then it will run to its conclusion. Don't know what precisely it fixes. Had a look and couldn't find it. " I confirm also the eventi for host already reported and due to missing packages: Gluster command [<UNKNOWN>] failed on server <UNKNOWN>. Gianluca
On Mon, May 25, 2020 at 8:50 AM Yedidyah Bar David <didi@redhat.com <mailto:didi@redhat.com>> wrote:
On Sun, May 24, 2020 at 9:36 PM Gianluca Cecchi <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote: > > On Sun, May 24, 2020 at 11:47 AM Yedidyah Bar David <didi@redhat.com <mailto:didi@redhat.com>> wrote: >> >> >> >> Hi, Gianluca. Replying to your email on "4.4 HCI Install Failure - >> Missing /etc/pki/CA/cacert.pem": >> >> On Sun, May 24, 2020 at 12:28 PM Gianluca Cecchi >> <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote: >> > >> > I I remember correctly it happened to me during the beta cycle and the only "strange" character I used for the admin password was the @ >> > Donna if it related with what you reported for the % character >> >> Did you open a bug? >> >> In any case, my above patch is not supposed to fix '@', only '%' (I think). >> >> Thanks and best regards, >> > > No, I didn't open a bug, because I scratched the system and installed again this time without the error, but I don't remember if I used the same password with the @ character or not.... > I will put attention in case of future 4.4 new installations
Very well, thanks :-) -- Didi
Just to avoid opening a bug for a different thing, today I tried a single host HCI setup with the wizard and it failed. Installed from ovirt-node-ng final 4.4 iso. I see I have no /etc/pki/CA directory on the host at the moment, but I don't know if the install workflow had not arrived there yet or what. Last lines in my wizard window are these ones below. I have had this too and saw that during the test week is was also reported. The 'solution' was to run /usr/sbin/ovirt-hosted-engine-cleanup and let
On 3-6-2020 15:29, Gianluca Cecchi wrote: the wizard stay where it is and afterwards click Redeploy VM and then it will run to its conclusion. Don't know what precisely it fixes. Had a look and couldn't find it. Joop
Password used contains only letters, numbers and the "_" character in this attempt I'm in the "Prepare VM" stage.
[ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt default network configuration] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n"}
Status of libvirtd service is this one:
[root@ovirt01 g.cecchi]# systemctl status libvirtd -l --no-pager ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─unlimited-core.conf Active: failed (Result: exit-code) since Wed 2020-06-03 15:13:35 CEST; 7min ago Docs: man:libvirtd(8) https://libvirt.org Process: 20001 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=6) Main PID: 20001 (code=exited, status=6) Tasks: 2 (limit: 32768) Memory: 70.1M CGroup: /system.slice/libvirtd.service ├─3926 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─3927 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 5. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Stopped Virtualization daemon. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Start request repeated too quickly. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: libvirtd.service: Failed with result 'exit-code'. Jun 03 15:13:35 ovirt01.mydomain.local systemd[1]: Failed to start Virtualization daemon. [root@ovirt01 g.cecchi]#
Let me know what files do you want to analyze the problem Under /var/log/ovirt-hosted-engine-setup I have:
[root@ovirt01 ovirt-hosted-engine-setup]# ls -lrt total 632 -rw-r--r--. 1 root root 123814 Jun 3 15:07 ovirt-hosted-engine-setup-ansible-get_network_interfaces-20205315737-ooohyb.log -rw-r--r--. 1 root root 126674 Jun 3 15:08 ovirt-hosted-engine-setup-ansible-validate_hostnames-20205315737-oqixuw.log -rw-r--r--. 1 root root 127548 Jun 3 15:10 ovirt-hosted-engine-setup-ansible-validate_hostnames-202053151022-yls4qo.log -rw-r--r--. 1 root root 261482 Jun 3 15:13 ovirt-hosted-engine-setup-ansible-initial_clean-20205315123-7x25zv.log [root@ovirt01 ovirt-hosted-engine-setup]#
In this environment no dns but entry in /etc/hosts of the server. Host is on 192.168.1.x on eno1 and a vlan 100 on the same interface, used for "simulated" storage network
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:ae:ed:7f:17:11 brd ff:ff:ff:ff:ff:ff inet 192.168.1.211/24 <http://192.168.1.211/24> brd 192.168.1.255 scope global noprefixroute eno1 valid_lft forever preferred_lft forever inet6 fe80::315c:2e9f:d009:8c0c/64 scope link noprefixroute valid_lft forever preferred_lft forever
7: eno1.100@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b8:ae:ed:7f:17:11 brd ff:ff:ff:ff:ff:ff inet 192.168.100.211/24 <http://192.168.100.211/24> brd 192.168.100.255 scope global noprefixroute eno1.100 valid_lft forever preferred_lft forever inet6 fe80::be0f:c4be:cf7a:9da5/64 scope link noprefixroute valid_lft forever preferred_lft forever
Thanks, Gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/IPDND2OXUV2DXL...
participants (5)
-
Gianluca Cecchi -
Joop -
Stephen Panicho -
Strahil Nikolov -
Yedidyah Bar David