[ovirt-users] Re: engine-setup fails: "Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute"
On Thu, Jul 4, 2024 at 9:11 AM Yedidyah Bar David wrote: > On Wed, Jun 19, 2024 at 10:38 PM Brent S. wrote: > >> As a quick update to this: >> >> # ovirt-aaa-jdbc-tool >> >> >> Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false >> >> >> >> Jun 19, 2024 7:28:14 PM >> org.ovirt.engine.extension.aaa.jdbc.binding.cli.Cli main >> >> >> SEVERE: Unexpected Exception invoking Cli: Could not read properties >> from: /etc/ovirt-engine/aaa/internal.properties >> >> Which is, of course, the same message in the log. >> >> This is probably expected, since *engine-setup never actually created the >> file*: >> > > Are you sure about this? > > >> >> # ls -la /etc/ovirt-engine/aaa >> total 4 >> drwxr-xr-x. 2 root root6 Jun 19 19:27 . >> drwxr-xr-x. 18 root root 4096 Jun 19 19:27 .. >> # >> > > I guess you checked the above only after engine-setup failed/finished, > right? > > >> >> And: >> >> 2024-06-19 19:27:10,917+ DEBUG >> otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc >> plugin.execute:923 execute-output: >> ['/usr/share/ovirt-engine-extension-aaa-jdbc/dbscripts/schema.sh', '-s', >> '[REDACTED_REMOTE_DB_HOST]', '-p', '5432', '-u', >> '[REDACTED_REMOTE_DB_USER]', '-d', '[REDACTED_REMOTE_DB_NAME]', '-e', >> 'aaa_jdbc', '-l', '/root/ovirt-engine-setup.log', '-c', 'apply'] stderr: >> >> >> 2024-06-19 19:27:10,917+ DEBUG otopi.transaction >> transaction._prepare:61 preparing 'File transaction for >> '/etc/ovirt-engine/aaa/internal.properties'' >> 2024-06-19 19:27:10,917+ DEBUG otopi.filetransaction >> filetransaction.prepare:184 file >> '/etc/ovirt-engine/aaa/internal.properties' missing >> > > Indeed > > >> 2024-06-19 19:27:10,920+ DEBUG otopi.transaction >> transaction._prepare:61 preparing 'File transaction for >> '/etc/ovirt-engine/extensions.d/internal-authn.properties'' >> 2024-06-19 19:27:10,920+ DEBUG otopi.filetransaction >> filetransaction.prepare:184 file >> '/etc/ovirt-engine/extensions.d/internal-authn.properties' missing >> 2024-06-19 19:27:10,921+ DEBUG otopi.transaction >> transaction._prepare:61 preparing 'File transaction for >> '/etc/ovirt-engine/extensions.d/internal-authz.properties'' >> 2024-06-19 19:27:10,921+ DEBUG otopi.filetransaction >> filetransaction.prepare:184 file >> '/etc/ovirt-engine/extensions.d/internal-authz.properties' missing >> 2024-06-19 19:27:10,921+ DEBUG >> otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc >> plugin.executeRaw:808 execute: ('/usr/bin/ovirt-aaa-jdbc-tool', >> (...) >> >> Is this because I'm using remote databases for the DWH? I was under the >> impression this was supported, especially given that engine-setup prompts >> for the host and it is documented. >> > > I don't think that's related. > > If you grep ovirt-engine sources, you'll find internal.properties in: > > packaging/setup/ovirt_engine_setup/engine/constants.py: > > AAA_JDBC_CONFIG_DB = os.path.join( > OVIRT_ENGINE_SYSCONFDIR, > 'aaa', > 'internal.properties' > ) > > If you then grep for AAA_JDBC_CONFIG_DB, you see it in: > > packaging/setup/plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py: > > def _setupAuth(self): > self.environment[otopicons.CoreEnv.MAIN_TRANSACTION].append( > filetransaction.FileTransaction( > name=oenginecons.FileLocations.AAA_JDBC_CONFIG_DB, > ... > visibleButUnsafe=True, > Forgot to mention: You can check otopi sources:src/otopi/filetransaction.py to see what this means. > ... > def _setupAdminUser(self): > toolArgs = ( > oenginecons.FileLocations.AAA_JDBC_TOOL, > '--db-config=%s' % > oenginecons.FileLocations.AAA_JDBC_CONFIG_DB, > ) > ... > @plugin.event( > stage=plugin.Stages.STAGE_MISC, > name=AAA_JDBC_SETUP_ADMIN_USER, > after=( > oengcommcons.Stages.DB_SCHEMA, > oengcommcons.Stages.DB_CONNECTION_AVAILABLE, > oenginecons.Stages.CONFIG_EXTENSIONS_UPGRADE, > ), > before=( > oenginecons.Stages.CONFIG_AAA_ADMIN_USER_SET
[ovirt-users] Re: engine-setup fails: "Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute"
On Wed, Jun 19, 2024 at 10:38 PM Brent S. wrote: > As a quick update to this: > > # ovirt-aaa-jdbc-tool > > > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > > > > Jun 19, 2024 7:28:14 PM > org.ovirt.engine.extension.aaa.jdbc.binding.cli.Cli main > > > SEVERE: Unexpected Exception invoking Cli: Could not read properties from: > /etc/ovirt-engine/aaa/internal.properties > > Which is, of course, the same message in the log. > > This is probably expected, since *engine-setup never actually created the > file*: > Are you sure about this? > > # ls -la /etc/ovirt-engine/aaa > total 4 > drwxr-xr-x. 2 root root6 Jun 19 19:27 . > drwxr-xr-x. 18 root root 4096 Jun 19 19:27 .. > # > I guess you checked the above only after engine-setup failed/finished, right? > > And: > > 2024-06-19 19:27:10,917+ DEBUG > otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc > plugin.execute:923 execute-output: > ['/usr/share/ovirt-engine-extension-aaa-jdbc/dbscripts/schema.sh', '-s', > '[REDACTED_REMOTE_DB_HOST]', '-p', '5432', '-u', > '[REDACTED_REMOTE_DB_USER]', '-d', '[REDACTED_REMOTE_DB_NAME]', '-e', > 'aaa_jdbc', '-l', '/root/ovirt-engine-setup.log', '-c', 'apply'] stderr: > > > 2024-06-19 19:27:10,917+ DEBUG otopi.transaction > transaction._prepare:61 preparing 'File transaction for > '/etc/ovirt-engine/aaa/internal.properties'' > 2024-06-19 19:27:10,917+ DEBUG otopi.filetransaction > filetransaction.prepare:184 file > '/etc/ovirt-engine/aaa/internal.properties' missing > Indeed > 2024-06-19 19:27:10,920+ DEBUG otopi.transaction > transaction._prepare:61 preparing 'File transaction for > '/etc/ovirt-engine/extensions.d/internal-authn.properties'' > 2024-06-19 19:27:10,920+ DEBUG otopi.filetransaction > filetransaction.prepare:184 file > '/etc/ovirt-engine/extensions.d/internal-authn.properties' missing > 2024-06-19 19:27:10,921+ DEBUG otopi.transaction > transaction._prepare:61 preparing 'File transaction for > '/etc/ovirt-engine/extensions.d/internal-authz.properties'' > 2024-06-19 19:27:10,921+ DEBUG otopi.filetransaction > filetransaction.prepare:184 file > '/etc/ovirt-engine/extensions.d/internal-authz.properties' missing > 2024-06-19 19:27:10,921+ DEBUG > otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc > plugin.executeRaw:808 execute: ('/usr/bin/ovirt-aaa-jdbc-tool', > (...) > > Is this because I'm using remote databases for the DWH? I was under the > impression this was supported, especially given that engine-setup prompts > for the host and it is documented. > I don't think that's related. If you grep ovirt-engine sources, you'll find internal.properties in: packaging/setup/ovirt_engine_setup/engine/constants.py: AAA_JDBC_CONFIG_DB = os.path.join( OVIRT_ENGINE_SYSCONFDIR, 'aaa', 'internal.properties' ) If you then grep for AAA_JDBC_CONFIG_DB, you see it in: packaging/setup/plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py: def _setupAuth(self): self.environment[otopicons.CoreEnv.MAIN_TRANSACTION].append( filetransaction.FileTransaction( name=oenginecons.FileLocations.AAA_JDBC_CONFIG_DB, ... visibleButUnsafe=True, ... def _setupAdminUser(self): toolArgs = ( oenginecons.FileLocations.AAA_JDBC_TOOL, '--db-config=%s' % oenginecons.FileLocations.AAA_JDBC_CONFIG_DB, ) ... @plugin.event( stage=plugin.Stages.STAGE_MISC, name=AAA_JDBC_SETUP_ADMIN_USER, after=( oengcommcons.Stages.DB_SCHEMA, oengcommcons.Stages.DB_CONNECTION_AVAILABLE, oenginecons.Stages.CONFIG_EXTENSIONS_UPGRADE, ), before=( oenginecons.Stages.CONFIG_AAA_ADMIN_USER_SETUP, ), condition=lambda self: self.environment[ oenginecons.ConfigEnv.ADMIN_USER_AUTHZ_TYPE ] == self.AAA_JDBC_AUTHZ_TYPE, ) def _misc(self): # TODO: if we knew that aaa-jdbc package was upgraded by engine-setup # TODO: we could display summary note that custom profiles have to be # TODO: upgraded manually self._setupSchema() self._setupAuth() self._setupAdminUser() ... This means that: At STAGE_MISC, _misc calls _setupAuth, which creates this file, and then it calls _setupAdminUser which tries to use it. Latter fails, and engine-setup rolls back the MAIN_TRANSACTION, including removing the file. I'd start debugging this issue by: 1. Patching _setupAuth to wait (e.g. using dialog.queryBoolean, search the source for examples) after it creates the file, so that I can investigate it 2. Patching _setupAdminUser to wait after it runs the tool, so that I can try to investigate the failure - e.g. run it myself under strace, if the existing logging is not enough. You can try using the otopi plugin wait_on_error for this, instead of patching. Good luck and best regards, -- Didi ___
[ovirt-users] Re: /etc/pki/ovirt-engine/ca.pem is not on a local filesystem
Hi, On Tue, Nov 14, 2023 at 11:31 AM wrote: > Hi Didi, > > Thanks for the reply. > > Finally solved it by exporting LANG=C in the shell before running the > command. > > Seems that the "pki-enroll-request.sh" does this check: > >LOCK="${PKIDIR}/${CA_FILE}".pem >df -l "${LOCK}" 2> /dev/null | grep -q "File" || die "${LOCK} is not > on a local filesystem" > > However, if LANG is a different language than C, the output will vary > and the grep command will return empty. > > It's working now. Thanks. > Thanks for the update! You might want to push a patch to enforce the locale for the `df` command (e.g. 'LC_ALL=C df -l...'). There are a few such places scattered around the code, but nothing systematic - and I think we do want, in general, to have localized error messages, so can't do this "too-high" in the execution hierarchy. Best regards, > > El 2023-11-14 09:12, Yedidyah Bar David escribió: > > On Tue, Nov 14, 2023 at 10:49 AM wrote: > > > >> Hi, > >> > >> We're running oVirt 4.5.4, recently we got this alert: > >> > >> Engine's certification is about to expire at 2023-11-19. Please > >> renew > >> the engine's certification. > >> > >> So I'm trying to run: > >> > >> engine-setup --offline > >> > >> However, it fails with the following error: > >> > >> [ INFO ] Upgrading CA > >> [ INFO ] Renewing engine certificate > >> [ ERROR ] Failed to execute stage 'Misc configuration': Command > >> '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute > >> > >> Digging into the logs I can see this: > >> > >> 2023-11-14 08:36:22,848+ DEBUG > >> otopi.plugins.ovirt_engine_setup.ovirt_engine.pki.ca [1] > >> plugin.execute:926 > >> execute-output: ('/usr/share/ovirt-engine/bin/pki-enroll- > >> pkcs12.sh', > >> '--name=engine', '--password=**FILTERED**', > >> '--subject=/C=US/O=stic.ull.es/CN=fqdn.es [2]', '--san=DNS:fqdn.es > >> [3]', > >> '--keep-key') stderr: > >> Ignoring -days; not generating a certificate > >> /etc/pki/ovirt-engine/ca.pem is not on a local filesystem > >> Cannot sign request > >> > >> 2023-11-14 08:36:22,849+ DEBUG otopi.context > >> context._executeMethod:145 method exception > >> Traceback (most recent call last): > >> File "/usr/lib/python3.6/site-packages/otopi/context.py", line > >> 132, > >> in _executeMethod > >> method['method']() > >> File > >> > > > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > >> > >> line 753, in _miscUpgrade > >> self._enrollCertificates(True, uninstall_files) > >> File > >> > > > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > >> > >> line 360, in _enrollCertificates > >> shortLife=entry['shortLife'], > >> File > >> > > > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > >> > >> line 250, in _enrollCertificate > >> + (('--days=398',) if shortLife else ()) > >> File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line > >> 931, > >> in execute > >> command=args[0], > >> RuntimeError: Command > >> '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute > >> 2023-11-14 08:36:22,852+ ERROR otopi.context > >> context._executeMethod:154 Failed to execute stage 'Misc > >> configuration': > >> Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to > >> > >> execute > >> > >> However, the file exists and is on a local filesystem: > >> > >> # ll /etc/pki/ovirt-engine/ca.pem > >> -rw-r--r--. 1 root root 4516 jun 24 2015 > >> /etc/pki/ovirt-engine/ca.pem > > > > This does not prove that it's on a local filesystem - can be on nfs, > > and nfs > > locking is sometimes problematic, so we prevented that. See > > pki-enroll-request.sh. > > > >> Can someone shed some light about why is this failing and how to > >> solve > >> it, please? > > > > What output do you get for: > > df -l /etc/pki/ovirt-engine/ca.pem > > ? > > > > Best regards,-- > > Didi > > > > > > Links: > > -- > > [1] http://otopi.plugins.ovirt_engine_setup.ovirt_engine.pki.ca > > [2] http://stic.ull.es/CN=fqdn.es > > [3] http://fqdn.es > ___ > 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/YXTXJIEQRN2ZH77ZSBGW2UARPMYSPEG3/ > -- 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/HM24AGSKFJIHQYLMXZZG7LXIGPPJIJOU/
[ovirt-users] Re: /etc/pki/ovirt-engine/ca.pem is not on a local filesystem
On Tue, Nov 14, 2023 at 10:49 AM wrote: > Hi, > > We're running oVirt 4.5.4, recently we got this alert: > >Engine's certification is about to expire at 2023-11-19. Please renew > the engine's certification. > > So I'm trying to run: > >engine-setup --offline > > However, it fails with the following error: > >[ INFO ] Upgrading CA >[ INFO ] Renewing engine certificate >[ ERROR ] Failed to execute stage 'Misc configuration': Command > '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute > > Digging into the logs I can see this: > >2023-11-14 08:36:22,848+ DEBUG > otopi.plugins.ovirt_engine_setup.ovirt_engine.pki.ca plugin.execute:926 > execute-output: ('/usr/share/ovirt-engine/bin/pki-enroll- pkcs12.sh', > '--name=engine', '--password=**FILTERED**', > '--subject=/C=US/O=stic.ull.es/CN=fqdn.es', '--san=DNS:fqdn.es', > '--keep-key') stderr: >Ignoring -days; not generating a certificate >/etc/pki/ovirt-engine/ca.pem is not on a local filesystem >Cannot sign request > >2023-11-14 08:36:22,849+ DEBUG otopi.context > context._executeMethod:145 method exception >Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, > in _executeMethod >method['method']() > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > > line 753, in _miscUpgrade >self._enrollCertificates(True, uninstall_files) > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > > line 360, in _enrollCertificates >shortLife=entry['shortLife'], > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/pki/ca.py", > > line 250, in _enrollCertificate >+ (('--days=398',) if shortLife else ()) > File "/usr/lib/python3.6/site-packages/otopi/plugin.py", line 931, > in execute >command=args[0], >RuntimeError: Command > '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to execute >2023-11-14 08:36:22,852+ ERROR otopi.context > context._executeMethod:154 Failed to execute stage 'Misc configuration': > Command '/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh' failed to > execute > > However, the file exists and is on a local filesystem: > ># ll /etc/pki/ovirt-engine/ca.pem >-rw-r--r--. 1 root root 4516 jun 24 2015 /etc/pki/ovirt-engine/ca.pem > This does not prove that it's on a local filesystem - can be on nfs, and nfs locking is sometimes problematic, so we prevented that. See pki-enroll-request.sh. > > Can someone shed some light about why is this failing and how to solve > it, please? > What output do you get for: df -l /etc/pki/ovirt-engine/ca.pem ? 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/NYQANBPVRZFUPMCHZIVTB2M4SVSKGASG/
[ovirt-users] Re: oVirt 4.5.4-1: engine-setup does not renew certificates
On Thu, Sep 14, 2023 at 10:26 AM Lars Stolpe wrote: > > Hi, > I wanted to add short names to the webgui apache certificate. I followed > these instructions: > „Engine can be accessed using alternate host names (or IP addresses) that can > configured by adding a new configuration file (for example > /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf) with following > content: SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com" > The list of alternate names has to be listed separated by spaces. It's > possible to add also IP addresses of engine host, but using IP addresses > instead of DNS names is not considered to be a good practise. Run > engine-setup to generate new certificates.“ Where did you copy this from? > > Certificates where not renewed. How do i get engine-setup to renew the apache > certificate? engine-setup can renew certificates that were generated by itself, not any random cert. If you add new names to the engine using SSO_ALTERNATE_ENGINE_FQDNS, you usually use certs generated elsewhere, not ones from engine-setup. 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/NBUUWKIEQAOFXSUQDD4PQWOMOSBGHJAI/
[ovirt-users] Re: Trouble restoring + upgrading to ovirt 4.5 system after host crashed
Hi, On Tue, Aug 8, 2023 at 9:21 PM David Johnson wrote: > Good afternoon all, > > We had a confluence of events hit all at once and need help desperately. > Our Ovirt engine system recently crashed and is unrecoverable. Due to a > power maintenance event at the data center, 1/3 of our VM's are offline. > > I have recent backups from the engine created with engine-backup. > How do you run engine-backup for backups? What version? What OS? > > I installed a clean Centos 9 and followed the directions to install > the ovirt-engine . > > After I restore the backup, the engine-setup fails on the keycloak > configuration. > > *From clean system:* > > *Install: **(Observe failed scriptlet during install, but rom install > still succeeds)* > > [root@ovirt2 administrator]# dnf install -y ovirt-engine > Last metadata expiration check: 2:08:15 ago on Tue 08 Aug 2023 10:11:31 AM > CDT. > Dependencies resolved. > > = > Package Architecture > VersionRepository > Size > > = > Installing: > ovirt-engine noarch > 4.5.4-1.el9centos-ovirt45 > 13 M > Installing dependencies: > SuperLU x86_64 > 5.3.0-2.el9epel > 182 k > > (Snip ...) > > > > > > * Running scriptlet: ovirt-vmconsole-1.0.9-1.el9.noarch > > 60/425Failed to resolve allow statement at > /var/lib/selinux/targeted/tmp/modules/400/ovirt_vmconsole/cil:539Failed to > resolve AST/usr/sbin/semodule: Failed!* > > This might cause a problem later on, but I do not think it's related to your current issue. > > (Snip ...) > xmlrpc-common-3.1.3-1.1.el9.noarch >xorg-x11-fonts-ISO8859-1-100dpi-7.5-33.el9.noarch > zziplib-0.13.71-9.el9.x86_64 > > Complete! > > > *Engine-restore (no visible issues):* > > [root@ovirt2 administrator]# engine-backup --mode=restore > --log=restore1.log --file=Downloads/engine-2023-08-06.22.00.02.bak > --provision-all-databases --restore-permissions > Start of engine-backup with mode 'restore' > scope: all > archive file: Downloads/engine-2023-08-06.22.00.02.bak > log file: restore1.log > Preparing to restore: > - Unpacking file 'Downloads/engine-2023-08-06.22.00.02.bak' > Restoring: > - Files > > -- > Please note: > > Operating system is different from the one used during backup. > Current operating system: centos9 > Operating system at backup: centos8 > > I do not think this is the problem, but you might try as well on centos8. > > Apache httpd configuration will not be restored. > You will be asked about it on the next engine-setup run. > > -- > Provisioning PostgreSQL users/databases: > - user 'engine', database 'engine' > - user 'ovirt_engine_history', database 'ovirt_engine_history' > - user 'ovirt_engine_history_grafana' on database 'ovirt_engine_history' > > > Restoring: > - Engine database 'engine' > - Cleaning up temporary tables in engine database 'engine' > - Updating DbJustRestored VdcOption in engine database > - Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine > database > - Resetting HA VM status > > -- > Please note: > > The engine database was backed up at 2023-08-06 22:00:19.0 -0500 . > > Objects that were added, removed or changed after this date, such as > virtual > machines, disks, etc., are missing in the engine, and will probably require > recovery or recreation. > > -- > - DWH database 'ovirt_engine_history' > - Grafana database '/var/lib/grafana/grafana.db' > > No Keycloak DB restored. I guess it was not backed up, perhaps not even configured. > You should now run engine-setup. > Done. > [root@ovirt2 administrator]# > > > *Engine-setup :* > > [root@ovirt2 administrator]# 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-20230808124501-joveku.log > Version: otopi-1.10.3 (otopi-1.10.3-1.el9) > [ INFO ] The engine DB has been restored from a backup > > *[ ERROR ] Failed to execute stage 'Environment setup':
[ovirt-users] Re: Restoring HE Fails, engine-config cannot connect to database
Hi, On Thu, Jul 6, 2023 at 6:36 AM Levi Wilbert wrote: > > I am attempting to restore n HE backup to a fresh host (not previously in the > old environment) in order to restore our old environment but running into > issues during the deployment. > > Basically my goal is to remove and redeploy an existing HE back into its same > environment on a new storage domain. > > What I've done: > backed up HE from prior environment > Installed oVirt 4.5.10 on a fresh node that was not in the prior environment > Ran the redeployment: hosted-engine --deploy --restore-from-file= --4 > The script pauses the deployment (even tho I told it not to), Did it say why it stopped? Most likely, because engine-backup failed to restore. I suggest to investigate this part - check the engine-backup logs etc. Good luck! Best regards, > during this part I update /etc/dnf/dnf.conf w/ "exclude=ansible-core" since > once ansible-core is updated it breaks the deployment script w/ Python > incompatibilities. > > But I'm running into the following: > [ ERROR ] fatal: [localhost -> 192.168.222.158]: FAILED! => {"changed": true, > "cmd": "set -euo pipefail && engine-config -g DisableFenceAtStartupInSec | > cut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", "delta": > "0:00:01.296169", "end": "2023-07-05 11:29:14.101292", "msg": "non-zero > return code", "rc": 1, "start": "2023-07-05 11:29:12.805123", "stderr": > "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false", "stderr_lines": > ["Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false"], "stdout": "", > "stdout_lines": []} > > I see that it fails running the engine-config command on the new hosted > engine, but when I SSH to it and try running it, I get: > # engine-config -l > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > Connection to the Database failed. Please check that the hostname and port > number are correct and that the Database service is up and running. > > I haven't been able to find anything specifically for this area searching > through Google. Anyone have any idea where to go with this? > > > ___ > 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/Y3NWBM3BKSLEYGHIFCYYL56BPICFJCVA/ -- 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/BMD663IWLCCLZTOFZ2E64S5PCA6TM76F/
[ovirt-users] Re: oVirt Self-hosted Engine Deployment fails
Hi, Please see: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/DMCC5QCHL6ECXN674JOLABH36U2LVJLJ/ Sandro/Michal - perhaps we want to add something about this to the front/download pages on the website. Good luck and best regards, On Wed, Apr 26, 2023 at 1:17 AM destfinal--- via Users wrote: > > Hi, > > I am struggling to get an oVirt cluster setup (for a PoC with some > workstations) for the past more than one week and am getting nowhere. > Following is my environment: > > Machine: Dell Workstation with i7, 16G RAM, 256G (I have got couple of more > of this machine but could not getr beyond the first one) > OS: oVirt minimal > (https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.4-2022120615/el9/ovirt-node-ng-installer-4.5.4-2022120615.el9.iso) > Documentation followed: > https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#Installing_Red_Hat_Virtualization_Hosts_SHE_deployment_host > Cluster name chosen: my.cluster > First node host name: node1-ovirt.my.cluster > Engine VM name: ovirt-engine.my.cluster > > The documentation states that there should be resolvable DNS entries for both > the oVirt hosts *as well as* for the oVirt engine VM. I am a bit confused on > this as the VM will get a DHCP address only after running the 'hosted-engine' > script. What ip address should I have for the engine VM (say if I have my > engine host name as ovirt-engine.my.cluster)? If I have no entry for the > engine in the DNS I get the following error: > > [ ERROR ] Host name is not valid: ovirt-engine.my.cluster did not resolve > into an IP address > Please provide the FQDN you would like to use for the > engine. > Note: This will be the FQDN of the engine VM you are now > going to launch, > it should not point to the base host or to any other > existing machine. > Engine VM FQDN: > > So I simply added an entry for 'ovirt-engine.my.cluster' with a dummy value > 192.168.0.222 (this is an ip address on the host subnet; but the engine gets > a DHCP address from a different subnet from a virtual network from the host; > I dont understand this) which moves away from the above problem and goes all > the way (after providing the values for a few other questions) to hang at > > 'Wait for the host to be up' > > for a while and eventually fail with an error message: > > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is > not up, please check logs, perhaps also on the engine machine"} > > At this point a vm is running in the host. I logged on to the VM and searched > the logs and found the following line in the /var/log/ovirt-engine/engine.log: > > ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] > (EE-ManagedThreadFactory-engine-Thread-1) > [728b2edd-d13a-48c3-a2c1-42a66a5334c5] Exception: Task Install ovs failed to > execute. Please check logs for more details: > /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20230425210047-node1-ovirt.my.cluster-728b2edd-d13a-48c3-a2c1-42a66a5334c5.log > > and in the file > /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20230425210047-node1-ovirt.my.cluster-728b2edd-d13a-48c3-a2c1-42a66a5334c5.log > I found the following error: > > "msg" : "The conditional check 'cluster_switch == \"ovs\" or (ovn_central is > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter > requires python's netaddr be installed on the ansible controller\n\nThe error > appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: > Install ovs\n^ here\n" > > On the host (node1-ovirt.my.cluster) > === > the result of 'rpm -qa | grep netaddr' is 'python3-netaddr-0.8.0-5.el9.noarch' > > the ansible version is: > > ansible [core 2.14.0] > config file = /etc/ansible/ansible.cfg > configured module search path = ['/root/.ansible/plugins/modules', > '/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python3.9/site-packages/ansible > ansible collection location = > /root/.ansible/collections:/usr/share/ansible/collections > executable location = /usr/bin/ansible > python version = 3.9.14 (main, Sep 21 2022, 00:00:00) [GCC 11.3.1 20220421 > (Red Hat 11.3.1-2)] (/usr/bin/python3.9) > jinja version = 3.1.2 > libyaml = True > > # rpm -qi ovirt-engine-appliance > Name: ovirt-engine-appliance > Version : 4.5 > Release : 20221206125848.1.el9 > > > On the vm (ovirt-engine.my.cluster) > === > the result of 'rpm -qa | grep netaddr' is: > python3-netaddr-0.7.19-8.1.2.el8.noarch > python39-netaddr-0.7.19-8.1.2.el
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
Hi, Great job! Perhaps you'd like to post this somewhere more noticeable/findable? I'd love to say "E.g. on the oVirt blog", but I have absolutely no idea how that is updated. Adding Sandro... Best regards, On Thu, Mar 9, 2023 at 6:46 AM wrote: > > instead of downgrading microcode i did eventually enabled the needed CPU flag: > #> grubby --update-kernel=ALL --args="tsx=on" > #> grub2-mkconfig -o /etc/grub2.cfg > #> reboot > > Reverse changes after change the default CPU type of the cluster: > set host in maintenance > #> grubby --update-kernel=ALL --remove-args="tsx=on" > #> grub2-mkconfig -o /etc/grub2.cfg > #> reboot > ___ > 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/4OJIR7XJU3PKJSSIWOZ2AHRHKJZE23FZ/ -- 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/5ED3KTRUYANNMBOZ25F7ZPHMGNJVSMIH/
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
On Thu, Feb 16, 2023 at 12:19 PM wrote: > Almost... > The deploy went good, til this host was added. There is a bug that prevents > vdsm to read the local configuration. > I used RHEL 8.5 and did not update, because the latest update 7.9 made oVirt > 4.2 inoperable. So i decided to use the version mentioned in the > documentation. 8.5? Where? RHV officially supports only RHEL 8.6, AFAIR. oVirt is tested regularly on Stream, so should most likely work on 8.7, or 8.8 when available. > > Update vdsm and back to square 1 Not sure what you mean. vdsm is on the host, not on the engine vm. -- 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/M3GMM76GUICHLTTYTWXLCYOSCFEVM22P/
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
On Wed, Feb 15, 2023 at 2:16 PM wrote: > > well, that's interesting... > The deploy abortion did not destroy the local runing VM as usual. When was it usual to destroy it? I think it remains up since at least 4.3, perhaps much longer. > So i disabled CentOS-Stream-PowerTools.repo again (was re-enabled by deploy), Did you try to check where/when/what does this? Perhaps on the host on /var/log/ovirt-hosted-engine-setup, not on the engine VM itself > and provided my modified oVirt repositories. > > I ran engine-setup on the running local VM, setup checked for updates, engine-setup also has an option '--offline'. Running HE deploy with offline should also use this. > nothing to be done, and then running fine through the complete setup. Now i > have a local VM engine running fine, the hosts are recognized as "up" , VMs > and storage domains are fine as well. Good! > > Is there a way to make the deploy jump to that stage and resume? Definitely not easily. If you just want to try this as a learning game, you can try. If you want to automate this, or plan for production, I'd use a different approach. > > Or: can i do the engine-setup(with restore or without) myself after providing > my modified repositories? There is no way to skip engine-setup and let you run it manually. You can provide before/after hooks. > If the deploy finds nothing to be updated, all should run afterwards? In principle yes, and this might be a good approach - replace all repos with yours (e.g. in a before hook), make sure yours do not include a release package that will overwrite your repos. > > Since this is the test for upgrading the production i should not depend on "i > hope the local VM is still running after deploy abort" Agreed, in principle. > > All i could find in engine-setup log is, that the repository could not be > reached. 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/LQSBX6X462RFOJH4LR5QIV463XPX2SSK/
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
On Wed, Feb 15, 2023 at 12:41 PM wrote: > > The backed up system is the latest 4.3 and the install sources of 4.4 are > also the latest available. > > i used "offline" and "pause" , set up squid on the deploy host, modified the > repository files in the fresh temporary engine VM to point to our satellite. > It worked fine to the point the deploy denies that "offline" parameter and > updated the repository package, overwriting my changes... Sorry, I do not remember where this is done. Did you check the logs? > .and aborted due to a non reachable repository > > Maybe i could put the repository package on the ignore list. Maybe > > Providing an own OVA may be a solution. Install a VM, run engine setup to > install all neded packages, export as OVA and provide it to the deploy > process and let it refill the engine with my backup file. Is it as simple as > that? More-or-less yes, in principle. See also https://github.com/oVirt/ovirt-appliance/ . > > I need to upgrade to 4.5 soon anyways, a direct upgrade from 4.3 to 4.5 is > not possible i assume? Sorry, do not remember either... A quick search finds: https://bugzilla.redhat.com/show_bug.cgi?id=2087735 https://bugzilla.redhat.com/show_bug.cgi?id=2072881 https://github.com/oVirt/ovirt-engine/pull/244 So it might work. 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/KOE35SY2H7IYFWQVEG2MUGJXBGFIVQ5U/
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
On Tue, Feb 14, 2023 at 1:36 PM wrote: > > Hi, > thank you for your answer, your hints are helpful > > > Hi! > > > > On Tue, Feb 14, 2023 at 12:40 PM > > > It's not completely clear, what you are trying to do. I suppose you > > refer to hosted-engine deployment with --restore-from-file. > > > I do an upgrade vorm 4.3 to 4.4 according to the official oVirt upgrade guide. > the deploy command is as follow: > hosted-engine --deploy --restore-from-file=/root/backup_ovirtman13.bck OK. That's a hosted-engine upgrade. A standalone engine is somewhat different. > > > > > IIUC this code runs inside the engine VM, not the host, so your > > customizations on the host do not apply there. The appliance image > > used for creating the engine VM includes in itself a suitable > > ovirt-release package, which also includes the above failing repo. > > Does the engine VM (via the host it's running on) have direct access > > to the Internet? Or do you force all comm to go through your satellite > > proxy? > > > The hosts do not have direct access to the internet. The new engine have per > default no access to MAN either. > The 4.3 appliance did not need accass for installation, why would one change > that... Many software packages upgrade themselves during installation, I think that's more-or-less the norm these days - no? A concrete reason: If your current engine is newer than the one included in the appliance, engine-backup inside the appliance will refuse to restore your backup. Upgrading to the latest before running engine-backup mitigates this issue. > > > > Anyway, some ways you can try to overcome the situation: > > - Run it offline (--ansible-extra-vars=he_offline_deployment=true) > > - Provide a custom enginevm_before_engine_setup hook to patch the > > configuration. See e.g. how this is done in ovirt-system-tests [1]. > > - Pass (similarly to above) he_pause_before_engine_setup=true . Should > > work since 4.4.7, https://bugzilla.redhat.com/show_bug.cgi?id=1959273 > > . > > What is "offline deployment" doing different, are the necessary packets > transferred internally? In this context, it means it's "offline" - does not require Internet access. In practice it means that whatever that's included in the appliance is going to be used for setup/deployment, without updating. You are welcome to search ovirt-engine-appliance source code for he_offline_deployment, to see the actual details - they are not that many. > > > > - See also [2] > > > > [1] https://github.com/oVirt/ovirt-system-tests Search the code for > > 'proxy', 'socks', etc. > > [2] > > https://github.com/didib/ovirt-ansible-collection/tree/master/roles/hoste... > > > > > > Good luck and best regards, > > Can the management bridge switched to another interface after installation? > That opens up some easier ways to enable access to repositories. The point where your deployment failed is before using the management bridge configured by the engine - it's a more-or-less the default 'default' libvirt network. > I know, that in 4.3 is is not possible to do that. > > ...i miss the option to install the engine during deploy with OS .iso file ;) At the time I also felt bad about this. Now, I can easily say it was worth it. The number of issues/problems that people ran into after we introduced the appliance and removed the option to do this manually greatly diminished, IMO. > > at least that pause parameter will give me the chance to fix the repositories Good luck, -- 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/FDKZSZWWKL7PDKI7TUIOSMOWLKOHTZT7/
[ovirt-users] Re: oVirt 4.4 hosted engine deploy fails - repository issues
Hi! On Tue, Feb 14, 2023 at 12:40 PM wrote: > > Hi, > I want to upgrade oVirt 4.3 to oVirt 4.4. Thus i have to reinstall one node > to EL8 an deploy the engine with restore. It's not completely clear, what you are trying to do. I suppose you refer to hosted-engine deployment with --restore-from-file. > > i get this error message at deploy: > [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] > [ ERROR ] fatal: [localhost -> 192.168.2.143]: FAILED! => {"changed": false, > "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-ceph-pacific': > Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving > data from the peer for > http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=storage-ceph-pacific > [Recv failure: Connection reset by peer]", "rc": 1, "results": []} > > Since i do use our satellite server, this URL is not included in the > repositories i provided. A repository named 'ovirt-4.4-centos-ceph-pacific' > is deinitely provided and available. > How do i get the deploy to use the correct repositories? IIUC this code runs inside the engine VM, not the host, so your customizations on the host do not apply there. The appliance image used for creating the engine VM includes in itself a suitable ovirt-release package, which also includes the above failing repo. Does the engine VM (via the host it's running on) have direct access to the Internet? Or do you force all comm to go through your satellite proxy? Anyway, some ways you can try to overcome the situation: - Run it offline (--ansible-extra-vars=he_offline_deployment=true) - Provide a custom enginevm_before_engine_setup hook to patch the configuration. See e.g. how this is done in ovirt-system-tests [1]. - Pass (similarly to above) he_pause_before_engine_setup=true . Should work since 4.4.7, https://bugzilla.redhat.com/show_bug.cgi?id=1959273 . - See also [2] [1] https://github.com/oVirt/ovirt-system-tests Search the code for 'proxy', 'socks', etc. [2] https://github.com/didib/ovirt-ansible-collection/tree/master/roles/hosted_engine_setup#make-changes-in-the-engine-vm-during-the-deployment > > I hope someone can help me out, 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/NUL42RNRZZ3KCAMTFWCCF3IHVAKLYTCH/
[ovirt-users] Re: Error when deploy Ovirt4.4 Hosted Engine
On Sun, Feb 12, 2023 at 10:39 PM wrote: > > Hello, I get error, need help. > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The conditional check 'not > ipv6_deployment|bool and route_rules_ipv4.stdout | from_json | > selectattr('priority', 'equalto', 100) | selectattr('dst', 'equalto', > virbr_cidr_ipv4 | ipaddr('address') ) | list | length == 0' failed. The error > was: error while evaluating conditional (not ipv6_deployment|bool and > route_rules_ipv4.stdout | from_json | selectattr('priority', 'equalto', 100) > | selectattr('dst', 'equalto', virbr_cidr_ipv4 | ipaddr('address') ) | list | > length == 0): 'dict object' has no attribute 'dst'\n\nThe error appears to be > in > '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': > line 81, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\nchanged_when: > true\n - name: Add IPv4 inbound route rules\n^ here\n"} A wild guess: The code adds a rule to the routing policy table, with priority 100 and dst equal to your IP address, but tries to do this only if it's not already done. But in reality it was probably never tested on a machine already having a rule with priority 100 and no 'dst'. Perhaps that's your case? What's the output of: $ ip -j rule | jq '' If it includes a rule with priority 100 and no 'dst', and if you can remove it, or add a 'dst', perhaps try that. Perhaps create an issue on the ovirt-ansible-collection project with all relevant details. 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/MX5OVWZQE4UEYYDIKMV5C5QHNHRFXL4E/
[ovirt-users] Re: Ovirt Hosted Engine - Offline Deployment
On Mon, Feb 6, 2023 at 8:22 PM wrote: > > Hi Team, > > I need some help deploying Ovirt Hosted Engine. I have installed Ovirt Node > 4.5.4 on my intel NUC as a small development environment for a bigger project. > > I am not able to connect the NUC to the internet but am able to download any > relevant packages onto a hard drive and connect this to the system. > > I have attempted to deploy Hosted Engine via the CLI with the following > command: "hosted-engine --deploy --4 > --ansible-extra-vars=he_offline_deployment=true". This Fails as it is unable > to resolve the URL for the mirror? I feel as though I must be missing some > pre-deployment step which changes the repo path but my knowledge in this area > is definitely not where it needs to be. I've trolled through the internet but > cant find any sort of documentation which details the involved steps. > > Does anyone have any knowledge on how do accomplish this with my previously > mentioned restrictions? Please provide more details - what did you install, what did you run, what was the error message, relevant snippets from relevant logs, etc. Thanks. It might be enough to pre-install the appliance package. 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/7HQX5O3OXDY6XBUHZ4J2CYCHSRGCCD4W/
[ovirt-users] Re: I need the deploy script to wait for fixing network configuration manually in oVirt 4.3.10
On Wed, Jan 25, 2023 at 1:17 PM wrote: > > Hi, > i'm planing to upgrade our production environment from oVirt 4.3 to 4.4. > So i do need a fresh oVirt 4.3 installation to test the procedure before > doing it in production. > > The command line deploy script can't handle network interfaces correctly. If > i use either a single NIC oder a bond (active/passive) i get the error > message "The selected network interface is not valid". > If i predefine the management bridge to a running state, the deploy process > goes on, but fails to activate the added host and removes the already running > engine vm. > The deploy process fails to synchronize the existing working network > configuration with the engine configuration. > I can already log in to the engine GUI and see, that the bridge "ovirtmgmt" > needs to be assigned to the bonding IF, but i'm not fast enough to do so, > because the deployment process ist already shutting down and erasing the vm. > > I do see the following ways to succeed: > 1. make the depoyment process accept the given interfaces (maybe ignore > errors) > 2. make the deploy process wait for me to take necessary actions before > checking the engine > > Do anyone know, how to achieve this? > > All i need is a running engine on hosted_storage... any other issues i can > fix later. > > Another idea is to use one of the destined hosts as a bare metal engine, add > hosts, backup the engine and use that backup for a hosted engine restore > deploy, since the deploy script asks to wait after local vm is ready, but > only if i do a recovery deploy. You are right that in 4.3 it only asked whether to pause if you were restoring. But IIUC you can force it to pause by adding to your answer file 'OVEHOSTED_CORE/pauseonRestore=bool:True', regardless. 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/4U4PVODXQ5ODX6YT7443FJ6NGZ5I67HW/
[ovirt-users] Re: Host Reboot Timeout of 10 Minutes
On Wed, Jan 25, 2023 at 2:08 AM Peter H wrote: > > I'm working in a group that maintains a large oVirt setup based on 4.4.1 > which works very well. We are afraid of upgrading and prefer setting up a new > installation and gradually enlist the hosts one by one into the new > installation. > > We have tried 4.4.10 and 4.5.1 - 4.5.4 based on CentOS Stream 8, Rocky 8, > Alma Linux 9.1 with various problems. Worst was the problem that the rpm db > ended up in a catch-22 state. > > Using Alma Linux 9.1 and current oVirt 4.5.4 seems promising as no rpm > problems are present after installation. We have only one nuisance left which > we have seen in all installation attempts we have made since 4.4.10. When > rebooting a host it takes 10 minutes before it's activated again. In 4.4.1 > the hosts are activated a few seconds after they have booted up. > > I have found the following in the engine log: > 2023-01-24 23:01:57,564+01 INFO > [org.ovirt.engine.core.bll.SshHostRebootCommand] > (EE-ManagedThreadFactory-engine-Thread-1513) [2bb08d20] Waiting 600 seconds, > for server to finish reboot process. > > Our ansible playbooks for deployment times out and we could increase the > timeout but how come that this 10 minutes delay has been introduced? > > Does a config file exist where this timeout can be set to a lower value? I intended to provide a short reply just pointing out what value to change, then realized this might not be helpful, so decided to give up and not reply. Then I decided to take this opportunity and write the following. For background, please see: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/HEKKBM6MZEKBEAXTJT45N5BZT72VI67T/ . You do not need to be a developer, to search and read source code. One of the biggest advantages of FOSS is that you can do this, even without knowing how to write/update it. My main work in oVirt was in packaging/setup/backup/restore, not in the engine itself or vdsm - the two main parts of the project. But I know enough to guess that the error message you got is from the engine. I already have the engine source code git cloned on my laptop, so grepped it for 'for server to finish reboot', and found this in backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/VdsCommand.java: private void sleepOnReboot(final VDSStatus status) { int sleepTimeInSec = Config. getValue(ConfigValues.ServerRebootTimeout); log.info("Waiting {} seconds, for server to finish reboot process.", sleepTimeInSec); Even without knowing Java, ServerRebootTimeout seems relevant. grepping for this, finds it also in: packaging/dbscripts/upgrade/pre_upgrade/_config.sql:582:select fn_db_add_config_value('ServerRebootTimeout','600','general'); packaging/dbscripts/upgrade/pre_upgrade/_config.sql:1460:-- Increase default ServerRebootTimeout from 5 to 10 minutes packaging/dbscripts/upgrade/pre_upgrade/_config.sql:1461:select fn_db_update_default_config_value('ServerRebootTimeout', '300', '600', 'general', false); where it's set and then updated, and in: packaging/etc/engine-config/engine-config.properties:119:ServerRebootTimeout.description="Host Reboot Timeout (in seconds)" packaging/etc/engine-config/engine-config.properties:120:ServerRebootTimeout.type=Integer where it's exposed to engine-config. So if all you want is to get this error message earlier, this should be enough. However, I also checked the git log (or blame, if you want, but I prefer the log) for the former file, trying to understand when and why it was changed from 5 to 10 minutes. 'git log -u packaging/dbscripts/upgrade/pre_upgrade/_config.sql' and then searching for 'ServerRebootTimeout' finds https://github.com/oVirt/ovirt-engine/commit/d324bbdd . This links at https://bugzilla.redhat.com/1947403 . That one sadly does not provide many more details. It does show that it was done in 4.4.6. So I can only guess that one of two things happened: 1. Someone complained that hosts become non-operational e.g. because their boot sequence/POST/whatever takes more than 5 minutes. Perhaps this was rare enough to be reported and handled only recently (two years ago, and not, say, 10). (Although I personally managed machines that needed more than 5 minutes to reboot, or even just test the RAM - but that's indeed rare). 2. Something else changed, and made this less comfortable. E.g. perhaps the engine didn't move them in the past to non-operational and now does, or something like that. Not sure which of these, it at all. You are welcome to change it to some low value using engine-config and see if it helps. If it's "just enough", you should notice no difference from previous versions. If it's not enough, you might indeed see different behavior and then decide how to continue - I can think of a few ways: 1. Just set it to slightly more than your own machines' reboot times, and decide that's, where you might need to manually activate a host after reboot if i
[ovirt-users] Re: ovirt upgrade - Failed to execute stage 'Misc configuration' FATAL: Ident authentication failed for user "root" (SOLVED)
On Tue, Jan 24, 2023 at 11:04 AM marek wrote: > > its all on one machine > > i'm not sure if grafana was used in 4.4.4 (dashboard was working) > > after repeated engine-setup and playing with > > /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf > > OVESETUP_GRAFANA_CORE/enable=bool:True Was it False? I think the failure you described can only happen if it's True. > OVESETUP_GRAFANA_CORE/grafanaDbCreatedByUs=none:None > OVESETUP_DWH_CORE/enable=bool:True Can't see how the last two settings can affect your issue. Perhaps you changed other things? > > its "somehow" solved now Fine, but if it's due to changes around pg_hba.conf, you might face other issues later on - around backup/restore, integrating other things, etc. Thanks for the update! Best regards, > > Dne 24/01/2023 v 08:37 Yedidyah Bar David napsal(a): > > Hi, > > > > On Tue, Jan 24, 2023 at 1:47 AM marek wrote: > >> upgrade from ovirt 4.4.4 to 4.5.5 > > Please provide more details, thanks. > > > > Is everything set up on the same machine - engine, dwh, grafana? > > If on separate machines, what's where and how was it set up? > > Did you have grafana already set up in 4.4.4? > > Do you have any custom local changes? > > > >> engine-setup > >> > >> 2023-01-24 00:35:17,885+0100 DEBUG otopi.context > >> context._executeMethod:145 method exception > >> Traceback (most recent call last): > >> File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, > >> in _executeMethod > >> method['method']() > >> File > >> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/db/default_privileges.py", > >> line 51, in _misc_set_default_privileges > >> user=self.environment[ogdwhcons.GrafanaDBEnv.USER], > >> File > >> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > >> line 1808, in setDefaultPrivilegesReadOnlyForUser > >> ownConnection=True, > >> File > >> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > >> line 249, in execute > >> database=database, > >> File > >> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > >> line 182, in connect > >> sslmode=sslmode, > >> File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line > >> 127, in connect > >> conn = _connect(dsn, connection_factory=connection_factory, > >> **kwasync) > >> psycopg2.OperationalError: FATAL: Ident authentication failed for user > >> "root" > >> FATAL: Ident authentication failed for user "root" > > This might be due to changes in /var/lib/pgsql/data/pg_hba.conf . Please > > check/ > > share it. Thanks. > > > > 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/AUGH6LZCSJWRU55OH6MSLJXZX55NKATT/
[ovirt-users] Re: ovirt upgrade - Failed to execute stage 'Misc configuration' FATAL: Ident authentication failed for user "root"
Hi, On Tue, Jan 24, 2023 at 1:47 AM marek wrote: > > upgrade from ovirt 4.4.4 to 4.5.5 Please provide more details, thanks. Is everything set up on the same machine - engine, dwh, grafana? If on separate machines, what's where and how was it set up? Did you have grafana already set up in 4.4.4? Do you have any custom local changes? > > engine-setup > > 2023-01-24 00:35:17,885+0100 DEBUG otopi.context > context._executeMethod:145 method exception > Traceback (most recent call last): >File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, > in _executeMethod > method['method']() >File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/db/default_privileges.py", > line 51, in _misc_set_default_privileges > user=self.environment[ogdwhcons.GrafanaDBEnv.USER], >File > "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > line 1808, in setDefaultPrivilegesReadOnlyForUser > ownConnection=True, >File > "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > line 249, in execute > database=database, >File > "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", > line 182, in connect > sslmode=sslmode, >File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line > 127, in connect > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > psycopg2.OperationalError: FATAL: Ident authentication failed for user > "root" > FATAL: Ident authentication failed for user "root" This might be due to changes in /var/lib/pgsql/data/pg_hba.conf . Please check/ share it. Thanks. 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/M6M4KN3YNOATAYY3IWV2ZTUEMCHLOPWN/
[ovirt-users] Re: Updating the DNS configuration for the Hosted Engine
On Thu, Jan 12, 2023 at 2:15 PM nathan.english--- via Users wrote: > > Hi All, > > I've had a look through the documentation and not been able to find any up to > date information on how to do this. > > We've now built a permanent DNS solution and need to update the Hosted Engine > DNS server details. Luckily, I have managed to update the hosts configuration > using the Data Center Settings so it's just the Hosted Engine to complete. > > Any advice on where should I update? I didn't want to update the if config > file, as I assumed it's controlled by ansible somewhere! Do you refer to -ha's dns monitor? This is done by calling 'dig' without specifying a server, so it uses (by default) your system-wide settings, usually in /etc/resolv.conf. If you meant to ask about something else, please clarify. 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/5ZJMM3NVH5Q2D3OWOUUNEA4GF3MGUQI6/
[ovirt-users] Re: Bug in the engine-backup script when no attached TTY -- Easy fix
On Wed, Jan 18, 2023 at 9:09 AM wrote: > > That is very useful. You are right; I was assuming a non-attached TTY; > however, it could very well be a closed/re-directed stdout. The NetBackup > client does fun things with stdout/stderr for logging and data transfer. I > will run some tests tomorrow to check. > > The scenario is quite simple. The NetBackup client runs a pre-script on > backup. I use this pre-script with dump-able databases (oVirt, MythTV, > Unifi, etc..) like this to create the backup file, then the backup program > scoops up the generated file(s), and finally the post script cleans up. The > pre-script is just calling: > > /usr/bin/engine-backup --mode=backup --file=$outf --log=$outl --scope=all > > You are right about output being run earlier, so yes it should have caused > problems earlier? I only tested at the very end. From the code: > > do${MODE} > ec="$?" > log "EC: ${ec}" > > output "Done." > > ec="$?" > log "EC: ${ec}" > > The exit code was 0 in the first one, but flipped to 1 after the output line. > What I didn't test was what it looks like right after the earlier output > lines. It could be the case that it gets set to 1, but then gets reset to 0 > by the actual backup, before anything tests for it again (or it's time to > exit). > > And I had tried a "2>&1 >/dev/null" wrap before, and tried to run it from > cron -- none of which I could get to work either. I will play around some > more. Good luck! No idea if this is relevant, but see this excerpt from the bash(1) man page: Note that the order of redirections is significant. For example, the command ls > dirlist 2>&1 directs both standard output and standard error to the file dirlist, while the command ls 2>&1 > dirlist directs only the standard output to file dirlist, because the standard error was duplicated from the standard output before the standard out‐ put was redirected to dirlist. 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/LBHVNOWY3VE3VP6TGBCETRBPC3RTC2J7/
[ovirt-users] Re: Bug in the engine-backup script when no attached TTY -- Easy fix
On Tue, Jan 17, 2023 at 11:37 PM wrote: > > The output() function. This line: > > printf "%s\n" "${m}" > > It will fail if there is no attached TTY, Are you sure it requires an attached _TTY_? Not merely stdout? It indeed requires a TTY in certain cases (see readdbpassword) but not in the common ones. > which will set the exit code to 1, which in turn will trigger the cleanup() > function notifying the engine that the backup failed. > This ironically happens when it should be writing "Done." Doesn't it use 'output' much earlier, thus failing much earlier? E.g. here: output "Start of engine-backup with mode '${MODE}'" > and exiting after a successful backup. Fix I used was to change it to: > > printf "%s\n" "${m}" >> "${LOG}" This is redundant - 'output' already writes to the log. > > You can't assume attached TTY Well, if we want to be able to input passwords safely, we need a tty. For common cases, we indeed do not, and do not assume it. We do indeed assume stdout. Almost all 'normal' programs do. E.g.: $ date >&- date: write error: Bad file descriptor $ echo $? 1 When needing to run such programs without stdout, you usually wrap them, e.g.: $ (date > /dev/null) >&- $ echo $? 0 > since a lot of people like me want to run this as part of a pre/post script > to an automated backup program. Please clarify your case. If it's a shell script that's calling engine-backup, can't this script redirect the output? E.g. to /dev/null, if you never look at it? If you provide this script directly to some backup program that does not provide an stdout (meaning, executes it with FD 1 closed), you indeed have to handle this somehow. I'd personally do this by creating a trivial one-line wrapper script and point the backup program to the wrapper. That said, I'd consider such behavior a bug in the calling backup program. I'd expect such a program to provide an stdout to the pre-/post- programs it calls, keep the output sent there, and log it to its own logs. When things fail, it will be so much easier for the user to investigate stuff if you can see the engine-backup output in the caller's log. (But admit that when I was a sysadmin and used such programs, I always wrote my own wrappers around them, and not vice-versa. I realize this isn't always the best choice or even possible). Hope this helps. If you still think there is a real bug, please provide more details. Thanks 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/DO6O4C5RJGW2O3DKQ5AY2WYGYZTS53XE/
[ovirt-users] Re: Preferred way to give customer access to VMs
On Fri, Jan 13, 2023 at 9:51 AM wrote: > > Hi. Just for an introduction, I'm a junior staff working on a way to deploy a > KVM cluster to provision VMs to our customer. Before this, we're using VMware > ESXi and connect it to OpenNebula as the console that we give to customers. > > We're moving to KVM due to VMware licensing cost. I've successfully deployed > an oVirt cluster and currently able to access it remotely via a VPN that I've > setup on a virtualized pfSense VM inside the cluster. > > My question is, what is the best way to give customer console access to the > VMs that we provisioned for them? Surely we doesn't want to give them access > to our VPN for security reasons. You can try running ovirt-websocket-proxy on a separate machine. You can also use independent tools - e.g. squid/varnish/apache httpd/nginx - as reverse proxies. I think you can find on the net examples showing how to do that with oVirt. 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/QJPIBXTR3QJQU2NXDXG7TODJ4XXSEA34/
[ovirt-users] Re: Regenerate DWH ovirt_engine_history
On Mon, Jan 2, 2023 at 2:33 PM Diego Ercolani wrote: > > Finally it worked: > After the step previous described: > 1. put cluster in global maintenance > 2. stop ovirt-engine and ovirt-engine-dwhd > 3. in the table dwh_history_timekeeping @enginedb I changed the dwhUuid > 4. launched engine-setup, the engine-setup asked to disconnect a "fantomatic" > DWH (I answered "YES") > 5. engine setup reconfigure things and set back the dwhUuid to the previous > state > 6. stopped ovirt-engine and ovirt-engine-dwhd because I saw that in the same > table I had timestamp in the future (year 2177), This might hint at the issue. I do not know the relevant logic well, sorry. Perhaps you had some local time issue which caused this line to be written? Perhaps there is then logic to not update/ignore/whatever stuff that's written "in the past". Anyway, good catch! > so I removed the erroneous timestamp (putting to [NULL]) > 7. in the /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log I saw: > Setting a value for the key "lastErrorSent" has failed. Error message: null > Setting a value for the key "lastErrorSent" has failed. Error message: null > so I put in "consistent" value: > > This is my set: > INSERT INTO public.dwh_history_timekeeping (var_name,var_value,var_datetime) > VALUES > ('dwhHostname','ovirt-engine.ovirt',NULL), > ('dwhUuid','53878f7e-cb3d-45cc-9edf-9e389414ce6e',NULL), > ('lastSampling',NULL,'2023-01-02 13:32:00.2+01'), > ('lastSync',NULL,'2023-01-02 13:31:00+01'), > ('lastErrorSent','2023-01-02 12:47:15.318 +0100','2023-01-02 > 12:47:15.318+01'), > ('lastOsinfoSync','2023-01-02 12:47:15.318 +0100','2023-01-02 > 12:47:15.318+01'), > ('lastFullHostCheck','2001-01-01 02:01:00.000 +0100','2023-01-02 > 13:03:00+01'), > ('lastOsinfoUpdate','2023-01-02 12:47:15.318 +0100','2023-01-02 > 12:47:15.318455+01'), > ('heartBeat',NULL,'2023-01-02 13:31:59.082+01'), > ('timesFailed','0',NULL); > INSERT INTO public.dwh_history_timekeeping (var_name,var_value,var_datetime) > VALUES > ('DwhCurrentlyRunning','1',NULL); 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/J6A7TKJ6CQTS3EB2SGDLH5XLHKJONVFZ/
[ovirt-users] Re: Regenerate DWH ovirt_engine_history
On Mon, Jan 2, 2023 at 1:38 PM Diego Ercolani wrote: > > I found the reference on that file: > https://github.com/oVirt/ovirt-dwh/blob/master/docs/Notes-about-single-dwhd I didn't remember I wrote it :-(. > > It's only to notice that I veryfied the contents of > dwh_history_timeskeeping table @engine db and the dwhUuid it's consistent > with the one in the 10-setup-uuid.conf file > > While ovirt-engine-dwh is running the value DwhCurrentlyRunning is correctly > set to "1" and when I issue > systemctl stop ovirt-engine-dwhd the parameter is set to 0, so the dwhd > correctly can talk with engine db... I suppose. > > The DisconnectDwh in the vdc_options table is correctly (?) set to its > default value "0" All looks good to me. Are you there was a problem (I saw your other mail saying you fixed it)? You get the very same log lines about the engine not updating statistics even if there is no problem at all - this is generally what happens on a new engine with no entities being updated, left doing nothing. 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/V2IVVEQEHULRBTY4UR3RRSXV4ECDRUEY/
[ovirt-users] Re: Regenerate DWH ovirt_engine_history
On Mon, Jan 2, 2023 at 12:09 PM Diego Ercolani wrote: > > Thank you for your infos. > > It's not the engine that is writing there, it's dwhd. The engine only > > reads. Did you check /var/log/ovirt-engine-dwh/ ? > What is confusing me are these line in > /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log > lastErrorSent|2011-07-03 12:46:47.00 > etlVersion|4.5.7 > dwhAggregationDebug|false > dwhUuid|53878f7e-cb3d-45cc-9edf-9e389414ce6e > ovirtEngineHistoryDbDriverClass|org.postgresql.Driver > ovirtEngineHistoryDbPassword|** > 2022-12-30 > 21:45:01|6kFI8I|Yi5fBA|8mXcq0|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can > not sample data, oVirt Engine is not updating the statistics. Please check > your oVirt Engine status.|9704 > 2022-12-30 > 22:00:01|HuESUa|Yi5fBA|8mXcq0|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can > not sample data, oVirt Engine is not updating the statistics. Please check > your oVirt Engine status.|9704 > 2022-12-30 > 22:15:01|i99aVI|Yi5fBA|8mXcq0|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can > not sample data, oVirt Engine is not updating the statistics. Please check > your oVirt Engine status.|9704 The process is like this: 1. The engine routinely updates its own database 2. dwhd reads the engine DB. If it notices updates, it updates its own DB. If it does not, after some time it emits the above lines to the log. Perhaps the problem is that dwhd fails to look at the engine DB? Or uses wrong creds? They are in /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf , keys starting with ENGINE_DB_ (those starting with DWH_DB_ are for its own db). > > > > > > What you did might be enough, in principle, but we do not have it > > documented/tested, IIRC. > It should be a "nice to have feature" We had it open for many years but never finished... https://bugzilla.redhat.com/show_bug.cgi?id=1060529 https://bugzilla.redhat.com/show_bug.cgi?id=1781095 > > > > How did you remove ovirt_engine_history? Did you remove both db and > > user? And lines from pghba.conf? > > > > You might need to remove also > > /etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf , before > > running engine-setup. That's the file the engine uses to get > > credentials for the dwh db. > I noticed that engine-setup wrote the correct credentials even if you don't > remove the file > > > > Good luck and best regards, > I decided to restart the clean process using your info so, I'm going to trace > what I do during the process in the following lines: > 1. put the cluster in global maintenance > 2. systemctl stop ovirt-engine-dwhd, systemctl stop ovirt-engine, systemctl > stop grafana-server > 3. verify what process i using the dwh db: SELECT * FROM pg_stat_activity > where datname='ovirt_engine_history'; > 4. "Clean" the database: DROP DATABASE ovirt_engine_history; DROP ROLE > ovirt_engine_history; DROP ROLE ovirt_engine_history_grafana; > 5. "Clean" the setup environment: > > --- /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf.bak 2022-12-30 > 12:52:19.810983574 + > +++ /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf 2023-01-02 > 09:48:43.642373549 + > @@ -19,10 +19,10 @@ > OVESETUP_CONFIG/adminUserId=str:9c1af7f1-5795-432a-b971-9883e0bed76d > OVESETUP_OVN/ovirtProviderOvn=bool:True > OVESETUP_OVN/ovirtProviderOvnId=str:e6b92384-b112-40e0-8d6f-2c6e4536cd1a > -OVESETUP_DWH_CORE/enable=bool:True > +OVESETUP_DWH_CORE/enable=bool:False > OVESETUP_DWH_CONFIG/remoteEngineConfigured=bool:False > OVESETUP_DWH_CONFIG/scale=str:2 > -OVESETUP_GRAFANA_CORE/enable=bool:True > +OVESETUP_GRAFANA_CORE/enable=bool:False > OVESETUP_GRAFANA_CORE/grafanaDbCreatedByUs=none:None > OVESETUP_KEYCLOAK_CONFIG/ovirtAdminUser=str:admin@ovirt > OVESETUP_VMCONSOLE_PROXY_CONFIG/vmconsoleProxyConfig=bool:True > > rm /etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf > > --- /var/lib/pgsql/data/pg_hba.conf.bak 2023-01-02 09:52:34.153904851 + > +++ /var/lib/pgsql/data/pg_hba.conf 2023-01-02 09:53:08.784158670 + > @@ -82,14 +82,6 @@ > > # "local" is for Unix domain socket connections only > local all all peer > -hostovirt_engine_history ovirt_engine_history_grafana 0.0.0.0/0 > md5 > -hostovirt_engine_history ovirt_engine_history_grafana ::0/0 > md5 > -hostovirt_engine_history ovirt_engine_history 0.0.0.0/0 md5 > -hostovirt_engine_history ovirt_engine_history ::0/0 md5 > hostengine engine 0.0.0.0/0 md5 > hostengine engine ::0/0 md5 > # IPv4 local connections: > @@ -99,18 +91,9 @@ > # Allow replication connections from localhost, by a user with the > # replication privilege. > local replication all peer > -hostovirt_engin
[ovirt-users] Re: Regenerate DWH ovirt_engine_history
Hi, On Sun, Jan 1, 2023 at 10:19 PM Diego Ercolani wrote: > > Hello to all and happy new year. > My question is "simple". > I need to "reset" the ovirt_engine_history database. > I tried to use: > engine-setup --reconfigure-optional-components > after removing: > - ovirt_engine_history > - set to "False" > OVESETUP_DWH_CORE/enable=bool:True > OVESETUP_GRAFANA_CORE/enable=bool:True > in /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf > > (obviously all in "Global Maintenance") > currently I have a system where I have an initialized ovirt_engine_history > but no engine is writing in it. It's not the engine that is writing there, it's dwhd. The engine only reads. Did you check /var/log/ovirt-engine-dwh/ ? > I tried to follow (in some manner): > https://www.ovirt.org/documentation/data_warehouse_guide/ > > In the ovirt engine's log there is no exception... so I cannot address the > issue. > > I need help to reinitialize the db... I don't need the history.. only from > now on. What you did might be enough, in principle, but we do not have it documented/tested, IIRC. How did you remove ovirt_engine_history? Did you remove both db and user? And lines from pghba.conf? You might need to remove also /etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf , before running engine-setup. That's the file the engine uses to get credentials for the dwh db. 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/M6WIKDORRUIUKK3U6Y6N7CHWMN2DVPFJ/
[ovirt-users] Re: Certificate expiration w/o warning on all clients. Cluster in zombie state
On Tue, Dec 27, 2022 at 6:18 PM Gilboa Davara wrote: > > Hello, > > On Tue, Dec 27, 2022 at 8:40 AM Yedidyah Bar David wrote: >> >> > Add issue https://github.com/oVirt/ovirt-engine/issues/784 >> >> Sorry, I do not follow. Is your immediate obstacle being that >> engine-setup refuses to continue, saying "Hosted Engine HA is in >> Global Maintenance mode."? >> >> You can cause it to ignore this test by passing >> 'OVESETUP_CONFIG/continueSetupOnHEVM=bool:True' (in the answer file or >> --otopi-environment). >> >> We recently added an option 'engine-setup >> --show-environment-documentation', exactly for this env key, see also: >> >> https://bugzilla.redhat.com/show_bug.ccontinueSetupOnHEVM=bool:Truegi?id=1700460 >> >> Best regards, >> -- >> Didi >> > > I actually managed to bypass the check by editing he.py and deleting the > "raise" statement, preventing hosted-engine from bombing out because it > wasn't able to connect to the nodes. > From there I managed to renew the certificates (see second mail), and even > connected two of the 3 nodes successfully (I had to create new temporary vdsm > certificates, get them semi-connected to the engine, and then "re-enroll > certificates" from the UI. Once I had a limping cluster up, I shut everything > down cleanly, and... and redeployed the cluster from scratch. (with all the > failed attempts, my HE was completely busted). > That said, I wonder if having to short circuit the environment variable isn't > a bit over-complicated, given the considerable number of cert related issues. I do not think it's "over complicated" in any technical sense - just one command line to copy/paste from somewhere. I'd say it's mainly that knowing that this is the solution to your exact problem is the hard thing. > > But thanks for the heads-up. > > Q: I'm willing to try and document all the steps I did, in my semi-success > attempt to save my cluster. I think that would be great. > That said, I rather not document wrong / broken steps. Can anyone @RH review > my writeup? Sure! But consider how you intend to publish it. If as something like a blog post (on ovirt.org or your own blog or whatever), that's less "authoritative" and understandably more local/specific. If you consider integrating it into the official guides, that's more delicate. -- 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/ZS3GZUZZDFUUX4RR3KQT4BO6TQOXHYF4/
[ovirt-users] Re: Certificate expiration w/o warning on all clients. Cluster in zombie state
On Tue, Dec 27, 2022 at 8:39 AM Yedidyah Bar David wrote: > > On Sun, Dec 25, 2022 at 5:15 PM Gilboa Davara wrote: > > > > > > > > On Sun, Dec 25, 2022 at 12:37 PM Gilboa Davara wrote: > >> > >> On Sun, Dec 25, 2022 at 12:36 PM Gilboa Davara wrote: > >>> > >>> Hello all, > >>> > >>> Even though I do my best to keep track of the certificate issue date > >>> across my different clusters, I somehow missed the vdsm certificate > >>> expiration in one of my clusters. > >>> Now I have an active cluster with multiple nodes (self-hosted / gluster > >>> storage), vdsm service is down on all nodes (due to certificate > >>> expiration) - hence, I cannot get the cluster into global maintenance > >>> mode (vdsms are down), and I cannot access my engine (to renew the engine > >>> certificates / re-enroll hosts). > >>> How can manual renew the host certificate? > >>> > >>> Thanks, > >>> Gilboa > >> > >> > >> P.S. CentOS 8 Streams engine and host, ovirt v4.5.3 (I think). > >> > >> - Gilboa > > > > > > Managed to find an old email in this group (that I saved...) > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/56QU2AD7YUX2VZUP4NZMRFXK32MJM7QE/ > > > > This got the nodes working... but the engine (GRRR) still cannot connect to > > the nodes (I assume it has expired certs as well), hence, it cannot detect > > the cluster is in global maintenance mode, and cannot run engine-setup. > > > > Add issue https://github.com/oVirt/ovirt-engine/issues/784 > > Sorry, I do not follow. Is your immediate obstacle being that > engine-setup refuses to continue, saying "Hosted Engine HA is in > Global Maintenance mode."? > > You can cause it to ignore this test by passing > 'OVESETUP_CONFIG/continueSetupOnHEVM=bool:True' (in the answer file or > --otopi-environment). > > We recently added an option 'engine-setup > --show-environment-documentation', exactly for this env key, see also: > > https://bugzilla.redhat.com/show_bug.cgi?id=1700460 (BTW, I now see that I warned there against trying to parse the output, as it might change in the future - and that I indeed actually already "broke" it, https://github.com/oVirt/otopi/pull/22 . If anyone volunteers to enhance this - either add some override to otopi calling textwrap.wrap or perhaps some '--json' option or whatever, great!). -- 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/F6YJ5C23EAEFQSZ76DFCYOCFYLIWRMZT/
[ovirt-users] Re: Certificate expiration w/o warning on all clients. Cluster in zombie state
On Sun, Dec 25, 2022 at 5:15 PM Gilboa Davara wrote: > > > > On Sun, Dec 25, 2022 at 12:37 PM Gilboa Davara wrote: >> >> On Sun, Dec 25, 2022 at 12:36 PM Gilboa Davara wrote: >>> >>> Hello all, >>> >>> Even though I do my best to keep track of the certificate issue date across >>> my different clusters, I somehow missed the vdsm certificate expiration in >>> one of my clusters. >>> Now I have an active cluster with multiple nodes (self-hosted / gluster >>> storage), vdsm service is down on all nodes (due to certificate expiration) >>> - hence, I cannot get the cluster into global maintenance mode (vdsms are >>> down), and I cannot access my engine (to renew the engine certificates / >>> re-enroll hosts). >>> How can manual renew the host certificate? >>> >>> Thanks, >>> Gilboa >> >> >> P.S. CentOS 8 Streams engine and host, ovirt v4.5.3 (I think). >> >> - Gilboa > > > Managed to find an old email in this group (that I saved...) > https://lists.ovirt.org/archives/list/users@ovirt.org/message/56QU2AD7YUX2VZUP4NZMRFXK32MJM7QE/ > > This got the nodes working... but the engine (GRRR) still cannot connect to > the nodes (I assume it has expired certs as well), hence, it cannot detect > the cluster is in global maintenance mode, and cannot run engine-setup. > > Add issue https://github.com/oVirt/ovirt-engine/issues/784 Sorry, I do not follow. Is your immediate obstacle being that engine-setup refuses to continue, saying "Hosted Engine HA is in Global Maintenance mode."? You can cause it to ignore this test by passing 'OVESETUP_CONFIG/continueSetupOnHEVM=bool:True' (in the answer file or --otopi-environment). We recently added an option 'engine-setup --show-environment-documentation', exactly for this env key, see also: https://bugzilla.redhat.com/show_bug.cgi?id=1700460 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/L4KZTEI424WD7YU4W2WIT4LELEU2FPAZ/
[ovirt-users] Re: Manager GUI session timeout
On Wed, Dec 21, 2022 at 9:34 PM Diggy Mc wrote: > > How can I increase the session timeout of the oVirt Manager GUI v4.4 ??? I think UserSessionTimeOutInterval in engine-config. 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/Q4UR2RZWEO3HOVK5JPRYQWWDY3GPXZK3/
[ovirt-users] Re: what happens at vdsm host certificate expiration
On Mon, Dec 19, 2022 at 5:45 PM Vinz Vinz wrote: > > Hi DAvid, > > Do you see this parameter on your side? on my side I don't: > > $engine-config -a | grep -i validity > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > WebSocketProxyTicketValiditySeconds: 120 version: general > CertificationValidityCheckTimeInHours: 24 version: general > ImageTransferClientTicketValidityInSeconds: 300 version: general I didn't test on a live system, only checked the source code. I now see that it was exposed to engine-config only in 4.5. It was added to the database before that, I think in 4.4.5 or so. See if you have it in vdc_options, and if so, you can update it there, using /usr/share/ovirt-engine/dbscripts/engine-psql.sh . Please search the mailing list for examples about how to do that, thanks. 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/ZRRILYE5WV4D5DGVXPUEZR3ONZSQBI22/
[ovirt-users] Re: OVF_Store In Every Storage Doamin - Can We Remove?
On Tue, Dec 20, 2022 at 12:30 PM Benny Zlotnik wrote: > > You can't and shouldn't delete them as they are the VM backups. If you don't > want to see them, you can apply the `alias != ovf_store` filter in the search > bar in the disks views > > On Tue, Dec 20, 2022 at 12:23 PM Matthew J Black > wrote: >> >> Hi All, >> >> The Subject pretty much sums up the question I want to ask: There are two >> OVF_Store Disks created in all eight Storage Domains we have, making 16 >> total. This is cluttering up several of our views in the oVirt Admin >> Webpages. Is there anything stopping us from deleting some/all of these? You might also want to check, as background material: https://www.ovirt.org/develop/release-management/features/storage/importstoragedomain.html 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/Y3OEEO3JXTJMX527FOLI33R4BWJQHGD2/
[ovirt-users] Re: what happens at vdsm host certificate expiration
On Fri, Dec 16, 2022 at 1:06 PM Vinz Vinz wrote: > > Hi David, > > thx for your answer. > > I have tried this non official documentation because it was the clearest and > more straight forward I've found. > indeed it's not perfect in terme of security, but having to renew each year > so many different certificate across multiple cluster is really not > convenient. The first time we had a certificate expiration we were not ready > and long story short it brought us a production issue... > > indeed this doc doesn't mention vdsm, but the current start date of our vdsm > certificate is matching with the date where we applied this doc, so I was > quite suprised too, but it's definitively not related. Anyway we have a lot > of vdsm cert that will expire next year, and we should be ready. (ovirt > 4.4.10) > > I did a recent install of ovirt 4.5, and vdsm cert are valid for 5 years, > which is really better. > > with our 4.4.10 clusters, if we "enrol cert", it will again be for one year? > I guess the only way to have a bigger period would be to update our cluster > to 4.5? I think you can also change the default cert lifetime with engine-config, item VdsCertificateValidityInDays. Didn't test this myself. If it works, it should affect new certificates, not existing ones. 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/6IW7H6D2EGZFWO2QT72OL7ZDBWWTM4GY/
[ovirt-users] Re: what happens at vdsm host certificate expiration
Hi, On Thu, Dec 15, 2022 at 3:29 PM Vinz Vinz wrote: > > Hi Team, > > we are using a custom certificate on the engine apache GUI > /etc/pki/ovirt-engine/certs/apache.cer (following > https://myhomelab.gr/linux/2020/01/20/replacing_ovirt_ssl.html) I didn't know this doc so far, and am sorry if the doc on ovirt.org (linked from it) is not enough. Patches/questions/issues are welcome! I think it makes more sense to refine and perfect the "official" documentation than to have each of us write his own blog post with a "patch", unless it details specific/local issues that are not relevant for a general document but would still be useful for other people. >and it works fine. The certificate is valid for a very long period. (Good for maintenance minimization, not so good for security. But not the scope of current email...) > > It seems the vdsm certificate (/etc/pki/vdsm/certs/vdsmcert.pem), on hosts > side, has been renewed automatically at that time, but for only one year. "at that time", meaning by following the official doc? Or the above link? I didn't read it, but it does not mention "vdsm". Perhaps it wasn't exactly at that time, but due to some other update/action/whatever? You can try to correlate the cert start time with your (engine+vdsm) logs. Anyway, the hosts certs were indeed made shorter at some point, but then back longer. So it greatly depends what exact version you used while you touched them. See also this bug, and the linked patches: https://bugzilla.redhat.com/show_bug.cgi?id=2079835 I think the previous point was: https://bugzilla.redhat.com/show_bug.cgi?id=1824103 Meaning: Until 4.4.2 it was 1800 days, 4.4.3 to 4.5.0.6 it was 398 days, and since 4.5.0.7 it's 1827 days. You should see a large part of the relevant history, even if I am not sure all of it, but checking the git log of this file, searching for "days". I usually search a somewhat-upper subdirectory, e.g. "packaging" - good enough when searching locally with 'git log' (and 'less'), less convenient on a browser: https://github.com/mz-pdm/ovirt-engine/commits/master/packaging/bin/pki-enroll-request.sh > > Now we wonder, what will happen when the vdsm certificate will expire? hosts > will stop to be in the cluster? Not sure, I think they'll become non-responsive. Disclaimer: I am not an expert on engine<->vdsm comm. > if yes what should we do to avoid that? The standard approach is to move each host to maintenance, then "Enroll Cert" from the menu, then activate. > is there a possibility to also apply our custom cert as vdsm cert? No. > > This is for ovirt 4.4 running on rhel8 If 4.4 > 4.4.3, then indeed you got 398 days. But again, this isn't part of the apache cert replacement procedure - more likely you did 'Enroll Cert', or reinstalled, or something like that. Good luck, -- 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/NCWVNRNZ6TZWRTRIJ5W6UXBGPXZDTXAD/
[ovirt-users] Re: oVirt Biz Continuity Plan recovery Q/A
Hi, On Thu, Dec 15, 2022 at 10:12 AM Peter B via Users wrote: > > Hello all, I am looking into implemented a BCP plan with oVirt, which intends > to recover VMs from a secondary SAN LUN (containing VM snapshots from a > production oVirt cluster site which is considered to have crashed/burned) and > presented to the recovery site oVirt cluster.Since the production cluster > is expected to have crashed/burned unexpectedly, leaving the VMs snapshots on > the recovery SAN LUN (which is at a different site) intact. However since > there can be no Export Domain / Import Domain scenario, I need to know what > exact steps I need to perform to re-incorporate/re-hydrate the VMs from the > recovery LUN presented to the recover oVirt cluster / KVM hosts.I think > that normally an Import Domain offers a "VM Import" tab/option, while regular > or non-import Storage Domains don't have the "VM Import" option. I've been > trying to track down what exactly is needed in the way of specific steps > within the oVirt manager and KVM hosts, besides presenting the recovery SAN > LUN to > it. Did you check oVirt Disaster Recovery? See also: https://www.ovirt.org/documentation/disaster_recovery_guide/ https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/disaster_recovery 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/BZX4LE6OKVDQ3TZEPQ4A4WXDI5VTEJB3/
[ovirt-users] Re: Max network performance on w2019 guest
On Thu, Dec 1, 2022 at 10:35 AM Gianluca Cecchi wrote: > > On Thu, Dec 1, 2022 at 7:38 AM Yedidyah Bar David wrote: >> >> >> If the fault is on the "legacy" application, how can it achieve 5Gbs on >> vSphere? >> >> Best regards, >> -- >> Didi >> > > Yes, your considerations do make sense, Didi. > My main concern at the beginning was that there could be some limitation "at > the wire" with the virtio drivers in Windows. > But I think that the iperf2 test has removed this doubt, correct? I think so, yes. > Possibly there are other "inefficiencies" in the virtio driver, like what > experimented with the iperf3, so that the application works better with > vSphere than with oVirt. > Do you or other ones have any suggestions to dig into that eventually? Not sure. Perhaps ask on the virtio-win project. > Does it make sense to set the VM as a high performance one and test the > application again? > One thing I noticed is that at source the VM was configured as 4 vcpus with 4 > sockets, besides the hypervisors (both vSphere and oVirt) having 2 sockets. > Do you think it can have any performance impact? My intuition says it might affect performance, but I do not know the specifics well enough. > What could be the best vcpu configuration: 2 sockets and 2 cores each or 1 > socket and 4 cores? I can try to tweak also this config parameters and see Not sure. Perhaps check qemu/libvirt documentation/lists/etc. But perhaps the impact is not due to them but due to how Windows (and perhaps the application?) behaves based on the "available" cpu cores/sockets. E.g. Perhaps with physical 4 sockets compared to 2x2 - where if it was a physical machine, it would affect caching, I guess - Windows/app would optimize memory allocation/use differently. 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/6H3RMUQHZBVAFBB3X3NUW3BDBNSX6KKJ/
[ovirt-users] Re: oVirt Update Errors
On Tue, Dec 6, 2022 at 9:44 AM Martin Perina wrote: > > Hi, > > Please upgrade to oVirt 4.5.4 released yesterday, it supports > ansible-core-2.13 from EL8.7 or CS8. Sorry, I missed the announcement. I do not see ovirt-hosted-engine-setup > 2.6.6 in any of these: http://mirror.centos.org/centos/8-stream/virt/x86_64/ovirt-45/Packages/o/ https://cbs.centos.org/koji/packageinfo?packageID=1976 Perhaps there is some problem, perhaps related to the outage of CBS yesterday. Best regards, > > Martin > > > On Tue, 6 Dec 2022, 08:11 Matthew J Black, wrote: >> >> Hi Guys, >> >> Attempting to do a Cluster update via the oVirt GUI and I'm getting the >> following errors (taken from the logs) which I've confirmed via a straight >> `dnf update`: >> >> Problem 1: package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch conflicts >> with ansible-core >= 2.13 provided by ansible-core-2.13.3-1.el8.x86_64 >> - cannot install the best update candidate for package >> ovirt-hosted-engine-setup-2.6.6-1.el8.noarch >> - cannot install the best update candidate for package >> ansible-core-2.12.7-1.el8.x86_64 >> Problem 2: problem with installed package >> ovirt-hosted-engine-setup-2.6.6-1.el8.noarch >> - package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch conflicts with >> ansible-core >= 2.13 provided by ansible-core-2.13.3-1.el8.x86_64 >> - package ovirt-ansible-collection-3.0.0-1.el8.noarch requires >> ansible-core >= 2.13.0, but none of the providers can be installed >> - cannot install the best update candidate for package >> ovirt-ansible-collection-2.3.0-1.el8.noarch >> >> Is it OK to do a `dnf update --nobest` or a `dnf update --allowerasing` on >> each host, or is there some other solution that I'm missing? >> >> Cheers >> >> Dulux-Oz >> ___ >> 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/IECKJBPJKV5IBJMQRPBTUHQW5QDZ45P2/ > > ___ > 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/7BVX2U5QUU6J4DL5HL5VEPPHX32GDHGI/ -- 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/CDFVQTGCFZ3HIMUWOC722GTZVWWJE3SX/
[ovirt-users] Re: oVirt Update Errors
On Tue, Dec 6, 2022 at 9:11 AM Matthew J Black wrote: > > Hi Guys, > > Attempting to do a Cluster update via the oVirt GUI and I'm getting the > following errors (taken from the logs) which I've confirmed via a straight > `dnf update`: > > Problem 1: package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch conflicts > with ansible-core >= 2.13 provided by ansible-core-2.13.3-1.el8.x86_64 > - cannot install the best update candidate for package > ovirt-hosted-engine-setup-2.6.6-1.el8.noarch > - cannot install the best update candidate for package > ansible-core-2.12.7-1.el8.x86_64 > Problem 2: problem with installed package > ovirt-hosted-engine-setup-2.6.6-1.el8.noarch > - package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch conflicts with > ansible-core >= 2.13 provided by ansible-core-2.13.3-1.el8.x86_64 > - package ovirt-ansible-collection-3.0.0-1.el8.noarch requires ansible-core > >= 2.13.0, but none of the providers can be installed > - cannot install the best update candidate for package > ovirt-ansible-collection-2.3.0-1.el8.noarch > > Is it OK to do a `dnf update --nobest` or a `dnf update --allowerasing` on > each host, or is there some other solution that I'm missing? `dnf update --nobest` is OK. --allowerasing is not, generally speaking, unless you want to remove part of oVirt... This should be fixed when 4.5.3 is released, where ansible-core 2.13 should work. You can try nightly [1], if interested. [1] https://www.ovirt.org/develop/dev-process/install-nightly-snapshot.html 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/5Q3H2RAG6T2KY2VH5TAEGTYSPLEVBWGS/
[ovirt-users] Re: Max network performance on w2019 guest
On Thu, Dec 1, 2022 at 1:36 AM Gianluca Cecchi wrote: > > On Wed, Nov 30, 2022 at 11:52 AM Volenbovskyi, Konstantin > wrote: >> >> Hi, >> >> Not a direct answer – but I think something to consider: >> >> >> >> -I am not sure what virtio is there ‘out of box’, but I imagine that you >> need to check what is latest virtio-win package >> >> containing NetKVM driver. >> >> (https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/ >> ?) >> >> -I would imagine that main driver of higher virtio-net performance is >> support and use of multiqueue. >> >> I don’t know about Windows 2019 , maybe it is matter of configuration. >> >> >> >> Check out https://access.redhat.com/solutions/6638561 and >> https://github.com/virtio-win/kvm-guest-drivers-windows/issues/237 >> >> >> >> BR, >> >> Konstantin >> >> > > > Thanks for your input, Konstantin. > Some more context. > Vm was migrated from vSphere (using an external provider via network). > The VM has an application that communicates with an Oracle System on a second > server (VM) running Linux. > With the Windows VM on vSphere, with vmxnet3 driver, the network performance > of the application was about 5Gbs. > The Linux server is a VM on oVirt infra. > The reason to move the Windows VM to oVirt is to investigate if it can get > better performance. > But after the migration test it seems that the application network > performance is about 2Gbs, so far worse than on vSphere. > > After these application results above, some bare tests with iperf3 were done. > On oVirt Linux -> Linux with VMs on two different hypervisors network > performance is more than 9Gbs > Windows -> Linux on same hypervisor 2Gbs > Windows -> Linux on different hypervisor 1.5Gbs > Linux -> Windows almost 10Gbs > > As suggested from the links you provided I tried iperf2, using EPEL iperf rpm > for Linux VM and sourceforge iperf-2.1.8-win.exe for Windows. > With VMs on different hosts and transferring from Windows to Linux I got > 9.3Gbs > So the problem is not the driver itself or VM configuration but probably the > "legacy" application doesn't support multiqueue or any network performance > optimizations that are available in the driver. If the fault is on the "legacy" application, how can it achieve 5Gbs on vSphere? 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/OEOW37KFPUUUNCUZKIBJNPRZSO7JDCQ5/
[ovirt-users] Re: 2nd Self-Hosted Engine Node Not Attached To "ovirtmgmt" Network
Hi, On Thu, Nov 24, 2022 at 7:26 AM Matthew J Black wrote: > > Hi All, > > So, I've got the Self-Hosted Engine up and running on the first Host, and > everything *seems* to be working OK. > > I'm now attempting to use the Web UI to add a new ie 2nd (Self-Hosted Engine) > Host to the cluster. Everything *seems* to go OK except the 2nd Host is left > in a Non-Operational state (which I believe is "normal") awaiting the set up > of the Host Networks. > > Its here where things go wrong: the 2nd Host does not have the ovirtmgmt > Network attached (nor any of the others, for that matter). When I drag the > ovirtmgmt Network to the 2nd Host's pre-existing (and working) bond interface > the Engine works away for a while and then reports "Error while executing > action HostSetupNetworks: Unexpected exception". > > I have located (but have not yet read) these logs from the 2nd Host: > > - agent.log > - broker.log > > I have located (but have not yet read) these logs from the Engine: > > - engine.log > - > ovirt-host-deploy-ansible-20221124150742-ovirt_node_1.mynet.local-c26ca3fc-3c3f-4ee0-9562-fd7fd5066f8b.log > - > ovirt-host-deploy-ansible-20221124150742-ovirt_node_2.mynet.local-c26ca3fc-3c3f-4ee0-9562-fd7fd5066f8b.log > > Just to make things clear: > > - Both the Hosts are physically the same. Same brand/model of M/Board, NICS, > HDDs, ect. Same layout, etc > - The Web UI says that the 2nd Host's Bond is working AOK (as is the 1st Host) > - I can ssh into the 2nd Host fine. > > So my questions are: > > 1) Which other logs should I be looking at? /var/log/vdsm > 2) Has anyone else struck this issue before (I had a look through the mail > list archives, etc, and couldn't really find anything relevant - but as > always, I may be mistaken)? Searching the net for "ovirt HostSetupNetworks", as well as searching bugzilla for "HostSetupNetworks", finds many reports. Right now, your problem does not sound to me hosted-engine-specific. 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/QPQCLY3AZUDROROEFLOKEM74VULK7EZU/
[ovirt-users]Re: About oVirt’s future
On Mon, Nov 14, 2022 at 6:29 PM Strahil Nikolov wrote: > > Hey Didi, > > thanks for the recap. > I hope that soon I will have some free time and I can more actively involve > in the next months. Thanks! > > I would like to get some hints about the Ansible code. How do we test it ? Do you refer to [1] (engine-initiated, mainly host-deploy) or [2] (most of the rest)? I do not think there is any "unit-testing" for any of them. Much of the code there is tested as part of [3] - host-deploy code is ran by all suites there, HE-deploy by the he-basic suite, and some of the other ansible code by the ansible suite. [3] used to run on our jenkins server, and so I could (and did) point people to successful runs there (e.g. if there was a question about content of some log file or whatever), but now we don't, anymore. It does still run routinely in systems internal to Red Hat. Anyone can run it manually - and if you try and run into problems, please report :-). Thanks and best regards, [1] https://github.com/oVirt/ovirt-engine/tree/master/packaging/ansible-runner-service-project [2] https://github.com/oVirt/ovirt-ansible-collection/ [3] https://github.com/oVirt/ovirt-system-tests/ > > Best Regards, > Strahil Nikolov > > > > On Mon, Nov 14, 2022 at 9:14, Yedidyah Bar David > wrote: > Hi all, > > Red Hat Virtualization (RHV) recently entered maintenance phase[1], > and the RHV development team is gradually shifting its efforts over to > other projects. > > We are still around, subscribed to the mailing lists, answering > questions and help as needed. > > There is a strong trend in the industry towards containers and > microservices, and Red Hat's part of that is OpenShift. People that > want to use OpenShift and still need virtualization, until they > transition their workloads to run in containers, would best be served > by using OpenShift Virtualization. Following this, if you are an oVirt > user, you might want to try OKD Virtualization [2], the Community > Distribution of Kubernetes that powers Red Hat OpenShift, and Forklift > [3], a migration tool that facilitates the transition of VM workloads > from oVirt to OKD Virtualization. > > We worked hard over the last year or so on making sure the oVirt > project will be able to sustain development even without much > involvement from us - including moving most of the infrastructure from > private systems that were funded by/for oVirt/RHV, elsewhere - code > review from Gerrit to GitHub, and CI (Continuous Integration) from > jenkins to GitHub/Copr/CentOS CBS. > > We see lots of activity in the community both trying and using oVirt, > and helping each other, which is great! > > We also see some work done on basing oVirt on Rocky/Alma Linux, which > is also great! We’ll be happy to help with this, where our specific > expertise is needed. > > Ultimately, the future of oVirt lies in the hands of the community. If > you, as a community member, use and like oVirt, and want to see it > thrive, now is the best time to help with this! > > In particular, we welcome long-time, active members of this list to > join the list moderation team. If you want to help with this, please > contact me directly, or email ovirt-users at ovirt.org. > > I am posting this message to both lists - users and devel, separately > - deliberately not cross-posting. If you are subscribed to both, and > feel like replying, please choose the list that best matches the > content of your reply. Thanks! :-) > > Best regards, > > [1] https://access.redhat.com/support/policy/updates/rhev > > [2] https://docs.okd.io/latest/virt/about-virt.html > > [3] https://www.konveyor.io/tools/forklift/ > -- > 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/HEKKBM6MZEKBEAXTJT45N5BZT72VI67T/ -- 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/RVPQNFLFZOKJWZ5B2K75RWOM5KYPEKZH/
[ovirt-users]About oVirt’s future
Hi all, Red Hat Virtualization (RHV) recently entered maintenance phase[1], and the RHV development team is gradually shifting its efforts over to other projects. We are still around, subscribed to the mailing lists, answering questions and help as needed. There is a strong trend in the industry towards containers and microservices, and Red Hat's part of that is OpenShift. People that want to use OpenShift and still need virtualization, until they transition their workloads to run in containers, would best be served by using OpenShift Virtualization. Following this, if you are an oVirt user, you might want to try OKD Virtualization [2], the Community Distribution of Kubernetes that powers Red Hat OpenShift, and Forklift [3], a migration tool that facilitates the transition of VM workloads from oVirt to OKD Virtualization. We worked hard over the last year or so on making sure the oVirt project will be able to sustain development even without much involvement from us - including moving most of the infrastructure from private systems that were funded by/for oVirt/RHV, elsewhere - code review from Gerrit to GitHub, and CI (Continuous Integration) from jenkins to GitHub/Copr/CentOS CBS. We see lots of activity in the community both trying and using oVirt, and helping each other, which is great! We also see some work done on basing oVirt on Rocky/Alma Linux, which is also great! We’ll be happy to help with this, where our specific expertise is needed. Ultimately, the future of oVirt lies in the hands of the community. If you, as a community member, use and like oVirt, and want to see it thrive, now is the best time to help with this! In particular, we welcome long-time, active members of this list to join the list moderation team. If you want to help with this, please contact me directly, or email ovirt-users at ovirt.org. I am posting this message to both lists - users and devel, separately - deliberately not cross-posting. If you are subscribed to both, and feel like replying, please choose the list that best matches the content of your reply. Thanks! :-) Best regards, [1] https://access.redhat.com/support/policy/updates/rhev [2] https://docs.okd.io/latest/virt/about-virt.html [3] https://www.konveyor.io/tools/forklift/ -- 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/HEKKBM6MZEKBEAXTJT45N5BZT72VI67T/
[ovirt-users] Re: Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."
On Tue, Nov 1, 2022 at 3:14 PM Michal Skrivanek wrote: > > > > > On 1. 11. 2022, at 11:46, Matthew J Black wrote: > > > > Hi All, > > > > Long story short, I just tried to do a `hosted-engine --deploy` on a brand, > > new "out-of-the-box box", following the oVirt doco *exactly*, and while I > > got past my "Host is not up" issue, but almost exactly afterwards got this > > in my console (I've included the couple of lines leading up to the "Host is > > no up" step): > > > > ~~~ > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using > > username/password credentials] > > [ INFO ] ok: [localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be > > up] > > [ INFO ] ok: [localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a > > failure] > > [ INFO ] skipping: [localhost] Skipped, so this means that host_result_up_check (the check itself) didn't fail. > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set host_id] > > [ INFO ] ok: [localhost] This means that we entered the block "Emit error messages about the failure", which means all of the 3 "and-ed" conditions in its "when:" were true. Sadly, this (the block) isn't logged in itself - see [1] (and [2], a simple attempt at a workaround that I eventually gave up on). This means that we did get a host in the result, and that its status is "non_operational". [1] https://github.com/ansible/ansible/issues/33581 [2] https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/115775 > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect error events from > > the Engine] > > [ INFO ] ok: [localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Generate the error > > message from the engine events] > > [ INFO ] ok: [localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify with error > > description] > > [ INFO ] ok: [localhost] This means that the above tasks did manage to generate an "error_description", but that for some reason it was not output to your console. This is quite weird, I have no idea how this happened. I am confident I tested it back then [3], and also can find examples (very few) where it worked for others [4]. Incidentally, [4] does not include the task name "Notify with error description", and neither google finds it anywhere, but your output above does include it. [4] does include the actual text, but your output does not. Perhaps this is a change in ansible since then or something similar. Would you like to create a github issue in [5] about it? Something like "HE deployment gets stuck without details" or whatever, and add relevant parts of the logs. Thanks. [3] https://github.com/oVirt/ovirt-ansible-collection/pull/181 [4] https://lists.ovirt.org/archives/list/users@ovirt.org/thread/UZHD5KCPMKXOSPFK7E6JWA27H6SPHHO6/ [5] https://github.com/oVirt/ovirt-ansible-collection > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify with generic error] > > [ INFO ] skipping: [localhost] (This is another indication that we did manage to generate an error message) > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Let the user connect to > > the bootstrap engine to manually fix host configuration] > > [ INFO ] ok: [localhost] Again - the actual text is missing. > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] > > [ INFO ] ok: [localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create temporary lock > > file] > > [ INFO ] changed: [localhost -> localhost] > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Pause execution until > > /tmp/ansible.volt5pvv_he_setup_lock is removed, delete it once ready to > > proceed] > > ~~~ > > > > I didn't ask for script to pause, so I need to ask: Is this normal? > > No. I guess you did ask for that, maybe by mistake. The default is not to > pause. This isn't the case here - it paused due to a problem, but didn't emit details. Can you please check the logs in /var/log/ovirt-hosted-engine-setup? You most likely should be able to find the messages there, including the URL to the web admin if needed. > can you get to webadmin now and confirm th host state? > and/or just remove that file and let it continue... If you do that, it will shortly thereafter fail in the following task "Check if the host is up". > > Thanks, > michal > > > > > I'm about to have a look at the logs, but its late here at the moment so I > > wanted to get this up on the mailing lists so I don't loose too much time > > while I'm asleep and everyone else is awake (& vice-versa). Good luck, sorry for all the obstacles you bump into, 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:
[ovirt-users] Re: Wrong engine version grts installed
On Wed, Oct 26, 2022 at 3:53 PM Lev Veyde wrote: > Hi Didi, > > On Wed, Oct 26, 2022 at 2:34 PM Yedidyah Bar David > wrote: > >> On Wed, Oct 26, 2022 at 2:06 PM Lev Veyde wrote: >> >>> Hi Ada, >>> >>> Have pushed an updated version of the ovirt-engine-appliance package, it >>> should be propagated to all mirrors soon. >>> >>> You can also fetch it directly from: >>> >>> https://resources.ovirt.org/pub/ovirt-4.5/rpm/el8/x86_64/ovirt-engine-appliance-4.5-20221026100732.1.el8.x86_64.rpm >>> >>> Please test it and let me know if it works for you or you still >>> experience the same issue. >>> >> >> Thanks, Lev. Do we have the appliance/node build/release process >> documented? Can you update [1]? Thanks. >> >> It seems to me like we have two separate rpm repos for it - [2] for >> nightlies, [3] for releases. >> >> It seems like [2] is updated by a github action in the appliance git repo. >> >> Is [3] updated only manually? What's the process? >> >> > Yes, it's a manual process. > One needs to take the *right* packages from [1] and [2] and add it to the > ovirt-4.5 compose, so it will end up in [3]. > Can we perhaps make the upload action upload to a branch-specific subdirectory? This way, it will make it trivial to not confuse builds from master and ovirt-4.5 branches. And perhaps we should bump master to 4.6... Best regards, > > [1] > https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-appliance-4.5/el8/ > [2] > https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-appliance-4.5/el8-SRPMS/ > [3] https://resources.ovirt.org/pub/ovirt-4.5/rpm/el8/ > > > >> With jenkins it was somewhat more clear... (to me, anyway). >> >> > Yes, I know... > > >> [1] >> https://www.ovirt.org/develop/release-management/process/making-a-release.html >> >> [2] https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-appliance/ >> >> [3] https://resources.ovirt.org/pub/ovirt-4.5/rpm/el8/ >> >> >>> >>> Thanks in advance, >>> >>> >>> On Wed, Oct 26, 2022 at 12:38 PM Lev Veyde wrote: >>> >>>> Hi Ada, >>>> >>>> Thanks for letting us know about the issue. >>>> The issue seems to be with the latest ovirt-engine-appliance. >>>> We'll need to rebuild this and provide a fixed package. >>>> >>>> Thanks in advance, >>>> >>>> On Wed, Oct 26, 2022 at 11:04 AM ada per wrote: >>>> >>>>> Thank you for your reply, >>>>> Indeed I 1. Installed ovirt-node on some host 2. Ran there >>>>> 'hosted-engine --deploy' 3. Got an engine VM that includes the master >>>>> engine >>>>> >>>>> Regarding your questions >>>>> >>>>> *Did you install/upgrade any package manually, prior to >>>>> deploying?ovirt-engine-appliance? Anything else?* >>>>> I did not upgrade any packages prior to deploying >>>>> >>>>> What i did is: >>>>> I installed ovirt node host 4.5.3.1 without adding any packages >>>>> manually- it deployed master version# >>>>> i removed it and on a different host >>>>> I installed ovirt node host 4.5.3 without adding any packages >>>>> manually- it deployed master version# >>>>> i then removed it and install node 4.5.2 without adding any packages >>>>> manually- it deployed master version >>>>> i removed it and reinstall 4.5.2 and install engine packages >>>>> manually and still master version was deployed even though when >>>>> running >>>>> engine appliance install it says >>>>> ovirt-engine-appliance-4.5-20221018071047.1.el8.x86_64 >>>>> >>>>> *the results of the commands are as below:* >>>>> >>>>> *rpm -qa | grep release* >>>>> centos-release-nfv-common-1-3.el8.noarch >>>>> centos-release-gluster10-1.0-1.el8s.noarch >>>>> centos-release-virt-common-1-2.el8.noarch >>>>> centos-release-ovirt45-8.7-2.el8s.noarch >>>>> centos-stream-release-8.6-1.el8.noarch >>>>> centos-release-storage-common-2-2.el8.noarch >>>>> centos-release-opstools-1-12.el8.noarch >>>>> ovirt-release-host-node-4.5.2-1.el8.x86_64 >>>>> centos-release-ceph-pacific-1.0-2.el8.noarch >>>>&
[ovirt-users] Re: Wrong engine version grts installed
On Wed, Oct 26, 2022 at 2:06 PM Lev Veyde wrote: > Hi Ada, > > Have pushed an updated version of the ovirt-engine-appliance package, it > should be propagated to all mirrors soon. > > You can also fetch it directly from: > > https://resources.ovirt.org/pub/ovirt-4.5/rpm/el8/x86_64/ovirt-engine-appliance-4.5-20221026100732.1.el8.x86_64.rpm > > Please test it and let me know if it works for you or you still experience > the same issue. > Thanks, Lev. Do we have the appliance/node build/release process documented? Can you update [1]? Thanks. It seems to me like we have two separate rpm repos for it - [2] for nightlies, [3] for releases. It seems like [2] is updated by a github action in the appliance git repo. Is [3] updated only manually? What's the process? With jenkins it was somewhat more clear... (to me, anyway). [1] https://www.ovirt.org/develop/release-management/process/making-a-release.html [2] https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-appliance/ [3] https://resources.ovirt.org/pub/ovirt-4.5/rpm/el8/ > > Thanks in advance, > > > On Wed, Oct 26, 2022 at 12:38 PM Lev Veyde wrote: > >> Hi Ada, >> >> Thanks for letting us know about the issue. >> The issue seems to be with the latest ovirt-engine-appliance. >> We'll need to rebuild this and provide a fixed package. >> >> Thanks in advance, >> >> On Wed, Oct 26, 2022 at 11:04 AM ada per wrote: >> >>> Thank you for your reply, >>> Indeed I 1. Installed ovirt-node on some host 2. Ran there >>> 'hosted-engine --deploy' 3. Got an engine VM that includes the master >>> engine >>> >>> Regarding your questions >>> >>> *Did you install/upgrade any package manually, prior to >>> deploying?ovirt-engine-appliance? Anything else?* >>> I did not upgrade any packages prior to deploying >>> >>> What i did is: >>> I installed ovirt node host 4.5.3.1 without adding any packages >>> manually- it deployed master version# >>> i removed it and on a different host >>> I installed ovirt node host 4.5.3 without adding any packages manually- >>> it deployed master version# >>> i then removed it and install node 4.5.2 without adding any packages >>> manually- it deployed master version >>> i removed it and reinstall 4.5.2 and install engine packages >>> manually and still master version was deployed even though when running >>> engine appliance install it says >>> ovirt-engine-appliance-4.5-20221018071047.1.el8.x86_64 >>> >>> *the results of the commands are as below:* >>> >>> *rpm -qa | grep release* >>> centos-release-nfv-common-1-3.el8.noarch >>> centos-release-gluster10-1.0-1.el8s.noarch >>> centos-release-virt-common-1-2.el8.noarch >>> centos-release-ovirt45-8.7-2.el8s.noarch >>> centos-stream-release-8.6-1.el8.noarch >>> centos-release-storage-common-2-2.el8.noarch >>> centos-release-opstools-1-12.el8.noarch >>> ovirt-release-host-node-4.5.2-1.el8.x86_64 >>> centos-release-ceph-pacific-1.0-2.el8.noarch >>> centos-release-nfv-openvswitch-1-3.el8.noarch >>> >>> *dnf repoquery -i ovirt-engine-appliance* >>> Last metadata expiration check: 0:28:15 ago on Wed 26 Oct 2022 10:22:40 >>> EEST. >>> Name : ovirt-engine-appliance >>> Version : 4.5 >>> Release : 20220419162115.1.el8 >>> Architecture : x86_64 >>> Size : 1.6 G >>> Source : ovirt-engine-appliance-4.5-20220419162115.1.el8.src.rpm >>> Repository : ovirt-45-upstream >>> Summary : The oVirt Engine Appliance image (OVA) >>> URL : https://www.ovirt.org/ >>> License : GPLv2 >>> Description : This package contains the prebuild oVirt Engine appliance >>> image. It is intended to >>> : be used with hosted-engine setup. >>> >>> Name : ovirt-engine-appliance >>> Version : 4.5 >>> Release : 20220511122240.1.el8 >>> Architecture : x86_64 >>> Size : 1.6 G >>> Source : ovirt-engine-appliance-4.5-20220511122240.1.el8.src.rpm >>> Repository : ovirt-45-upstream >>> Summary : The oVirt Engine Appliance image (OVA) >>> URL : https://www.ovirt.org/ >>> License : GPLv2 >>> Description : This package contains the prebuild oVirt Engine appliance >>> image. It is intended to >>> : be used with hosted-engine setup. >>> >>> Name
[ovirt-users] Re: Wrong engine version grts installed
On Wed, Oct 26, 2022 at 8:50 AM ada per wrote: > > Hello, > > Both node version 4.5.3 and 4.5.2 ate installing the master version. By your question, I suppose that you mean that you: 1. Installed ovirt-node on some host 2. Ran there 'hosted-engine --deploy' 3. Got an engine VM that includes the 4.5.4 master engine Can you please check this, on the host: # rpm -qa | grep release # dnf repoquery -i ovirt-engine-appliance Did you install/upgrade any package manually, prior to deploying? ovirt-engine-appliance? Anything else? Adding Lev. Thanks and best regards, > > The version of the engine that gets installed is > 4.5.4-0.2.master.20221025103923.git936a8fcd09.el8 > > I do not understand why master version was installed, as I wanted the stable > version. > > > ___ > 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/D3YMM2L2AQQU3UHXWAP4I7LN7RBHEHJ7/ -- 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/OGE7PDZG7ZRWCIENUC6GWFSASRWHJ64Z/
[ovirt-users] Re: URGENT HELP NEEDED!! Hosts are in non-operational state.
On Tue, Oct 25, 2022 at 7:38 PM Darrell Budic wrote: > > Both the initial messages and the additional detail in these vdsm logs show > that it can’t mount a storage volume. In a multi node environment, it’s > usually iscsi, gluster, etc, so start by looking at your network and the > storage devices and figuring out why it can’t mount them. Comparison to any > remaining running nodes may be helpful. Indeed, but in this particular case, it also provides more details: [' /dev/mapper/3600c0ff00051441d1 e145f5e0100: Checksum error at offset 30099960109568', " Couldn't read volume group metadata from /dev/mapper/3600c0ff00051441d1e145f5e0100.", ' Metadata location on /dev/mapper/3600c0ff00051441d1e145f5e0100 at 30099960109568 has invalid summary for VG.', ' Failed to read metadata summary from /dev/mapper/3600c0ff00051441d1e145f5e0100', ' Failed to scan VG from /dev/mapper/3600c0ff00051441d1e145f5e0100'] If this VG does work well from some other host, perhaps it's a local issue. Otherwise, it's probably corrupted - if you have good and recent backups, it might be best to restore them, otherwise you can try fixing the VG - I'd start by searching the net for relevant parts of this error message and see how people handled similar cases. Good luck and best regards, > > > On Oct 25, 2022, at 3:40 AM, eug...@knorydev.com wrote: > > > > Hi Tomas, > > > > [root@host1 vdsm]# tail -f vdsm.log > > StorageUnavailableError: Unable to get volume size for domain > > 107f73a2-8c3e-43a7-bf18-ce8ef4be2a19 volume > > 581f65d2-3db5-4fde-960f-4c4ffe27341e > > 2022-10-25 16:39:51,785+0800 INFO (periodic/3) [virt.vm] > > (vmId='a8d6fcaf-a673-46df-b00a-925a8b9791ef') Requesting extension for > > volume 581f65d2-3db5-4fde-960f-4c4ffe27341e on domain > > 107f73a2-8c3e-43a7-bf18-ce8ef4be2a19 (apparent: 91268055040, capacity: > > 322122547200, allocated: 90872676352, physical: 91268055040 > > threshold_state: exceeded) (vm:1289) > > 2022-10-25 16:39:51,787+0800 INFO (periodic/3) [vdsm.api] START > > sendExtendMsg(spUUID='81f9e45a-5879-11ea-a3bd-00163e27dfef', > > volDict={'newSize': 92341796864, 'domainID': > > '107f73a2-8c3e-43a7-bf18-ce8ef4be2a19', 'name': 'vda', 'poolID': > > '81f9e45a-5879-11ea-a3bd-00163e27dfef', 'clock': > extend-volume=0.00*)>, 'internal': False, 'volumeID': > > '581f65d2-3db5-4fde-960f-4c4ffe27341e', 'imageID': > > '2d1375ba-ce52-4da1-9873-d9181d9e775b'}, newSize=92341796864, > > callbackFunc= > object at 0x7fea007336d0>>) from=internal, > > task_id=2b0c7a67-0f31-4f62-af70-a29e0b84dafb (api:48) > > 2022-10-25 16:39:51,787+0800 INFO (periodic/3) [vdsm.api] FINISH > > sendExtendMsg return=None from=internal, > > task_id=2b0c7a67-0f31-4f62-af70-a29e0b84dafb (api:54) > > 2022-10-25 16:39:52,635+0800 INFO (mailbox-hsm) > > [storage.MailBox.HsmMailMonitor] HSM_MailMonitor sending mail to SPM - > > ['/usr/bin/dd', > > 'of=/rhev/data-center/81f9e45a-5879-11ea-a3bd-00163e27dfef/mastersd/dom_md/inbox', > > 'iflag=fullblock', 'oflag=direct', 'conv=notrunc', 'bs=4096', 'count=1', > > 'seek=1'] (mailbox:380) > > 2022-10-25 16:39:52,710+0800 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC > > call Host.ping2 succeeded in 0.00 seconds (__init__:312) > > 2022-10-25 16:39:52,715+0800 INFO (jsonrpc/3) [api.virt] START getStats() > > from=::1,39184, vmId=6579a9c4-d55e-4d61-9c3a-c745cdcfa430 (api:48) > > 2022-10-25 16:39:52,715+0800 INFO (jsonrpc/3) [api] FINISH getStats > > error=Virtual machine does not exist: {'vmId': > > u'6579a9c4-d55e-4d61-9c3a-c745cdcfa430'} (api:129) > > 2022-10-25 16:39:52,715+0800 INFO (jsonrpc/3) [api.virt] FINISH getStats > > return={'status': {'message': "Virtual machine does not exist: {'vmId': > > u'6579a9c4-d55e-4d61-9c3a-c745cdcfa430'}", 'code': 1}} from=::1,39184, > > vmId=6579a9c4-d55e-4d61-9c3a-c745cdcfa430 (api:54) > > 2022-10-25 16:39:52,715+0800 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC > > call VM.getStats failed (error 1) in 0.00 seconds (__init__:312) > > 2022-10-25 16:39:53,786+0800 INFO (periodic/5) [virt.vm] > > (vmId='a8d6fcaf-a673-46df-b00a-925a8b9791ef') Requesting extension for > > volume 581f65d2-3db5-4fde-960f-4c4ffe27341e on domain > > 107f73a2-8c3e-43a7-bf18-ce8ef4be2a19 (apparent: 91268055040, capacity: > > 322122547200, allocated: 90872676352, physical: 91268055040 > > threshold_state: exceeded) (vm:1289) > > 2022-10-25 16:39:53,787+0800 INFO (periodic/5) [vdsm.api] START > > sendExtendMsg(spUUID='81f9e45a-5879-11ea-a3bd-00163e27dfef', > > volDict={'newSize': 92341796864, 'domainID': > > '107f73a2-8c3e-43a7-bf18-ce8ef4be2a19', 'name': 'vda', 'poolID': > > '81f9e45a-5879-11ea-a3bd-00163e27dfef', 'clock': > extend-volume=0.00*)>, 'internal': False, 'volumeID': > > '581f65d2-3db5-4fde-960f-4c4ffe27341e', 'imageID': > > '2d1375ba-ce52-4da1-9873-d9181d9e775b'}, newSize=92341796864, > > callbackFunc= > object at 0x7fea007336d0>>) from=internal, > > task_id=197234ba-5cab-4098-86c8-7f2c979171d2 (a
[ovirt-users] Re: Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."
On Tue, Oct 25, 2022 at 6:27 AM Matthew J Black wrote: > > OK, so, with all the tooing-and-frowing things stand as follows (@03:15UTC > 25-Oct-2022): > > - I managed to solve the "DNF Timeout" issue (see my post "Local (Deployment) > VM Can't Reach "centos-ceph-pacific" Repo") and so simplified the deployment > command to `hosted-engine --deploy`. Unfortunately this still results in a > "Host is not up" error, with the logs as per before. > > - As mentioned elsewhere in this thread I uploaded the (previous) logs to > Dropbox along with a couple of other relevant(?) files: > https://www.dropbox.com/sh/eymwdy8hzn3sa7z/AACscSP2eaFfoiN-QzyeEVfaa?dl=0 > > - I followed the suggestion of ajude.pereira (see post in this thread) but > this did not resolve the issue. > > - As per one of my other posts in this thread, digging into the logs further > revealed this issue: "Failed to authenticate session > with host 'ovirt_node_1.mynet.local': SSH authentication to > 'root(a)ovirt_node_1.mynet.local' failed. Please verify provided credentials. > Make sure key is authorized at host" > > - I also did a `hosted-engine --deploy > --ansible-extra-vars=he_pause_host=true` (as per the suggestion of Konstantin > - see post in this thread) and tried to work out why ssh wasn't working. I > ssh'd into the deployment VM and then attempted to ssh back into the > deployment host (ie `ssh root@ovirt_node_1.mynet.local`). While I could > connect, I was asked for the root's password. Good. > I was under the impression that this was supposed to be a "password-less" > operation. It should. At this point, the operation that is attempted and which is failing with the error you see in engine.log ("Failed to authenticate session"), is done using Java code, using the Java library apache-sshd, not the command line ssh. Some of the relevant code is here: https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/hostdeploy/AddVdsCommand.java I do not know this code well, sorry, nor the specifics of apache-sshd vs openssh (and there are such "specifics", as can easily be seen by looking at the engine git log). > As I do not provide the root@ovirt_node_1.mynet.local password anywhere in > the deployment script, I suspect that this is why I'm getting the "Host is > not up" error. > > - To reiterate: the host'd sshd_config file is configured as per the oVirt > documentation. > > So am I wrong in my understanding of the password-less ssh-nature of the > situation and how the deployment script is supposed to work? I think this should work more or less like this: After running engine-setup, and when the engine is already up, we fetch the public key of the engine from it, and store it in your authorized_keys file. This is done here: https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml#L36 - name: Set Engine public key as authorized key without validating the TLS/SSL certificates I do see this in your log in dropbox. Do you see /root/.ssh/authorized_keys on the host (with a timestamp similar to the log line)? If so, you can try this, from the engine VM: ssh -v -i /etc/pki/ovirt-engine/keys/engine_id_rsa ovirt_node_1.mynet.local If this does not work, you can continue debugging this until you manage to understand/fix. Perhaps check sshd config etc. If it does work, it means the issue might be due to incompatibility between apache-sshd and openssh and/or the configuration. > > Also, does *anyone* have any pointers, suggestions, or can otherwise help me > out - thanks. At this point, you should be able to log into the admin UI (the pause message provides a link) and try to manually add the host. It seems like this didn't work for you. This is because "host_result_up_check" is "failed", and we pause only if it succeeded and the host is returned with status "non_operational". Feel free to create an issue to make the code pause also if "host_result_up_check" is "failed" - not sure why we do not, perhaps we did have a reason. Anyway, you can force the code to pause after trying to add the host but before checking if this worked, by passing "--ansible-extra-vars=he_pause_host=true". You can also check/share more of engine.log - there might be more information prior to the failure (but as I said, I do not know this code well). You can try running sshd (the server) with debug info and check its own log - the issue might be due to incompatible keys on one or both of the sides, or something like that. Sorry that I do not remember if you wrote this before - is this your first attempt to install oVirt? If so, perhaps try first to start with a clean host, without any custom configuration (e.g. of sshd), and see if this works for you. If you do have access to a successful setup, you can more easily compare. Good luck and best regards, -- Didi ___
[ovirt-users] Re: Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."
On Thu, Oct 20, 2022 at 1:59 PM Matthew J Black wrote: > > Hi Everyone, > > Could someone please help me - I've been trying to do an install of oVirt for > *weeks* (including false starts and self-inflicted wounds/errors) and it is > still not working. > > My setup: > > - oVirt v4.5.3 > - A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK > - 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all > working AOK > - All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK > - All relevant IPv4 Address in "/etc/hosts" file - all working AOK > - IPv6 (using "method=auto" in the interface config file) enabled on the > relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, > but I'm trying to cover all the bases. > - All relevant Ports (as per the oVirt documentation) set up on the firewall > - ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | > ovirt-vmconsole | vdsm }} > - All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & > PowerTools, and the EPEL, plus the ones from the oVirt documentation) > > I have followed the oVirt documentation (including the special > RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, > no special settings, exactly as they are written. > > All the dnf installs, etc, went off without a hitch, including the "dnf > install centos-release-ovirt45", "dnf install ovirt-engine-appliance", and > "dnf install ovirt-hosted-engine-setup" - no errors anywhere. > > Here is the results of a "dnf repolist": > > - appstreamRocky Linux 8 - > AppStream > - baseos Rocky Linux 8 - > BaseOS > - centos-ceph-pacific CentOS-8-stream - Ceph > Pacific > - centos-gluster10 CentOS-8-stream - > Gluster 10 > - centos-nfv-openvswitchCentOS-8 - NFV OpenvSwitch > - centos-opstoolsCentOS-OpsTools - > collectd > - centos-ovirt45 CentOS Stream 8 - > oVirt 4.5 > - cs8-extras CentOS Stream 8 > - Extras > - cs8-extras-common CentOS Stream 8 - > Extras common packages > - epel Extra > Packages for Enterprise Linux 8 - x86_64 > - epel-modular Extra Packages for > Enterprise Linux Modular 8 - x86_64 > - ovirt-45-centos-stream-openstack-yogaCentOS Stream 8 - oVirt 4.5 - > OpenStack Yoga Repository > - ovirt-45-upstream oVirt upstream for > CentOS Stream 8 - oVirt 4.5 > - powertools Rocky Linux 8 - > PowerTools > > So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 > --ansible-extra-vars=he_offline_deployment=true". > > I used "--ansible-extra-vars=he_offline_deployment=true" because without that > flag I was getting "DNF timout" issues (see my previous post `Local > (Deployment) VM Can't Reach "centos-ceph-pacific" Repo`). > > I answer the defaults to all of questions the script asked, or entered the > deployment-relevant answers where appropriate. In doing this I double-checked > every answer before hitting . Everything progressed smoothly until the > deployment reached the "Wait for the host to be up" task... which then hung > for more than 30 minutes before failing. > > From the ovirt-hosted-engine-setup... log file: > > - 2022-10-20 17:54:26,285+1100 ERROR > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": > false, "msg": "Host is not up, please check logs, perhaps also on the engine > machine"} > > I checked the following log files and found all of the relevant ERROR lines, > then checked several 10s of proceeding and succeeding lines trying to > determine what was going wrong, but I could not determine anything. > > - ovirt-hosted-engine-setup... > - ovirt-hosted-engine-setup-ansible-bootstrap_local_vm... > - ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I > believe > > I can include the log files (or the relevant parts of the log files) if > people want - but that are very large: several 100 kilobytes each. You can upload to some file sharing service (dropbox, google drive, etc.) and share a link. If it's just not-too-long text you can use some pastebin (might be more or less convenient for some readers, I didn't do a poll). > > I also googled "oVirt Host is not up" and found several entries, but after > reading them all the most relevant seems to be a thread from these mailing > list: `Install of RHV 4.4 failing - "Host is not up, please check logs, > perhaps also on the en
[ovirt-users] Re: Network Interface Already In USe - Self-Hosted Install
Hi, On Tue, Oct 11, 2022 at 9:10 AM Matthew J Black wrote: > > Hi All, > > OK, so after much reading of logs, Ansible files, blog posts, documentation, > and much gnashing of teeth, glasses of bourbon, language to make a sailor > blush, tears, blood, sweat, and various versions of "DOH!", I finally worked > out what was wrong - what I did wrong - and so I'm putting it down here so > that the next person who comes along with the same (or a similar) issue > doesn't have to go through what I went through - and I'm including a couple > of suggestions to the devs/doco writers which (I believe) would have stopped > me from making my mistake in the first place. Much appreciated! > > When I did my install I used the command: > > ~~~ > hosted-engine --deploy --4 > --ansible-extra-vars=he_ipv4_subnet_prefix=172.16.1 > ~~~ > > I did this because we're running an IPv4 network and because the oVirt Engine > needs to be on the 172.16.1.0/24 network - and that's what I thought the > "he_ipv4_subnet_prefix" option did, and I was trying to let the deployment > script know this in advance instead of having to discover this itself. > > Now that I've gone back over *all* the doco I realise that the > "he_ipv4_subnet_prefix" option is *not* used for this purpose, but is instead > used for the *temporary* ip address of the deployment engine when the default > subnet of 192.168.222.0/24 is not available. > > Because I was specifying the 172.16.1.0/24 network (which is already in use) > the deployment failed because it was attempting to create that network as a > temporary network for the initial deployment. > > So yes, as I said, my fault - no question about that at all. > > Some suggestions: > > Although it is stated in the documentation - Installing oVirt As A > Self-Hosted Engine Using The Command Line, section 2.3.2 > (https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#Network-range-for-SHE-deployment_SHE_cli_deploy) > - (I believe) it is not very clear what is happening here, so a "Note:" or > some sort of statement explicitly stating what this is used for might be in > order. For example, here is the note I made for our team in our internal > documentation: > > ~~~ > **Note:** he_ipv4_subnet_prefix=x.x.x: - This is a temporary network > prefix if 192.168.222.0/24 (the default) is not available - this is ***NOT*** > the final working subnet of the oVirt Engine. > ~~~ I now read the subsection you linked to above - and IMO the context is well-presented - if you read the entirety of 2.3.2 (6 lines, in my browser), it should be clear. But of course - patches are welcome! This page has, like most others in the website, an "Edit this page" link at the bottom. > > I also believe - quite strongly, in fact - that having the entire deployment > hidden behind the "black box" that is the Ansible deployment - while making > things easy by automating the deployment - makes troubleshooting more > difficult. I believe that if there was a definite "Step-By-Step" list of what > was going on behind the scenes - perhaps as an Appendix to the documentation > - then the mistake I made would have been a lot harder to make - ie if there > was such a list then it would have been less likely to make the assumption I > made. > > I'm thinking something along the lines of (and I am aware that what follows > is not correct): > > ~~~ > 1. Collect info - this is stored in "/path/file" temporarily. > 2. Install Deployment VM. > 3. Deployment VM creates internal bridge - this uses 192.168.222.0/24 by > default but can be overridden by "he_ipv4_subnet_prefix". > 4. Deployment Engine creates oVirt Engine. > etc, etc, etc > ~~~ Makes sense, but I do not think doing this well, and above that maintaining this well over time/versions - is going to happen. We have a very nice presentation from a few years ago, still relevant even if not up-to-date, which might help get the big picture. Searching google for "ovirt hosted-engine deep dive" finds it, for me: https://www.ovirt.org/media/Hosted-Engine-4.3-deep-dive.pdf BTW, in the long distant past, hosted-engine deployment was much more manual (the script guided you through stuff, but you did a lot more by hand - including installing the OS and engine on the VM, configuring stuff, etc.) and the move to what we have now (called "node zero" or "node 0" in some places, including above pdf) was definitely a huge improvement. > > Anyway, that's my feedback / suggestions / mea culpa / whatever. :-) Thanks! 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/RPF2TK7FY2PUDTJPAPAED66QS
[ovirt-users] Re: hosted-engine-setup --deploy fail on Centos Stream 8
On Tue, Oct 11, 2022 at 4:54 AM andrea.crisanti--- via Users wrote: > > Hy, > > I am trying to install ovirt 4.5 on a 4-host cluster running Centos Stream > 8, but the engine does not start and the whole process fails. > > Here is my procedure > > dnf install centos-release-ovirt45 > dnf module reset virt > dnf module enable virt:rhel > dnf install ovirt-engine-appliance > dnf install ovirt-hosted-engine-setup > > The latest version of ansible [ansible-core 2.13] uses python3.9 and the > installation fails because some python3.9 modules are missing > [python39-netaddr, python39-jmespath] and cannot be installed [conflict > python3-jmespath]. So I downgraded ansible to ansible-core 2.12 > > dnf downgrade ansible-core +1 > > Now > > hosted-engine-setup --deploy --4 > > goes proceed further but stops because it cannot start the engine > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a > failure] > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is > not up, please check logs, perhaps also on the engine machine"} Please note the error message - "Host is not up", not "engine is not up". This means that the deploy process did setup and start an engine, then tried to add the host (the one you deploy on) to the engine, and this failed somewhere. > > I looked into the log file > > /var/log//ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20221007132728-yp7cd1.log > and I found the following error: > > 2022-10-07 13:28:30,881+0200 ERROR ansible failed { > "ansible_host": "localhost", > "ansible_playbook": > "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", > "ansible_result": { > "_ansible_no_log": false, > "changed": false, > "cmd": [ > "virsh", > "net-undefine", > "default" > ], > "delta": "0:00:00.039258", > "end": "2022-10-07 13:28:30.710401", > "invocation": { > "module_args": { > "_raw_params": "virsh net-undefine default", > "_uses_shell": false, > "argv": null, > "chdir": null, > "creates": null, > "executable": null, > "removes": null, > "stdin": null, > "stdin_add_newline": true, > "strip_empty_ends": true, > "warn": false > } > }, > "msg": "non-zero return code", > "rc": 1, > "start": "2022-10-07 13:28:30.671143", > "stderr": "error: failed to get network 'default'\nerror: Network not > found: no network with matching name 'default'", > "stderr_lines": [ > "error: failed to get network 'default'", > "error: Network not found: no network with matching name > 'default'" > ], > "stdout": "", > "stdout_lines": [] > }, > "ansible_task": "Update libvirt default network configuration, undefine", This isn't your issue. If you check the code, you see that this task has "ignore_errors: true", and actually failure there is almost always expected. > "ansible_type": "task", > "status": "FAILED", > "task_duration": 0 > } > > Needless to say > firewalld and libvirtd are both up > and virsh net-list gives: > > Name StateAutostart Persistent > > ;vdsmdummy; active no no > default active no yes > > I googled around without success. > > Has anyone had similar problems? Please check/share /var/log/ovirt-engine on the engine machine trying to understand why adding the host failed. The engine machine, at this point, is still local to your host, having a private IP address - you can find that one by searching /var/log/ovirt-hosted-engine-setup/* for 'local_vm_ip'. I usually use this: # ssh -o StrictHostKeyChecking=No -o UserKnownHostsFile=/dev/null -l root $(grep -A20 local_vm_ip $(ls -t /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm* | head -1) | sed -n 's/^"stdout": "\([^"]*\)",/\1/p' | sed 's/\\n.*//') 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/XPS6HNOTGCLSGA57IAMZRELWG3ZUMMSI/
[ovirt-users] Re: Hyperconverged install fails to add second and third hosts
On Fri, Oct 7, 2022 at 7:46 PM Calvin Ellison wrote: > Hello fellow users, I'm having trouble sending up a brand new cluster > using Equinix Metal. The three servers are their "n3.xlarge.x86" model, > which uses an Intel Xeon Gold 6314U CPU in a Supermicro > SSG-110P-NTR10-EI018 server. > > The entire Hyperconverged installation process appears to complete without > error, but when I log into the manager only one host is listed and only > that host's Gluster brick appears in the UI. The only hint of a problem in > the UI is in the Tasks pane: two failed tasks to add the other hosts. > > Where do I get started troubleshooting? > Usually on the engine machine, in /var/log/ovirt-engine (including host-deploy). 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/3P6ENRMFO5BSXXZ4KSVVE3NSVFOO2Z5S/
[ovirt-users] Re: Creating an oVirt Engine Appliance on a different EL Distro (eg Rocky Linux)
On Mon, Oct 3, 2022 at 7:07 AM Matthew J Black wrote: > > Thanks David & Klaas, > > I think Klass is closer to what I was asking - and I'll follow his suggestion > about asking on the Dev List > > I appreciate the help from both of you - thank you :-) You might want to check also these threads: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D6YHIIBEABPLK3Q54O7WGDGKC2J5LPSN/ https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/FRIIET5XFR3G332NAWGNRP4VJK7S6NVD/ 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/N7SGPMD7GX62F4ZFBFGND3OL4WGJNJXT/
[ovirt-users] Re: ovirt-engine-appliance Location (Pre-Installation)
Hi, On Fri, Sep 30, 2022 at 8:26 AM Matthew J Black wrote: > > Hi All, > > A couple of Qs: > > During the `TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package]` > stage of the Management Engine deployment, is this trying to install the > ovirt-engine-appliance, or something else? It's here: https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/engine_setup/tasks/install_packages.yml So - it tries to install 'ovirt-engine'. This is ran inside the engine VM, not on the host. > > When we do a pre-install of the ovirt-engine-appliance (ie dnf install > ovirt-engine-appliance) where is this installed too, so that we can enter > this information into the deployment script at the `Engine Appliance Image > Path` stage? Not sure what exactly you ask here. (On some somewhat lagging-behind machine: ) # rpm -ql ovirt-engine-appliance /etc/ovirt-hosted-engine/10-appliance.conf /usr/share/doc/ovirt-engine-appliance /usr/share/doc/ovirt-engine-appliance/ovirt-engine-appliance-manifest-rpm /usr/share/ovirt-engine-appliance /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.5-20220523064055.1.el8.ova So e.g. in this case, I could have responded, to the prompt asking which image to use, '/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.5-20220523064055.1.el8.ova'. If you want to make the deploy process not try to install/update packages inside the engine VM, but only use whatever that's inside the appliance image, you can try: # hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true 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/EFF2B5ZBK63ZDMA653AMNU26CFYUUBJA/
[ovirt-users] Re: Failed to deploy ovirt engine with CLI
On Wed, Sep 21, 2022 at 5:21 PM Pablo Olivera wrote: > > Hi community, > > I'm trying to deploy the engine via CLI on an ovirt 4.5.2 (CentOS 8) > node over a clean install. > Previously I was trying to deploy it via cockpit but I got the following > error: > > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using > username/password credentials] > [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication > access_denied : Cannot authenticate user Invalid user credentials. > [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": > false, "msg": "Error during SSO authentication access_denied : Cannot > authenticate user Invalid user credentials."} > > After researching in different threads of this forum, I decided to setup > it via CLI by recommendation of different users, since it seems that > cockpit hosted-engine deployment is broken. Indeed. Sorry for that. > > I attach the hosted-engine setup log but I am not sure where is the > problem now. It's here, apparently: 2022-09-21 14:30:50,466+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} > > Can you help me? As the message says, please check/share relevant logs. 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/NIVM6NVK4SIVUDPEXRHIV5S3RRHI3GEI/
[ovirt-users] Re: Self-hosted-engine timeout and recovering time
On Wed, Sep 21, 2022 at 12:22 AM Marcos Sungaila wrote: > > Hi all, > > I have a cluster running the 4.4.10 release with 6 KVM hosts and > Self-Hosted-Engine. What storage? > I'm testing some network outage scenarios, and I faced strange behavior. I suppose you have redundancy in your network. It's important to clarify (for yourself, mainly) what exactly you test, what's important, what's expected, etc. > After disconnecting the KVM hosts hosting the SHE, there was a long timeout > until switching the Self-Hosted-Engine to another host as expected. I suggest studying the ha-agent logs, /var/log/ovirt-hosted-engine-ha/agent.log. Much of the relevant code is in ovirt_hosted_engine_ha/agent/states.py (in the git repo, or under /usr/lib/python3.6/site-packages/ on your machine). > Also, there took a relatively long time to take over the HA VMs from the > failing server. That's a separate issue, about which I personally know very little. You might want to start a separate thread about it. I do know, though, that if you keep the storage connected, the host might be able to keep updating VM leases on the storage. See e.g.: https://www.ovirt.org/develop/release-management/features/storage/vm-leases.html I didn't check the admin guide, but I suppose it has some material about HA VMs. > Is there a configuration where I can reduce the SHE timeout to make this > recover process faster? IIRC there is nothing user-configurable. You can see most relevant constants in ovirt_hosted_engine_ha/agent/constants.py{,.in}. Nothing stops you from changing them, but please note that this is somewhat risky, and I strongly suggest to do very careful testing with your new settings. It might make sense to try to methodically go through all the possible state changes in the above state machine. The general assumption is that network and storage, for critical setups, are redundant, and that the engine itself is not considered critical, in the sense that if it's dead, all your VMs are still alive. And also, that it's more important to not corrupt VM disk images (e.g. by starting the VM concurrently on two hosts) than to keep the VM alive. 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/DLSI7CNZV2Z37CG2VL4U2WSXE2QGIQYS/
[ovirt-users] Re: How do I migrate a running VM off unassigned host?
On Tue, Sep 20, 2022 at 4:50 AM David White via Users wrote: > > This is resolved. > I manually shutdown each VM, and then from within oVirt, I went to the host, > and in the upper corner of the page when looking at the host, I clicked on > 'Confirm Host has been rebooted'. > > This allowed oVirt to then recognize that the VMs were down, and I was able > to bring them back online on a healthy host. > > . That's what you're supposed to do, anyway. > I intentionally cheated, and did the order of things a little bit > differently. I knew that none of the VMs on that host were currently > configured for HA, so I knew that if oVirt thought the VMs were turned off, > that oVirt would NOT turn the VMs back online. > > So just to make sure that it would even work, I marked the problematic host > as rebooted FIRST. Then, once I knew that worked, and the VMs were showing > down in the oVirt UI (but still online on the problematic host), I ssh'd to > each server and manually shut them down before bringing them back online. OK :-) > > Hopefully this helps someone else! > > -David > > Sent with Proton Mail secure email. > > --- Original Message --- > On Monday, September 19th, 2022 at 3:44 PM, David White via Users > wrote: > > Restarting the vdsmd service on 1 of the problematic hosts brought that host > back, and ovirt can see it. > > But that did not fix the problem on the last remaining host. I'm still > troubleshooting... > > Sent with Proton Mail secure email. > > --- Original Message --- > On Monday, September 19th, 2022 at 11:37 AM, David White via Users > wrote: > > I tried rebooting the engine to see if that would magically solve the problem > (worth a try, right?). But as I expected, it didn't help. > > Now one of the hosts is in a "Non Responsive" state and the other is > permanently in a "Connecting" state. All VMs associated with those 2 hosts > now show a question mark on the oVirt dashboard. > > The storage for these VMs is good, and these VMs are online. Everything is > "working" -- I just need to get these VMs moved onto hosts that oVirt is able > to manage. > > If it helps for troubleshooting purposes, prior to rebooting the engine, the > following errors were showing up in the oVirt UI for both of these hosts: > > VDSM cha1-storage.example.com command Get Host Capabilities failed: Internal > JSON-RPC error: {'reason': '[Errno 24] Too many open files'} Did you also see this error elsewhere? In the engine log? vdsm? Elsewhere? It might either imply there is some leak somewhere, or this might be a symptom of a deeper problem (or both). Thanks for the update and best regards, > > Any ideas? If I need to take some downtime for these VMs, so be it, but I > need to keep downtime at a minimum. > > Sent with Proton Mail secure email. > > --- Original Message --- > On Monday, September 19th, 2022 at 8:41 AM, David White via Users > wrote: > > Ok, now that I'm able to (re)deploy ovirt to new hosts, I now need to migrate > VMs that are running on hosts that are currently in an "unassigned" state in > the cluser. > > This is the result of having moved the oVirt engine OUT of a hyperconverged > environment onto its own stand-alone system, while simultaneously upgrading > oVirt from v4.4 to the latest v4.5. > > See the following email threads: > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/TZAUCM3GB5ERSTZMIAJEUCNNXDHTS6VA/ > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/3IWXZ7VXM6CYYSVANT32SK6ESBRKO4VM/ > > > The oVirt engine knows about the VMs, and oVirt knows about the storage that > those VMs are on. But the engine sees 2 of my hosts as "unassigned", and I've > been unable to migrate the disks to new storage, nor live migrate a VM from > an unassigned host, nor make a clone of an existing VM. > > Is there a way to recover from this scenario? I was thinking something along > the lines of manually shutting down the VM on the unassigned host, and then > somehow force the engine to bring the VM online again from a healthy host? > > Thanks, > David > > Sent with Proton Mail secure email. > > > > > ___ > 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/3Q4SYDCUHALHNCPDG7R6YUAA24ZAIMCQ/ -- 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/HZCG2VQ7JPE2ZUFM6OMCGC3YLSOPXDNQ/
[ovirt-users] Re: Unable to deploy to new host
On Mon, Sep 19, 2022 at 12:15 PM David White wrote: > > --- Original Message --- > On Monday, September 19th, 2022 at 4:44 AM, Yedidyah Bar David > wrote: > > > > On Mon, Sep 19, 2022 at 11:31 AM David White dmwhite...@protonmail.com > > wrote: > > > > > > Thank you. > > > > > > > On the engine: > > > > > > > [root@ovirt-engine1 dwhite]# rpm -qa | grep -i ansible-core > > > ansible-core-2.13.3-1.el8.x86_64 > > > > > > > So I downgraded ansible-core: > > > [root@ovirt-engine1 dwhite]# yum downgrade ansible-core > > > > > > > [root@ovirt-engine1 dwhite]# rpm -qa | grep ansible-core > > > ansible-core-2.12.7-1.el8.x86_64 > > > > > > > After this, I tried again to deploy to the host, and that failed. The > > > playbooks got further. Reviewing the host-deploy log, it failed on: > > > > > > > "task" : "Enable firewalld rules", > > > "task_path" : > > > "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-firewalld/tasks/firewalld.yml:15", > > > > > > > ... with the following failure: > > > "msg" : "ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: > > > INVALID_SERVICE: 'glusterfs' not among existing services Permanent and > > > Non-Permanent(immediate) operation, Services are defined by port/tcp > > > relationship and named as they are in /etc/services (on most systems)", > > > > > > > QUESTION: > > > Probably not the best, or most elegant solution, but for my use case, is > > > there something within the engine itself that I can (should) configure > > > (maybe in the Postgres database somewhere?) to tell it that I'm no longer > > > using Gluster? I'm completely off gluster now, so I'd prefer to not > > > deploy it... > > > > > > > > I think it's a setting per DC/cluster, whether it supports gluster. > > Try editing your DCs/clusters. > > > > > > Or is there a better way? > > You're right. I went to Compute -> Clusters, clicked Edit, and in the General > section, I scrolled down, and there is a checkbox to enable (or disable) the > gluster service. That was enabled, so I just disabled it. > > That said, it's interesting to me that I confirmed gluster was actually > installed on the new host - but yet no service was available. So it does > appear to me that there's a bug somewhere else: > > [root@cha2-storage]# firewall-cmd --get-services | grep -i gluster > > (That command produces nothing, yet glusterfs is installed:) > > root@cha2-storage]# yum info glusterfs > Last metadata expiration check: 0:25:10 ago on Mon 19 Sep 2022 04:20:28 AM > EDT. > Installed Packages > Name : glusterfs > Version : 10.2 > Release : 1.el8s > Architecture : x86_64 > Size : 2.6 M > Source : glusterfs-10.2-1.el8s.src.rpm > Repository : @System > From repo: centos-gluster10 As I wrote below, > > > > > > It might be enough to copy /usr/lib/firewalld/services/glusterfs.xml > > (in the rpm glusterfs-server) it's in the glusterfs-server rpm, not glusterfs. > from some other machine and put it > > either there or in /etc/firewalld/services/ . I didn't test this. Not > > sure it's better :-). > > Simply disabling the gluster service from the ovirt web UI as described above > fixed the issue. Good. Thanks for the update. Best regards, > > Thank you. > > > Best regards, > > > > > > Sent with Proton Mail secure email. > > > > > > > --- Original Message --- > > > On Monday, September 19th, 2022 at 2:44 AM, Yedidyah Bar David > > > d...@redhat.com wrote: > > > > > > > > Hi, > > > > > > > > please see my reply to "[ovirt-users] Error during deployment of > > > > ovirt-engine". > > > > > > > > Best regards, > > > > > > > > On Mon, Sep 19, 2022 at 5:02 AM David White via Users users@ovirt.org > > > > wrote: > > > > > > > > > I currently have a self-hosted engine that was restored from a backup > > > > > of an engine that was originally in a hyperconverged state. (See > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/APQ3XBUM34TG76XGRBV6GIW62RP6MZOD/). > > > > > > > > > This was
[ovirt-users] Re: Unable to deploy to new host
On Mon, Sep 19, 2022 at 11:31 AM David White wrote: > > > Thank you. > > On the engine: > > [root@ovirt-engine1 dwhite]# rpm -qa | grep -i ansible-core > ansible-core-2.13.3-1.el8.x86_64 > > So I downgraded ansible-core: > [root@ovirt-engine1 dwhite]# yum downgrade ansible-core > > [root@ovirt-engine1 dwhite]# rpm -qa | grep ansible-core > ansible-core-2.12.7-1.el8.x86_64 > > After this, I tried again to deploy to the host, and that failed. The > playbooks got further. Reviewing the host-deploy log, it failed on: > > "task" : "Enable firewalld rules", > "task_path" : > "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-firewalld/tasks/firewalld.yml:15", > > ... with the following failure: > "msg" : "ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: > INVALID_SERVICE: 'glusterfs' not among existing services Permanent and > Non-Permanent(immediate) operation, Services are defined by port/tcp > relationship and named as they are in /etc/services (on most systems)", > > QUESTION: > Probably not the best, or most elegant solution, but for my use case, is > there something within the engine itself that I can (should) configure (maybe > in the Postgres database somewhere?) to tell it that I'm no longer using > Gluster? I'm completely off gluster now, so I'd prefer to not deploy it... I think it's a setting per DC/cluster, whether it supports gluster. Try editing your DCs/clusters. > > Or is there a better way? It might be enough to copy /usr/lib/firewalld/services/glusterfs.xml (in the rpm glusterfs-server) from some other machine and put it either there or in /etc/firewalld/services/ . I didn't test this. Not sure it's better :-). Best regards, > > Sent with Proton Mail secure email. > > --- Original Message --- > On Monday, September 19th, 2022 at 2:44 AM, Yedidyah Bar David > wrote: > > > > Hi, > > > > > please see my reply to "[ovirt-users] Error during deployment of > > ovirt-engine". > > > > > Best regards, > > > > > On Mon, Sep 19, 2022 at 5:02 AM David White via Users users@ovirt.org wrote: > > > > > > I currently have a self-hosted engine that was restored from a backup of > > > an engine that was originally in a hyperconverged state. (See > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/APQ3XBUM34TG76XGRBV6GIW62RP6MZOD/). > > > > > > > This was also an upgrade from ovirt 4.4 to ovirt 4.5. > > > > > > > There were 4 hosts in this cluster. Unfortunately, 2 of them are > > > completely in an "Unassigned" state right now, and I don't know why. The > > > VMs on those hosts are working fine, but I have no way to move the VMs or > > > manage them. > > > > > > > More to the point of this email: > > > I'm trying to re-deploy onto a 3rd host. I did a fresh install of Rocky > > > Linux 8, and followed the instructions at https://ovirt.org/download/ and > > > at https://ovirt.org/download/install_on_rhel.html, including the part > > > there that is specific to Rocky. > > > > > > > After installing the centos-release-ovirt45 package, I then logged into > > > the oVirt engine web UI, and went to Compute -> Hosts -> New, and have > > > tried (and failed) many times to install / deploy to this new host. > > > > > > > The last error in the host deploy log is the following: > > > > > > > 2022-09-18 21:29:39 EDT - { > > > "uuid" : "94b93e6a-5410-4d26-b058-d7d1db0a151e", > > > "counter" : 404, > > > "stdout" : "fatal: [cha2-storage.mgt.example.com]: FAILED! => {\"msg\": > > > \"The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is > > > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr > > > filter requires python's netaddr be installed on the ansible > > > controller\\n\\nThe error appears to be in > > > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > > > line 3, column 5, but may\\nbe elsewhere in the file depending on the > > > exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n- > > > block:\\n - name: Install ovs\\n ^ here\\n\"}", > > > "start_line" : 405, > > > "end_line" : 406
[ovirt-users] Re: oVirt 4.5 on Rocky 9
On Sun, Sep 18, 2022 at 10:03 PM Bjorn M wrote: > > Hi, > > I'm moving all my infra nodes to Rocky 9 and my oVirt cluster is next on the > list. I'm deploying a standalone oVirt VM on a KVM box and will set up the > hosts afterwards. All are to run on Rocky 9 x86_64. The engine is not ready yet for EL9. People are working on this, notably Martin: https://github.com/oVirt/ovirt-engine/pull/647 Best regards, > > I followed https://www.ovirt.org/download/install_on_rhel.html and created an > Ansible playbook to set up the customisations. > > I now have all repos set up correctly, or at least that is my understanding. > > When I run yum search ovirt-engine I get a number of packages available from > the repos, but not the ovirt-engine package. I do see the > ovirt-hosted-engine, but I prefer the standalone option. > > This makes sense as I don't find the package at > http://mirror.stream.centos.org/SIGs/9-stream/virt/x86_64/ovirt-45/Packages/o/ > , which I where all ovirt- packages are, except this one. > > Yum whatprovides engine-setup also turns out negative. > > I then decided to install ovirt-engine-appliance 4.5-20220419160254.1.el9 > from ovirt-45-upstream, but that package produces an error on the GPG key > import. > > It's unclear whether the issue is on my specific stack or wider. The missing > ovirt-engine package is confusing though. > > > Any help is appreciated, > > Cheers, Bjorn > > > > OUTPUT : > > > (0)[root@ovirt ~]# yum repolist > Updating Subscription Management repositories. > Unable to read consumer identity > > This system is not registered with an entitlement server. You can use > subscription-manager to register. > > repo id > repo name > appstream > Rocky Linux 9 - AppStream > baseos > Rocky Linux 9 - BaseOS > c9s-extras-common > CentOS Stream 9 - Extras packages > centos-ceph-pacific > CentOS-9-stream - Ceph Pacific > centos-gluster10 > CentOS-9-stream - Gluster 10 > centos-nfv-openvswitch > CentOS Stream 9 - NFV OpenvSwitch > centos-openstack-yoga > CentOS-9 - OpenStack yoga > centos-opstools > CentOS Stream 9 - OpsTools - collectd > centos-ovirt45 > CentOS Stream 9 - oVirt 4.5 > centos-rabbitmq-38 > CentOS-9 - RabbitMQ 38 > crb > Rocky Linux 9 - CRB > epel > Extra Packages for Enterprise Linux 9 - x86_64 > extras > Rocky Linux 9 - Extras > ovirt-45-upstream > oVirt upstream for CentOS Stream 9 - oVirt 4.5 > resilientstorage > Rocky Linux 9 - Resilient Storage > (0)[root@ovirt ~]# yum search ovirt-engine > Updating Subscription Management repositories. > Unable to read consumer identity > > This system is not registered with an entitlement server. You can use > subscription-manager to register. > > Last metadata expiration check: 3:37:50 ago on Wed 14 Sep 2022 08:24:39 AM > CEST. > > Name Matched: ovirt-engine > > ovirt-engine-appliance.x86_64 : The oVirt Engine Appliance image (OVA) > ovirt-engine-extension-aaa-ldap.noarch : oVirt Engine LDAP Users Management > Extension > ovirt-engine-extension-aaa-ldap-setup.noarch : oVirt Engine LDAP Users > Management Extension Setup Tool > ovirt-engine-extensions-api.noarch : oVirt engine extensions API > ovirt-engine-extensions-api-javadoc.noarch : oVirt engine extensions API > documentation > ovirt-engine-nodejs-modules.noarch : Node.js modules required
[ovirt-users] Re: Error during deployment of ovirt-engine
Hi, please see my reply to "[ovirt-users] Error during deployment of ovirt-engine". Best regards, On Sun, Sep 18, 2022 at 9:56 PM Peter H wrote: > > Hi Jonas, > > I get the same error when I try to install. Last weekend I managed to do it > (but with a lot of other problems) so something has changed during the week. > > After the VM is up I logged in through ssh and saw that the oVirt appliance > comes with Python-3.6 and Python-3.8 which both have netaddr installed. > > Part of the log: > ... > [ INFO ] TASK [ovirt.ovirt.engine_setup : Update setup packages] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Copy yum configuration file] > [ INFO ] changed: [localhost -> 192.168.222.35] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Set 'best' to false] > [ INFO ] changed: [localhost -> 192.168.222.35] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages] > [ INFO ] changed: [localhost -> 192.168.222.35] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Remove temporary yum configuration > file] > [ INFO ] changed: [localhost -> 192.168.222.35] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Set offline parameter if variable > is set] > ... > I noticed that after the task "Update all packages" Python-3.9 gets installed > and that version does not have netaddr installed. My theory is that the > playbook somehow uses the newest version of Python which is installed. > > pip3.9 list > Package Version > --- > ansible-core 2.13.3 > cffi 1.14.3 > cryptography 3.3.1 > idna 2.10 > pip 20.2.4 > ply 3.11 > pycparser2.20 > PyYAML 5.4.1 > setuptools 50.3.2 > six 1.15.0 > > I have tried another run where I installed the netaddr module as soon as > Python-3.9 got installed and that installation went further but then it had > another error. > > When I log into my hosted engine VM from last week there is no Python-3.9. > > My dnf(1) skills are not good enough to figure out which dependency is > causing Python-3.9 to be installed. > > There are probably a lot of other modules missing that can explain the other > error(s) I see. > > I will see if I can find out how to file a proper bug report. > > BR > Peter > > ___ > 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/TDB7QQF3BQ3KGPG34RX2AAKEVHLCJW5G/ -- 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/WY7IOOUGFJGZZLKRC4JO2KRZLVMYSH3L/
[ovirt-users] Re: Unable to deploy to new host
Hi, please see my reply to "[ovirt-users] Error during deployment of ovirt-engine". Best regards, On Mon, Sep 19, 2022 at 5:02 AM David White via Users wrote: > > I currently have a self-hosted engine that was restored from a backup of an > engine that was originally in a hyperconverged state. (See > https://lists.ovirt.org/archives/list/users@ovirt.org/message/APQ3XBUM34TG76XGRBV6GIW62RP6MZOD/). > > This was also an upgrade from ovirt 4.4 to ovirt 4.5. > > There were 4 hosts in this cluster. Unfortunately, 2 of them are completely > in an "Unassigned" state right now, and I don't know why. The VMs on those > hosts are working fine, but I have no way to move the VMs or manage them. > > More to the point of this email: > I'm trying to re-deploy onto a 3rd host. I did a fresh install of Rocky Linux > 8, and followed the instructions at https://ovirt.org/download/ and at > https://ovirt.org/download/install_on_rhel.html, including the part there > that is specific to Rocky. > > After installing the centos-release-ovirt45 package, I then logged into the > oVirt engine web UI, and went to Compute -> Hosts -> New, and have tried (and > failed) many times to install / deploy to this new host. > > The last error in the host deploy log is the following: > > 2022-09-18 21:29:39 EDT - { > "uuid" : "94b93e6a-5410-4d26-b058-d7d1db0a151e", > "counter" : 404, > "stdout" : "fatal: [cha2-storage.mgt.example.com]: FAILED! => {\"msg\": > \"The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter > requires python's netaddr be installed on the ansible controller\\n\\nThe > error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\\nbe elsewhere in the file depending on the exact > syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - > name: Install ovs\\n^ here\\n\"}", > "start_line" : 405, > "end_line" : 406, > "runner_ident" : "e2cbd38d-64fa-4ecd-82c6-114420ea14a4", > "event" : "runner_on_failed", > "pid" : 65899, > "created" : "2022-09-19T01:29:38.983937", > "parent_uuid" : "02113221-f1b3-920f-8bd4-003d", > "event_data" : { > "playbook" : "ovirt-host-deploy.yml", > "playbook_uuid" : "73a6e8f1-3836-49e1-82fd-5367b0bf4e90", > "play" : "all", > "play_uuid" : "02113221-f1b3-920f-8bd4-0006", > "play_pattern" : "all", > "task" : "Install ovs", > "task_uuid" : "02113221-f1b3-920f-8bd4-003d", > "task_action" : "package", > "task_args" : "", > "task_path" : > "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml:3", > "role" : "ovirt-provider-ovn-driver", > "host" : "cha2-storage.mgt.example.com", > "remote_addr" : "cha2-storage.mgt.example.com", > "res" : { > "msg" : "The conditional check 'cluster_switch == \"ovs\" or > (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The > ipaddr filter requires python's netaddr be installed on the ansible > controller\n\nThe error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: > Install ovs\n^ here\n", > "_ansible_no_log" : false > }, > "start" : "2022-09-19T01:29:38.919334", > "end" : "2022-09-19T01:29:38.983680", > "duration" : 0.064346, > "ignore_errors" : null, > "event_loop" : null, > "uuid" : "94b93e6a-5410-4d26-b058-d7d1db0a151e" > } > } > > On the engine, I have verified that netaddr is installed. And just for kicks, > I've installed as many different versions as I can find: > > [root@ovirt-engine1 host-deploy]# rpm -qa | grep netaddr > python38-netaddr-0.7.19-8.1.1.el8.noarch > python2-netaddr-0.7.19-8.1.1.el8.noarch > python3-netaddr-0.7.19-8.1.1.el8.noarch > > The engine is based on CentOS Stream 8 (when I moved the engine out of the > hyperconverged environment, my goal was to keep things as close to the > original environment as possible) > [root@ovirt-engine1 host-deploy]# cat /etc/redhat-release > CentOS Stream release 8 > > The engine is fully up-to-date: > [root@ovirt-engine1 host-deploy]# uname -a > Linux ovirt-engine1.mgt.barredowlweb.com 4.18.0-408.el8.x86_64 #1 SMP Mon Jul > 18 17:42:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux > > And the engine has the following repos: > [root@ovirt-engine1 host-deploy]# yum repolist > repo id >repo name > appstream >CentOS Stream 8 - AppStr
[ovirt-users] Re: Error during deployment of ovirt-engine
On Sat, Sep 17, 2022 at 4:15 PM wrote: > > I meant what exactly is broken and if there is a workaround or a planned fix. The breakage happened due to: - ansible-core recently moved to python 3.9 - oVirt needs several python libraries in its use of ansible, some of which are packaged by oVirt. Those are not yet built for python 3.9. > > I performed a deployment using hosted-engine. This goes on step further, but > fails while waiting for the host: > [...] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using > username/password credentials] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a > failure] > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is > not up, please check logs, perhaps also o > n the engine machine"} > [...] > > On the hosted-engine, I see in > /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20220917140938-server-005.admin.int.rabe.ch-937b3c69-a4d5-45c7-af0f-b8705490ff2a.log: > [...] > 2022-09-17 14:12:30 CEST - { > "uuid" : "97891064-a215-4709-b944-ceba2d13b19f", > "counter" : 391, > "stdout" : "fatal: [server-005.admin.int.rabe.ch]: FAILED! => {\"msg\": > \"The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter > requires python's netaddr be installed on the ansible controller\\n\\nThe > error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\\nbe elsewhere in the file depending on the exact > syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - > name: Install ovs\\n^ here\\n\"}", > [...] > > But netaddr is installed: python38-netaddr might be installed, but python39-netaddr is probably not. > [root@ovirt-engine-test host-deploy]# pip3 install netaddr > WARNING: Running pip install with root privileges is generally not a good > idea. Try `pip3 install --user` instead. > Requirement already satisfied: netaddr in /usr/lib/python3.6/site-packages > > Any ideas what I can do? For the time being, try to downgrade ansible-core to 2.12, or the last version requiring python 3.8. We merged this patch to the engine master branch (to eventually become 4.5.3): https://github.com/oVirt/ovirt-engine/pull/654 Going forward: 1. We hope to finish porting the engine to CS9 soon, and if this proves stable, consider dropping support for CS8. 2. We might try, in the time being, to build the missing dependencies for python 3.9. It's not clear if it's worth the effort. 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/ERXMH7NVN7Q6DPDJO7U5CD5XOB4YEUAQ/
[ovirt-users] Re: Should I migrate existing oVirt Engine, or deploy new?
On Sun, Sep 18, 2022 at 4:10 AM David White via Users wrote: > > I thought I'd report back to the list and mention that I was successful in > migrating off of the hyperconverged environment onto a stand-alone engine > environment, and Gluster has been removed from the oVirt configuration. Thanks for the report. > > I ran into a few minor hiccups, all of which were resolved fairly easily, and > I took notes. I intend to submit a PR to the github documentation, since none > currently exist for migrating the engine off of a hyperconverged environment. > > My only remaining questions at this point is: > > Are there things on the hosts themselves that I should cleanup? You might want to reinstall them from scratch, one-by-one, if you care that much about them being clean. I personally do not think it's worth it if your only reason is getting rid of hosted-engine remains, but you might want to do this regardless for other reasons (e.g. if they are old machines and accumulated other kinds of cruft). > I noticed that the "hosted-engine" command still exists. I went to run a yum > remove on that, and it tried to remove basically everything... You can try 'dnf remove --noautoremove ovirt-hosted-engine-setup ovirt-hosted-engine-ha'. This will remove also 'ovirt-host', which is not such a good idea - it's a package that has no content, other than a list of dependencies, on the various packages needed for a functional oVirt host. Nothing will be broken immediately, but in principle you risk losing new deps added to a future version of it, etc. > so I figured that wasn't actually a good idea. > > Do I need to do anything in the oVirt config (maybe something in the Postgres > database) to basically tell it that it is no longer self-hosted, but is > instead stand-alone? I do not know all the details, sorry. You might want to deploy a hosted-engine, dump the engine db, then search the dump for 'hosted' or something like that. Even checking a dump of a standalone engine can show you relevant stuff to check. One item I do know about is how to prevent 'engine-setup' from preventing you from continuing because it thinks it's a hosted-engine and not in global maintenance: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SKGWY5ZIBAG5GTWHIPDUO5O64PUZN7Y2/ There is also the field 'hosted_engine_configured' in 'vds_dynamic', not sure it's safe to change it outside of the engine (but no idea why it might not be). Good luck and best regards, > > > Sent with Proton Mail secure email. > > --- Original Message --- > On Friday, August 19th, 2022 at 11:01 AM, David White via Users > wrote: > > Hi Paul, > Thanks for the response. > > I think you're suggesting that I take a hybrid approach, and do a restore of > the current Engine onto the new VM. I hadn't thought about this option. > > Essentially what I was considering was either: > > Export to OVA or something > OR > Build a completely new oVirt engine with a completely new domain, etc... and > try to live migrate the VMs from the old engine to the new engine. > > > Do I understand you correctly that you're suggesting I install the OS onto a > new VM, and try to do a restore of the oVirt settings onto the new VM (after > I put the cluster into Global maintenance mode and shutdown the old oVirt)? > > Sent with Proton Mail secure email. > > --- Original Message --- > On Friday, August 19th, 2022 at 10:46 AM, Staniforth, Paul > wrote: > > Hello David, > I don't think there's a documentated method to go from > a Hosted Engine to standalone just the other way standalone to HE. > > I would suggest doing a full backup of the engine prepare the new VM and > restore to that rather than trying to export it. > This way you can shut down the original engine and run the new engine VM to > test it works as you will be able to restart the original engine if it > doesn't work. > > Regards, > Paul S. > > > > > From: David White via Users > Sent: 19 August 2022 15:27 > To: David White > Cc: oVirt Users > Subject: [ovirt-users] Re: Should I migrate existing oVirt Engine, or deploy > new? > > > Caution External Mail: Do not click any links or open any attachments unless > you trust the sender and know that the content is safe. > > In other words, I want to migrate the Engine from a hyperconverged > environment into a stand-alone setup. > > Sent with Proton Mail secure email. > > --- Original Message --- > On Friday, August 19th, 2022 at 10:17 AM, David White via Users > wrote: > > Hello, > I have just purchased a Synology SA3400 which I plan to use for my oVirt > storage domain(s) going forward. I'm currently using Gluster storage in a > hyperconverged environment. > > My goal now is to: > > Use the Synology Virtual Machine manager to host the oVirt Engine on the > Synology > Setup NFS storage on the Synology as the storage domain for all VMs in our > enviro
[ovirt-users] Re: Error during deployment of ovirt-engine
On Thu, Sep 15, 2022 at 10:46 PM Jonas wrote: > > Ok, thanks for the info. Do you have any further information? Not sure what you mean. How to deploy HE using the CLI? Here: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html Best regards, > > On 9/15/22 09:11, Yedidyah Bar David wrote: > > On Wed, Sep 14, 2022 at 11:31 PM Jonas wrote: > >> Ok even after resetting the password through SSH it is not accepted on the > >> web page. > >> > >> [root@ovirt-engine-test ~]# ovirt-aaa-jdbc-tool user password-reset admin > >> --password-valid-to="-09-14 20:07:39Z" --password="interactive:" > >> --force > >> Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > >> Password: > >> Reenter password: > >> updating user admin... > >> user updated successfully > >> > >> On 9/14/22 21:40, Jonas wrote: > >> > >> Hello all > >> > >> I'm trying to deploy an oVirt Engine through the cockpit interface. > >> Unfortunately the deployment fails with the following error: > > Sorry, but the cockpit hosted-engine deployment is broken. Please use > > the CLI. Thanks. > > > > 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/VT377NH2YGJJYKQBS66ZMOLZ26WH6GHW/
[ovirt-users] Re: Error during deployment of ovirt-engine
On Wed, Sep 14, 2022 at 11:31 PM Jonas wrote: > > Ok even after resetting the password through SSH it is not accepted on the > web page. > > [root@ovirt-engine-test ~]# ovirt-aaa-jdbc-tool user password-reset admin > --password-valid-to="-09-14 20:07:39Z" --password="interactive:" --force > Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false > Password: > Reenter password: > updating user admin... > user updated successfully > > On 9/14/22 21:40, Jonas wrote: > > Hello all > > I'm trying to deploy an oVirt Engine through the cockpit interface. > Unfortunately the deployment fails with the following error: Sorry, but the cockpit hosted-engine deployment is broken. Please use the CLI. Thanks. 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/MKXPPQJEFHKRJXFM56IULJ37K7JYSCWX/
[ovirt-users]Re: Blog Post - Using Ceph Only Storage For oVirt Datacenter by Sandro Bonazzola – Wednesday 14 July 2021
Hi Matthew, On Tue, Sep 13, 2022 at 12:26 PM Matthew J Black wrote: > > Well, if I can put my $0.02 worth in... > > What I've been trying to do is set up an oVirt cluster (v4.5.X) to use a Ceph > (Quincey) cluster as the back-end via iSCSI. One thing I found was that > up-to-date, relevant information from both the Ceph-side *and* the oVirt side > on how to do this was... hard to find, not explained very well, and often out > of date (like this relevant Blog post, if it is now out of date, and based on > the posts of this thread that is what it appears to be) - this also applies > to pre-installing / not pre-installing OpenVSwitch (see my other thread from > today). I agree. And, let me take back my previous reply, about updating the blog post. A blog post is, by definition, out-of-date, very soon after it's published. It's inside a blog, right? A kind of diary. You don't update your paper diary after you wrote some entry in it, right? Project/product Documentation, OTOH, is supposed/expected to be kept up-to-date over time. If a doc/guide is out-of-date, you'd naturally consider this a bug. Not so for a blog post. In oVirt, it's basically the same. Blog posts, here, are mainly POCs - demonstrations that something is doable. The fact that you do not find oVirt-on-Ceph in the main documentation is not a mistake - it's simply not considered (yet? See below) stable/supportable enough to enter that space. > > So I've been experimenting in a test environment (using Rocky Linux - > initially v9 but now v8.6), tearing down and re-building (physical) boxes, > and making notes for myself as I go. And, as may be implied from this and my > other thread from today, the types of problems and issues I'm encountering > are relatively trivial and easily answered **once I can get on to someone who > knows** (those issues that aren't "self-inflicted", of course). > > And for what it is worth, I am extremely grateful for the help I've received > today - thank you all! > > So if people are talking about doco, etc, then this might be worth > considering as well (ie, how to go about doing what I've been doing). > > I'm reluctant to write this up myself for a number of reasons, including (but > not limited to) the issue of maintainability, the fact that I'm not > experienced enough with oVirt to hold myself out as an "expert", and because > of an incident in the past where I ended up taking a lot of flack that wasn't > really my fault (the old "once bitten, twice shy"). I understand very well. The fact is, that no-one else did, right? If no-one does, it will never happen. What you can do: - Create a ticket/bug/issue for tracking this. Despite what perhaps some people might think, this isn't useless, even if you are not going to handle it yourself, nor know about anyone that is. - Include there what you already know and had to do. This most definitely does not put you in any position of authority - I think no-one will expect you to keep a comment in an issue up-to-date. It's less authoritative than a blog post, right? Just a comment. But it's extremely helpful, for both people that want to do what you want to do, those that want to actually handle the issue (by writing docs), and those wanting to review the eventual doc patches. - It also makes it much easier to find, link, etc., so will likely get more traction than a thread like current. I'd like to use this opportunity to add some more thoughts, at-most-tangentially related to the current thread. Speaking only for myself, not for Red Hat. Red Hat already decided that the future lies in containers, and people that still need VMs for their legacy stuff (as considered by Red Hat) should handle that inside OpenShift using CNV. See also e.g. [1] for what might eventually, when it matures enough, be a more-or-less replacement for oVirt's functionality, although definitely not for oVirt's behavior. This means, in particular, that if Red Hat decides to support so-called Hyper Converged Infrastructure (HCI) setups (or it might already have done, no idea), it will be based on OpenShift/CNV + Ceph, not RHV. AFAIU, IMHO, etc. But this does not mean that oVirt-on-Ceph HCI is impossible - it means that for this to happen, someone else should do most of the work. We (as in, Red Hat employees working on oVirt) will definitely be able to help if/where needed, but can't be expected to do the bulk of the work. I personally still think that oVirt is most probably the best small-/medium-scale Open Source clustered virtualization system. But to keep it thriving, more people should help. Including those that think that they are not experienced enough :-) > > "Anyway, it's just a thought - you all have a good day." - Beau Of The Fifth > Column Thanks for your message. I think it was helpful. [1] https://okd-virtualization.github.io/ Best regards, -- Didi ___ Users mailing list -- users@ovirt.org To unsubscribe send
[ovirt-users]Re: Blog Post - Using Ceph Only Storage For oVirt Datacenter by Sandro Bonazzola – Wednesday 14 July 2021
No idea about ceph/storage, but the cockpit deployment guide was removed because it's deprecated: https://bugzilla.redhat.com/show_bug.cgi?id=2020448 We also cleaned up various links to that guide [1], but apparently not in the blog - no idea how that one is maintained. Sandro? Perhaps this (how the blog is maintained) should also be mentioned in one of the top-level md files (README*, CONTRIBUTING.md, not sure). [1] https://github.com/oVirt/ovirt-site/issues?q=cockpit+ 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/V3R45YYRF6V7SBRY2RMMRQF4EM2WLV4A/
[ovirt-users] Re: Engine and host certificates expired
On Wed, Sep 7, 2022 at 11:58 AM wrote: > > Many thanks Didi, > > I presume the above command can be used with the --offline option > > 'engine-setup --offline > --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True' Should be, yes. 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/5UFIUXGL7YTBJ4GSWFITFBS4SG3TOLCX/
[ovirt-users] Re: oVirt 4.5.2.4 api access with keycloak
On Fri, Sep 2, 2022 at 4:07 AM Don Dupuis wrote: > > Hello > I have installed ovirt 4.5.2.4 and keycloak authentication is now standard. > On previous installs it could be accessed via a web browser as > https://engine_FQDN/ovirt-engine/api. What is the proper url syntax to work > with the new keycloak way and I know the username is now > admin@ovirt@internalsso? Should be the same - did you try this? Had problems? Which? 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/C44XLLV5WMPRX726PIQRRSRFBDWP5FDB/
[ovirt-users] Re: Engine and host certificates expired
Also: Considering that many people now have oVirt setups that are old enough to start having expired certs, and also the changes done in recent years around certs longevity, it would be nice if we have a doc page on the web site about how to handle this situation, as we see more such cases on the list. Any volunteers to start such a page? Or at least create a github issue with the details you currently know? Even such an open github issue is often easier to find and use (and link) than searching the mailing list. Best regards, On Wed, Sep 7, 2022 at 10:33 AM Yedidyah Bar David wrote: > > On Wed, Sep 7, 2022 at 12:37 AM wrote: > > > > I tried your 'Try restore old certificates and simply run again > > engine-setup' but the validation fails with: > > - > > [ ERROR ] It seems that you are running your engine inside of the > > hosted-engine VM and are not in "Global Maint > > enance" mode. > > In that case you should put the system into the "Global > > Maintenance" mode before running engine-setup, > > or the hosted-engine HA > > agent might kill the machine, which might corrupt your data. > > > > [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup > > detected, but Global Maintenance is n > > ot set. > > - > > even though I have placed it into Global Maintenance mode. > > > > The problem is that all 3 hosts are currently 'Non Responsive' > > > > FYI - In another environment where the vdsm certificates had expired on one > > of 2 clusters, copying the certs from a host in the other cluster allowed > > the hosts to become responsive so I could 'Enroll certificates'. > > I guess that the engine failed to notice the move to global > maintenance, due to the expired certs. > > If you are certain that indeed all hosts see that they are in global > maintenance - check with 'hosted-engine --vm-status' - you can update > the engine DB directly, e.g. with something like: > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/7KAHVACMATMWQZYFZLVHXEN57JPB3UWE/ > > /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c 'update > vds_statistics set ha_global_maintenance=f' > > If all you want is to enforce engine-setup to skip this check, you can > try instead: > > engine-setup --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True > > Good luck and best regards, > -- > Didi -- 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/FKPSEDBWQ4M3OA7FNQTFMBPXIEHATTCH/
[ovirt-users] Re: Engine and host certificates expired
On Wed, Sep 7, 2022 at 12:37 AM wrote: > > I tried your 'Try restore old certificates and simply run again engine-setup' > but the validation fails with: > - > [ ERROR ] It seems that you are running your engine inside of the > hosted-engine VM and are not in "Global Maint > enance" mode. > In that case you should put the system into the "Global Maintenance" > mode before running engine-setup, > or the hosted-engine HA agent might kill > the machine, which might corrupt your data. > > [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup > detected, but Global Maintenance is n > ot set. > - > even though I have placed it into Global Maintenance mode. > > The problem is that all 3 hosts are currently 'Non Responsive' > > FYI - In another environment where the vdsm certificates had expired on one > of 2 clusters, copying the certs from a host in the other cluster allowed the > hosts to become responsive so I could 'Enroll certificates'. I guess that the engine failed to notice the move to global maintenance, due to the expired certs. If you are certain that indeed all hosts see that they are in global maintenance - check with 'hosted-engine --vm-status' - you can update the engine DB directly, e.g. with something like: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/7KAHVACMATMWQZYFZLVHXEN57JPB3UWE/ /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c 'update vds_statistics set ha_global_maintenance=f' If all you want is to enforce engine-setup to skip this check, you can try instead: engine-setup --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True 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/ZHW555AFXKD3PS53G4ZCYCNYUQJXI6RQ/
[ovirt-users] Re: Self-hosted engine deploy failed
On Tue, Aug 23, 2022 at 8:01 PM Henry Wong wrote: > > Yes, I used cockpit to deploy the hosted-engine as I wasn't aware it's been > deprecated. Sorry for that. > If you believe this issue is specific to the cockpit deployment method only, Can't be certain, obviously, but it does look so - and for the CLI, unlike cockpit, we have automated testing, so at least for the common case we are likely to find bugs before actual users do. > is there a need to open a bug since it should/will be removed from cockpit in > the future, correct? If enough people want cockpit back, and enough of these people want to invest the time in maintaining it, it can live on... I didn't try cockpit myself recently, and frankly, hardly ever did overall - other than when trying to fix bugs in it. I personally find the CLI much better, main reason being that you can run it inside tmux and get back to it if the network went down in the middle. We had a bug asking to be able to return back to a running cockpit HE deploy, but eventually gave up on it - required too much work. > Just need to update the documentation to point that out? I guess so, yes. Would you like to create a documentation bug/issue for this? Or send a patch? How to do this: Start with the page you followed when deciding to deploy - the point in which you'd expect such a note - then scroll down to the bottom press either 'Report an issue with this page' or 'Edit this page'. Thanks. > > To be honest, 4.5 has been a headache for me. I have been on 4.4 for over a > year and never had so many issues. This all started from the upgrade of 4.4. > to 4.5, which caused the engine failed to start, Was this resolved? Did you report a bug? > and later found out was related to the postgresql version incompatibility > issue. PG itself? Or postgresql-jdbc? We had problems around that during 4.4 time - I think in 4.5 they are all resolved. > But it was already too late as I decided to do a fresh install and thought > it would be much cleaner and faster.In any way I have it back and it's on > 4.5 but it will make me think twice next time before going for an update. If this is a production setup, I definitely recommend trying an update on a test env beforehand. Not only for oVirt, BTW... 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/5NOZEVL3DANPZVV2PSCNMYQPQHP7V6Q6/
[ovirt-users] Re: Hosted engine restarting
On Tue, Aug 23, 2022 at 10:41 AM wrote: > > Found the problem.. > I did tcpdump and found that some DNS requests didn't get responeses. > > One of upstream DNS servers didn't have TCP enabled for DNS requests so > requests that were sent to that server were unanswered, thats why I had > Engine restarts at random times. Thanks for the update! > > Since I don't control upstream DNS servers (my ovirt DNS server is Gateway > that just resends reqests to upstream) . A tcp-level gateway? It might be not that hard to replace it with a real caching DNS server. Up to you, of course. > I am thinking that maybe ping would be better in my case for liveness check.. The reason we changed from ping (the only test we had some time ago) to dns, and from dns udp to tcp, is that many routers/switches try harder to handle tcp, under load - they assume that udp is cheaper to lose. So I'd personally consider the tcp test, unless you have other means to make sure ping is reliable, or you deliberately want the engine to move to some other host if ping fails often enough. 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/653SN2RIZTFJGFKHLQIGMOSVO5KOE6HH/
[ovirt-users] Re: Problem Upgrading DWH from 4.5.1 to 4.5.2
On Tue, Aug 23, 2022 at 8:53 AM Nur Imam Febrianto wrote: > > Hi, > > > > I’m keep getting this kind of error whenever try to run engine-setup to > upgrade my separated DWH server : > > [ 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/20-setup-ovirt-post.conf > > Log file: > /var/log/ovirt-engine/setup/ovirt-engine-setup-20220823110720-28vs78.log > > Version: otopi-1.10.2 (otopi-1.10.2-1.el8) > > [ INFO ] Stage: Environment packages setup > > [ INFO ] Stage: Programs detection > > [ INFO ] Stage: Environment customization > > > > --== PRODUCT OPTIONS ==-- > > > > [ ERROR ] Failed to execute stage 'Environment customization': > ok_to_renew_cert() missing 2 required positional arguments: 'short_life' and > 'environment' > > [ INFO ] Stage: Clean up > > > > Maybe anybody here can give any idea to solve this issue ? It's a bug, would you like to report it in bugzilla? This should fix it: https://github.com/oVirt/ovirt-dwh/pull/48 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/MRA23HEAFUNB6WCAKZU3ZESKVM4PVU3R/
[ovirt-users] Re: Self-hosted engine deploy failed
Hi, On Mon, Aug 22, 2022 at 5:45 PM Henry Wong wrote: > > I finally gave up directly installing 4.5.2 and 4.5.1. I went back to > freshly install 4.4.10 ovirt node and then deployed the 4.4.10 self-hosted > engine using the workaround here > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/ > to get the self-hosted to complete the installation. IIUC you refer to hosted-engine deployment via cockpit - the web ui - right? See also e.g. https://lists.ovirt.org/archives/list/users@ovirt.org/message/CBDUBBKLTCW4MMWCXTRXNWDYPLP5CBUP/ As I wrote there, cockpit HE deployment is deprecated, please use the CLI. That said, I am not aware of a detailed bug report. Would you like to create one in bugzilla, and attach relevant logs? If it's easy to fix, someone might fix it... > Once it's up I used the GUI to update it to 4.5.2. You mean, the engine's web admin ui, not cockpit, right? Also the engine itself can only be updated via the CLI, right now - or perhaps using the engine_setup ansible role from ovirt-ansible-collection - but I don't use it myself, nor am I aware of anyone that does - for *upgrades*. 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/HVIL5MRDVJQCRY2JK44BTG662I6ORH73/
[ovirt-users] Re: Hosted engine restarting
On Mon, Aug 22, 2022 at 11:58 AM wrote: > > > 2440 is pretty low - did you check what lowers it, other than the > > single failed network test below? > > As far as I can see in agent.log, only thing that lowers that score is > "network status" > There are a lot of lines like this: > Penalizing score by 319 due to network status > Penalizing score by 640 due to network status > Penalizing score by 1280 due to network status > Penalizing score by 960 due to network status > > > What exactly do you test? > On another vm on same host where which contains hosted engine i tried this: > 1. Continuous ping command to 8.8.8.8 (0 lost packages) > 2. dig command every second -> dig +tries=1 +time=5 +tcp (no errors, query > time between 2 and 15ms) > > > Before fixing the above bug, we added to ovirt-system-tests loops of > > 'dig', and did see drops - not many, but enough, apparently, and > > often. > > > > The 'dig' test is not very configurable, from -ha's POV - but you do > > have control over it from elsewhere - resolv.conf, your name server, > > etc. Also, note that it runs 'dig' without passing a query, and the > > default query is for '.' - the root - perhaps your name server has > > some problem with this? > Given that the dig command from the other vm goes through without problems, I > think the nameserver should be ok. Did you run such a dig loop also on the host? Does it use the same name server? > > > You can configure the agent/broker to log at DEBUG level, to see some > > more details. > > > > You can also change the network monitoring method, and/or configure > > options for methods that do have them - e.g. 'tcp' and > > 'tcp_t_address', 'tcp_t_port'. See e.g.: > > > > https://www.ovirt.org/documentation/administration_guide/index.html#Admin... > > https://www.ovirt.org/develop/release-management/features/sla/hosted-engi... > I will try this, thank you. 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/A5BZLRGHIL7A6WQLO4W4JTPIJI5CAMYF/
[ovirt-users] Re: Hosted engine restarting
On Mon, Aug 22, 2022 at 9:52 AM wrote: > > Hi! > In the last few days I am having problem with Hosted-Engine, it keeps > restarting. Sometimes after few minutes, sometimes after few hours.. > I haven't done any changes on oVirt or network in that time. > Version is 4.4.10.7-1.el8. (this was also installation version) > > Here are the logs: > Agent.log-- > MainThread::INFO::2022-08-21 > 09:48:36,200::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUp (score: 2440) 2440 is pretty low - did you check what lowers it, other than the single failed network test below? > MainThread::INFO::2022-08-21 > 09:48:36,200::hosted_engine::525::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Best remote host node3.ovirt.example.org (id: 3, score: 2440) > MainThread::ERROR::2022-08-21 > 09:48:46,212::states::398::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) > Host node3.ovirt.example.org (id 3) score is significantly better than local > score, shutting down VM on this host > MainThread::INFO::2022-08-21 > 09:48:46,641::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) > Success, was notification of state_transition (EngineUp-EngineStop) sent? > ignored > MainThread::INFO::2022-08-21 > 09:48:46,706::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineStop (score: 3400) > MainThread::INFO::2022-08-21 > 09:48:46,706::hosted_engine::525::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Best remote host node3.ovirt.example.org (id: 3, score: 3400) > MainThread::INFO::2022-08-21 > 09:48:56,714::hosted_engine::934::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) > Shutting down vm using `/usr/sbin/hosted-engine --vm-shutdown` > MainThread::INFO::2022-08-21 > 09:48:56,871::hosted_engine::941::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) > stdout: > MainThread::INFO::2022-08-21 > 09:48:56,871::hosted_engine::942::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) > stderr: > MainThread::ERROR::2022-08-21 > 09:48:56,871::hosted_engine::950::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) > Engine VM stopped on localhost > MainThread::INFO::2022-08-21 > 09:48:56,880::state_decorators::102::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(check) > Timeout set to Sun Aug 21 09:53:56 2022 while transitioning 'ovirt_hosted_engine_ha.agent.states.EngineStop'> -> 'ovirt_hosted_engine_ha.agent.states.EngineStop'> > MainThread::INFO::2022-08-21 > 09:48:56,959::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineStop (score: 3400) > MainThread::INFO::2022-08-21 > 09:49:06,977::states::537::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) > Engine vm not running on local host > MainThread::INFO::2022-08-21 > 09:49:06,983::state_decorators::95::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(check) > Timeout cleared while transitioning 'ovirt_hosted_engine_ha.agent.states.EngineStop'> -> 'ovirt_hosted_engine_ha.agent.states.EngineDown'> > MainThread::INFO::2022-08-21 > 09:49:07,173::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) > Success, was notification of state_transition (EngineStop-EngineDown) sent? > ignored > MainThread::INFO::2022-08-21 > 09:49:07,795::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineDown (score: 3400) > MainThread::INFO::2022-08-21 > 09:49:16,811::states::472::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) > Engine down and local host has best score (3400), attempting to start engine > VM > MainThread::INFO::2022-08-21 > 09:49:16,998::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) > Success, was notification of state_transition (EngineDown-EngineStart) sent? > ignored > MainThread::INFO::2022-08-21 > 09:49:17,179::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineStart (score: 3400) > MainThread::INFO::2022-08-21 > 09:49:17,195::hosted_engine::895::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state) > Ensuring VDSM state is clear for engine VM > MainThread::INFO::2022-08-21 > 09:49:17,200::hosted_engine::915::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state) > Cleaning state for non-running VM > MainThread::INFO::2022-08-21 > 09:49:18,211::hosted_engine::907::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state) > Vdsm state for VM clean > MainThread::INFO::2022-08-21 > 09:49:18,212::hosted_engine::853::ovirt
[ovirt-users] Re: Changing Cluster Compatibility Version from 4.6 to 4.7 issue
On Fri, May 27, 2022 at 11:40 AM Alexandr Mikhailov wrote: > > Hi! > Just uprgaded from 4.4. to 4.5. Had all the problems with this update, such > as postgresql-jdbc version and with stripeCount in cli.y . But I managed it, > everything works more or less. > Now I cannot raise the Cluster compatibility level. The problem is that > increasing the level tries to change something in the HE configuration but > cannot. > This is error massage: > Error while executing action: Cannot update cluster because the update > triggered update of the VMs/Templates and it failed for the following: > HostedEngine. "There was an attempt to change Hosted Engine VM values that > are locked." is one of the error(s). > > To fix the issue, please go to each VM/Template, edit, change the Custom > Compatibility Version (or other fields changed previously in the cluster > dialog) and press OK. If the save does not pass, fix the dialog validation. > After successful cluster update, you can revert your Custom Compatibility > Version change (or other changes). If the problem still persists, you may > refer to the engine.log file for further details. > If i trying to edit HE machine without changing anything i se next error: > There was an attempt to change Hosted Engine VM values that are locked/ I > think this is linked issues. > Log from engine log when i trying to update Cluster version: > 2022-05-27 14:20:54,410+06 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-212) [1b8b6b78] EVENT_ID: > CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Ca > nnot update compatibility version of Vm/Template: [HostedEngine], Message: > There was an attempt to change Hosted Engine VM values that are locked. > Log from engine log when i trying to save HE configuration without any > changing: > 2022-05-27 14:34:10,965+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] > (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock Acquired to > object 'EngineLock:{exclusiveLocks='[HostedEngine= > VM_NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' > 2022-05-27 14:34:10,968+06 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] > (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Validation of > action 'UpdateVm' failed for user admin@internal-auth > z. Reasons: > VAR__ACTION__UPDATE,VAR__TYPE__VM,VM_CANNOT_UPDATE_HOSTED_ENGINE_FIELD > 2022-05-27 14:34:10,969+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] > (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock freed to > object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_ > NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' > It is not clear what is happening and what changes to the configuration are > trying to be saved and what to do about it. Help please. On Sat, Aug 13, 2022 at 12:39 PM Alexandr Mikhailov wrote: > > This is solution: update vm_static set time_zone='Etc/GMT' where > vm_name='HostedEngine'; Thanks for the update! Arik/Liran - is this risky? If not, is it worth it to allow doing this from the engine? And/or document this? 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/3I6N53NYTUDUAIA5J7RZSMT3G4B7SVPT/
[ovirt-users] Re: Upgrade 4.4 to 4.5 node package issue
On Fri, Aug 12, 2022 at 6:23 PM Jason Beard wrote: > > You're correct, extras wasn't enabled. I enabled it and pulled the package. > Both my nodes are updated now. Thanks for the update. Which doc/guide did you follow with 'dnf install -y centos-release-ovirt45'? Perhaps you'd like to send a patch for it, or open a ticket, if needed (to enable 'extras' repo)? 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/T5FQXLZX42F3GLDI3IF2W7FQMNKTXJMF/
[ovirt-users] Re: hosted-engine --deploy --restore-from-file fails on oVirt node 4.5.1.3
On Mon, Aug 8, 2022 at 9:47 AM Yedidyah Bar David wrote: > > On Sun, Aug 7, 2022 at 6:34 AM P F wrote: > > > > I'm unable to recreate the original problem. > > > > The good news is, the process moves past the engine_setup now. > > The ovirt-engine server actually starts, and is exposed on > > https://:6900/ovirt-engine > > > > The bad news is, when I try to access the engine Web UI at that URL, I get > > a '500 Internal Server Error'. > > I don't see any obvious errors in the log files in /var/log/ovirt-engine > > Can you check/share all of /var/log/ovirt-engine and /var/log/httpd? > > > > > I'm able to access the URL https://:6900/ovirt-engine > > However, as soon as I click the "Administration Portal" link on the main > > page, I see the '500 Internal Server Error' > > > > I do notice the following error in /var/log/httpd/ssl_error_log; > > > > [Sat Aug 06 18:45:32.106641 2022] [auth_openidc:error] [pid 1648:tid > > 139896547178240] [client 192.168.222.3:58098] oidc_authenticate_user: the > > URL hostname (ovirt-engine.internal.net) of the configured OIDCRedirectURI > > does not match the URL hostname of the URL being accessed > > (ovirt-node04.internal.net): the "state" and "session" cookies will not be > > shared between the two!, referer: > > https://ovirt-node04.internal.net:6900/ovirt-engine/ > > I am not an expert on how this should work. Adding Martin. In any > case, this sounds like a bug to me, even though not sure it's > possible/easy to fix - would you like to create one? > > > > > The error above would suggest that it will not be possible to access the > > engine Web UI which is temporarily exposed on port 6900. > > Seems so. > > > How has this ever been possible in the past? > > Most likely this is a result of enabling keycloak integration. Perhaps > you can try again and answer 'No' to 'Configure Keycloak integration > on the engine'. If this works, it might be the simplest way for now - > you can enable keycloak integration later if you want. > > > What do I need to do in order to access the engine Web UI, since I need to > > configure the hosts's network to include several VLANs necessary to > > complete the restore of the engine DB? > > I am just guessing here, not knowing anything about openidc. Perhaps > it does not like being accessed as a different hostname and/or port. > > The engine does not like this either, but we "convince" it: > > [1] > https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/bootstrap_local_vm/04_engine_final_tasks.yml#L30 > > - name: Allow the webadmin UI to be accessed over the first host > block: > - name: Saving original value > ansible.builtin.replace: > path: /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf > regexp: '^(SSO_ALTERNATE_ENGINE_FQDNS=.*)' > replace: '#\1 # pre hosted-engine-setup' > - name: Adding new SSO_ALTERNATE_ENGINE_FQDNS line > ansible.builtin.lineinfile: > path: /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf > line: 'SSO_ALTERNATE_ENGINE_FQDNS="{{ he_host_address }}" # > hosted-engine-setup' > > But this isn't mandatory, it's just a convenience we added at some point. > > Instead, you can do something similar to what we do to allow access on > port 6900: > > [2] > https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml#L12 > > - name: Open a port on firewalld > ansible.builtin.command: firewall-cmd --zone=public --add-port {{ > he_webui_forward_port }}/tcp > changed_when: true > - name: Expose engine VM webui over a local port via ssh port forwarding > ansible.builtin.command: >- > sshpass -e ssh -tt -o ServerAliveInterval=5 -o > StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -g -L > {{ he_webui_forward_port }}:{{ he_fqdn }}:443 {{ he_fqdn }} > environment: > "{{ he_cmd_lang | combine( { 'SSHPASS': he_appliance_password } ) }}" > changed_when: true > async: 86400 > poll: 0 > register: sshpf > > But instead of opening the port on firewalld from the host, do the > entire tunnelling from your laptop (or where you run the web browser): > > 1. Add the engine VM's name to your /etc/hosts, to the line of '127.0.0.1' > > 2. Find the (temporary, local) IP address of the engine VM, in you
[ovirt-users] Re: hosted-engine --deploy --restore-from-file fails on oVirt node 4.5.1.3
On Sun, Aug 7, 2022 at 6:34 AM P F wrote: > > I'm unable to recreate the original problem. > > The good news is, the process moves past the engine_setup now. > The ovirt-engine server actually starts, and is exposed on > https://:6900/ovirt-engine > > The bad news is, when I try to access the engine Web UI at that URL, I get a > '500 Internal Server Error'. > I don't see any obvious errors in the log files in /var/log/ovirt-engine Can you check/share all of /var/log/ovirt-engine and /var/log/httpd? > > I'm able to access the URL https://:6900/ovirt-engine > However, as soon as I click the "Administration Portal" link on the main > page, I see the '500 Internal Server Error' > > I do notice the following error in /var/log/httpd/ssl_error_log; > > [Sat Aug 06 18:45:32.106641 2022] [auth_openidc:error] [pid 1648:tid > 139896547178240] [client 192.168.222.3:58098] oidc_authenticate_user: the URL > hostname (ovirt-engine.internal.net) of the configured OIDCRedirectURI does > not match the URL hostname of the URL being accessed > (ovirt-node04.internal.net): the "state" and "session" cookies will not be > shared between the two!, referer: > https://ovirt-node04.internal.net:6900/ovirt-engine/ I am not an expert on how this should work. Adding Martin. In any case, this sounds like a bug to me, even though not sure it's possible/easy to fix - would you like to create one? > > The error above would suggest that it will not be possible to access the > engine Web UI which is temporarily exposed on port 6900. Seems so. > How has this ever been possible in the past? Most likely this is a result of enabling keycloak integration. Perhaps you can try again and answer 'No' to 'Configure Keycloak integration on the engine'. If this works, it might be the simplest way for now - you can enable keycloak integration later if you want. > What do I need to do in order to access the engine Web UI, since I need to > configure the hosts's network to include several VLANs necessary to complete > the restore of the engine DB? I am just guessing here, not knowing anything about openidc. Perhaps it does not like being accessed as a different hostname and/or port. The engine does not like this either, but we "convince" it: [1] https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/bootstrap_local_vm/04_engine_final_tasks.yml#L30 - name: Allow the webadmin UI to be accessed over the first host block: - name: Saving original value ansible.builtin.replace: path: /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf regexp: '^(SSO_ALTERNATE_ENGINE_FQDNS=.*)' replace: '#\1 # pre hosted-engine-setup' - name: Adding new SSO_ALTERNATE_ENGINE_FQDNS line ansible.builtin.lineinfile: path: /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf line: 'SSO_ALTERNATE_ENGINE_FQDNS="{{ he_host_address }}" # hosted-engine-setup' But this isn't mandatory, it's just a convenience we added at some point. Instead, you can do something similar to what we do to allow access on port 6900: [2] https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml#L12 - name: Open a port on firewalld ansible.builtin.command: firewall-cmd --zone=public --add-port {{ he_webui_forward_port }}/tcp changed_when: true - name: Expose engine VM webui over a local port via ssh port forwarding ansible.builtin.command: >- sshpass -e ssh -tt -o ServerAliveInterval=5 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -g -L {{ he_webui_forward_port }}:{{ he_fqdn }}:443 {{ he_fqdn }} environment: "{{ he_cmd_lang | combine( { 'SSHPASS': he_appliance_password } ) }}" changed_when: true async: 86400 poll: 0 register: sshpf But instead of opening the port on firewalld from the host, do the entire tunnelling from your laptop (or where you run the web browser): 1. Add the engine VM's name to your /etc/hosts, to the line of '127.0.0.1' 2. Find the (temporary, local) IP address of the engine VM, in your case that's '192.168.222.3' 3. Create an ssh tunnel - something like: # ssh -L443:192.168.222.3:443 r...@ovirt-node04.internal.net Then you can access the engine (and keycloak) web UI via the "real" FQDN: https://ovirt-engine.internal.net/ovirt-engine/ 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/FOSD7O2OTNYB56BTWMSU6EBQ3WZJ3D3Y/
[ovirt-users] Re: Problem with engine deployment
On Tue, Aug 2, 2022 at 3:51 PM Facundo Badaracco wrote: > hi everyone, thanks for ur help. > > i tried what itforums suggested, but nothing worked. > cleaned the log, make a new run, i have found what u say david, > "otopi_net_host" but i cant find something that helps me to fix it. i have > attached the logs if u can help with this, will be greatly appreciated. > In your ovirt-hosted-engine-setup-20220802093048-j34sz6.log.txt, there is this error: 2022-08-02 09:31:17,677-0300 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py", line 156, in _customization 'otopi_host_net' KeyError: 'otopi_host_net' And indeed, you can't find 'otopi_host_net' in ovirt-hosted-engine-setup-ansible-get_network_interfaces-20220802093113-agfg7e.log.txt. In fact, the last tasks there are 'Collect Team devices', then 'Filter team devices', then 'Fail if only team devices are available', and that's it - which is very weird, as these are in filter_team_devices.yml, which is imported in the middle of 001_validate_network_interfaces.yml - right after that, it imports filter_unsupported_vlan_devices.yml, but nothing from there is in the log. The next task you should have seen is 'Search VLAN devices', as I can see in my own log (for example). Please check: - rpm -q rpm -q ovirt-ansible-collection - rpm -V ovirt-ansible-collection - Perhaps some more logs, such as /var/log/messages, journalctl, etc., that might include relevant errors from ansible. Weird. > > > if u run the deploy from cockpit, no logs are created but if i do it from > cli, the logs are created. > The cockpit deployment is deprecated. Not sure we ever announced this officially for oVirt. We did remove the cockpit-based installation guide from the documentation section on the website. It had too many problems and quite little use. So please use the CLI. Thanks. Best regards, > > > El mar, 2 ago 2022 a la(s) 02:49, escribió: > >> Hi, your issue is probably related to this >> https://www.mail-archive.com/users@ovirt.org/msg70657.html >> >> I also have 3x servers (using bond for storage network) and was able to >> successfully deploy the engine, but using the workaround suggested by 'Dax >> Kelson's thread above' and also later by editing a vars file on an ansible >> role: https://github.com/oVirt/ovirt-engine/issues/520 >> >> I'd say give it a try and let us know the outcome. >> ___ >> 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/647W6ROQFCDVKREHIZMCQ474MV3TFBNR/ >> > ___ > 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/QD65NZ5TFLZINJXAJNKF4VZHUS4P7CVG/ > -- 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/CBDUBBKLTCW4MMWCXTRXNWDYPLP5CBUP/
[ovirt-users] Re: HostedEngine Restore woes
On Thu, Aug 4, 2022 at 2:51 AM wrote: > Many thanks for your help Didi. > > I must've missed the following section you pointed out: > > | We do have a section about restoring a backup inside the engine VM, > | assuming that it's still ok - search for "Overwriting a Self-Hosted > | Engine from an Existing Backup". > > It worked perfectly thanks. > Glad to hear that. Thanks for the update! > > As for the build of a 3 node environment using Foreman and ansible, it > takes about 1-2 hours from start to finish. > Yes, we do run it routinely in our QE - but I seldom hear about real users doing that... And our QE did sometimes find bugs there, that did not affect 'hosted-engine --deploy', but I can't recall even one such bug report from a real user. The main practical difference between them, other than the obvious one of having to provide all answers in a var file beforehand, is that it does not use our ansible callback for generating the log files. Depending on how you run ansible, this will likely make it somewhat harder to investigate problems - with the callback, we log each time an ansible var changed its value, but without this callback, you rely on the code having enough 'debug' tasks at relevant points. 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/UIFDG4ZNMVWKGJ4NHTHHVBQGRSXTK4KI/
[ovirt-users] Re: Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
On Tue, Aug 2, 2022 at 4:25 PM Igor Davidoff wrote: > > works: > > --== END OF SUMMARY ==-- > > [ INFO ] Stage: Clean up > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20220802132133-qv0xmp.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20220802132206-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ INFO ] Execution of setup completed successfully Thanks for verifying and for the update! Now filed: https://bugzilla.redhat.com/show_bug.cgi?id=2113980 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/J3OOMAENCHTIEPAY6IRM226UHTMWNNVJ/
[ovirt-users] Re: Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
On Tue, Aug 2, 2022 at 3:46 PM Igor Davidoff wrote: > > Hi Didi, > > the fix did not solved the bug. > The error is now different: > > > runing "engine-setup" > > --== END OF SUMMARY ==-- > > [ ERROR ] Failed to execute stage 'Closing up': 'NoneType' object has no > attribute 'copy_to_engine' > [ INFO ] Stage: Clean up > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20220802122804-g9ybse.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20220802122925-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed > > > The part of log file with error details: > ... > 2022-08-02 12:29:25,444+ DEBUG otopi.plugins.otopi.dialog.human > dialog.__logString:204 DIALOG:SEND --== END OF SUMMARY ==-- > 2022-08-02 12:29:25,444+ DEBUG otopi.plugins.otopi.dialog.human > dialog.__logString:204 DIALOG:SEND > 2022-08-02 12:29:25,452+ DEBUG otopi.context context._executeMethod:127 > Stage closeup METHOD > otopi.plugins.ovirt_engine_setup.ovirt_engine_grafana_dwh.core.config.Plugin._closeup_engine_grafana_access > 2022-08-02 12:29:25,452+ DEBUG otopi.context context._executeMethod:145 > method exception > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in > _executeMethod > method['method']() > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/core/config.py", > line 410, in _closeup_engine_grafana_access > content=self._get_engine_access_config(), > File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/remote_engine.py", > line 88, in copy_to_engine > return self._style.copy_to_engine( > AttributeError: 'NoneType' object has no attribute 'copy_to_engine' Sorry, this was quite expected, as I wrote :-(. Can you please try this one, instead? Thanks! https://github.com/oVirt/ovirt-dwh/pull/44 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/ZNNUUCMCNRVKMDWOPDUEPZGBOUWNTMO2/
[ovirt-users] Re: Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
On Tue, Aug 2, 2022 at 3:00 PM Yedidyah Bar David wrote: > > On Tue, Aug 2, 2022 at 11:12 AM Igor Davidoff > wrote: > > > > Hi Didi, > > > > the logfile is attached. > > OK, it indeed seems like a real bug, caused by > https://github.com/oVirt/ovirt-dwh/pull/39 . > > I now pushed this fix, can you please test it? Thanks! > > https://github.com/oVirt/ovirt-dwh/pull/43 Please note that I didn't test it, and that I am not sure it makes sense in itself - perhaps we need to add a different condition to _closeup_engine_grafana_access instead (or in addition). -- 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/IAHF6XRZ7K7FIT2VZ7TPE7IQIA76POXB/
[ovirt-users] Re: Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
On Tue, Aug 2, 2022 at 11:12 AM Igor Davidoff wrote: > > Hi Didi, > > the logfile is attached. OK, it indeed seems like a real bug, caused by https://github.com/oVirt/ovirt-dwh/pull/39 . I now pushed this fix, can you please test it? Thanks! https://github.com/oVirt/ovirt-dwh/pull/43 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/YLDBJPXIPRDTJQKYTCNTUWTLCNHOONIV/
[ovirt-users] Re: HostedEngine Restore woes
On Tue, Aug 2, 2022 at 11:01 AM wrote: > > Hi All, > I've been asked to test the HE restore process but after taking a look at the > documentation I'm afraid I'm none the wiser. > I thought there would be a simple 'restore in situ' option but it appears not. Please clarify exactly what you mean. Are you currently already in a restore situation, where something is broken enough so that you want to restore from backup? What's broken? Are you preparing/exercising for a future restore event? What use-cases do you want to prepare/test for? E.g. it's very different to prepare to a case where a trivial corruption/user-error/bug/whatever "just" removed some critical files on your engine VM, and to prepare to a case where the complete site/hardware went through a natural disaster and you buy new hardware/storage/etc. and want to restore on them. And obviously there are many other cases in-between/around these. > My environments were build using ansible with a hostedengine .json answer > file. Meaning, running the hosted_engine_setup role directly? Without 'hosted-engine --deploy'? Nice to know about that - it's quite rare. > From what I've read so far it appears that a new HE VM needs to be built with > new engine storage etc Correct, in most cases. We do have a section about restoring a backup inside the engine VM, assuming that it's still ok - search for "Overwriting a Self-Hosted Engine from an Existing Backup". On Tue, Aug 2, 2022 at 11:03 AM wrote: > > ...Hit send before I'd finished. > Is there a tried and tested simple solution for restoring a hosted engine in > a 3 node HCI GlusterFS 2+1 environment please? Not sure about HCI/gluster - adding Ritesh. 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/IQ6P7L6H3BFMNF6NXJRDWLYOYWYAX2GJ/ -- 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/TQJHVKOEERWRDD65TBJRX3BMYDZGVK2V/
[ovirt-users] Re: Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
On Tue, Jul 26, 2022 at 6:08 PM Igor Davidoff wrote: > > Hello, > > while upgrading from version 4.5.0 to 4.5.1, i see now the following error > (Logfile): > " > ... > 2022-07-26 14:49:25,108+ DEBUG otopi.plugins.otopi.dialog.human > dialog.__logString:204 DIALOG:SEND > 2022-07-26 14:49:25,112+ DEBUG otopi.context context._executeMethod:127 > Stage closeup METHOD > otopi.plugins.ovirt_engine_setup.ovirt_engine_grafana_dwh.core.config.Plugin._closeup_engine_grafana_access > 2022-07-26 14:49:25,112+ DEBUG otopi.context context._executeMethod:145 > method exception > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in > _executeMethod > method['method']() > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/core/config.py", > line 398, in _closeup_engine_grafana_access > self._remote_engine.copy_to_engine( > AttributeError: 'Plugin' object has no attribute '_remote_engine' > 2022-07-26 14:49:25,127+ ERROR otopi.context context._executeMethod:154 > Failed to execute stage 'Closing up': 'Plugin' object has no attribute > '_remote_engine' Are you sure it's the only error? Please share the complete log file. Thanks. > 2022-07-26 14:49:25,127+ DEBUG otopi.context context.dumpEnvironment:765 > ENVIRONMENT DUMP - BEGIN > ... > " > > It looks like an error at the clean up stage: Not exactly: > > " > [ ERROR ] Failed to execute stage 'Closing up': 'Plugin' object has no > attribute '_remote_engine' > [ INFO ] Stage: Clean up It happened right before entering the cleanup stage, at closeup stage. > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20220726150224-tbwn3w.log > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20220726150307-setup.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Execution of setup failed > " > > Can i fix it spmoehow? > What happens at the "clean up" stage? The Service ovirt-engine-dwhd.service > is running auf the setup. Generally speaking, the closeup stage should consist of non-critical stuff, so in theory you might be ok. But I think that the real problem happened before that, and the above error is just a side-effect of it. See also the discussion here, even if probably not really relevant to your case - despite looking as if it is: https://github.com/oVirt/ovirt-engine/pull/492 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/CZLSTIYYW3M7KCCKYZXN44SDW5VDMCTX/
[ovirt-users] Re: hosted-engine --deploy --restore-from-file fails on oVirt node 4.5.1.3
On Tue, Aug 2, 2022 at 8:15 AM P F wrote: > > I'm running three oVirt 4.5.1.3 nodes with a hosted engine v4.5.1.3. > I've installed ovirt node using the iso downloaded from; > https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.1-2022062306/el8/ovirt-node-ng-installer-4.5.1-2022062306.el8.iso > > I recently attempted to reinstall the environment using a freshly taken > engine backup. > > After installing a fresh oVirt node, and copying the backup to the node, I > ran the command; > hosted-engine --deploy --restore-from-file=backup-20220723-2 > > The problem appears to occur after the engine_setup ansible task starts. > Where the error can be seen; > [ ERROR ] Failed to execute stage 'Misc configuration': > 'OVESETUP_OVN/ovirtProviderOvnSecret' Can you please check/share /var/log/ovirt-hosted-engine-setup/engine-logs*/log/ovirt-engine/setup/* ? Especially what you find there around 'OVESETUP_OVN/ovirtProviderOvnSecret'. Thanks. 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/GFNBYJS3UHRVKWO2RG5TY2ZNMYEW5YGJ/
[ovirt-users] Re: Problem with engine deployment
Hi, On Tue, Aug 2, 2022 at 2:20 AM Facundo Badaracco wrote: > > someone can help me? please > > El vie., 29 de julio de 2022 10:04, Facundo Badaracco > escribió: >> >> An update: >> >> I already tried removing the bond as i have seen in other post, same result, >> same error. >> >> El jue., 28 de julio de 2022 08:48, escribió: >>> >>> HI everyone, hope all is good. >>> >>> OS: Centos Stream >>> ovirt 4.5 >>> I'm having problems deploying the hosted engine both through cockpit and >>> cli. >>> I have 3 servers, where through cockpit, I have managed to configure and >>> deploy glusterfs without problems. but when I want to deploy the hosted >>> engine it tells me "No valid network interface has been found". Please check/share relevant logs from /var/log/ovirt-hosted-engine-setup. Thanks. In particular, search for: otopi_net_host bb_filtered_list host_net invalid_net_if otopi_host_net For reference, the relevant code is in: https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml >>> >>> the 3 servers have 2 nic each one, I have created a bond in each one with >>> cockpit and with the name bond0 and in XOR mode. It should have worked, in principle. >>> >>> if someone can help me, please. >>> ansible packages installed: >>> [root@vs05 pre_checks]# rpq -qa | ansi >>> -bash: ansi: no se encontró la orden >>> -bash: rpq: no se encontró la orden >>> [root@vs05 pre_checks]# rpq -qa |grep ansi >>> -bash: rpq: no se encontró la orden >>> [root@vs05 pre_checks]# rpm -qa |grep ansi >>> ansible-collection-ansible-posix-1.3.0-1.2.el8.noarch >>> ansible-collection-ansible-netcommon-2.2.0-3.2.el8.noarch >>> ansible-collection-ansible-utils-2.3.0-2.2.el8.noarch >>> gluster-ansible-maintenance-1.0.1-12.el8.noarch >>> gluster-ansible-features-1.0.5-15.el8.noarch >>> ovirt-ansible-collection-2.1.0-1.el8.noarch >>> gluster-ansible-cluster-1.0-5.el8.noarch >>> gluster-ansible-repositories-1.0.1-5.el8.noarch >>> ansible-core-2.12.7-1.el8.x86_64 >>> gluster-ansible-roles-1.0.5-28.el8.noarch >>> gluster-ansible-infra-1.0.4-22.el8.noarch 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/PAP5AAYTMWWJZQU6I5SIZC7K3RNAZQB2/
[ovirt-users] Re: Help needed
On Thu, Jul 21, 2022 at 10:10 AM less foobar via Users wrote: > I'll send the logs a bit later after I boot the server. OK. And about the network if you search for the error word you are getting a > ton of errors for not finding the "default" network in libvirt, this is why > I've assumed its the network > These errors are indeed weird, and might in theory cause future problems - although other than during hosted-engine deployment, oVirt does not use the 'default' libvirt network, so might be worth investigating a bit but should not be fatal - but as you can see from the log, they were ignored, and I do not think this was the root cause for the failure. 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/H2ISAWW27HVAGXIVCACFSITVERDXMUNI/
[ovirt-users] Re: Help needed
Hi, On Wed, Jul 20, 2022 at 9:18 PM less foobar via Users wrote: > > I'm installing self hosted engine and there is an error that I can't > understand can somebody help me? The logs are here: https://termbin.com/vht61 I think the relevant error from this log is: Creating initial Keycloak admin user\n[ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/usr/share/ovirt-engine/services/ovirt-engine/keycloakz26apcu3/keycloak-add-user.json Can you please check/share all of the logs under /var/log/ovirt-hosted-engine-setup, and if you can access the engine VM, also /var/log/ there? Perhaps upload to some file sharing service and add a link. In particular: I see from the above log that the appliance you use, ovirt-engine-appliance-4.5-20220511122240, while being the latest we published (in [1]), is somewhat old. This shouldn't be a problem, because during setup we also: 2022-07-20 18:56:26,297+0200 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.engine_setup : Update all packages] 2022-07-20 19:10:06,521+0200 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> 192.168.222.20] Which, as you can see, took quite some time, so hopefully worked as expected - but I can't see in this log which versions of ovirt-engine and ovirt-engine-keyclock you eventually had, before engine-setup was ran. Adding Artur, our keycloak integration developer. Artur, any idea what might have caused this error? [1] https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-appliance-4.5/el8/ On Wed, Jul 20, 2022 at 9:25 PM less foobar via Users wrote: > > I can see that its the network, Where do you see this? > but I don't get why it is not being created what is the problem with it? > Right now I have virbr0 which is the default on libvirt should I rename it > manually? Generally speaking, on a clean installation you should not need to do anything around the network yourself. 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/CXZFHVRHUPJMAGKIOXMSXNEU5QTAANSQ/
[ovirt-users] Re: Please help: Failure Restoring Data on Clean Engine After Migration
On Tue, Jul 19, 2022 at 9:38 AM Andrei Verovski wrote: > > Hi, > > > Thanks, I solved this problem before by means of executing these commands: > > su - postgres -s/bin/bash > psql -d ovirt_engine_history > > CREATE ROLE ovirt_engine_history_grafana; > ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public GRANT > SELECT ON TABLES TO ovirt_engine_history_grafana; > ALTER ROLE ovirt_engine_history_grafana WITH ENCRYPTED PASSWORD ‘my_password'; > ALTER ROLE ovirt_engine_history_grafana WITH LOGIN; So this last one, 'LOGIN', was the missing part. OK. Thanks for the update. Glad to hear that you solved it! Any other conclusions/suggestions you'd like to make? 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/D4B727TOLDUYM3BOGVVH3CCOCKCSDAD4/
[ovirt-users] Re: Please help: Failure Restoring Data on Clean Engine After Migration
On Fri, Jul 15, 2022 at 10:31 AM Andrei Verovski wrote: > > Hi, > > I did this and still struck at that Grafana stage. > > CREATE ROLE ovirt_engine_history_grafana; > ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public GRANT > SELECT ON TABLES TO ovirt_engine_history_grafana; > ALTER ROLE ovirt_engine_history_grafana WITH PASSWORD ‘my_password’; You are probably missing pg_hba.conf configuration, see e.g. https://www.ovirt.org/documentation/data_warehouse_guide/#Allowing_Read_Only_Access_to_the_History_Database . > > > How to delete Grafana completely from old setup??? I don't think we have this documented anywhere. If you only want to get rid of the setup issue, it's probably enough to edit /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, changing the line 'OVESETUP_GRAFANA_CORE/enable=bool:True' to 'OVESETUP_GRAFANA_CORE/enable=bool:False'. This will not "delete Grafana completely", only make engine-setup ignore it. > > > I don’t need it. > > Thanks in advance. > > > > > On 14 Jul 2022, at 17:37, Moritz Baumann wrote: > > > > I had a similar issue. > > > > for me, taking the password from > > /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf > > (GRAFANA_DB_PASSWORD) > > > > and set that password in postgres for the > > user ovirt_engine_history_grafana did the trick. > > > > Best > > Mo > > > > > > On 7/14/22 16:28, Andrei Verovski wrote: > >> Hi, > >> I have oVirt engine 4.4.7 running on dedicated PC (not hosted engine). > >> After several unsuccessful upgrade attempts of 4.4.7 to 4.4.10 decided to > >> install clean 4.4.10 and migrate data. > >> On old engine > >> engine-backup --scope=all --mode=backup > >> On new engine > >> engine-backup --mode=restore --provision-all-databases > >> --no-restore-permissions --file=ovirt-engine-backup-20220713160717.backup I am sorry to note that your issue was most likely caused by '--no-restore-permissions', although the documentation (including --help/manpage) does not hint about this at all. You might want to open a doc bug to document this, or even an RFE bug, to make this a separate option. for a long time, it was mandatory to pass either --no-restore-permissions or --restore-permissions: https://bugzilla.redhat.com/show_bug.cgi?id=1220791 But I recently changed this to default to --restore-permissions: https://bugzilla.redhat.com/1821018 With --restore-permissions, if you previously manually created extra users and gave them access permissions, e.g. using the doc in above link, --mode=restore could not know the passwords for these users, and created them with random passwords, outputting "- extra user '${extrau}' having grants on database ${database}, created with a random password": https://bugzilla.redhat.com/1369757 But for grafana, this isn't true - the password is saved in the above-mentioned conf, and so --mode=restore can (and does) create the user with the saved password: https://bugzilla.redhat.com/show_bug.cgi?id=1837460 Bottom line: I now think that --restore-permissions almost always makes sense, therefore changed it to be the default. If you have scripts/procedures that pass --no-restore-permissions, I recommend rethinking these and considering dropping it altogether, relying on the default, or passing --restore-permissions. A scenario I can think of where '--no-restore-permissions' does make sense: If you do have extra users you created for some other applications to access the DWH DB, and would rather not have a restore procedure replace their passwords to random ones, but prefer having your restore procedure handle this manually - restore/setup with --no-restore-permissions, then manually add the users+passwords you need and give them permissions. 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/YMNPAFLEQ62O6BYJVA6NNMCTGUCS3EWA/
[ovirt-users] Re: Error after restoring hosted-engine
On Wed, Jul 6, 2022 at 8:14 PM Roberto Bertucci wrote: > thank you Didi, > let's focus on first problem: hosted engine. > For other problems i will open other threads, just to give other users > clearer threads. > i restored the hosted engine just to move it to a new storage domain. > > I followed the step-by-step guide from redhat: > https://access.redhat.com/solutions/2998291 This is an old article, relevant for versions <= 4.2. What version do you use? > > > I already did those steps successfully, but this time i noticed that > --noansible option was no more available during provisioning step: > > hosted-engine --deploy --noansible > > become > > hosted-engine --deploy > > I tried first to use an iscsi target as new SD with no luck and then i > used an NFS SD. > Restore has been done after deploying, as documented in the link above. > In 4.2, this was possible - you were asked whether the deploy process should run engine-setup for you, and for following the above doc, you should have replied 'no', login to the engine vm, then restore, and then run engine-setup. In 4.3 and later this is not an option anymore - engine-setup is always ran, and on restore, deploy also runs the restore for you, and if you need to do/fix stuff manually in the middle, there are means for that [1]. I recommend upgrading to 4.5, anyway. 4.4 and older are EOL. > > Installation job and setup job gave no errors, but now engine is not > inside vm list. > > Any hint about what to search for? > If things went too much though, i could do a brend new install of a host > and therefore hosted engine and manage vm migration in some way (i.e. > sharing SD, exporting and importing VMs) > This is also an option and has its own pros and cons, which greatly depend on your specific needs/use case/etc. [1] https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/hosted_engine_setup#make-changes-in-the-engine-vm-during-the-deployment 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/766IM2H5YPR3ICBB5AYBXUJYNNU224JU/
[ovirt-users] Re: ONN upgrade failing due to /var/cache/dnf filling up
On Tue, Jul 5, 2022 at 4:59 PM nroach44--- via Users wrote: > I'm just wondering if anyone else has seen this, and if it's worth logging > a case? > > I've found that this seems to manifest itself as "Stop service" will > succeed in the log, and them some time later the upgrade will fail. rm -rfv > /var/cache/dnf* will resolve it. > Might be a result of https://bugzilla.redhat.com/2055829 . Can you check/share the used space you had on /var, /var/tmp, /var/cache, before and after the upgrade? Anyway, might be worth reporting this as a bug. If so, I think the fix would be to check for enough free space on /var/cache early in the upgrade process, failing if not enough with a suitable message. Makes sense to you? Do you have some other suggestion? Thanks 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/GSED23A5CTPA23D6DU3JM6QIAPNL7NV5/