[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-27 Thread David White via Users 
Still banging my head against the wall on this.
The point I'm trying to make here is that when the password is wrong, or when I 
don't enter the password, I get a clear message saying that the access was 
denied.

curl -u 'admin@internal'@'PASS' -X POST 
https://ovirt-engine1.mydomain.com/ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
 -k
Enter host password for user 'admin@internal@PASS':
Erroraccess_denied: Cannot authenticate 
user 'admin@internal@PASS': No valid profile found in 
credentials..d

When I use the correct password, on the other hand, I get no stdout, making me 
believe that the (correct) password is accepted, and works.I can easily login 
to ovirt-engine/api/imagetransfers and see the XML document. 

Here is the full stdout from when I run the curl with -vv, where it prompts for 
the password, and I enter it correctly:

~$ curl -vv -u admin@internal -X POST 
https://ovirt-engine1.mydomain.com/ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
 -k
Enter host password for user 'admin@internal':
*   Trying 10.1.0.6:443...
* Connected to ovirt-engine1.mydomain.com (10.10.10.7) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; O=mydomain.com; CN=ovirt-engine1.mydomain.com
*  start date: Sep 17 00:08:06 2021 GMT
*  expire date: Oct 21 00:08:06 2022 GMT
*  issuer: C=US; O=mydomain.com; CN=ovirt-engine1.mydomain.com.51591
*  SSL certificate verify result: self signed certificate in certificate chain 
(19), continuing anyway.
* Server auth using Basic with user 'admin@internal'
> POST 
> /ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
>  HTTP/1.1
> Host: ovirt-engine1.mydomain.com
> Authorization: Basic YWRtaW5AaW5030184ZXJuYWw6d1kQnB2VHBobTlqZ2Vm0VM=
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 415 Unsupported Media Type
< Date: Wed, 27 Oct 2021 20:44:51 GMT
< Server: Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 
mod_wsgi/4.6.4 Python/3.6
< Content-Length: 0
< Correlation-Id: 2dc94c1d-d7e2-499e-9d4f-fd332260299f
<
* Connection #0 to host ovirt-engine1.mydomain.com left intact

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Saturday, October 23rd, 2021 at 3:35 AM, Strahil Nikolov via Users 
 wrote:

> That's why I put the user and the pass in single quotes... Like this: 
> 'user@domain'@'pass'
> 

> Best Regards,Strahil Nikolov
> 

> > On Thu, Oct 21, 2021 at 23:47, David White via Users 
> > wrote:___
> > 

> > 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/ZHKLXPAKQTCIWESHO33UAJA5ZO65BOGT/

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/QYF6ICREEM6IJ7O5SRONBY5V7R5YQLZ3/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-23 Thread Strahil Nikolov via Users 
That's why I put the user and the pass in single quotes... Like this: 
'user@domain'@'pass'
Best Regards,Strahil Nikolov
 
 
  On Thu, Oct 21, 2021 at 23:47, David White via Users wrote:  
 ___
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/ZHKLXPAKQTCIWESHO33UAJA5ZO65BOGT/
  
___
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/FTJ7ACB32Q2KOZ4U4JJRFSP7HIZ7SXDM/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-21 Thread David White via Users 
When I tried with admin@internal@password, I got prompted for a password.

So then, I tried admin@internal without the password, and I got prompted for 
the password.

$ curl -u admin@internal@password -X POST 
https://ovirt-engine.mydomain.com/ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
 -k
Enter host password for user 'admin@internal@password':

$ curl -u admin@internal -X POST 
https://ovirt-engine.mydomain.com/ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
 -k
Enter host password for user 'admin@internal':

In the case of admin@internal@password, I got what I suspected, which was 
access denied... 

Erroraccess_denied: Cannot authenticate 
user 'admin@internal@password': No valid profile found in 
credentials..

In the other case, there was no stdout.

So then I ran a curl with -vv for verbose stdout, and I see this interesting 
tidbit:

< HTTP/1.1 415 Unsupported Media Type< Date: Thu, 21 Oct 2021 20:41:43 GMT< 
Server: Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 
mod_wsgi/4.6.4 Python/3.6< Content-Length: 0< Correlation-Id: 
2b181b06-5b10-4b3a-a704-ee75ad2300c2<* Connection #0 to host 
ovirt-engine.mydomain.com left intact

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Wednesday, October 20th, 2021 at 11:55 PM, Strahil Nikolov 
 wrote:

> Try with curl -u 'admin@internal'@'pass' ...
> 

> Best Regards,Strahil Nikolov
> 

> > On Thu, Oct 21, 2021 at 2:17, David White via Users 
> > wrote:___
> > 

> > 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/7Z33Y3DIMNVC72N72XZP4ZZSTF3GHMWP/

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/ZHKLXPAKQTCIWESHO33UAJA5ZO65BOGT/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread Strahil Nikolov via Users 
Try with curl -u 'admin@internal'@'pass' ...
Best Regards,Strahil Nikolov
 
 
  On Thu, Oct 21, 2021 at 2:17, David White via Users wrote:   
___
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/7Z33Y3DIMNVC72N72XZP4ZZSTF3GHMWP/
  
___
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/D6VNRR7IFU2DDMDUJDKCCMAFWI7DROF2/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread David White via Users 
Ok, I was able to login to ovirt-engine/api/imagetransfers, and I see the 3 
image transfers in here.
Thanks for the help on that.

Based on the example that I'm pasting below, and based on your last email, I 
tried to run the following curl command:
$ curl -u admin@password -X POST 
https://ovirt-engine.mydomain.com/ovirt-engine/api/imagetransfers/2bf042e8-7ddd-4f43-a2b1-4a16de5c750a/finalize
 -k

That produced zero output, and when I refresh the imagetransfers xml file, the 
image is still there... so I'm not sure if it's doing anything. 

Here's an example from apti/imagetransfers:








false
upload
raw
60
finalizing_failure
https://ovirt-engine.mydomain.com:54323/images/a7b1853a-92c2-4f8a-b8ca-a25b60f86535
false
legacy
https://host1.mydomain.com:54322/images/a7b1853a-92c2-4f8a-b8ca-a25b60f86535
0




Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Wednesday, October 20th, 2021 at 7:12 AM, Eyal Shenitzky 
 wrote:

> On Wed, 20 Oct 2021 at 12:36, David White  wrote:
> 

> > Hah. Wow. 
> > Thanks for your patience on this. lol.
> > 

> > There they are! 
> > I just cross-checked these disk_id's, and can confirm these are the 3 that 
> > continue to show up in the oVirt UI.
> > 

> > engine=# SELECT command_id, disk_id, last_updated, message, timeout_policy, 
> > type, active FROM image_transfers;  command_id  |   
> >     disk_id    |    last_updated    |    
> > message    | timeout_policy | type | active
> > --+--++---++--+
> > 2bf042e8-7ddd-4f43-a2b1-4a16de5c750a | 06bd3678-bfab-4793-a839-ec8cad4b96e5 
> > | 2021-09-20 21:37:48.464-04 | Finalizing failure... | legacy |    
> > 2 | f
> > b632c4ea-2e36-44d1-858f-de03895947b1 | e0f46dc5-7f98-47cf-a586-4645177bd6a2 
> > | 2021-09-20 20:29:16.603-04 | Finalizing failure... | legacy |    
> > 2 | f
> > b6a81f14-bf3d-467d-899c-4906fef35078 | 13cef086-3878-463b-a224-cc42b44d8468 
> > | 2021-09-23 16:20:39.612-04 | Finalizing failure... | legacy |    
> > 2 | f
> > (3 rows)
> > 

> > Is it safe for me to simply run DELETE FROM image_transfers; ?
> 

> It will be better to try to finalize the transfers first - 
> 

> POST path_to_your_engine/api/imagetransfers//finalize
> 

> > Sent with ProtonMail Secure Email.
> > 

> > ‐‐‐ Original Message ‐‐‐
> > 

> > On Wednesday, October 20th, 2021 at 4:08 AM, Eyal Shenitzky 
> >  wrote:
> > 

> > > Hi David, 
> > > 

> > > Since you tried first to execute the query without semicolon the second 
> > > attempt to run the query with the semicolon failed.It considers both 
> > > lines as one query.
> > > 

> > > Try only - SELECT * FROM image_transfers;
> > > 

> > > On Tue, 19 Oct 2021 at 23:32, David White  
> > > wrote:
> > > 

> > > > I tried that, but whenever I use semicolons, I get a syntax error. 
> > > > Here's my full stdout with and without the semicolon: 
> > > > 

> > > > postgres=# \c engine
> > > > You are now connected to database "engine" as user "postgres".
> > > > engine=# SELECT * FROM image_transfers
> > > > engine-# SELECT * FROM image_transfers;
> > > > ERROR:  syntax error at or near "SELECT"
> > > > LINE 2: SELECT * FROM image_transfers;
> > > >     ^
> > > > 

> > > > Sent with ProtonMail Secure Email.
> > > > 

> > > > ‐‐‐ Original Message ‐‐‐
> > > > 

> > > > On Tuesday, October 19th, 2021 at 6:57 AM, Eyal Shenitzky 
> > > >  wrote:
> > > > 

> > > > > You are missing ';' at the end of the query.
> > > > > 

> > > > > That's why you see no output.
> > > > > 

> > > > > On Tue, 19 Oct 2021 at 13:24, David White  
> > > > > wrote:
> > > > > 

> > > > > > Thank you.
> > > > > > However, that was one of the queries I already tried.
> > > > > > 

> > > > > > All of the queries I listed in my previous email returned empty 
> > > > > > results, which is why I was confused. Given the name of some of 
> > > > > > these tables, I expect to see some data in them.
> > > > > > I just tried re-running that query, making sure to capitalize the 
> > > > > > "FROM" just in case, but got the same results:
> > > > > > 

> > > > > > engine=# SELECT * FROM image_transfers
> > > > > > engine-#
> > > > > > 

> > > > > > I then went into the UI, and migrated a VM from 1 host to another.
> > > > > > During the migration, I re-ran that query, and it still came back 
> > > > > > empty.
> > > > > > 

> > > > > > Does this table store information about moving a disk from 1 volume 
> > > > > > to another, or moving VMs from 1 host to another?
> > > > > > 

> > > > > > Sent with ProtonMail Secure Email.
> > > > > > 

> > > > > > ‐‐‐ Original Message ‐‐‐
> > > > > > 

> > > > > > On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky 
> > > > > >  wrote:
> > > > > > 

> > > > > > > Please try the following query and share the output - 
> > >

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread Eyal Shenitzky 
On Wed, 20 Oct 2021 at 12:36, David White  wrote:

> Hah. Wow.
> Thanks for your patience on this. lol.
>
> There they are!
> I just cross-checked these disk_id's, and can confirm these are the 3 that
> continue to show up in the oVirt UI.
>
> *engine=# SELECT command_id, disk_id, last_updated, message,
> timeout_policy, type, active FROM image_transfers;*
>   command_id  |
> disk_id|last_updated|message
> | timeout_policy | type | active
>
> --+--++---++--+
> 2bf042e8-7ddd-4f43-a2b1-4a16de5c750a |
> 06bd3678-bfab-4793-a839-ec8cad4b96e5 | 2021-09-20 21:37:48.464-04 |
> Finalizing failure... | legacy |2 | f
> b632c4ea-2e36-44d1-858f-de03895947b1 |
> e0f46dc5-7f98-47cf-a586-4645177bd6a2 | 2021-09-20 20:29:16.603-04 |
> Finalizing failure... | legacy |2 | f
> b6a81f14-bf3d-467d-899c-4906fef35078 |
> 13cef086-3878-463b-a224-cc42b44d8468 | 2021-09-23 16:20:39.612-04 |
> Finalizing failure... | legacy |2 | f
> (3 rows)
>
> Is it safe for me to simply run *DELETE FROM image_transfers;* ?
>

It will be better to try to finalize the transfers first -

POST path_to_your_engine/api/imagetransfers//finalize



>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, October 20th, 2021 at 4:08 AM, Eyal Shenitzky <
> eshen...@redhat.com> wrote:
>
> Hi David,
>
> Since you tried first to execute the query without semicolon the second
> attempt to run the query with the semicolon failed.
> It considers both lines as one query.
>
> Try only - SELECT * FROM image_transfers;
>
>
>
> On Tue, 19 Oct 2021 at 23:32, David White 
> wrote:
>
>> I tried that, but whenever I use semicolons, I get a syntax error. Here's
>> my full stdout with and without the semicolon:
>>
>> postgres=# \c engine
>> You are now connected to database "engine" as user "postgres".
>> engine=# SELECT * FROM image_transfers
>> engine-# SELECT * FROM image_transfers;
>> ERROR:  syntax error at or near "SELECT"
>> LINE 2: SELECT * FROM image_transfers;
>> ^
>>
>>
>>
>> Sent with ProtonMail  Secure Email.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On Tuesday, October 19th, 2021 at 6:57 AM, Eyal Shenitzky <
>> eshen...@redhat.com> wrote:
>>
>> You are missing ';' at the end of the query.
>>
>> That's why you see no output.
>>
>> On Tue, 19 Oct 2021 at 13:24, David White 
>> wrote:
>>
>>> Thank you.
>>> However, that was one of the queries I already tried.
>>>
>>> All of the queries I listed in my previous email returned empty results,
>>> which is why I was confused. Given the name of some of these tables, I
>>> expect to see some data in them.
>>> I just tried re-running that query, making sure to capitalize the "FROM"
>>> just in case, but got the same results:
>>>
>>> engine=# SELECT * FROM image_transfers
>>> engine-#
>>>
>>> I then went into the UI, and migrated a VM from 1 host to another.
>>> During the migration, I re-ran that query, and it still came back empty.
>>>
>>> Does this table store information about moving a disk from 1 volume to
>>> another, or moving VMs from 1 host to another?
>>>
>>> Sent with ProtonMail  Secure Email.
>>>
>>> ‐‐‐ Original Message ‐‐‐
>>> On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky <
>>> eshen...@redhat.com> wrote:
>>>
>>> Please try the following query and share the output -
>>>
>>> SELECT * FROM image_transfers;
>>>
>>> On Tue, 19 Oct 2021 at 03:48, David White 
>>> wrote:
>>>
 Would this be found in the "image_transfers" table?

 \dt shows me that there are 156 tables in the engine database.
 And I see an image_transfers table. But it looks empty, like a lot of
 other tables.

 This seems strange to me. All of these tables are empty, unless I'm
 doing something wrong (I'm new to Postgres).

 engine=# SELECT * from images
 engine-# SELECT * from image_transfers
 engine-# select * from users
 engine-# SELECT * from users
 engine-# SELECT * from cluster
 engine-# select * from vm_pools
 engine-# select * from vm_static


 Sent with ProtonMail  Secure Email.

 ‐‐‐ Original Message ‐‐‐
 On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky <
 eshen...@redhat.com> wrote:

 The host cannot be set to maintenance if there are image transfer with
 status different then PAUSED (by user or system - 4/5 in the DB) or
 FINISHED (success or failure - 9/10 in the DB).

 If there are image transfer session in the DB with status that is
 different then those that I mentioned, you should see why the have a
 different status and finalize/clean them before setting the host to
 maintenance.

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread David White via Users 
Hah. Wow. 
Thanks for your patience on this. lol.

There they are! 
I just cross-checked these disk_id's, and can confirm these are the 3 that 
continue to show up in the oVirt UI.

engine=# SELECT command_id, disk_id, last_updated, message, timeout_policy, 
type, active FROM image_transfers;  command_id  |   
    disk_id    |    last_updated    |    message
    | timeout_policy | type | active
--+--++---++--+
2bf042e8-7ddd-4f43-a2b1-4a16de5c750a | 06bd3678-bfab-4793-a839-ec8cad4b96e5 | 
2021-09-20 21:37:48.464-04 | Finalizing failure... | legacy |    2 | f
b632c4ea-2e36-44d1-858f-de03895947b1 | e0f46dc5-7f98-47cf-a586-4645177bd6a2 | 
2021-09-20 20:29:16.603-04 | Finalizing failure... | legacy |    2 | f
b6a81f14-bf3d-467d-899c-4906fef35078 | 13cef086-3878-463b-a224-cc42b44d8468 | 
2021-09-23 16:20:39.612-04 | Finalizing failure... | legacy |    2 | f
(3 rows)

Is it safe for me to simply run DELETE FROM image_transfers; ?

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Wednesday, October 20th, 2021 at 4:08 AM, Eyal Shenitzky 
 wrote:

> Hi David, 
> 

> Since you tried first to execute the query without semicolon the second 
> attempt to run the query with the semicolon failed.It considers both lines as 
> one query.
> 

> Try only - SELECT * FROM image_transfers;
> 

> On Tue, 19 Oct 2021 at 23:32, David White  wrote:
> 

> > I tried that, but whenever I use semicolons, I get a syntax error. Here's 
> > my full stdout with and without the semicolon: 
> > 

> > postgres=# \c engine
> > You are now connected to database "engine" as user "postgres".
> > engine=# SELECT * FROM image_transfers
> > engine-# SELECT * FROM image_transfers;
> > ERROR:  syntax error at or near "SELECT"
> > LINE 2: SELECT * FROM image_transfers;
> >     ^
> > 

> > Sent with ProtonMail Secure Email.
> > 

> > ‐‐‐ Original Message ‐‐‐
> > 

> > On Tuesday, October 19th, 2021 at 6:57 AM, Eyal Shenitzky 
> >  wrote:
> > 

> > > You are missing ';' at the end of the query.
> > > 

> > > That's why you see no output.
> > > 

> > > On Tue, 19 Oct 2021 at 13:24, David White  
> > > wrote:
> > > 

> > > > Thank you.
> > > > However, that was one of the queries I already tried.
> > > > 

> > > > All of the queries I listed in my previous email returned empty 
> > > > results, which is why I was confused. Given the name of some of these 
> > > > tables, I expect to see some data in them.
> > > > I just tried re-running that query, making sure to capitalize the 
> > > > "FROM" just in case, but got the same results:
> > > > 

> > > > engine=# SELECT * FROM image_transfers
> > > > engine-#
> > > > 

> > > > I then went into the UI, and migrated a VM from 1 host to another.
> > > > During the migration, I re-ran that query, and it still came back empty.
> > > > 

> > > > Does this table store information about moving a disk from 1 volume to 
> > > > another, or moving VMs from 1 host to another?
> > > > 

> > > > Sent with ProtonMail Secure Email.
> > > > 

> > > > ‐‐‐ Original Message ‐‐‐
> > > > 

> > > > On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky 
> > > >  wrote:
> > > > 

> > > > > Please try the following query and share the output - 
> > > > > 

> > > > > SELECT * FROM image_transfers;
> > > > > 

> > > > > On Tue, 19 Oct 2021 at 03:48, David White  
> > > > > wrote:
> > > > > 

> > > > > > Would this be found in the "image_transfers" table?
> > > > > > 

> > > > > > \dt shows me that there are 156 tables in the engine database.
> > > > > > And I see an image_transfers table. But it looks empty, like a lot 
> > > > > > of other tables. 
> > > > > > 

> > > > > > This seems strange to me. All of these tables are empty, unless I'm 
> > > > > > doing something wrong (I'm new to Postgres). 
> > > > > > 

> > > > > > engine=# SELECT * from images
> > > > > > engine-# SELECT * from image_transfers
> > > > > > engine-# select * from users
> > > > > > engine-# SELECT * from users
> > > > > > engine-# SELECT * from cluster
> > > > > > engine-# select * from vm_pools
> > > > > > engine-# select * from vm_static
> > > > > > 

> > > > > > Sent with ProtonMail Secure Email.
> > > > > > 

> > > > > > ‐‐‐ Original Message ‐‐‐
> > > > > > 

> > > > > > On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky 
> > > > > >  wrote:
> > > > > > 

> > > > > > > The host cannot be set to maintenance if there are image transfer 
> > > > > > > with status different then PAUSED (by user or system - 4/5 in the 
> > > > > > > DB) or FINISHED (success or failure - 9/10 in the DB).
> > > > > > > 

> > > > > > > If there are image transfer session in the DB with status that is 
> > > > > > > different then those that I mentioned, you should see why the 
> > > > > > > have

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread Eyal Shenitzky 
On Tue, 19 Oct 2021 at 23:49, David White via Users  wrote:

> I missed this email.
>
> You can check by getting
>
> https://myengine/ovirt-engine/api/imagetransfers
>
> If there are no image transfers, check the relevant disks status:
>
> https://myengine/ovirt-engine/api/disks/{id}
>
>
> Apparently, I don't have credentials to the API. My "admin" username &
> password aren't working, and I get this error:
> *access_denied: Cannot authenticate user 'admin@N/A': No valid profile
> found in credentials..*
>

You should provide the profile also -

*admin@*



>
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Sunday, October 17th, 2021 at 8:39 AM, Nir Soffer 
> wrote:
>
> On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
> wrote:
>
>> Thank you very much.
>> I was able to (re)set the `engine` user's password in Postgres.
>> Unfortunately, I'm still having trouble unlocking the disks.
>>
>> The following command produces no output underneath "Locked disks" when I
>> run this command on the hosted engine VM:
>>
>> *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
>> *Locked disks*
>>
>> However, in the oVirt UI, when I try to put the host into maintenance
>> mode I continue to get the message that there are (3) locked disks
>> (screenshot below).
>> [image: Screenshot from 2021-10-15 04-29-15.png]
>>
>>
> Do  you have active image transfers?
>
> You can check by getting
>
> https://myengine/ovirt-engine/api/imagetransfers
>
> If there are no image transfers, check the relevant disks status:
>
> https://myengine/ovirt-engine/api/disks/{id}
>
> If the disks status is "locked", it may be engine bug, not cleaning up
> after
> failed image transfer.
>
> If there is no task in engine using this disk, you can change the disk
> status using:
>
> # sudo -u postgres psql -d engine
>
> Finding the locked images:
>
> # select image_group_id,imagestatus from images where imagestatus=2;
>
> Unlocking an image:
>
> # update images set imagestatus=1 where image_group_id='xxx-yyy';
>
> Nir
>
>
> ___
> 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/OYR56MMJCF36RA6OIGZ3PHR2TLGY42CK/
>


-- 
Regards,
Eyal Shenitzky
___
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/LNLJ6SCLXWOROGGNBYB2MG6UFVRCNGAW/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-20 Thread Eyal Shenitzky 
Hi David,

Since you tried first to execute the query without semicolon the second
attempt to run the query with the semicolon failed.
It considers both lines as one query.

Try only - SELECT * FROM image_transfers;



On Tue, 19 Oct 2021 at 23:32, David White  wrote:

> I tried that, but whenever I use semicolons, I get a syntax error. Here's
> my full stdout with and without the semicolon:
>
> postgres=# \c engine
> You are now connected to database "engine" as user "postgres".
> engine=# SELECT * FROM image_transfers
> engine-# SELECT * FROM image_transfers;
> ERROR:  syntax error at or near "SELECT"
> LINE 2: SELECT * FROM image_transfers;
> ^
>
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, October 19th, 2021 at 6:57 AM, Eyal Shenitzky <
> eshen...@redhat.com> wrote:
>
> You are missing ';' at the end of the query.
>
> That's why you see no output.
>
> On Tue, 19 Oct 2021 at 13:24, David White 
> wrote:
>
>> Thank you.
>> However, that was one of the queries I already tried.
>>
>> All of the queries I listed in my previous email returned empty results,
>> which is why I was confused. Given the name of some of these tables, I
>> expect to see some data in them.
>> I just tried re-running that query, making sure to capitalize the "FROM"
>> just in case, but got the same results:
>>
>> engine=# SELECT * FROM image_transfers
>> engine-#
>>
>> I then went into the UI, and migrated a VM from 1 host to another.
>> During the migration, I re-ran that query, and it still came back empty.
>>
>> Does this table store information about moving a disk from 1 volume to
>> another, or moving VMs from 1 host to another?
>>
>> Sent with ProtonMail  Secure Email.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky <
>> eshen...@redhat.com> wrote:
>>
>> Please try the following query and share the output -
>>
>> SELECT * FROM image_transfers;
>>
>> On Tue, 19 Oct 2021 at 03:48, David White 
>> wrote:
>>
>>> Would this be found in the "image_transfers" table?
>>>
>>> \dt shows me that there are 156 tables in the engine database.
>>> And I see an image_transfers table. But it looks empty, like a lot of
>>> other tables.
>>>
>>> This seems strange to me. All of these tables are empty, unless I'm
>>> doing something wrong (I'm new to Postgres).
>>>
>>> engine=# SELECT * from images
>>> engine-# SELECT * from image_transfers
>>> engine-# select * from users
>>> engine-# SELECT * from users
>>> engine-# SELECT * from cluster
>>> engine-# select * from vm_pools
>>> engine-# select * from vm_static
>>>
>>>
>>> Sent with ProtonMail  Secure Email.
>>>
>>> ‐‐‐ Original Message ‐‐‐
>>> On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky <
>>> eshen...@redhat.com> wrote:
>>>
>>> The host cannot be set to maintenance if there are image transfer with
>>> status different then PAUSED (by user or system - 4/5 in the DB) or
>>> FINISHED (success or failure - 9/10 in the DB).
>>>
>>> If there are image transfer session in the DB with status that is
>>> different then those that I mentioned, you should see why the have a
>>> different status and finalize/clean them before setting the host to
>>> maintenance.
>>>
>>> On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
>>>
 On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
 wrote:

> Thank you very much.
> I was able to (re)set the `engine` user's password in Postgres.
> Unfortunately, I'm still having trouble unlocking the disks.
>
> The following command produces no output underneath "Locked disks"
> when I run this command on the hosted engine VM:
>
> *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
> *Locked disks*
>
> However, in the oVirt UI, when I try to put the host into maintenance
> mode I continue to get the message that there are (3) locked disks
> (screenshot below).
> [image: Screenshot from 2021-10-15 04-29-15.png]
>
>
 Do  you have active image transfers?

 You can check by getting

 https://myengine/ovirt-engine/api/imagetransfers

 If there are no image transfers, check the relevant disks status:

 https://myengine/ovirt-engine/api/disks/{id}

 If the disks status is "locked", it may be engine bug, not cleaning up
 after
 failed image transfer.

 If there is no task in engine using this disk, you can change the disk
 status using:

 # sudo -u postgres psql -d engine

 Finding the locked images:

 # select image_group_id,imagestatus from images where imagestatus=2;

 Unlocking an image:

 # update images set imagestatus=1 where image_group_id='xxx-yyy';

 Nir
 ___
 Users

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-19 Thread David White via Users 
I missed this email. 

> You can check by getting
> 

>    https://myengine/ovirt-engine/api/imagetransfers
>  
> If there are no image transfers, check the relevant disks status:
> 

>    https://myengine/ovirt-engine/api/disks/{id}

Apparently, I don't have credentials to the API. My "admin" username & password 
aren't working, and I get this error: 
access_denied: Cannot authenticate user 'admin@N/A': No valid profile found in 
credentials..

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Sunday, October 17th, 2021 at 8:39 AM, Nir Soffer  wrote:

> On Fri, Oct 15, 2021 at 11:38 AM David White via Users  
> wrote:
> 

> > Thank you very much.
> > I was able to (re)set the `engine` user's password in Postgres.
> > Unfortunately, I'm still having trouble unlocking the disks.
> > 

> > The following command produces no output underneath "Locked disks" when I 
> > run this command on the hosted engine VM:
> > 

> > [root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
> > /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -qLocked 
> > disks
> > 

> > However, in the oVirt UI, when I try to put the host into maintenance mode 
> > I continue to get the message that there are (3) locked disks (screenshot 
> > below).
> > [Screenshot from 2021-10-15 04-29-15.png]
> 

> Do  you have active image transfers?
> 

> You can check by getting
> 

>     https://myengine/ovirt-engine/api/imagetransfers
> 

> If there are no image transfers, check the relevant disks status:
> 

>     https://myengine/ovirt-engine/api/disks/{id}
> 

> If the disks status is "locked", it may be engine bug, not cleaning up after
> failed image transfer.
> 

> If there is no task in engine using this disk, you can change the disk status 
> using:
> 

> # sudo -u postgres psql -d engine
> 

> Finding the locked images:
> 

> # select image_group_id,imagestatus from images where imagestatus=2;
> 

> Unlocking an image:
> 

> # update images set imagestatus=1 where image_group_id='xxx-yyy';
> 

> Nir

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/OYR56MMJCF36RA6OIGZ3PHR2TLGY42CK/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-19 Thread David White via Users 
I tried that, but whenever I use semicolons, I get a syntax error. Here's my 
full stdout with and without the semicolon: 

postgres=# \c engine
You are now connected to database "engine" as user "postgres".
engine=# SELECT * FROM image_transfers
engine-# SELECT * FROM image_transfers;
ERROR:  syntax error at or near "SELECT"
LINE 2: SELECT * FROM image_transfers;
    ^

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Tuesday, October 19th, 2021 at 6:57 AM, Eyal Shenitzky  
wrote:

> You are missing ';' at the end of the query.
> 

> That's why you see no output.
> 

> On Tue, 19 Oct 2021 at 13:24, David White  wrote:
> 

> > Thank you.
> > However, that was one of the queries I already tried.
> > 

> > All of the queries I listed in my previous email returned empty results, 
> > which is why I was confused. Given the name of some of these tables, I 
> > expect to see some data in them.
> > I just tried re-running that query, making sure to capitalize the "FROM" 
> > just in case, but got the same results:
> > 

> > engine=# SELECT * FROM image_transfers
> > engine-#
> > 

> > I then went into the UI, and migrated a VM from 1 host to another.
> > During the migration, I re-ran that query, and it still came back empty.
> > 

> > Does this table store information about moving a disk from 1 volume to 
> > another, or moving VMs from 1 host to another?
> > 

> > Sent with ProtonMail Secure Email.
> > 

> > ‐‐‐ Original Message ‐‐‐
> > 

> > On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky 
> >  wrote:
> > 

> > > Please try the following query and share the output - 
> > > 

> > > SELECT * FROM image_transfers;
> > > 

> > > On Tue, 19 Oct 2021 at 03:48, David White  
> > > wrote:
> > > 

> > > > Would this be found in the "image_transfers" table?
> > > > 

> > > > \dt shows me that there are 156 tables in the engine database.
> > > > And I see an image_transfers table. But it looks empty, like a lot of 
> > > > other tables. 
> > > > 

> > > > This seems strange to me. All of these tables are empty, unless I'm 
> > > > doing something wrong (I'm new to Postgres). 
> > > > 

> > > > engine=# SELECT * from images
> > > > engine-# SELECT * from image_transfers
> > > > engine-# select * from users
> > > > engine-# SELECT * from users
> > > > engine-# SELECT * from cluster
> > > > engine-# select * from vm_pools
> > > > engine-# select * from vm_static
> > > > 

> > > > Sent with ProtonMail Secure Email.
> > > > 

> > > > ‐‐‐ Original Message ‐‐‐
> > > > 

> > > > On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky 
> > > >  wrote:
> > > > 

> > > > > The host cannot be set to maintenance if there are image transfer 
> > > > > with status different then PAUSED (by user or system - 4/5 in the DB) 
> > > > > or FINISHED (success or failure - 9/10 in the DB).
> > > > > 

> > > > > If there are image transfer session in the DB with status that is 
> > > > > different then those that I mentioned, you should see why the have a 
> > > > > different status and finalize/clean them before setting the host to 
> > > > > maintenance. 
> > > > > 

> > > > > On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
> > > > > 

> > > > > > On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
> > > > > >  wrote:
> > > > > > 

> > > > > > > Thank you very much.
> > > > > > > I was able to (re)set the `engine` user's password in Postgres.
> > > > > > > Unfortunately, I'm still having trouble unlocking the disks.
> > > > > > > 

> > > > > > > The following command produces no output underneath "Locked 
> > > > > > > disks" when I run this command on the hosted engine VM:
> > > > > > > 

> > > > > > > [root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
> > > > > > > /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk 
> > > > > > > -qLocked disks
> > > > > > > 

> > > > > > > However, in the oVirt UI, when I try to put the host into 
> > > > > > > maintenance mode I continue to get the message that there are (3) 
> > > > > > > locked disks (screenshot below).
> > > > > > > [Screenshot from 2021-10-15 04-29-15.png]
> > > > > > 

> > > > > > Do  you have active image transfers?
> > > > > > 

> > > > > > You can check by getting
> > > > > > 

> > > > > >     https://myengine/ovirt-engine/api/imagetransfers
> > > > > > 

> > > > > > If there are no image transfers, check the relevant disks status:
> > > > > > 

> > > > > >     https://myengine/ovirt-engine/api/disks/{id}
> > > > > > 

> > > > > > If the disks status is "locked", it may be engine bug, not cleaning 
> > > > > > up after
> > > > > > failed image transfer.
> > > > > > 

> > > > > > If there is no task in engine using this disk, you can change the 
> > > > > > disk status using:
> > > > > > 

> > > > > > # sudo -u postgres psql -d engine
> > > > > > 

> > > > > > Finding the locked images:
> > > > > > 

> > > > > > # select image_group_id,imagestatus from images where imagestatus=2;
> > > > > > 

> > > > > > Unlocking

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-19 Thread Eyal Shenitzky 
You are missing ';' at the end of the query.

That's why you see no output.

On Tue, 19 Oct 2021 at 13:24, David White  wrote:

> Thank you.
> However, that was one of the queries I already tried.
>
> All of the queries I listed in my previous email returned empty results,
> which is why I was confused. Given the name of some of these tables, I
> expect to see some data in them.
> I just tried re-running that query, making sure to capitalize the "FROM"
> just in case, but got the same results:
>
> engine=# SELECT * FROM image_transfers
> engine-#
>
> I then went into the UI, and migrated a VM from 1 host to another.
> During the migration, I re-ran that query, and it still came back empty.
>
> Does this table store information about moving a disk from 1 volume to
> another, or moving VMs from 1 host to another?
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky <
> eshen...@redhat.com> wrote:
>
> Please try the following query and share the output -
>
> SELECT * FROM image_transfers;
>
> On Tue, 19 Oct 2021 at 03:48, David White 
> wrote:
>
>> Would this be found in the "image_transfers" table?
>>
>> \dt shows me that there are 156 tables in the engine database.
>> And I see an image_transfers table. But it looks empty, like a lot of
>> other tables.
>>
>> This seems strange to me. All of these tables are empty, unless I'm doing
>> something wrong (I'm new to Postgres).
>>
>> engine=# SELECT * from images
>> engine-# SELECT * from image_transfers
>> engine-# select * from users
>> engine-# SELECT * from users
>> engine-# SELECT * from cluster
>> engine-# select * from vm_pools
>> engine-# select * from vm_static
>>
>>
>> Sent with ProtonMail  Secure Email.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky <
>> eshen...@redhat.com> wrote:
>>
>> The host cannot be set to maintenance if there are image transfer with
>> status different then PAUSED (by user or system - 4/5 in the DB) or
>> FINISHED (success or failure - 9/10 in the DB).
>>
>> If there are image transfer session in the DB with status that is
>> different then those that I mentioned, you should see why the have a
>> different status and finalize/clean them before setting the host to
>> maintenance.
>>
>> On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
>>
>>> On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
>>> wrote:
>>>
 Thank you very much.
 I was able to (re)set the `engine` user's password in Postgres.
 Unfortunately, I'm still having trouble unlocking the disks.

 The following command produces no output underneath "Locked disks" when
 I run this command on the hosted engine VM:

 *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
 /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
 *Locked disks*

 However, in the oVirt UI, when I try to put the host into maintenance
 mode I continue to get the message that there are (3) locked disks
 (screenshot below).
 [image: Screenshot from 2021-10-15 04-29-15.png]


>>> Do  you have active image transfers?
>>>
>>> You can check by getting
>>>
>>> https://myengine/ovirt-engine/api/imagetransfers
>>>
>>> If there are no image transfers, check the relevant disks status:
>>>
>>> https://myengine/ovirt-engine/api/disks/{id}
>>>
>>> If the disks status is "locked", it may be engine bug, not cleaning up
>>> after
>>> failed image transfer.
>>>
>>> If there is no task in engine using this disk, you can change the disk
>>> status using:
>>>
>>> # sudo -u postgres psql -d engine
>>>
>>> Finding the locked images:
>>>
>>> # select image_group_id,imagestatus from images where imagestatus=2;
>>>
>>> Unlocking an image:
>>>
>>> # update images set imagestatus=1 where image_group_id='xxx-yyy';
>>>
>>> Nir
>>> ___
>>> 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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/
>>>
>>
>>
>> --
>> Regards,
>> Eyal Shenitzky
>>
>>
>>
>
> --
> Regards,
> Eyal Shenitzky
>
>
>

-- 
Regards,
Eyal Shenitzky
___
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/5WRNDUPOM4HHNKJAIM6M5LBU74SLDP3Z/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-19 Thread David White via Users 
Thank you.
However, that was one of the queries I already tried.

All of the queries I listed in my previous email returned empty results, which 
is why I was confused. Given the name of some of these tables, I expect to see 
some data in them.
I just tried re-running that query, making sure to capitalize the "FROM" just 
in case, but got the same results:

engine=# SELECT * FROM image_transfers
engine-#

I then went into the UI, and migrated a VM from 1 host to another.
During the migration, I re-ran that query, and it still came back empty.

Does this table store information about moving a disk from 1 volume to another, 
or moving VMs from 1 host to another?

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Tuesday, October 19th, 2021 at 1:58 AM, Eyal Shenitzky  
wrote:

> Please try the following query and share the output - 
> 

> SELECT * FROM image_transfers;
> 

> On Tue, 19 Oct 2021 at 03:48, David White  wrote:
> 

> > Would this be found in the "image_transfers" table?
> > 

> > \dt shows me that there are 156 tables in the engine database.
> > And I see an image_transfers table. But it looks empty, like a lot of other 
> > tables. 
> > 

> > This seems strange to me. All of these tables are empty, unless I'm doing 
> > something wrong (I'm new to Postgres). 
> > 

> > engine=# SELECT * from images
> > engine-# SELECT * from image_transfers
> > engine-# select * from users
> > engine-# SELECT * from users
> > engine-# SELECT * from cluster
> > engine-# select * from vm_pools
> > engine-# select * from vm_static
> > 

> > Sent with ProtonMail Secure Email.
> > 

> > ‐‐‐ Original Message ‐‐‐
> > 

> > On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky 
> >  wrote:
> > 

> > > The host cannot be set to maintenance if there are image transfer with 
> > > status different then PAUSED (by user or system - 4/5 in the DB) or 
> > > FINISHED (success or failure - 9/10 in the DB).
> > > 

> > > If there are image transfer session in the DB with status that is 
> > > different then those that I mentioned, you should see why the have a 
> > > different status and finalize/clean them before setting the host to 
> > > maintenance. 
> > > 

> > > On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
> > > 

> > > > On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
> > > >  wrote:
> > > > 

> > > > > Thank you very much.
> > > > > I was able to (re)set the `engine` user's password in Postgres.
> > > > > Unfortunately, I'm still having trouble unlocking the disks.
> > > > > 

> > > > > The following command produces no output underneath "Locked disks" 
> > > > > when I run this command on the hosted engine VM:
> > > > > 

> > > > > [root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
> > > > > /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk 
> > > > > -qLocked disks
> > > > > 

> > > > > However, in the oVirt UI, when I try to put the host into maintenance 
> > > > > mode I continue to get the message that there are (3) locked disks 
> > > > > (screenshot below).
> > > > > [Screenshot from 2021-10-15 04-29-15.png]
> > > > 

> > > > Do  you have active image transfers?
> > > > 

> > > > You can check by getting
> > > > 

> > > >     https://myengine/ovirt-engine/api/imagetransfers
> > > > 

> > > > If there are no image transfers, check the relevant disks status:
> > > > 

> > > >     https://myengine/ovirt-engine/api/disks/{id}
> > > > 

> > > > If the disks status is "locked", it may be engine bug, not cleaning up 
> > > > after
> > > > failed image transfer.
> > > > 

> > > > If there is no task in engine using this disk, you can change the disk 
> > > > status using:
> > > > 

> > > > # sudo -u postgres psql -d engine
> > > > 

> > > > Finding the locked images:
> > > > 

> > > > # select image_group_id,imagestatus from images where imagestatus=2;
> > > > 

> > > > Unlocking an image:
> > > > 

> > > > # update images set imagestatus=1 where image_group_id='xxx-yyy';
> > > > 

> > > > Nir___
> > > > 

> > > > 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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/
> > > 

> > > --
> > > 

> > > Regards,
> > > Eyal Shenitzky
> 

> --
> 

> Regards,
> Eyal Shenitzky

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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:

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-19 Thread Eyal Shenitzky 
Please try the following query and share the output -

SELECT * FROM image_transfers;

On Tue, 19 Oct 2021 at 03:48, David White  wrote:

> Would this be found in the "image_transfers" table?
>
> \dt shows me that there are 156 tables in the engine database.
> And I see an image_transfers table. But it looks empty, like a lot of
> other tables.
>
> This seems strange to me. All of these tables are empty, unless I'm doing
> something wrong (I'm new to Postgres).
>
> engine=# SELECT * from images
> engine-# SELECT * from image_transfers
> engine-# select * from users
> engine-# SELECT * from users
> engine-# SELECT * from cluster
> engine-# select * from vm_pools
> engine-# select * from vm_static
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky <
> eshen...@redhat.com> wrote:
>
> The host cannot be set to maintenance if there are image transfer with
> status different then PAUSED (by user or system - 4/5 in the DB) or
> FINISHED (success or failure - 9/10 in the DB).
>
> If there are image transfer session in the DB with status that is
> different then those that I mentioned, you should see why the have a
> different status and finalize/clean them before setting the host to
> maintenance.
>
> On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
>
>> On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
>> wrote:
>>
>>> Thank you very much.
>>> I was able to (re)set the `engine` user's password in Postgres.
>>> Unfortunately, I'm still having trouble unlocking the disks.
>>>
>>> The following command produces no output underneath "Locked disks" when
>>> I run this command on the hosted engine VM:
>>>
>>> *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
>>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
>>> *Locked disks*
>>>
>>> However, in the oVirt UI, when I try to put the host into maintenance
>>> mode I continue to get the message that there are (3) locked disks
>>> (screenshot below).
>>> [image: Screenshot from 2021-10-15 04-29-15.png]
>>>
>>>
>> Do  you have active image transfers?
>>
>> You can check by getting
>>
>> https://myengine/ovirt-engine/api/imagetransfers
>>
>> If there are no image transfers, check the relevant disks status:
>>
>> https://myengine/ovirt-engine/api/disks/{id}
>>
>> If the disks status is "locked", it may be engine bug, not cleaning up
>> after
>> failed image transfer.
>>
>> If there is no task in engine using this disk, you can change the disk
>> status using:
>>
>> # sudo -u postgres psql -d engine
>>
>> Finding the locked images:
>>
>> # select image_group_id,imagestatus from images where imagestatus=2;
>>
>> Unlocking an image:
>>
>> # update images set imagestatus=1 where image_group_id='xxx-yyy';
>>
>> Nir
>> ___
>> 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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/
>>
>
>
> --
> Regards,
> Eyal Shenitzky
>
>
>

-- 
Regards,
Eyal Shenitzky
___
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/M5ZMRBXCAKVTRQPJIYV4XTHUVYGOUVBL/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-18 Thread David White via Users 
Would this be found in the "image_transfers" table?

\dt shows me that there are 156 tables in the engine database.
And I see an image_transfers table. But it looks empty, like a lot of other 
tables. 

This seems strange to me. All of these tables are empty, unless I'm doing 
something wrong (I'm new to Postgres). 

engine=# SELECT * from images
engine-# SELECT * from image_transfers
engine-# select * from users
engine-# SELECT * from users
engine-# SELECT * from cluster
engine-# select * from vm_pools
engine-# select * from vm_static

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Monday, October 18th, 2021 at 3:10 AM, Eyal Shenitzky  
wrote:

> The host cannot be set to maintenance if there are image transfer with status 
> different then PAUSED (by user or system - 4/5 in the DB) or FINISHED 
> (success or failure - 9/10 in the DB).
> 

> If there are image transfer session in the DB with status that is different 
> then those that I mentioned, you should see why the have a different status 
> and finalize/clean them before setting the host to maintenance. 
> 

> On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:
> 

> > On Fri, Oct 15, 2021 at 11:38 AM David White via Users  
> > wrote:
> > 

> > > Thank you very much.
> > > I was able to (re)set the `engine` user's password in Postgres.
> > > Unfortunately, I'm still having trouble unlocking the disks.
> > > 

> > > The following command produces no output underneath "Locked disks" when I 
> > > run this command on the hosted engine VM:
> > > 

> > > [root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
> > > /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -qLocked 
> > > disks
> > > 

> > > However, in the oVirt UI, when I try to put the host into maintenance 
> > > mode I continue to get the message that there are (3) locked disks 
> > > (screenshot below).
> > > [Screenshot from 2021-10-15 04-29-15.png]
> > 

> > Do  you have active image transfers?
> > 

> > You can check by getting
> > 

> >     https://myengine/ovirt-engine/api/imagetransfers
> > 

> > If there are no image transfers, check the relevant disks status:
> > 

> >     https://myengine/ovirt-engine/api/disks/{id}
> > 

> > If the disks status is "locked", it may be engine bug, not cleaning up after
> > failed image transfer.
> > 

> > If there is no task in engine using this disk, you can change the disk 
> > status using:
> > 

> > # sudo -u postgres psql -d engine
> > 

> > Finding the locked images:
> > 

> > # select image_group_id,imagestatus from images where imagestatus=2;
> > 

> > Unlocking an image:
> > 

> > # update images set imagestatus=1 where image_group_id='xxx-yyy';
> > 

> > Nir___
> > 

> > 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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/
> 

> --
> 

> Regards,
> Eyal Shenitzky

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/GTNZTI6NBLARGSHNUD7WIOAC4ZXFJNV4/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-18 Thread Eyal Shenitzky 
The host cannot be set to maintenance if there are image transfer with
status different then PAUSED (by user or system - 4/5 in the DB) or
FINISHED (success or failure - 9/10 in the DB).

If there are image transfer session in the DB with status that is different
then those that I mentioned, you should see why the have a different status
and finalize/clean them before setting the host to maintenance.

On Sun, 17 Oct 2021 at 15:43, Nir Soffer  wrote:

> On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
> wrote:
>
>> Thank you very much.
>> I was able to (re)set the `engine` user's password in Postgres.
>> Unfortunately, I'm still having trouble unlocking the disks.
>>
>> The following command produces no output underneath "Locked disks" when I
>> run this command on the hosted engine VM:
>>
>> *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
>> *Locked disks*
>>
>> However, in the oVirt UI, when I try to put the host into maintenance
>> mode I continue to get the message that there are (3) locked disks
>> (screenshot below).
>> [image: Screenshot from 2021-10-15 04-29-15.png]
>>
>>
> Do  you have active image transfers?
>
> You can check by getting
>
> https://myengine/ovirt-engine/api/imagetransfers
>
> If there are no image transfers, check the relevant disks status:
>
> https://myengine/ovirt-engine/api/disks/{id}
>
> If the disks status is "locked", it may be engine bug, not cleaning up
> after
> failed image transfer.
>
> If there is no task in engine using this disk, you can change the disk
> status using:
>
> # sudo -u postgres psql -d engine
>
> Finding the locked images:
>
> # select image_group_id,imagestatus from images where imagestatus=2;
>
> Unlocking an image:
>
> # update images set imagestatus=1 where image_group_id='xxx-yyy';
>
> Nir
> ___
> 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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/
>


-- 
Regards,
Eyal Shenitzky
___
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/24ROVDVAVLKFOFWNQ3QEFCYDCJ7A653E/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-17 Thread David White via Users 
Thank you.
Unfortunately, this is still an issue. 

I have indeed tried running the taskcleaner.sh script, but I just tried it 
again.

[root@ovirt-engine1 dwhite]# PGPASSWORD=password 
/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -Rt
This will remove all async_tasks table content!!!
Caution, this operation should be used with care. Please contact support prior 
to running this command
Are you sure you want to proceed? [y/n]
y
TRUNCATE TABLE

I then ran a select * from async_tasks... and we can confirm that there's zero 
rows:

engine=# SELECT * from async_tasks;task_id | action_type | status | result | 
step_id | command_id | started_at | storage_pool_id | task_type | vdsm_task_id 
| root_command_id | user_id
-+-+++-+++-+---+--+-+-
(0 rows)

I'm still unclear what SPM is.
I ran that command on the "problematic" host, and I get this stdout,

[root@cha1-storage]# vdsm-client Host getAllTasksStatusesvdsm-client: Command 
Host.getAllTasksStatuses with args {} failed:
(code=654, message=Not SPM: ())

And finally, I tried Strahil's suggestion:

[root@ovirt-engine1 dwhite]# PGPASSWORD=password 
/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all -r
##
CAUTION, this operation may lead to data corruption and should be used with 
care. Please contact support prior to running this command
##

Are you sure you want to proceed? [y/n]
y
select fn_db_unlock_all();

INSERT 0 1
unlock all  completed successfully.

Unfortunately, I'm still getting the same error message in the admin UI with 
the 3 disks listed as "image transfer in progress".

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Sunday, October 17th, 2021 at 5:34 AM, Shani Leviim  
wrote:

> Hi David,Have you tried running the taskcleaner script with the updated 
> password?$ PGPASSWORD=xx 
> /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R
> 

> You can also verify if the SPM itself has some locked tasks by running on it:
> 

>    vdsm-client Host getAllTasksStatuses
> 

> Then clear those tasks:
> 

>    vdsm-client Task clear taskID=12345
> 

> To verify there are no more async tasks, you can run this SQL query on the 
> engine:
> 

> engine=# select * from async_tasks WHERE storage_pool_id = '123'; 
> 

> Regards,
> Shani Leviim
> 

> On Sun, Oct 17, 2021 at 12:14 PM Strahil Nikolov  
> wrote:
> 

> > Try unlock_entitiy.sh with '-t all -r'
> > 

> > Best Regards,Strahil Nikolov
> > 

> > > On Sat, Oct 16, 2021 at 13:43, David White via Users 
> > > wrote:___
> > > 

> > > 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/4CUOM4K4EUKT5XUR2AW35ZCI3XKVU5TL/

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
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/WCSGZJXE26YTGOGYV7WQ5L4KYE65KOEL/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-17 Thread Nir Soffer 
On Fri, Oct 15, 2021 at 11:38 AM David White via Users 
wrote:

> Thank you very much.
> I was able to (re)set the `engine` user's password in Postgres.
> Unfortunately, I'm still having trouble unlocking the disks.
>
> The following command produces no output underneath "Locked disks" when I
> run this command on the hosted engine VM:
>
> *[root@ovirt-engine1 dwhite]# PGPASSWORD=snip
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -q*
> *Locked disks*
>
> However, in the oVirt UI, when I try to put the host into maintenance mode
> I continue to get the message that there are (3) locked disks (screenshot
> below).
> [image: Screenshot from 2021-10-15 04-29-15.png]
>
>
Do  you have active image transfers?

You can check by getting

https://myengine/ovirt-engine/api/imagetransfers

If there are no image transfers, check the relevant disks status:

https://myengine/ovirt-engine/api/disks/{id}

If the disks status is "locked", it may be engine bug, not cleaning up after
failed image transfer.

If there is no task in engine using this disk, you can change the disk
status using:

# sudo -u postgres psql -d engine

Finding the locked images:

# select image_group_id,imagestatus from images where imagestatus=2;

Unlocking an image:

# update images set imagestatus=1 where image_group_id='xxx-yyy';

Nir
___
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/3UE6CJLEGBR27KWJQH3TA5AX7LXX5URV/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-17 Thread Shani Leviim 
Hi David,
Have you tried running the taskcleaner script with the updated password?
$ PGPASSWORD=xx /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R

You can also verify if the SPM itself has some locked tasks by running on
it:
   vdsm-client Host getAllTasksStatuses

Then clear those tasks:
   vdsm-client Task clear taskID=12345

To verify there are no more async tasks, you can run this SQL query on the
engine:
engine=# select * from async_tasks WHERE storage_pool_id = '123';


*Regards,*

*Shani Leviim*


On Sun, Oct 17, 2021 at 12:14 PM Strahil Nikolov 
wrote:

> Try unlock_entitiy.sh with '-t all -r'
>
> Best Regards,
> Strahil Nikolov
>
> On Sat, Oct 16, 2021 at 13:43, David White via Users
>  wrote:
> ___
> 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/4CUOM4K4EUKT5XUR2AW35ZCI3XKVU5TL/
>
>
___
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/Q6LWCPIVDTQRQ6LOTLESYDQG45WGA6NB/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-17 Thread Strahil Nikolov via Users 
Try unlock_entitiy.sh with '-t all -r'
Best Regards,Strahil Nikolov
 
 
  On Sat, Oct 16, 2021 at 13:43, David White via Users wrote:  
 ___
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/4CUOM4K4EUKT5XUR2AW35ZCI3XKVU5TL/
  
___
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/R2M4H5PMS27MWTFJYTZACPBOUF6YIBYA/

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-16 Thread David White via Users 
This is still an issue.
As part of my troubleshooting process, I manually migrated all of the VMs off 
of this host. When I still couldn't put it into maintenance mode, I manually 
ran "yum update" from the command line, and then rebooted it.

The oVirt UI detected that it was down, and marked it as "Unavailable" for a 
while, but once the host came back up, everything was marked green again, and 
the host is a useful part of the cluster.

Unfortunately, I still cannot put it into maintenance mode because oVirt still 
thinks these disks are locked.

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Friday, October 15th, 2021 at 4:32 AM, David White via Users 
 wrote:

> Thank you very much.
> I was able to (re)set the `engine` user's password in Postgres.
> Unfortunately, I'm still having trouble unlocking the disks.
> 

> The following command produces no output underneath "Locked disks" when I run 
> this command on the hosted engine VM:
> 

> [root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -qLocked disks
> 

> However, in the oVirt UI, when I try to put the host into maintenance mode I 
> continue to get the message that there are (3) locked disks (screenshot 
> below).
> [Screenshot from 2021-10-15 04-29-15.png]
> 

> I've tried the following multiple times:
> 

> PGPASSWORD=snip /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t 
> disk 
> e0f46dc5-7f98-47cf-a586-4645177bd6a2##CAUTION,
>  this operation may lead to data corruption and should be used with care. 
> Please contact support prior to running this 
> command##Are you sure you want to 
> proceed? [y/n]yselect 
> fn_db_unlock_disk('e0f46dc5-7f98-47cf-a586-4645177bd6a2');INSERT 0 1unlock 
> disk e0f46dc5-7f98-47cf-a586-4645177bd6a2 completed successfully.
> 

> Any other ideas?
> 

> Sent with ProtonMail Secure Email.
> 

> ‐‐‐ Original Message ‐‐‐
> 

> On Thursday, October 14th, 2021 at 10:15 AM, Shani Leviim 
>  wrote:
> 

> > Hi David,
> > Taken from [1], for setting the password for the engine user.
> > su - postgres
> > 

> > psql
> > 

> > postgres=# create role engine with login encrypted password 'password';
> > 

> > You can set the password for the postgres with 'sudo passwd 
> > postgres'(Alghout the password should be postgres)
> > 

> > For unlocking the disk, follow the example here [2]
> > $ PGPASSWORD=xx ./unlock_entity.sh -t disk -q
> > 

> > [1] 
> > https://www.ovirt.org/develop/Using-oVirt-Engine-with-a-PostgreSQL-container.html[2]
> >  
> > https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html
> > 

> > Regards,
> > Shani Leviim
> > 

> > On Thu, Oct 14, 2021 at 12:45 PM David White via Users  
> > wrote:
> > 

> > > I am trying to put a host into maintenance mode, and keep getting this 
> > > error:
> > > 

> > > Error while executing action: Cannot switch Host 
> > > cha1-storage.my-domain.com to Maintenance mode. Image transfer is in 
> > > progress for the following (3) disks:
> > > 

> > > e0f46dc5-7f98-47cf-a586-4645177bd6a2,
> > > 06bd3678-bfab-4793-a839-ec8cad4b96e5,
> > > 13cef086-3878-463b-a224-cc42b44d8468
> > > 

> > > Reviewing documentation online, it seems I need to do this:
> > >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > > -t disk e0f46dc5-7f98-47cf-a586-4645177bd6a2
> > >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > > -t disk 06bd3678-bfab-4793-a839-ec8cad4b96e5
> > >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > > -t disk 13cef086-3878-463b-a224-cc42b44d8468
> > >    /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R
> > > 

> > > When I run those commands, it *seems* to run successfully.
> > > However, I don't think that I have the correct password, because I cannot 
> > > get a psql interface:
> > > 

> > > [root@ovirt-engine1 ovirt-engine]# psql -U admin -h localhost -p 5432
> > > psql: error: FATAL:  Ident authentication failed for user "admin"
> > > [root@ovirt-engine1 ovirt-engine]# psql -U admin -W -h localhost -p 5432
> > > Password:
> > > psql: error: FATAL:  Ident authentication failed for user "admin"
> > > [root@ovirt-engine1 ovirt-engine]# psql -U engine -h localhost -p 5432
> > > Password for user engine:
> > > 

> > > Checking 
> > > https://www.ovirt.org/develop/developer-guide/db-issues/postgresql-changing-db-pass.html,
> > >  I tried:
> > > [root@ovirt-engine1 ovirt-engine]# read PASSWD
> > > /etc/pki/ovirt-engine/encryptpasswd.sh
> > > [root@ovirt-engine1 ovirt-engine]# cat 
> > > /etc/pki/ovirt-engine/encryptpasswd.sh $PASSWD
> > > cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
> > > cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
> > > 

> > > I must be doing something wrong here. 
> > > 

> > > 1) How can I reset the Postgres

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-15 Thread David White via Users 
Thank you very much.
I was able to (re)set the `engine` user's password in Postgres.
Unfortunately, I'm still having trouble unlocking the disks.

The following command produces no output underneath "Locked disks" when I run 
this command on the hosted engine VM:

[root@ovirt-engine1 dwhite]# PGPASSWORD=snip 
/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -qLocked disks

However, in the oVirt UI, when I try to put the host into maintenance mode I 
continue to get the message that there are (3) locked disks (screenshot below).
[Screenshot from 2021-10-15 04-29-15.png]

I've tried the following multiple times:

PGPASSWORD=snip /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk 
e0f46dc5-7f98-47cf-a586-4645177bd6a2##CAUTION,
 this operation may lead to data corruption and should be used with care. 
Please contact support prior to running this 
command##Are you sure you want to 
proceed? [y/n]yselect 
fn_db_unlock_disk('e0f46dc5-7f98-47cf-a586-4645177bd6a2');INSERT 0 1unlock disk 
e0f46dc5-7f98-47cf-a586-4645177bd6a2 completed successfully.

Any other ideas?

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Thursday, October 14th, 2021 at 10:15 AM, Shani Leviim  
wrote:

> Hi David,
> Taken from [1], for setting the password for the engine user.
> su - postgres
> 

> psql
> 

> postgres=# create role engine with login encrypted password 'password';
> 

> You can set the password for the postgres with 'sudo passwd postgres'(Alghout 
> the password should be postgres)
> 

> For unlocking the disk, follow the example here [2]
> $ PGPASSWORD=xx ./unlock_entity.sh -t disk -q
> 

> [1] 
> https://www.ovirt.org/develop/Using-oVirt-Engine-with-a-PostgreSQL-container.html[2]
>  https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html
> 

> Regards,
> Shani Leviim
> 

> On Thu, Oct 14, 2021 at 12:45 PM David White via Users  
> wrote:
> 

> > I am trying to put a host into maintenance mode, and keep getting this 
> > error:
> > 

> > Error while executing action: Cannot switch Host cha1-storage.my-domain.com 
> > to Maintenance mode. Image transfer is in progress for the following (3) 
> > disks:
> > 

> > e0f46dc5-7f98-47cf-a586-4645177bd6a2,
> > 06bd3678-bfab-4793-a839-ec8cad4b96e5,
> > 13cef086-3878-463b-a224-cc42b44d8468
> > 

> > Reviewing documentation online, it seems I need to do this:
> >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > -t disk e0f46dc5-7f98-47cf-a586-4645177bd6a2
> >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > -t disk 06bd3678-bfab-4793-a839-ec8cad4b96e5
> >    PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh 
> > -t disk 13cef086-3878-463b-a224-cc42b44d8468
> >    /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R
> > 

> > When I run those commands, it *seems* to run successfully.
> > However, I don't think that I have the correct password, because I cannot 
> > get a psql interface:
> > 

> > [root@ovirt-engine1 ovirt-engine]# psql -U admin -h localhost -p 5432
> > psql: error: FATAL:  Ident authentication failed for user "admin"
> > [root@ovirt-engine1 ovirt-engine]# psql -U admin -W -h localhost -p 5432
> > Password:
> > psql: error: FATAL:  Ident authentication failed for user "admin"
> > [root@ovirt-engine1 ovirt-engine]# psql -U engine -h localhost -p 5432
> > Password for user engine:
> > 

> > Checking 
> > https://www.ovirt.org/develop/developer-guide/db-issues/postgresql-changing-db-pass.html,
> >  I tried:
> > [root@ovirt-engine1 ovirt-engine]# read PASSWD
> > /etc/pki/ovirt-engine/encryptpasswd.sh
> > [root@ovirt-engine1 ovirt-engine]# cat 
> > /etc/pki/ovirt-engine/encryptpasswd.sh $PASSWD
> > cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
> > cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
> > 

> > I must be doing something wrong here. 
> > 

> > 1) How can I reset the Postgres password? What user should I be using?
> > 2) Once I have the correct password, will the commands I provided earlier 
> > work to unlock the disk?
> > 

> > Sent with ProtonMail 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/AO3JBKZZDMTNTRD7GYLUKV7VG6OMVY5G/

publickey - dmwhite823@protonmail.com - 0x320CD582.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to

[ovirt-users] Re: Unable to put host in maintenance mode & unable to login to Postgres

2021-10-14 Thread Shani Leviim 
Hi David,
Taken from [1], for setting the password for the engine user.
su - postgres
psql
postgres=# create role engine with login encrypted password 'password';

You can set the password for the postgres with 'sudo passwd postgres'
(Alghout the password should be postgres)

For unlocking the disk, follow the example here [2]
$ PGPASSWORD=xx ./unlock_entity.sh -t disk -q

[1]
https://www.ovirt.org/develop/Using-oVirt-Engine-with-a-PostgreSQL-container.html
[2]
https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html


*Regards,*

*Shani Leviim*


On Thu, Oct 14, 2021 at 12:45 PM David White via Users 
wrote:

> I am trying to put a host into maintenance mode, and keep getting this
> error:
>
> Error while executing action: Cannot switch Host
> cha1-storage.my-domain.com to Maintenance mode. Image transfer is in
> progress for the following (3) disks:
>
> e0f46dc5-7f98-47cf-a586-4645177bd6a2,
> 06bd3678-bfab-4793-a839-ec8cad4b96e5,
> 13cef086-3878-463b-a224-cc42b44d8468
>
> Reviewing documentation online, it seems I need to do this:
>PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
> -t disk e0f46dc5-7f98-47cf-a586-4645177bd6a2
>PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
> -t disk 06bd3678-bfab-4793-a839-ec8cad4b96e5
>PGPASSWORD=pass /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
> -t disk 13cef086-3878-463b-a224-cc42b44d8468
>/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -R
>
> When I run those commands, it *seems* to run successfully.
> However, I don't think that I have the correct password, because I cannot
> get a psql interface:
>
> [root@ovirt-engine1 ovirt-engine]# psql -U admin -h localhost -p 5432
> psql: error: FATAL:  Ident authentication failed for user "admin"
> [root@ovirt-engine1 ovirt-engine]# psql -U admin -W -h localhost -p 5432
> Password:
> psql: error: FATAL:  Ident authentication failed for user "admin"
> [root@ovirt-engine1 ovirt-engine]# psql -U engine -h localhost -p 5432
> Password for user engine:
>
> Checking
> https://www.ovirt.org/develop/developer-guide/db-issues/postgresql-changing-db-pass.html,
> I tried:
> [root@ovirt-engine1 ovirt-engine]# read PASSWD
> /etc/pki/ovirt-engine/encryptpasswd.sh
> [root@ovirt-engine1 ovirt-engine]# cat
> /etc/pki/ovirt-engine/encryptpasswd.sh $PASSWD
> cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
> cat: /etc/pki/ovirt-engine/encryptpasswd.sh: No such file or directory
>
> I must be doing something wrong here.
>
> 1) How can I reset the Postgres password? What user should I be using?
> 2) Once I have the correct password, will the commands I provided earlier
> work to unlock the disk?
>
> Sent with ProtonMail  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/AO3JBKZZDMTNTRD7GYLUKV7VG6OMVY5G/
>
___
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/W7ULHHPWM2H6PQO6E4ZZIB3G65UUO6VA/