[ovirt-users] Re: How to install and configure the monitoring portal ?
On Wed, Jan 6, 2021 at 10:17 AM tommy wrote: > > You mean that : It's recommended to inst all VDSM and ovirt engine on > separate server ? Either that, or use hosted-engine. > Just like hosted engine ? In that way, the engine is installed on vm, and the > vdsm is installed on vm hosts. > > But, my env not using hosted-engine, I use the standalone mode. Can I > separate the VDSM and engine on the standalone mode ? If you want to use oVirt on a single physical machine, and not use hosted-engine, you have to create multiple separate VMs on it (using e.g. virt-install/virt-manager) - one for the engine, one or more others for hosts, perhaps one for storage, etc. Best regards, -- Didi ___ 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/DXATIYM37NFNLIF4TQTSUKP7NMVSYLUA/
[ovirt-users] Re: How to install and configure the monitoring portal ?
You mean that : It's recommended to inst all VDSM and ovirt engine on separate server ? Just like hosted engine ? In that way, the engine is installed on vm, and the vdsm is installed on vm hosts. But, my env not using hosted-engine, I use the standalone mode. Can I separate the VDSM and engine on the standalone mode ? -Original Message- From: ybard...@redhat.com On Behalf Of Yedidyah Bar David Sent: Wednesday, January 6, 2021 4:04 PM To: tommy Cc: users Subject: Re: [ovirt-users] Re: How to install and configure the monitoring portal ? On Wed, Jan 6, 2021 at 9:32 AM tommy wrote: > > OK, I got it. > > But ,after I reconfig, I found that is VDSM.service status is not right. > > Is there any problem ? Sorry, I have no idea. You seem to run vdsm and engine on the same machine, right? This is called all-in-one, and is not supported (used to be, until 3.6, several years ago). Generally speaking, it's likely due to one of two things that engine-setup might have done: 1. changed some configuration 2. updated some packages You can check its log to see what it did. > > > > > [root@ooengh1 ~]# systemctl status vdsmd.service ● vdsmd.service - > Virtual Desktop Server Manager >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor > preset: enabled) >Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; > 2min 9s ago > Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh > --post-stop (code=exited, status=0/SUCCESS) > Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh > --pre-start (code=exited, status=1/FAILURE) > > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop > Server Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, > scheduling restart. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server > Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated > too quickly for vdsmd.service Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: > Failed to start Virtual Desktop Server Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# systemctl start vdsmd.service Job for vdsmd.service > failed because the control process exited with error code. See "systemctl > status vdsmd.service" and "journalctl -xe" for details. > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# journalctl -xe > -- > -- The result is dependency. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start > failed with result 'dependency'. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job > for unit libvirtd.socket, ignoring: Invalid request descriptor Perhaps this is the problem? Did libvirtd.socket work before? Similarly for the others below. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job > for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan > 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 > 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 > 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit > libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 > ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit > libvirtd-admin.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 > ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit > libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 > ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling > restart. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Unit is masked. This is probably why it failed, but it's not clear what masked it. If it was also masked before engine-setup, then perhaps this isn't the reason for vdsmd's failure. If you want, you can try 'systemctl unmask $UNIT' for one of more of these and see if this helps. If you suspect that this is due to updated packages, perhaps check 'dnf history' and 'dnf history info $ID' to see what changed. To revert, you can try 'dnf history undo $ID'. Good luck and best regards, -- Didi ___ Users mailing list --
[ovirt-users] Re: How to install and configure the monitoring portal ?
On Wed, Jan 6, 2021 at 9:32 AM tommy wrote: > > OK, I got it. > > But ,after I reconfig, I found that is VDSM.service status is not right. > > Is there any problem ? Sorry, I have no idea. You seem to run vdsm and engine on the same machine, right? This is called all-in-one, and is not supported (used to be, until 3.6, several years ago). Generally speaking, it's likely due to one of two things that engine-setup might have done: 1. changed some configuration 2. updated some packages You can check its log to see what it did. > > > > > [root@ooengh1 ~]# systemctl status vdsmd.service > ● vdsmd.service - Virtual Desktop Server Manager >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor > preset: enabled) >Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; > 2min 9s ago > Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh > --post-stop (code=exited, status=0/SUCCESS) > Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh > --pre-start (code=exited, status=1/FAILURE) > > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop > Server Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, > scheduling restart. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server > Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated too > quickly for vdsmd.service > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop > Server Manager. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# systemctl start vdsmd.service > Job for vdsmd.service failed because the control process exited with error > code. See "systemctl status vdsmd.service" and "journalctl -xe" for details. > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# > [root@ooengh1 ~]# journalctl -xe > -- > -- The result is dependency. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start > failed with result 'dependency'. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered > failed state. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Invalid request descriptor Perhaps this is the problem? Did libvirtd.socket work before? Similarly for the others below. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd-ro.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd-ro.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd-ro.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd-admin.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Invalid request descriptor > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, > scheduling restart. > Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for > unit libvirtd.socket, ignoring: Unit is masked. This is probably why it failed, but it's not clear what masked it. If it was also masked before engine-setup, then perhaps this isn't the reason for vdsmd's failure. If you want, you can try 'systemctl unmask $UNIT' for one of more of these and see if this helps. If you suspect that this is due to updated packages, perhaps check 'dnf history' and 'dnf history info $ID' to see what changed. To revert, you can try 'dnf history undo $ID'. Good luck and best regards, -- Didi ___ 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/TOTFOYY62SDP5SAJOJ4B3JUECJEKP6KP/
[ovirt-users] Re: How to install and configure the monitoring portal ?
OK, I got it. But ,after I reconfig, I found that is VDSM.service status is not right. Is there any problem ? [root@ooengh1 ~]# systemctl status vdsmd.service ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; 2min 9s ago Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS) Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE) Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop Server Manager. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling restart. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server Manager. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated too quickly for vdsmd.service Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop Server Manager. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state. Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed. [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# systemctl start vdsmd.service Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details. [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# journalctl -xe -- -- The result is dependency. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-admin.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling restart. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd.socket, ignoring: Unit is masked. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-ro.socket, ignoring: Unit is masked. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-ro.socket, ignoring: Unit is masked. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd-admin.socket, ignoring: Unit is masked. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit libvirtd.socket, ignoring: Unit is masked. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server Manager. -- Subject: Unit vdsmd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vdsmd.service has finished shutting down. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: start request repeated too quickly for vdsmd.service Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop Server Manager. -- Subject: Unit vdsmd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit vdsmd.service has failed. -- -- The result is failed. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Dependency failed for MOM instance configured for VDSM purposes. -- Subject: Unit mom-vdsm.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mom-vdsm.service has failed. -- -- The result is dependency. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start failed with result 'dependency'. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered failed state. Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
[ovirt-users] Re: How to install and configure the monitoring portal ?
On Wed, Jan 6, 2021 at 8:51 AM tommy wrote: > > The version is 4.3.6, and it's not hosted engine. It was added in 4.4, sorry. See also recent thread on this list: [ovirt-users] oVirt 4.3 DWH with Grafana Best regards, -- Didi ___ 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/NW3EK6ABKA2YRHW6J4LB26TELAHC3WEP/
[ovirt-users] Re: How to install and configure the monitoring portal ?
It looks not function. [root@ooengh1 ~]# engine-setup --reconfigure-optional-components [ 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-20210106145124-7ru32c.log Version: otopi-1.8.3 (otopi-1.8.3-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- Set up Cinderlib integration (Currently in tech preview) (Yes, No) [No]: [ INFO ] ovirt-provider-ovn already installed, skipping. --== PACKAGES ==-- [ INFO ] Checking for product updates... [ INFO ] No product updates found --== NETWORK CONFIGURATION ==-- Setup can automatically configure the firewall on this system. Note: automatic configuration of the firewall may overwrite current settings. NOTICE: iptables is deprecated and will be removed in future releases Do you want Setup to configure the firewall? (Yes, No) [Yes]: [ INFO ] firewalld will be configured as firewall manager. --== DATABASE CONFIGURATION ==-- The detected DWH database size is 39 MB. Setup can backup the existing database. The time and space required for the database backup depend on its size. This process takes time, and in some cases (for instance, when the size is few GBs) may take several hours to complete. If you choose to not back up the database, and Setup later fails for some reason, it will not be able to restore the database and all DWH data will be lost. Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]: No [WARNING] Are you sure you do not want to backup the DWH database? A positive reply makes sense only if you do not need the data in DWH, or have some other, external means to restore it to a working state. Are you sure you do not want to backup the DWH database?(Yes, No) [No]: No The DWH Database will be backed up prior to upgrade. Perform full vacuum on the oVirt engine history database ovirt_engine_history@localhost? This operation may take a while depending on this setup health and the configuration of the db vacuum process. See https://www.postgresql.org/docs/10/sql-vacuum.html (Yes, No) [No]: ^C[ ERROR ] Failed to execute stage 'Environment customization': SIG2 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20210106145124-7ru32c.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20210106145233-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# [root@ooengh1 ~]# engine-setup --reconfigure-optional-components [ 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-20210106145236-bhsl50.log Version: otopi-1.8.3 (otopi-1.8.3-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- Set up Cinderlib integration (Currently in tech preview) (Yes, No) [No]: [ INFO ] ovirt-provider-ovn already installed, skipping. --== PACKAGES ==-- [ INFO ] Checking for product updates... [ INFO ] No product updates found --== NETWORK CONFIGURATION ==-- Setup can automatically configure the firewall on this system. Note: automatic configuration of the firewall may overwrite current settings. NOTICE: iptables is deprecated and will be removed in future releases Do you want Setup to configure the firewall? (Yes, No) [Yes]: [ INFO ] firewalld will be configured as firewall manager. --== DATABASE CONFIGURATION ==-- The detected DWH database size is 39 MB. Setup can backup the existing database. The time and space required for the database backup depend on its size. This process takes time, and in some cases (for instance, when the size is few GBs) may take several hours to complete. If you choose to not back up the database, and Setup later fails for some reason, it will not be able to restore the
[ovirt-users] Re: How to install and configure the monitoring portal ?
The version is 4.3.6, and it's not hosted engine. I'll have a try to run reconfigure-optional-com, thanks. -Original Message- From: ybard...@redhat.com On Behalf Of Yedidyah Bar David Sent: Wednesday, January 6, 2021 2:40 PM To: tommy ; Shirly Radco Cc: users Subject: Re: [ovirt-users] How to install and configure the monitoring portal ? On Wed, Jan 6, 2021 at 5:41 AM tommy wrote: > > Hi,everyone: > > > > There’s no monitoring portal in my oVirt env. > > > > How to install and configure it in additional ? Please provide some more details. Which version? How did you set up? Is it an upgrade, or a new setup? If it's a hosted-engine setup, then indeed grafana is not set up by default. Login to the engine machine and run there: engine-setup --reconfigure-optional-components This was done for this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1866780 We recently had another discussion about refining the condition. Not sure we have a bug for tracking this. Input is most welcome! Adding Shirly. Best regards, -- Didi ___ 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/4GBNGXKR2HSDN6MLVCJAB62U3UZR2SHL/
[ovirt-users] Re: How to install and configure the monitoring portal ?
On Wed, Jan 6, 2021 at 5:41 AM tommy wrote: > > Hi,everyone: > > > > There’s no monitoring portal in my oVirt env. > > > > How to install and configure it in additional ? Please provide some more details. Which version? How did you set up? Is it an upgrade, or a new setup? If it's a hosted-engine setup, then indeed grafana is not set up by default. Login to the engine machine and run there: engine-setup --reconfigure-optional-components This was done for this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1866780 We recently had another discussion about refining the condition. Not sure we have a bug for tracking this. Input is most welcome! Adding Shirly. Best regards, -- Didi ___ 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/K6OH3AQPICD433YRCNFCP5AJGD2DYR25/
