date:20181218

[ovirt-users] Re: Backup & Restore

2018-12-18 Thread Yedidyah Bar David

On Tue, Dec 18, 2018 at 5:20 PM Torsten Stolpmann
 wrote:
>
> Hi Yedidyah,
>
> please find the logs at the following URL:
> http://www.klaros-testmanagement.com/files/ovirt/ovirt-restore-logs.tar.gz
>
> Let me know once you received them safely so I can remove them again.

Done.

>
> I also added the restore.log containing the actual error which occured
> during the restore.
>
> Since this was a clean system I restored on, the setup has been executed
> after the database restore, so the setup logs probably contain nothing
> of interest. I added them anyway.

Sorry I wasn't clear enough. I meant the setup logs on the machine used
to create the backup. So that I can try to see why your backup contained
this function. Do you still have these by any chance?

Indeed, I can't see anything wrong in the logs above.

>
> Please let me know if there is anything I can add to this.

If you do not have setup logs from the original machine, at least try
to think about its history and tell us notable points - including entire
version history, setup/upgrade (or similar) problems you had there (and
perhaps worked around), etc.

If you, or anyone, manages to come up with a flow resulting in a 4.2
engine database that contains a function uuid_generate_v1 in the engine
database schema, I'd definitely want to know about it.

Re-adding others posting in this thread, in case someone has a clue.
Perhaps one of you has setup logs of the machine on which the backup
was generated? If so, please share. Thanks.

That said, on a second thought, the implications of this are not that
significant - mainly somewhat lower performance - so perhaps it's more
important to fix your bug (by adding a line to IGNORED_ERRORS, as you
suggested)... but it's still weird.

Thanks and best regards,

>
> Cheers,
>
> Torsten
>
>
> On 18.12.2018 07:54, Yedidyah Bar David wrote:
> > On Mon, Dec 17, 2018 at 2:26 PM Torsten Stolpmann
> >  wrote:
> >>
> >> I experienced the same issue while restoring a full backup (engine &
> >> dwh) on a clean machine. Both machines are running CentOS 7.6 and
> >> oVirt 4.2.7.
> >>
> >> The issue went away when adding the following line to the IGNORED_ERRORS
> >> list starting at 1944 in engine-backup:
> >>
> >> must be owner of function uuid_generate_v1
> >>
> >> Hope this helps,
> >
> > It does, and thanks for the report!
> >
> > Can you please share all of your setup logs (/var/log/ovirt-engine/setup/*)?
> >
> > Thanks!
> >
> > More details:
> >
> > This function should not normally be included in a 4.2 backup, and I do
> > not yet understand why you get this error.
> >
> > If it's a clean 4.2 setup, it should never have been defined.
> > Earlier versions did create it, and the upgrade process should have
> > dropped it, if it's an upgraded setup. See also:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1515635
> >
> > Best regards,
> >
> >>
> >> Torsten
> >>
> >> On 24.05.2018 11:32, emmanuel.the...@obs-nancay.fr wrote:
> >>> hi,
> >>>
> >>> I have the same error when I try to restore on a new hosted VM (ovirt 
> >>> 4.2.3)
> >>> Have you a solution ?
> >>>
> >>> Emmanuel
> >>> ___
> >>> Users mailing list -- users@ovirt.org
> >>> To unsubscribe send an email to users-le...@ovirt.org
> >>>
> >> ___
> >> 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/YMMFCYUMLCM47OJSTHXS2IMOIKEEFU27/
> >
> >
> >
> ___
> 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/FCN5WVAJOGFBUTFV276O2RMCTMACAGTS/



-- 
Didi
___
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/6D4L2DPEW7QZJDEPL7CFRWXV7SMWRYIG/

[ovirt-users] Re: Unable to install oVirt on RHEL7.5

2018-12-18 Thread Sandro Bonazzola

Il giorno mer 19 dic 2018 alle ore 06:42  ha
scritto:

> Thanks  Jingjie Jiang, for your reply.
>
> Could you please elaborate the it. Which repo I need to enable for above
> mentioned issue.
>

Looks like you didn't install ovirt-release42 rpm because you're missing
the dependency repos.
Can you please yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm
this will set up your repos.


>
> Looking forward for your reply.
>
> Regards
> Sumit Sahay
> ___
> 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/465UO3N4PN4P6ZN5YVKFWMMTCTBJZOS6/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
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/65LRJBHXP5Q4PHSBYQTZAMXVZPYYC7V6/

[ovirt-users] Re: Unable to install oVirt on RHEL7.5

2018-12-18 Thread ss00514758

Thanks  Jingjie Jiang, for your reply.

Could you please elaborate the it. Which repo I need to enable for above 
mentioned issue.

Looking forward for your reply.

Regards
Sumit Sahay
___
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/465UO3N4PN4P6ZN5YVKFWMMTCTBJZOS6/

[ovirt-users] Re: Running different minor versions in different clusters?

2018-12-18 Thread Darrell Budic

It survives and continues to work fine. I’ve been in this situation during 
upgrades when I haven’t been able to do all my clusters at the same time.


> On Dec 18, 2018, at 12:17 PM, Florian Schmid  wrote:
> 
> Hi,
> 
> does nobody has a clue on this? I would need a clear statement about that. ;)
> 
> LG Florian
> 
> 
> - Ursprüngliche Mail -
> Von: "Florian Schmid" 
> An: "users" 
> Gesendet: Dienstag, 11. Dezember 2018 13:31:35
> Betreff: [ovirt-users] Running different minor versions in different clusters?
> 
> Hi,
> 
> I want to ask, if this is a supported Environment, 
> when I have for example the latest 4.2 version running on engine and all 
> hosts in a cluster have an earlier release of 4.2 running?
> 
> Example:
> - ovirt engine: 4.2.7
> - hosts in cluster A: 4.2.5
> - hosts in cluster B: 4.2.7
> 
> The engine VM would run in cluster A with the older version.
> 
> I ask, because we have a very huge ovirt setup, split into different clusters.
> In one cluster, I would like to have always the latest version and in the 
> others, the upgrade will be done in bigger time-intervals.
> 
> LG Florian Schmid
> ___
> 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/TVSWNPPOON5RYDYQVHRXPUDTIFBCWBJO/
> ___
> 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/C7C2JXVXR3NEF5ZVESMCSGPBYFQSUA5U/
___
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/5LHVX6IC2DJ6DXHYZ5DWTAY3FNDGW4GJ/

[ovirt-users] Re: Running different minor versions in different clusters?

2018-12-18 Thread Florian Schmid

Hi,

does nobody has a clue on this? I would need a clear statement about that. ;)

LG Florian


- Ursprüngliche Mail -
Von: "Florian Schmid" 
An: "users" 
Gesendet: Dienstag, 11. Dezember 2018 13:31:35
Betreff: [ovirt-users] Running different minor versions in different clusters?

Hi,

I want to ask, if this is a supported Environment, 
when I have for example the latest 4.2 version running on engine and all hosts 
in a cluster have an earlier release of 4.2 running?

Example:
- ovirt engine: 4.2.7
- hosts in cluster A: 4.2.5
- hosts in cluster B: 4.2.7

The engine VM would run in cluster A with the older version.

I ask, because we have a very huge ovirt setup, split into different clusters.
In one cluster, I would like to have always the latest version and in the 
others, the upgrade will be done in bigger time-intervals.

LG Florian Schmid
___
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/TVSWNPPOON5RYDYQVHRXPUDTIFBCWBJO/
___
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/C7C2JXVXR3NEF5ZVESMCSGPBYFQSUA5U/

[ovirt-users] Re: Backup & Restore

2018-12-18 Thread Torsten Stolpmann


Hi Yedidyah,

please find the logs at the following URL: 
http://www.klaros-testmanagement.com/files/ovirt/ovirt-restore-logs.tar.gz


Let me know once you received them safely so I can remove them again.

I also added the restore.log containing the actual error which occured 
during the restore.


Since this was a clean system I restored on, the setup has been executed 
after the database restore, so the setup logs probably contain nothing 
of interest. I added them anyway.


Please let me know if there is anything I can add to this.

Cheers,

Torsten


On 18.12.2018 07:54, Yedidyah Bar David wrote:

On Mon, Dec 17, 2018 at 2:26 PM Torsten Stolpmann
 wrote:


I experienced the same issue while restoring a full backup (engine &
dwh) on a clean machine. Both machines are running CentOS 7.6 and
oVirt 4.2.7.

The issue went away when adding the following line to the IGNORED_ERRORS
list starting at 1944 in engine-backup:

must be owner of function uuid_generate_v1

Hope this helps,


It does, and thanks for the report!

Can you please share all of your setup logs (/var/log/ovirt-engine/setup/*)?

Thanks!

More details:

This function should not normally be included in a 4.2 backup, and I do
not yet understand why you get this error.

If it's a clean 4.2 setup, it should never have been defined.
Earlier versions did create it, and the upgrade process should have
dropped it, if it's an upgraded setup. See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1515635

Best regards,



Torsten

On 24.05.2018 11:32, emmanuel.the...@obs-nancay.fr wrote:

hi,

I have the same error when I try to restore on a new hosted VM (ovirt 4.2.3)
Have you a solution ?

Emmanuel
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


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





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

[ovirt-users] Re: VM protal : Erorr in some VMs

2018-12-18 Thread Greg Sheremeta

Also, I forgot to mention, this piece of documentation may be helpful:

from [1]
"""
Disable strict user checking
Click the Advanced Parameters arrow and select the check box to use this
option. With this option selected, the virtual machine does not need to be
rebooted when a different user connects to it.

By default, strict checking is enabled so that only one user can connect to
the console of a virtual machine. No other user is able to open a console
to the same virtual machine until it has been rebooted. The exception is
that a SuperUser can connect at any time and replace a existing connection.
When a SuperUser has connected, no normal user can connect again until the
virtual machine is rebooted.

Disable strict checking with caution, because you can expose the previous
user's session to the new user.
"""

[1]
https://www.ovirt.org/documentation/vmm-guide/appe-Reference_Settings_in_Administration_Portal_and_User_Portal_Windows.html


On Tue, Dec 18, 2018 at 9:13 AM Greg Sheremeta  wrote:

> Ok, thanks for searching for it. This is already fixed and will be in 4.3.
>
> If you'd like to try it now, you can run the ovirt-web-ui master
> (1.5.0-snapshot) container against your engine like so:
> docker run --rm -it -e ENGINE_URL=https://[OVIRT.ENGINE.FQDN]/ovirt-engine/
> -p 3000:3000 ovirtwebui/ovirt-web-ui:master
> (then navigate to localhost:3000 ...)
>
> On Tue, Dec 18, 2018 at 8:59 AM mustafa taha 
> wrote:
>
>> My error  is like this one :
>>
>> https://github.com/oVirt/ovirt-web-ui/issues/510
>>
>>
>>
>>
>>
>> Sent from Mail  for
>> Windows 10
>>
>>
>>
>> *From: *Greg Sheremeta 
>> *Sent: *Tuesday, December 18, 2018 3:39 PM
>> *To: *mustafa taha 
>> *Cc: *users 
>> *Subject: *Re: [ovirt-users] Re: VM protal : Erorr in some VMs
>>
>>
>>
>> That sounds like a bug of some sort. Please open an issue at
>> https://github.com/oVirt/ovirt-web-ui/issues and we'll look into it. Is
>> your VM definitely running (i.e. not suspended) when users first try to
>> connect? I ask because [https://github.com/oVirt/ovirt-web-ui/issues/516]
>> was reported already for that.
>>
>>
>>
>> Please attach:
>>
>> 1. engine.log from your engine that shows any messages that occur when
>> this happens
>>
>> 2. screenshots of VM Portal showing the error
>>
>> 3. browser console log from VM Portal while this is happening (feel free
>> to scrub host names and such) - F12 > Console
>>
>>
>>
>> Best wishes,
>>
>> Greg
>>
>>
>>
>> On Tue, Dec 18, 2018 at 8:31 AM  wrote:
>>
>> the version of my engine is 4.2.6
>> note : the console run after i shutdown -> run  the VM
>> ___
>> 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/FWJ5ZWMVNXBD27LIYVD4BXWJYBTBMYPW/
>>
>>
>>
>>
>> --
>>
>> *GREG SHEREMETA*
>>
>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>>
>> Red Hat NA
>>
>> 
>>
>> gsher...@redhat.comIRC: gshereme
>>
>> [image: https://www.redhat.com/files/brand/email/sig-redhat.png]
>> 
>>
>>
>>
>>
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

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

[ovirt-users] Re: VM protal : Erorr in some VMs

2018-12-18 Thread Greg Sheremeta

Ok, thanks for searching for it. This is already fixed and will be in 4.3.

If you'd like to try it now, you can run the ovirt-web-ui master
(1.5.0-snapshot) container against your engine like so:
docker run --rm -it -e ENGINE_URL=https://[OVIRT.ENGINE.FQDN]/ovirt-engine/
-p 3000:3000 ovirtwebui/ovirt-web-ui:master
(then navigate to localhost:3000 ...)

On Tue, Dec 18, 2018 at 8:59 AM mustafa taha 
wrote:

> My error  is like this one :
>
> https://github.com/oVirt/ovirt-web-ui/issues/510
>
>
>
>
>
> Sent from Mail  for
> Windows 10
>
>
>
> *From: *Greg Sheremeta 
> *Sent: *Tuesday, December 18, 2018 3:39 PM
> *To: *mustafa taha 
> *Cc: *users 
> *Subject: *Re: [ovirt-users] Re: VM protal : Erorr in some VMs
>
>
>
> That sounds like a bug of some sort. Please open an issue at
> https://github.com/oVirt/ovirt-web-ui/issues and we'll look into it. Is
> your VM definitely running (i.e. not suspended) when users first try to
> connect? I ask because [https://github.com/oVirt/ovirt-web-ui/issues/516]
> was reported already for that.
>
>
>
> Please attach:
>
> 1. engine.log from your engine that shows any messages that occur when
> this happens
>
> 2. screenshots of VM Portal showing the error
>
> 3. browser console log from VM Portal while this is happening (feel free
> to scrub host names and such) - F12 > Console
>
>
>
> Best wishes,
>
> Greg
>
>
>
> On Tue, Dec 18, 2018 at 8:31 AM  wrote:
>
> the version of my engine is 4.2.6
> note : the console run after i shutdown -> run  the VM
> ___
> 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/FWJ5ZWMVNXBD27LIYVD4BXWJYBTBMYPW/
>
>
>
>
> --
>
> *GREG SHEREMETA*
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
>
> [image: https://www.redhat.com/files/brand/email/sig-redhat.png]
> 
>
>
>
>
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

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

[ovirt-users] Re: Disk corruption on hosted engine

2018-12-18 Thread Callum Smith

Dear Simone,

Thanks for the response. Unfortunately I didn't get the install up to 4.7 in 
time for this event, so we might go down the spare host route just to be triple 
safe pending the arrival of some networking kit.

Regards,
Callum

--

Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. cal...@well.ox.ac.uk

On 18 Dec 2018, at 10:08, Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:



On Mon, Dec 17, 2018 at 2:24 PM Callum Smith 
mailto:cal...@well.ox.ac.uk>> wrote:
Dear All,

So we've had some major disk corruption on our hosted engine (hardware to 
blame), and we have taken backups. However, the hosted-engine VM will no longer 
boot at all, database is thoroughly corrupted, and we need to rebuild the 
thing. Just a sanity check on the best route:

Preamble:
VMs are still running fine - only hosted engine affected
VMs are distributed across our entire 3 node cluster
All 3 nodes are registered as hosted engine candidates

1. Do another hosted-engine --deploy on one of the existing hosts, and then 
restore the backup into that
2. Build a new host, deploy the hosted-engine, then restore a backup on a fresh 
node

Hi,
since 4.2.7 you can use
hosted-engine --deploy --restore-from-file=backup.tar.gz

And the deployment will restore your backup on the fly.
Technically you an also use one of the existing hosts with running VMs but if 
you want to be on the safe and you have a spare host I'd suggest to use that 
one.
You will be asked to create a new SD for the new engine VM, the previous HE SD 
will be still visible in the engine if you have to migrate other disks stored 
there.



Regards,
Callum

--

Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. cal...@well.ox.ac.uk

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

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

[ovirt-users] Re: VM protal : Erorr in some VMs

2018-12-18 Thread Greg Sheremeta

That sounds like a bug of some sort. Please open an issue at
https://github.com/oVirt/ovirt-web-ui/issues and we'll look into it. Is
your VM definitely running (i.e. not suspended) when users first try to
connect? I ask because [https://github.com/oVirt/ovirt-web-ui/issues/516]
was reported already for that.

Please attach:
1. engine.log from your engine that shows any messages that occur when this
happens
2. screenshots of VM Portal showing the error
3. browser console log from VM Portal while this is happening (feel free to
scrub host names and such) - F12 > Console

Best wishes,
Greg

On Tue, Dec 18, 2018 at 8:31 AM  wrote:

> the version of my engine is 4.2.6
> note : the console run after i shutdown -> run  the VM
> ___
> 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/FWJ5ZWMVNXBD27LIYVD4BXWJYBTBMYPW/
>

-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA

gsher...@redhat.comIRC: gshereme

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

[ovirt-users] Re: VM protal : Erorr in some VMs

2018-12-18 Thread mustafa . taha . mu95

the version of my engine is 4.2.6
note : the console run after i shutdown -> run  the VM 
___
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/FWJ5ZWMVNXBD27LIYVD4BXWJYBTBMYPW/

[ovirt-users] Re: VM protal : Erorr in some VMs

2018-12-18 Thread Greg Sheremeta

Hi,

What version are you using?

Greg


On Mon, Dec 17, 2018 at 7:05 AM  wrote:

> hi
>
> i want some users to connect to some ovirt VMs .so i add them to the
> permission of that VMs.
> after that my users connect to VM portal and success to login but when
> they want to run console
> some VMs work with console and other does not and this massage appear :
> "
> Failed to retrieve VM console details Conflict
> "
>
> any idea about that ?
> ___
> 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/YYJMPBBUSQTALRHFUADDPAGDWNPDTMHF/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

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

[ovirt-users] Re: Hyperconvergend Setup stuck

2018-12-18 Thread Gobinda Das

Which version of gdeploy you are using?

On Tue, Dec 18, 2018 at 6:06 PM Stefan Wolf  wrote:

> Hello
>
>
>
> I like to setup hyperconvergend
>
>
>
> I ve 3 hosts, everyone is fresh installed
>
> Kvm320 has one additional harddrive with 1TB SATA
>
> And kvm360 and kvm380 with two additional harddrives with 300gb and 600gb
> SAS
>
>
>
>
>
> #gdeploy configuration generated by cockpit-gluster plugin
>
> [hosts]
>
> kvm380.durchhalten.intern
>
> kvm360.durchhalten.intern
>
> kvm320.durchhalten.intern
>
>
>
> [script1:kvm380.durchhalten.intern]
>
> action=execute
>
> ignore_script_errors=no
>
> file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb,sdc -h
> kvm380.durchhalten.intern, kvm360.durchhalten.intern,
> kvm320.durchhalten.intern
>
>
>
> [script1:kvm360.durchhalten.intern]
>
> action=execute
>
> ignore_script_errors=no
>
> file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb,sdc -h
> kvm380.durchhalten.intern, kvm360.durchhalten.intern,
> kvm320.durchhalten.intern
>
>
>
> [script1:kvm320.durchhalten.intern]
>
> action=execute
>
> ignore_script_errors=no
>
> file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h
> kvm380.durchhalten.intern, kvm360.durchhalten.intern,
> kvm320.durchhalten.intern
>
>
>
> [disktype]
>
> raid6
>
>
>
> [diskcount]
>
> 12
>
>
>
> [stripesize]
>
> 256
>
>
>
> [service1]
>
> action=enable
>
> service=chronyd
>
>
>
> [service2]
>
> action=restart
>
> service=chronyd
>
>
>
> [shell2]
>
> action=execute
>
> command=vdsm-tool configure --force
>
>
>
> [script3]
>
> action=execute
>
> file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh
>
> ignore_script_errors=no
>
>
>
> [pv1:kvm380.durchhalten.intern]
>
> action=create
>
> devices=sdb
>
> ignore_pv_errors=no
>
>
>
> [pv2:kvm380.durchhalten.intern]
>
> action=create
>
> devices=sdc
>
> ignore_pv_errors=no
>
>
>
> [pv1:kvm360.durchhalten.intern]
>
> action=create
>
> devices=sdb
>
> ignore_pv_errors=no
>
>
>
> [pv2:kvm360.durchhalten.intern]
>
> action=create
>
> devices=sdc
>
> ignore_pv_errors=no
>
>
>
> [pv1:kvm320.durchhalten.intern]
>
> action=create
>
> devices=sdb
>
> ignore_pv_errors=no
>
>
>
> [vg1:kvm380.durchhalten.intern]
>
> action=create
>
> vgname=gluster_vg_sdb
>
> pvname=sdb
>
> ignore_vg_errors=no
>
>
>
> [vg2:kvm380.durchhalten.intern]
>
> action=create
>
> vgname=gluster_vg_sdc
>
> pvname=sdc
>
> ignore_vg_errors=no
>
>
>
> [vg1:kvm360.durchhalten.intern]
>
> action=create
>
> vgname=gluster_vg_sdb
>
> pvname=sdb
>
> ignore_vg_errors=no
>
>
>
> [vg2:kvm360.durchhalten.intern]
>
> action=create
>
> vgname=gluster_vg_sdc
>
> pvname=sdc
>
> ignore_vg_errors=no
>
>
>
> [vg1:kvm320.durchhalten.intern]
>
> action=create
>
> vgname=gluster_vg_sdb
>
> pvname=sdb
>
> ignore_vg_errors=no
>
>
>
> [lv1:kvm380.durchhalten.intern]
>
> action=create
>
> poolname=gluster_thinpool_sdc
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> lvtype=thinpool
>
> size=1005GB
>
> poolmetadatasize=5GB
>
>
>
> [lv2:kvm360.durchhalten.intern]
>
> action=create
>
> poolname=gluster_thinpool_sdc
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> lvtype=thinpool
>
> size=1005GB
>
> poolmetadatasize=5GB
>
>
>
> [lv3:kvm320.durchhalten.intern]
>
> action=create
>
> poolname=gluster_thinpool_sdb
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdb
>
> lvtype=thinpool
>
> size=41GB
>
> poolmetadatasize=1GB
>
>
>
> [lv4:kvm380.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_engine
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdb
>
> mount=/gluster_bricks/engine
>
> size=100GB
>
> lvtype=thick
>
>
>
> [lv5:kvm380.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_data
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> mount=/gluster_bricks/data
>
> lvtype=thinlv
>
> poolname=gluster_thinpool_sdc
>
> virtualsize=500GB
>
>
>
> [lv6:kvm380.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_vmstore
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> mount=/gluster_bricks/vmstore
>
> lvtype=thinlv
>
> poolname=gluster_thinpool_sdc
>
> virtualsize=500GB
>
>
>
> [lv7:kvm360.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_engine
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdb
>
> mount=/gluster_bricks/engine
>
> size=100GB
>
> lvtype=thick
>
>
>
> [lv8:kvm360.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_data
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> mount=/gluster_bricks/data
>
> lvtype=thinlv
>
> poolname=gluster_thinpool_sdc
>
> virtualsize=500GB
>
>
>
> [lv9:kvm360.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_vmstore
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdc
>
> mount=/gluster_bricks/vmstore
>
> lvtype=thinlv
>
> poolname=gluster_thinpool_sdc
>
> virtualsize=500GB
>
>
>
> [lv10:kvm320.durchhalten.intern]
>
> action=create
>
> lvname=gluster_lv_engine
>
> ignore_lv_errors=no
>
> vgname=gluster_vg_sdb
>
> mount=/gluster_bricks/engine
>
> size=20GB
>
> lvtype=thick
>
>
>
> [lv11:kvm320.durchhalten.intern]
>
> action=create
>
>

[ovirt-users] Hyperconvergend Setup stuck

2018-12-18 Thread Stefan Wolf

Hello

 

I like to setup hyperconvergend

 

I ve 3 hosts, everyone is fresh installed

Kvm320 has one additional harddrive with 1TB SATA

And kvm360 and kvm380 with two additional harddrives with 300gb and 600gb
SAS

 

 

#gdeploy configuration generated by cockpit-gluster plugin

[hosts]

kvm380.durchhalten.intern

kvm360.durchhalten.intern

kvm320.durchhalten.intern

 

[script1:kvm380.durchhalten.intern]

action=execute

ignore_script_errors=no

file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb,sdc -h
kvm380.durchhalten.intern, kvm360.durchhalten.intern,
kvm320.durchhalten.intern

 

[script1:kvm360.durchhalten.intern]

action=execute

ignore_script_errors=no

file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb,sdc -h
kvm380.durchhalten.intern, kvm360.durchhalten.intern,
kvm320.durchhalten.intern

 

[script1:kvm320.durchhalten.intern]

action=execute

ignore_script_errors=no

file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h
kvm380.durchhalten.intern, kvm360.durchhalten.intern,
kvm320.durchhalten.intern

 

[disktype]

raid6

 

[diskcount]

12

 

[stripesize]

256

 

[service1]

action=enable

service=chronyd

 

[service2]

action=restart

service=chronyd

 

[shell2]

action=execute

command=vdsm-tool configure --force

 

[script3]

action=execute

file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh

ignore_script_errors=no

 

[pv1:kvm380.durchhalten.intern]

action=create

devices=sdb

ignore_pv_errors=no

 

[pv2:kvm380.durchhalten.intern]

action=create

devices=sdc

ignore_pv_errors=no

 

[pv1:kvm360.durchhalten.intern]

action=create

devices=sdb

ignore_pv_errors=no

 

[pv2:kvm360.durchhalten.intern]

action=create

devices=sdc

ignore_pv_errors=no

 

[pv1:kvm320.durchhalten.intern]

action=create

devices=sdb

ignore_pv_errors=no

 

[vg1:kvm380.durchhalten.intern]

action=create

vgname=gluster_vg_sdb

pvname=sdb

ignore_vg_errors=no

 

[vg2:kvm380.durchhalten.intern]

action=create

vgname=gluster_vg_sdc

pvname=sdc

ignore_vg_errors=no

 

[vg1:kvm360.durchhalten.intern]

action=create

vgname=gluster_vg_sdb

pvname=sdb

ignore_vg_errors=no

 

[vg2:kvm360.durchhalten.intern]

action=create

vgname=gluster_vg_sdc

pvname=sdc

ignore_vg_errors=no

 

[vg1:kvm320.durchhalten.intern]

action=create

vgname=gluster_vg_sdb

pvname=sdb

ignore_vg_errors=no

 

[lv1:kvm380.durchhalten.intern]

action=create

poolname=gluster_thinpool_sdc

ignore_lv_errors=no

vgname=gluster_vg_sdc

lvtype=thinpool

size=1005GB

poolmetadatasize=5GB

 

[lv2:kvm360.durchhalten.intern]

action=create

poolname=gluster_thinpool_sdc

ignore_lv_errors=no

vgname=gluster_vg_sdc

lvtype=thinpool

size=1005GB

poolmetadatasize=5GB

 

[lv3:kvm320.durchhalten.intern]

action=create

poolname=gluster_thinpool_sdb

ignore_lv_errors=no

vgname=gluster_vg_sdb

lvtype=thinpool

size=41GB

poolmetadatasize=1GB

 

[lv4:kvm380.durchhalten.intern]

action=create

lvname=gluster_lv_engine

ignore_lv_errors=no

vgname=gluster_vg_sdb

mount=/gluster_bricks/engine

size=100GB

lvtype=thick

 

[lv5:kvm380.durchhalten.intern]

action=create

lvname=gluster_lv_data

ignore_lv_errors=no

vgname=gluster_vg_sdc

mount=/gluster_bricks/data

lvtype=thinlv

poolname=gluster_thinpool_sdc

virtualsize=500GB

 

[lv6:kvm380.durchhalten.intern]

action=create

lvname=gluster_lv_vmstore

ignore_lv_errors=no

vgname=gluster_vg_sdc

mount=/gluster_bricks/vmstore

lvtype=thinlv

poolname=gluster_thinpool_sdc

virtualsize=500GB

 

[lv7:kvm360.durchhalten.intern]

action=create

lvname=gluster_lv_engine

ignore_lv_errors=no

vgname=gluster_vg_sdb

mount=/gluster_bricks/engine

size=100GB

lvtype=thick

 

[lv8:kvm360.durchhalten.intern]

action=create

lvname=gluster_lv_data

ignore_lv_errors=no

vgname=gluster_vg_sdc

mount=/gluster_bricks/data

lvtype=thinlv

poolname=gluster_thinpool_sdc

virtualsize=500GB

 

[lv9:kvm360.durchhalten.intern]

action=create

lvname=gluster_lv_vmstore

ignore_lv_errors=no

vgname=gluster_vg_sdc

mount=/gluster_bricks/vmstore

lvtype=thinlv

poolname=gluster_thinpool_sdc

virtualsize=500GB

 

[lv10:kvm320.durchhalten.intern]

action=create

lvname=gluster_lv_engine

ignore_lv_errors=no

vgname=gluster_vg_sdb

mount=/gluster_bricks/engine

size=20GB

lvtype=thick

 

[lv11:kvm320.durchhalten.intern]

action=create

lvname=gluster_lv_data

ignore_lv_errors=no

vgname=gluster_vg_sdb

mount=/gluster_bricks/data

lvtype=thinlv

poolname=gluster_thinpool_sdb

virtualsize=20GB

 

[lv12:kvm320.durchhalten.intern]

action=create

lvname=gluster_lv_vmstore

ignore_lv_errors=no

vgname=gluster_vg_sdb

mount=/gluster_bricks/vmstore

lvtype=thinlv

poolname=gluster_thinpool_sdb

virtualsize=20GB

 

[selinux]

yes

 

[service3]

action=restart

service=glusterd

slice_setup=yes

 

[firewalld]

action=add

ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,5
4322/tcp

services=glusterfs

 

[script2]

action=execute

[ovirt-users] Re: Port 9090 Redirect Nginx Proxy

2018-12-18 Thread Donny Davis

I think haproxy is probably more appropriate for your use case. Use TCP
mode, and you should be good to go.


Donny Davis

"Ease is a greater threat to progress  than hardship"

On Mon, Dec 17, 2018, 1:29 PM  I've run into a small issue I'm looking to resolve. I currently have 5
> hosts I'm working to configure as oVirt Hosts and a single oVirt Manager to
> manage them all. The oVirt Manager can talk to the hosts, the hosts show
> up, they can be managed, etc.
>
> Our client PCs reside on a different network (and this can't be changed).
> We used to just add the interfaces to communicate on the new network but
> because of IP spaces and DFARS/NIST requirements, we are moving away from
> this. I've set up a reverse proxy so only a single machine serves as the
> gateway between the networks. This works for everything except one small
> issue. If you click "Host Console" from the ovirt manager, it opens up a
> new page with port 9090 to the cockpit page of the host.
>
> I have this working except I am getting a blank page for cockpit after
> logging in. What's even more odd, I can use the reverse proxy settings to
> browse to the 443 port and redirect to 9090 and i can load everything fine,
> but 9090 to 9090 does not work. I've looked at other threads and posts,
> including the GitLab thing, which got me here, but can't get this last
> missing piece. Is anybody able to provide any assistance? Based off
> research it looks like something I could edit in the cockpit.conf file,
> except ovirt apparently doesn't make the cockpit.conf file... and trying to
> force it through the GUI by adding /settings to the URL says page not found.
>
> Alternatively I could edit the oVirt Mgr to point to client to the 443
> port and that'd work, if I knew where to edit those hyperlinks upon click.
>
> P.S. this is a test/develop internal network env which is why i have
> proxy_ssl_verify off.
>
> Nginx Reverse Proxy config:
> map $http_upgrade $connection_upgrade {
> default upgrade;
> '' close;
> }
>
> upstream websocket {
> server host11.:9090;
> }
>
> server {
>listen 80;
>server_namehost11.;
>return 301 https://$server_name$request_uri;
> }
>
> #Allows user to go directly to server (I work!)
> server {
> listen 443;
> server_name host11.;
>
> ssl on;
> ssl_certificate ;
> ssl_certificate_key ;
> proxy_ssl_verify off;
>
> location / {
> proxy_pass https://websocket;
> proxy_http_version 1.1;
> proxy_buffering off;
> proxy_set_header X-Real-IP  $remote_addr;
> proxy_set_header Host $host;
> proxy_set_header X-Forwarded-For $remote_addr;
>
> # needed for websocket
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection $connection_upgrade;
>
> # change scheme of "Origin" to https
> proxy_set_header Origin https://$host;
>
> gzip off;
> }
>
> }
>
> #allows ovirtmgr host console redirect (I don't work)
> server {
> listen 9090;
> server_name host11.;
>
> ssl on;
> ssl_certificate ;
> ssl_certificate_key ;
> proxy_ssl_verify off;
>
> location / {
> proxy_pass https://websocket;
> proxy_http_version 1.1;
> proxy_buffering off;
> proxy_set_header X-Real-IP  $remote_addr;
> proxy_set_header Host $host;
> proxy_set_header X-Forwarded-For $remote_addr;
>
> # needed for websocket
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection $connection_upgrade;
>
> # change scheme of "Origin" to https
> proxy_set_header Origin https://$host;
>
> gzip off;
> }
>
> }
>
>
> Host Error Log:
> #Log in Page
> Dec 17 11:22:15 ovirt11 systemd: Cannot add dependency job for unit
> lvm2-lvmetad.socket, ignoring: Unit is masked.
> Dec 17 11:22:15 ovirt11 systemd: Starting Cockpit Web Service...
> Dec 17 11:22:15 ovirt11 systemd: Started Cockpit Web Service.
> Dec 17 11:22:16 ovirt11 cockpit-ws: Using certificate:
> /etc/cockpit/ws-certs.d/0-self-signed.cert
> Dec 17 11:22:16 ovirt11 kernel: HTTPS SYN: IN=ovirtmgmt OUT=
> MAC=b8:2a:72:de:a3:76:00:50:56:8b:01:ca:08:00 SRC=192.168.100.251
> DST=192.168.100.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=18185 DF PROTO=TCP
> SPT=34518 DPT=9090 WINDOW=29200 RES=0x00 SYN URGP=0
> Dec 17 11:22:42 ovirt11 kernel: HTTPS SYN: IN=ovirtmgmt OUT=
> MAC=b8:2a:72:de:a3:76:00:50:56:8b:01:ca:08:00 SRC=192.168.100.251
> DST=192.168.100.111 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=54797 DF PROTO=TCP
> SPT=34520 DPT=9090 WINDOW=29200 RES=0x00 SYN URGP=0
>
> #after successfully logging in
> Dec 17 11:22:42 ovirt11 cockpit-session:

[ovirt-users] Re: Gluster Disk Full

2018-12-18 Thread suporte

Hi, 

It's possible to remove a gluster folder and files (corresponding to a disk) 
from the command line? 

Thanks 
José 


From: supo...@logicworks.pt 
To: "users"  
Sent: Monday, December 17, 2018 11:46:54 PM 
Subject: [ovirt-users] Gluster Disk Full 

Hi, 

I have a gluster volume with disk full. It's a simple oVirt all in one. 
The VM with the disk on that volume stopped. 

The error message: 
Failed to update OVF disks 1252828a-3265-4d5c-9440-40b2b85c1feb, OVF data isn't 
updated on those OVF stores (Data Center Default, Storage Domain gfs1). 
VDSM command SetVolumeDescriptionVDS failed: Error while updating volume meta 
data: 
("(u'/rhev/data-center/mnt/glusterSD/gfs1.growtrade.pt:_gv0/0f21e2bf-44d9-4afd-8800-28e99d617a4b/images/1252828a-3265-4d5c-9440-40b2b85c1feb/f8b62638-ba48-4ed8-8101-3027c124d20c',)[Errno
 28] No space left on device: 
u'/rhev/data-center/mnt/glusterSD/gfs1.growtrade.pt:_gv0/0f21e2bf-44d9-4afd-8800-28e99d617a4b/images/1252828a-3265-4d5c-9440-40b2b85c1feb/f8b62638-ba48-4ed8-8101-3027c124d20c.meta.new'",)
 


Any idea what can I do? 

Thanks 

-- 

Jose Ferradeira 
http://www.logicworks.pt 

___ 
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/LLVOIBFXYI2T7T67IRKPZ2VNW7GRI5ZL/
 
___
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/EXQANCP7UR645J5LX5FZ6O5SFS2PAYRE/

[ovirt-users] Re: Disk corruption on hosted engine

2018-12-18 Thread Simone Tiraboschi

On Mon, Dec 17, 2018 at 2:24 PM Callum Smith  wrote:

> Dear All,
>
> So we've had some major disk corruption on our hosted engine (hardware to
> blame), and we have taken backups. However, the hosted-engine VM will no
> longer boot at all, database is thoroughly corrupted, and we need to
> rebuild the thing. Just a sanity check on the best route:
>
> Preamble:
> VMs are still running fine - only hosted engine affected
> VMs are distributed across our entire 3 node cluster
> All 3 nodes are registered as hosted engine candidates
>
> 1. Do another hosted-engine --deploy on one of the existing hosts, and
> then restore the backup into that
> 2. Build a new host, deploy the hosted-engine, then restore a backup on a
> fresh node
>

Hi,
since 4.2.7 you can use
hosted-engine --deploy --restore-from-file=backup.tar.gz

And the deployment will restore your backup on the fly.
Technically you an also use one of the existing hosts with running VMs but
if you want to be on the safe and you have a spare host I'd suggest to use
that one.
You will be asked to create a new SD for the new engine VM, the previous HE
SD will be still visible in the engine if you have to migrate other disks
stored there.



>
> Regards,
> Callum
>
> --
>
> Callum Smith
> Research Computing Core
> Wellcome Trust Centre for Human Genetics
> University of Oxford
> e. cal...@well.ox.ac.uk
>
> ___
> 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/VYQM7WWIBP7Z7FQQ6TG7HH3IFDZ64LXQ/
>
___
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/BPWTYY5J74Y4J7XJ6YWNBSSY7IXHNFBB/

[ovirt-users] Re: Disk corruption on hosted engine

2018-12-18 Thread Callum Smith

Memory error on the storage array that cause postgres to become corrupted. 
Attempting to restore from backup before the DIMM was replaced was ill advised 
and now the whole HE is trash.

We're having a long talk with our vendor of the affected piece of kit.

Regards,
Callum

--

Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. cal...@well.ox.ac.uk

On 17 Dec 2018, at 15:45, femi adegoke 
mailto:ov...@fateknollogee.com>> wrote:

Curious question: How did the hardware corrupt the HE?

On Dec 17 2018, at 5:02 am, Callum Smith 
mailto:cal...@well.ox.ac.uk>> wrote:
Dear All,

So we've had some major disk corruption on our hosted engine (hardware to 
blame), and we have taken backups. However, the hosted-engine VM will no longer 
boot at all, database is thoroughly corrupted, and we need to rebuild the 
thing. Just a sanity check on the best route:

Preamble:
VMs are still running fine - only hosted engine affected
VMs are distributed across our entire 3 node cluster
All 3 nodes are registered as hosted engine candidates

1. Do another hosted-engine --deploy on one of the existing hosts, and then 
restore the backup into that
2. Build a new host, deploy the hosted-engine, then restore a backup on a fresh 
node

Regards,
Callum

--

Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. cal...@well.ox.ac.uk

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

___
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/3MWI53U5OHUQJ2IJFMF4L6GNNNH2QV44/

[ovirt-users] Re: ovirt agent

2018-12-18 Thread Simone Tiraboschi

On Mon, Dec 17, 2018 at 10:14 AM  wrote:

> i am trying to install ovirt agent on ubuntu and try to open this documnet
> but it does not work and this page will appear :
> https://www.ovirt.org/develop/
> can the ovirt team fixed that or there is new thing other than agent ?
>

Only guest agent; this one:
https://launchpad.net/ubuntu/bionic/+package/ovirt-guest-agent



> ___
> 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/IAKRVQO3552RHHHXRWEENL4352EGNNBH/
>
___
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/YCVZMWKKGQPCX26PCAGJSNFILI7EBKVU/

[ovirt-users] Re: Import OVA

2018-12-18 Thread suporte

Hi Alex, 

I know now that I need first select the image, but before I need to put it on 
the node disk, right? 
Is not possible to upload an image using the gui admin. 

Thanks 

José 


De: "Alex K"  
Para: "users"  
Enviadas: Segunda-feira, 17 de dezembro de 2018 8:59:32 
Assunto: [ovirt-users] Re: Import OVA 



On Fri, Dec 14, 2018 at 5:45 PM < supo...@logicworks.pt > wrote: 



Hi, 

I have created a export domain using Glusterfs. 
When I go to Storage-Domains, click on the export domain, on VM Import the 
Import button is greyed out. 



Did you first select the image you need to import? 

BQ_BEGIN

My test environment is running a 4.2.7.5-1.el7 version. 

Any idea? 

Thanks 



-- 

Jose Ferradeira 
http://www.logicworks.pt 
___ 
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/QYVQMDHASVTSUORI43QBXW6WHYJI5DB4/
 

BQ_END


___ 
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/BIM3TC6YUYOBGSZ4RXMIKVV4UGJGHYR3/
 
___
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/G3ALAX5TYC2MJ7DYSGEMYGIMVABDBLVZ/

[ovirt-users] Re: Backup & Restore

[ovirt-users] Re: Unable to install oVirt on RHEL7.5

[ovirt-users] Re: Unable to install oVirt on RHEL7.5

[ovirt-users] Re: Running different minor versions in different clusters?

[ovirt-users] Re: Running different minor versions in different clusters?

[ovirt-users] Re: Backup & Restore

[ovirt-users] Re: VM protal : Erorr in some VMs

[ovirt-users] Re: VM protal : Erorr in some VMs

[ovirt-users] Re: Disk corruption on hosted engine

[ovirt-users] Re: VM protal : Erorr in some VMs

[ovirt-users] Re: VM protal : Erorr in some VMs

[ovirt-users] Re: VM protal : Erorr in some VMs

[ovirt-users] Re: Hyperconvergend Setup stuck

[ovirt-users] Hyperconvergend Setup stuck

[ovirt-users] Re: Port 9090 Redirect Nginx Proxy

[ovirt-users] Re: Gluster Disk Full

[ovirt-users] Re: Disk corruption on hosted engine

[ovirt-users] Re: Disk corruption on hosted engine

[ovirt-users] Re: ovirt agent

[ovirt-users] Re: Import OVA

20 matches

Site Navigation

Mail list logo

Footer information