[ovirt-users] Cluster CPU Type
Hi all I'm just putting in some new servers to be used as hosts in RHV 4.3 (soon to go to v4.4 or v4.5) but I'm having problems with the cluster CPU. These are HPE DL360 Gen10 with "Xeon Gold 6338N". Google tells me these are "Ice Lake" but RHV complains unless I set the cluster CPU type to "SandyBridge". Is this expected? What do I need to do to get these recognised as the corect CPU type? Thanks CC ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MVARZPDJABDS7OPOX3KP6ZRGPMAVTAMA/
[ovirt-users] Re: Ovirt-engine , certificate issue
On Tue, May 17, 2022 at 7:36 PM Sharon Gratch wrote:
> Hi,
>
> On Tue, May 17, 2022 at 7:33 PM Angel R. Gonzalez
> wrote:
>
>> Hello,
>>
>> I've a issue when I try log in ovirt-engine manager with a browser. The
>> error message is:
>>
>> PKIX path validation failed:
>> java.security.cert.CertPathValidatorException: validity check failed
>>
>> The ovirt version is 4.4.5.11-1.
>>
>> I follow the next commands for try resolve it.
>>
>>
>> > # cp -a /etc/pki/ovirt-engine "/etc/pki/ovirt-engine.$(date "+%Y%m%d")"
>> > # SUBJECT="$(openssl x509 -subject -noout -in
>> > /etc/pki/ovirt-engine/certs/apache.cer | sed 's/subject= //')"
>> > # /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache
>> > --password="PASSWORD" --subject="${SUBJECT}"
>> > # openssl pkcs12 -passin "pass:PASSWORD" -nokeys -in
>> > /etc/pki/ovirt-engine/keys/apache.p12 >
>> > /etc/pki/ovirt-engine/certs/apache.cer
>> > # openssl pkcs12 -passin "pass:PASSWORD" -nocerts -nodes -in
>> > /etc/pki/ovirt-engine/keys/apache.p12 >
>> > /etc/pki/ovirt-engine/keys/apache.key.nopass
>> > # chmod 0600 /etc/pki/ovirt-engine/keys/apache.key.nopass
>> > # systemctl restart ovirt-engine.service
>> But after restarting the issue is the same.
>>
>> Any idea?
>>
>
> Maybe try to restart the apache HTTP Server as well:
> *systemctl restart httpd*
>
> If it still doesn't work then please share the errors within the engine
> log /var/log/ovirt-engine/engine.log
>
> Thanks,
> Sharon
>
>
>
Otherwise you can run
engine-setup --offline
(it will not change anything on current config and will not try to update
any package)
between the answers to give it will notice that your certificate is expired
and you have to answer yes to the question to renew it
After that you should be able to access the engine again
HIH,
Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MHQNQRN4B7KRNTJ6XGRT4P5RVATV6UJ2/
[ovirt-users] Re: list-view instead of tiled-view in oVirt VM Portal?
Hi Bertjan, This requirement is currently not supported by the VM portal and not planned to be supported. Can you please share why a list view is preferable for you over a tiled view? Please note that the VM portal dashboard design is based on accessing a max of ~20 VMs and usually much less than that since used by non admin users which usually have permissions to access a limited number of VMs. You can filter those VMs on the dashboard by name, OS and status and also sort them by those parameters as well. We are also planning as part of Patternfly 4 upgrade to maybe reduce the area size of each VM card - which might help as well. Thanks, Sharon On Thu, May 12, 2022 at 3:22 PM Goorkate, B.J. wrote: > Hi all, > > Is it possible to have a list of vm's in the oVirt VM-portal instead of > the tiled view? > (can't find it, but may have overlooked) > > Thanks! > > Regards, > > Bertjan > > > > -- > > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is > uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht > ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender > direct > te informeren door het bericht te retourneren. Het Universitair Medisch > Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de > W.H.W. > (Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd > bij > de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197. > > Denk s.v.p aan het milieu voor u deze e-mail afdrukt. > > > -- > > This message may contain confidential information and is intended > exclusively > for the addressee. If you receive this message unintentionally, please do > not > use the contents but notify the sender immediately by return e-mail. > University > Medical Center Utrecht is a legal person by public law and is registered at > the Chamber of Commerce for Midden-Nederland under no. 30244197. > > Please consider the environment before printing this e-mail. > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/EUZE2RWZM4GFB4ITVWDSO5NPE2WPOSIB/ > --- Begin Message --- Hi, the ansible-runner-service cleanup PR is not yet merged: https://github.com/oVirt/ovirt-engine/pull/257 So until merged please just remove /etc/httpd/conf.d/zz-ansible-runner-service.conf Once this file is removed, python3-mod_wsgi should no longer be needed. Thanks, Martin On Sun, Apr 17, 2022 at 11:16 PM Nir Soffer wrote: > I upgraded today to > ovirt-engine-4.5.1-0.2.master.20220414121739.gitb2384c6521.el8.noarch > > Engine setup failed to complete when restarting httpd: > > # engine-setup > ... > [ INFO ] Restarting httpd > [ ERROR ] Failed to execute stage 'Closing up': Failed to start service > 'httpd' > [ INFO ] Stage: Clean up > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20220418000357-gn9jww.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20220418000447-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed > > [root@engine ~]# systemctl status httpd > ● httpd.service - The Apache HTTP Server >Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; > vendor preset: disabled) >Active: failed (Result: exit-code) since Mon 2022-04-18 00:04:47 IDT; > 19s ago > Docs: man:httpd.service(8) > Process: 15359 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND > (code=exited, status=1/FAILURE) > Main PID: 15359 (code=exited, status=1/FAILURE) >Status: "Reading configuration..." > > Apr 18 00:04:47 engine.local systemd[1]: Starting The Apache HTTP Server... > Apr 18 00:04:47 engine.local httpd[15359]: [Mon Apr 18 00:04:47.727854 > 2022] [so:warn] [pid 15359:tid 140623023360320] AH01574: mo> > Apr 18 00:04:47 engine.local httpd[15359]: AH00526: Syntax error on > line 4 of /etc/httpd/conf.d/zz-ansible-runner-service.conf: > Apr 18 00:04:47 engine.local httpd[15359]: Invalid command > 'WSGIDaemonProcess', perhaps misspelled or defined by a module not > incl> > > After installing python3-mod_wsgi httpd can be started, and engine-setup > works. > > Do we miss requires: in the spec? > > Nir > > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. ___ Devel mailing list -- de...@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct:
[ovirt-users] Re: Ovirt-engine , certificate issue
Hi,
On Tue, May 17, 2022 at 7:33 PM Angel R. Gonzalez
wrote:
> Hello,
>
> I've a issue when I try log in ovirt-engine manager with a browser. The
> error message is:
>
> PKIX path validation failed:
> java.security.cert.CertPathValidatorException: validity check failed
>
> The ovirt version is 4.4.5.11-1.
>
> I follow the next commands for try resolve it.
>
>
> > # cp -a /etc/pki/ovirt-engine "/etc/pki/ovirt-engine.$(date "+%Y%m%d")"
> > # SUBJECT="$(openssl x509 -subject -noout -in
> > /etc/pki/ovirt-engine/certs/apache.cer | sed 's/subject= //')"
> > # /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache
> > --password="PASSWORD" --subject="${SUBJECT}"
> > # openssl pkcs12 -passin "pass:PASSWORD" -nokeys -in
> > /etc/pki/ovirt-engine/keys/apache.p12 >
> > /etc/pki/ovirt-engine/certs/apache.cer
> > # openssl pkcs12 -passin "pass:PASSWORD" -nocerts -nodes -in
> > /etc/pki/ovirt-engine/keys/apache.p12 >
> > /etc/pki/ovirt-engine/keys/apache.key.nopass
> > # chmod 0600 /etc/pki/ovirt-engine/keys/apache.key.nopass
> > # systemctl restart ovirt-engine.service
> But after restarting the issue is the same.
>
> Any idea?
>
Maybe try to restart the apache HTTP Server as well:
*systemctl restart httpd*
If it still doesn't work then please share the errors within the engine log
/var/log/ovirt-engine/engine.log
Thanks,
Sharon
> Thanks in advance
>
> Ángel.
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MPFXIEDZBFVC7JAOV77DCLDR3IVOSOMU/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SF4RZT5YKTSOT3IIS4U5LEYMIVVNB57Q/
[ovirt-users] Ovirt-engine , certificate issue
Hello,
I've a issue when I try log in ovirt-engine manager with a browser. The
error message is:
PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed
The ovirt version is 4.4.5.11-1.
I follow the next commands for try resolve it.
# cp -a /etc/pki/ovirt-engine "/etc/pki/ovirt-engine.$(date "+%Y%m%d")"
# SUBJECT="$(openssl x509 -subject -noout -in
/etc/pki/ovirt-engine/certs/apache.cer | sed 's/subject= //')"
# /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache
--password="PASSWORD" --subject="${SUBJECT}"
# openssl pkcs12 -passin "pass:PASSWORD" -nokeys -in
/etc/pki/ovirt-engine/keys/apache.p12 >
/etc/pki/ovirt-engine/certs/apache.cer
# openssl pkcs12 -passin "pass:PASSWORD" -nocerts -nodes -in
/etc/pki/ovirt-engine/keys/apache.p12 >
/etc/pki/ovirt-engine/keys/apache.key.nopass
# chmod 0600 /etc/pki/ovirt-engine/keys/apache.key.nopass
# systemctl restart ovirt-engine.service
But after restarting the issue is the same.
Any idea?
Thanks in advance
Ángel.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MPFXIEDZBFVC7JAOV77DCLDR3IVOSOMU/
[ovirt-users] Re: OVA Import Fail
Once I upgraded my engine and nodes it seemed to work, thank you Liran. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N7OF2WF4QJNNBQC3XPBBRIALRTUV72JU/
[ovirt-users] getting grafana back connect database (to be able to upgrade ovirt again)
Hi after upgrade from ovirt-4.4 -> ovirt 4.5 We had to face the jdbc problem and that we had old database enties which prohibited an upgrade. I had dropped all dbs and restored from engine backup but now I get the following error when I want to upgrade again [root@ovirt-engine ~]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20220517153716-whf2lg.log Version: otopi-1.10.0 (otopi-1.10.0-1.el8) [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220517153716-whf2lg.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220517153720-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed the log shows: RuntimeError: Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 2022-05-17 15:37:20,461+0200 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment setup': Cannot connec t to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 How can I get grafana to connect to database again? With kinde regards Moritz ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JAAVH6RTT7B73QOJLFP7LA2HZJEXN5U2/
[ovirt-users] Re: OVA Import Fail
On Fri, May 13, 2022 at 7:21 AM Abe E wrote:
> Anyone getting issues with OVA Imports on 4.4?
> I exported this from ovirt back in March although now importing again it
> is failing.
>
> My engine logs show it erroring out here:
> Command, return: StatusReturn:{status='Status [code=0, message=Done]'},
> log id: 7f970c1f
> 2022-05-12 17:14:40,396-06 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) []
> EVENT_ID: USER_ADD_DISK_TO_VM_FINISHED_SUCCESS(97), The d
> isk Nextgen-CC-Tools_Disk1 was successfully added to VM
> Nextgen-CC-Tools.
> 2022-05-12 17:14:40,678-06 INFO
> [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] Running command: ExtractOvaComman
> d internal: true. Entities affected : ID:
> 66ff7ebd-7682-4b94-b98d-5ceb76661830 Type: VM
> 2022-05-12 17:14:40,691-06 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] START, PrepareImageVDSCom
> mand(HostName = ovirt-2.removed.com,
> PrepareImageVDSCommandParameters:{hostId='0fbd6429-9c91-44d7-8d50-dcc08c8301f9'}),
> log id: 6915fcb6
> 2022-05-12 17:14:40,731-06 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] FINISH, PrepareImageVDSCo
> mmand, return: PrepareImageReturn:{status='Status
> [code=0, message=Done]'}, log id: 6915fcb6
> 2022-05-12 17:14:46,893-06 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] EVENT_ID: ANSIBLE_RUN
> NER_EVENT_NOTIFICATION(559), Import OVA. Run import yaml
> on py3.
> 2022-05-12 17:14:46,918-06 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] EVENT_ID: ANSIBLE_RUN
> NER_EVENT_NOTIFICATION(559), Import OVA. Set facts.
> 2022-05-12 17:14:49,936-06 ERROR
> [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] Command 'org.ovirt.engine.core.bl
> l.exportimport.ExtractOvaCommand' failed:
> Task Run extraction script failed to execute. Please check logs for more
> details:
> /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20220512171440-ovirt-2.removed.com-192f636b-0dd4-4a61-a673-1b94
> 6d7e0b56.log
> 2022-05-12 17:14:49,936-06 ERROR
> [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68)
> [192f636b-0dd4-4a61-a673-1b946d7e0b56] Exception: org.ovirt.engine.core.
>
> common.utils.ansible.AnsibleRunnerCallException: Task Run extraction script
> failed to execute. Please check logs for more details:
> /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20220512171440-ovirt-2.removed.com-192f636b-0dd4-4a61-a6
> 73-1b946d7e0b56.log
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleRunnerHttpClient.processEvents(AnsibleRunnerHttpClient.java:251)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:227)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:74)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:51)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand.runAnsibleImportOvaPlaybook(ExtractOvaCommand.java:129)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand.executeVmCommand(ExtractOvaCommand.java:79)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VmCommand.executeCommand(VmCommand.java:178)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1174)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1332)
> at
> deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2010)
> at
>
