And just to add, per the attached output from alex, I didn't see the
image_transfer records in command_entities.

On Wed, Jul 25, 2018 at 12:57 PM, aduckers <alex.duck...@gmail.com> wrote:

> Thanks, command outputs attached.
> Note that there are currently no transfers showing in the GUI.
>
>
>
>
> On Jul 25, 2018, at 7:03 AM, Daniel Erez <de...@redhat.com> wrote:
>
> Hi Randi,
>
> To understand if it's indeed the same issue, can you please attach the
> output of:
> - select * from image_transfers;
> - select * from command_entities;
>
> Every image_transfer record should have a correlated command_entity.
> If it's missing from entities then you probably hit a similar issue.
> In that case, you can change the image_transfers phase value to 4
> ('Pause'),
> and for cleanup, cancel the transfer manually (e.g. from webadmin -> disks
> -> cancel).
>
> On Wed, Jul 25, 2018 at 3:54 AM Randy Bender <randobe...@gmail.com> wrote:
>
>> We've just updated our hosted engine to 4.2.4.
>> When trying to place one of the hosts in maintenance mode, we get the
>> error in the subject line.  I've found the following that looks to be the
>> issue we are hitting:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1586126
>>
>> I've looked in the engine database with the following command and results:
>>
>> engine=# select disk_id from image_transfers ;
>>                disk_id
>> --------------------------------------
>>  52966b71-2d01-4a16-9830-65a888717656
>>  c72d64b7-93c9-485b-b031-29c785c5bf9a
>> (2 rows)
>>
>> Full details on these records show that they are indeed old - there are
>> no transfers actually in progress.
>>
>> Can anyone confirm the correct way to remedy this?  The bug report notes
>> changing the phase on the record in question.  Before I try that, I'd like
>> confirmation if anyone else has seen this issue and resolved it.
>> And if this is the resolution, can you describe the exact psql commands
>> to achieve this?
>>
>> Thanks
>>
>>
>>
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
>> guidelines/
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
>> message/IRT6E43OYO52CIKC42AWLQJTNIFMYF3C/
>>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
> message/E3AFM4K36HLSLT3ZFNFBJLPWT2SHFT4O/
>
>
>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OFAFLZV2MOKFDDXUXGVKBOID2R2BJA24/

Reply via email to