[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain

2023-10-25 Thread Devin A. Bougie
Thanks again, Gianluca.

I'm currently ssh'd into the new local engine VM, and Postgres is running.  
However, an engine DB doesn't exist?  Should it at this point, and do you have 
any other suggestions of where I should look?

Devin

--
[root@lnxvirt-engine ~]# su - postgres
Last login: Wed Oct 25 15:47:18 EDT 2023 on pts/0
[postgres@lnxvirt-engine ~]$ psql
psql (12.12)
Type "help" for help.

postgres=# \l
  List of databases
   Name|  Owner   | Encoding |   Collate   |Ctype|   Access 
privileges
---+--+--+-+-+---
 postgres  | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |   template0 | 
postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres  +
   |  |  | | | 
postgres=CTc/postgres
 template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres  
+
   |  |  | | | 
postgres=CTc/postgres
(3 rows)

postgres=# 
--


> On Oct 25, 2023, at 12:40 PM, Gianluca Cecchi  
> wrote:
> 
> 
> On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie  
> wrote:
> I've had a chance to try this restore again, and this time login to the local 
> (new) hosted-engine VM to verify that /root/DisableFenceAtStartupInSec.txt 
> just contains:
> to
> 
> And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new 
> hosted-engine VM, my connection closes.
> [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt
> to
> [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g 
> DisableFenceAtStartupInSec
> 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.
> Connection to 192.168.222.25 closed.
> 
> Any new suggestions or more tests I can run would be greatly appreciated.
> 
> Thanks,
> Devin
> 
> 
> The key thing here is that for some reason it seems it is not able to connect 
> to the database and so when "engine-config" command tries to get the second 
> field of the output (the " | cut -d' ' -f2" part) it gets the "to" string 
> here:
> 
> Connection to the Database failed
> and anyway it returns error with failure of the overall playbook
> It should be investigated if there is a problem with the database itself on 
> the new engine or if for some reason the "engine-config" command is not able 
> to implicitly connect to the database
> 

___
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/XJ6PEGB2LUCIOXJ5RKA35IUMIGR6LPIF/


[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

2023-10-25 Thread Michaal R via Users
I checked for the Fast Startup feature, which I figured wouldn't be enabled, 
and it's not even configurable.

I tried, again, to import from vCenter and got error "All chosen VMs couldn't 
be retrieved by the external system and therefore have been filtered. Please 
see log for details." When I look at the log, there's nothing there referencing 
the error. Not even sure I'm looking in the right place.

I fired up the VM, double verified Fast Startup was disabled, shut down the VM 
again, and exported it as an OVF (folder of files). Tried to import as Windows 
2019 x64, same error as before ("Cannot import VM. Invalid time zone for given 
OS type."). Tried to import as Other OS, failed, event ID 1153. I get the below 
error log from the import log:

{ "message": "Copying disk 1/1", "timestamp": 
"2023-10-25T10:49:56.302914729-05:00", "type": "message" }
[ 222.2] Copying disk 1/1
protocol: newstyle-fixed without TLS, using structured packets
export="":
export-size: 214748364800 (200G)
content: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 
"Invalid partition table" at offset 0x17b "Error loading operating system" at 
offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS 
(0x0,0,2), end-CHS (0x1fb,254,63), startsector 1, 4294967295 sectors
uri: nbd+unix:///?socket=/tmp/v2v.qObfRy/in0
contexts:
base:allocation
is_rotational: false
is_read_only: false
can_cache: true
can_df: true
can_fast_zero: true
can_flush: true
can_fua: true
can_multi_conn: true
can_trim: true
can_zero: true
block_size_minimum: 1
block_size_preferred: 4096
block_size_maximum: 33554432

And this from the vdsm.log file right around when the import log ends:

2023-10-25 10:54:07,224-0500 ERROR (v2v/e81442fd) [root] Job 
'e81442fd-04fc-4100-b9a1-7e0938164397' failed (v2v:851)
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
self._import()
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
self._watch_process_output()
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
_watch_process_output
for event in parser.parse(out):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
for chunk in self._iter_progress(stream):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 963, in 
_iter_progress
raise OutputParserError('copy-disk stream closed unexpectedly')
vdsm.v2v.OutputParserError: copy-disk stream closed unexpectedly


Tried importing as Other Linux. Failed, event ID 1153. Import log has below 
snippet (much like above):
export="":
export-size: 214748364800 (200G)
content: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 
"Invalid partition table" at offset 0x17b "Error loading operating system" at 
offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS 
(0x0,0,2), end-CHS (0x1fb,254,63), startsector 1, 4294967295 sectors
uri: nbd+unix:///?socket=/tmp/v2v.kRmHY0/in0
contexts:
base:allocation
is_rotational: false
is_read_only: false
can_cache: true
can_df: true
can_fast_zero: true
can_flush: true
can_fua: true
can_multi_conn: true
can_trim: true
can_zero: true
block_size_minimum: 1
block_size_preferred: 4096
block_size_maximum: 33554432

vdsm.log shows below:

2023-10-25 11:25:58,100-0500 ERROR (v2v/542ae3e4) [root] Job 
'542ae3e4-8ea8-4f85-a35f-30bc702b8d5d' failed (v2v:851)
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
self._import()
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
self._watch_process_output()
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
_watch_process_output
for event in parser.parse(out):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
for chunk in self._iter_progress(stream):
  File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 963, in 
_iter_progress
raise OutputParserError('copy-disk stream closed unexpectedly')
vdsm.v2v.OutputParserError: copy-disk stream closed unexpectedly

Not sure what's going on, since the folder that the OVF is accessible from is 
an SMB mount in /mnt/ (mount dir: /mnt/vmexports). It's mounted rw, even, in 
case it needs it, and the uid:gid is set 36:36.

Below are links to the screenshot of the directory listing for the mount point, 
as well as the vdsm and import logs. Something's not clicking with me, and it 
may just be that I've been wrestling with this issue for so long that my 
brain's gotten clouded. Thanks for the help, guys.

vmexports mount directory listing: 

[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain

2023-10-25 Thread Gianluca Cecchi
On Wed, Oct 25, 2023 at 5:50 PM Devin A. Bougie 
wrote:

> I've had a chance to try this restore again, and this time login to the
> local (new) hosted-engine VM to verify that
> /root/DisableFenceAtStartupInSec.txt just contains:
> to
>
> And if I try the "engine-config -g DisableFenceAtStartupInSec" from the
> new hosted-engine VM, my connection closes.
> [root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt
> to
> [root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g
> DisableFenceAtStartupInSec
> 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.
> Connection to 192.168.222.25 closed.
>
> Any new suggestions or more tests I can run would be greatly appreciated.
>
> Thanks,
> Devin
>
>
The key thing here is that for some reason it seems it is not able to
connect to the database and so when "engine-config" command tries to get
the second field of the output (the " | cut -d' ' -f2" part) it gets the
"to" string here:

Connection to the Database failed
and anyway it returns error with failure of the overall playbook
It should be investigated if there is a problem with the database itself on
the new engine or if for some reason the "engine-config" command is not
able to implicitly connect to the database
___
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/FR7KU3LAMEDTAZYBWJM4JO22M3FUVO65/


[ovirt-users] Re: Hosted-engine restore failing when migrating to new storage domain

2023-10-25 Thread Devin A. Bougie
I've had a chance to try this restore again, and this time login to the local 
(new) hosted-engine VM to verify that /root/DisableFenceAtStartupInSec.txt just 
contains:
to

And if I try the "engine-config -g DisableFenceAtStartupInSec" from the new 
hosted-engine VM, my connection closes.
[root@lnxvirt-engine ~]# cat /root/DisableFenceAtStartupInSec.txt
to
[root@lnxvirt-engine ~]# set -euo pipefail && engine-config -g 
DisableFenceAtStartupInSec
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.
Connection to 192.168.222.25 closed.

Any new suggestions or more tests I can run would be greatly appreciated.

Thanks,
Devin

> On Oct 15, 2023, at 9:10 AM, Devin A. Bougie  wrote:
> 
> Hi Gianluca,
> 
> Thanks for taking another look.  I'm not sure what to make of 
> /var/log/ovirt-hosted-engine-setup/engine-logs-2023-10-14T14:30:39Z/log/ovirt-engine/setup/restore-backup-20231014150412.log,
>  but here it is.  Does that explain anything to you, or give an idea of where 
> to look next?
> 
> Thanks again!
> Devin
> 
> --
> 2023-10-14 11:04:12 7680: Start of engine-backup mode restore scope all file 
> /root/engine_backup
> 2023-10-14 11:04:12 7680: OUTPUT: Start of engine-backup with mode 'restore'
> 2023-10-14 11:04:12 7680: OUTPUT: scope: all
> 2023-10-14 11:04:12 7680: OUTPUT: archive file: /root/engine_backup
> 2023-10-14 11:04:12 7680: OUTPUT: log file: 
> /var/log/ovirt-engine/setup/restore-backup-20231014150412.log
> 2023-10-14 11:04:12 7680: OUTPUT: Preparing to restore:
> 2023-10-14 11:04:12 7680: OUTPUT: - Unpacking file '/root/engine_backup'
> 2023-10-14 11:04:12 7680: Opening tarball /root/engine_backup to 
> /tmp/engine-backup.Onm6LsDR0g
> 2023-10-14 11:04:13 7680: Verifying hash
> 2023-10-14 11:04:13 7680: Verifying version
> 2023-10-14 11:04:13 7680: Reading config
> 2023-10-14 11:04:13 7680: Scope after checking backup content:
> 2023-10-14 11:04:13 7680: SCOPE_FILES:1
> 2023-10-14 11:04:13 7680: SCOPE_ENGINE_DB:1
> 2023-10-14 11:04:13 7680: SCOPE_DWH_DB:1
> 2023-10-14 11:04:13 7680: SCOPE_CINDERLIB_DB:
> 2023-10-14 11:04:13 7680: SCOPE_KEYCLOAK_DB:
> 2023-10-14 11:04:13 7680: SCOPE_GRAFANA_DB:1
> 2023-10-14 11:04:13 7680: OUTPUT: Restoring:
> 2023-10-14 11:04:13 7680: OUTPUT: - Files
> 2023-10-14 11:04:13 7680: Restoring files
> tar: var/lib/grafana/plugins/performancecopilot-pcp-app: Cannot open: File 
> exists
> tar: Exiting with failure status due to previous errors
> 2023-10-14 11:04:13 7680: FATAL: Failed restoring /etc/ovirt-engine
> /etc/ovirt-engine-dwh
> /etc/ovirt-provider-ovn/conf.d
> /etc/ovirt-provider-ovn/logger.conf
> /etc/ovirt-vmconsole
> /etc/pki/ovirt-engine
> /etc/pki/ovirt-vmconsole
> /etc/ovirt-engine-setup.conf.d
> /etc/httpd/conf.d/internalsso-openidc.conf
> /etc/httpd/conf.d/ovirt-engine-grafana-proxy.conf
> /etc/httpd/conf.d/ovirt-engine-root-redirect.conf
> /etc/httpd/conf.d/ssl.conf
> /etc/httpd/conf.d/z-ovirt-engine-proxy.conf
> /etc/httpd/conf.d/z-ovirt-engine-keycloak-proxy.conf
> /etc/httpd/http.keytab
> /etc/httpd/conf.d/ovirt-sso.conf
> /etc/yum/pluginconf.d/versionlock.list
> /etc/dnf/plugins/versionlock.list
> /etc/firewalld/services/ovirt-https.xml
> /etc/firewalld/services/ovirt-http.xml
> /etc/firewalld/services/ovirt-postgres.xml
> /etc/firewalld/services/ovirt-provider-ovn.xml
> /etc/firewalld/services/ovn-central-firewall-service.xml
> /var/lib/openvswitch
> /etc/grafana
> /var/lib/ovirt-engine/content
> /var/lib/ovirt-engine/setup
> /var/lib/grafana/plugins
> --
> 
>> On Oct 15, 2023, at 5:59 AM, Gianluca Cecchi  
>> wrote:
>> 
>> On Sat, Oct 14, 2023 at 7:05 PM Devin A. Bougie  
>> wrote:
>> [snip] 
>> Any additional questions or suggestions would be greatly appreciated.
>> 
>> Thanks again,
>> Devin
>> 
>> 
>> There is another FATAL line regarding restore itself, before the message I 
>> pointed out in my previous message.
>> Can you analyze and/or share the contents of 
>> /var/log/ovirt-engine/setup/restore-backup-20231014150412.log?
>> 
>> Gianluca
> 

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7LPPXNHQV3YCVSA7CSJHRXYU3T2FWQF/


[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

2023-10-25 Thread Tomáš Golembiovský
On Tue, Oct 24, 2023 at 01:16:27PM -, Michaal R via Users wrote:
> Well, that's interesting... I wonder if the other imports I've tried give the 
> same error. That VM SHOULD have been shut down properly, but I'll check 
> again. I've three VMs that won't import, I'll check them again. Do you have 
> any insight into why the import from vCenter doesn't work? 

Well if you say that you stopped the VM and it is not hibernated then
the reason is most likely the Fast Startup feature of Windows. You can
temporarily enforce shutdown if you hold 'Shift' key when you select
'Shutdown'. If you want to disable Fast Startup then I suggest you
search the web. There are plenty of manuals covering that based on the
Windows version.

Tomas


> ___
> 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/ROIZLLQMKJO4X2I5AQGQCZEZCSSGAACT/
___
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/725GLOOME7HF6AUZVXT3NYGDTLGGXDIU/