Re: [ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Sahina Bose]

This is a compatibility issue on executing cli commands. Is it possible 
to upgrade your glusterfs server to higher version, or downgrade the 
glusterfs-cli on node to 3.7.6.


Please log a bug in HE deploy to handle this error so that installation 
can proceed. (--remote-host option throws errors  when there's a version 
mismatch)


On 07/01/2016 10:25 AM, Kevin Hung wrote:
Version 3.7.11 on node and version 3.7.6 on server. The node was set 
up using the ovirt-node-ng-installer-ovirt-4.0-2016062412 ISO.


On 7/1/2016 12:50 AM, Sahina Bose wrote:

Sorry, missed that you already ran it.
Version of glusterfs on node and server?


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Kevin Hung]

Version 3.7.11 on node and version 3.7.6 on server. The node was set up 
using the ovirt-node-ng-installer-ovirt-4.0-2016062412 ISO.


On 7/1/2016 12:50 AM, Sahina Bose wrote:

Sorry, missed that you already ran it.
Version of glusterfs on node and server?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Sahina Bose]

Sorry, missed that you already ran it.
Version of glusterfs on node and server?

On 07/01/2016 10:15 AM, Kevin Hung wrote:

The same as the other command, two blank lines.

On 7/1/2016 12:41 AM, Sahina Bose wrote:

What's the output of below from the node?
# gluster volume info mgmttank --remote-host=storage1.nullaxiom.com

On 07/01/2016 08:52 AM, Kevin Hung wrote:

Hello,

I thought I would ask the list if anyone is aware of this issue (or 
if I am doing something obviously wrong) before I submit a bug report.


It looks like I am not able to choose glusterfs as a storage option 
for deploying a Hosted Engine in oVirt 4.0 Node Next. I believe it 
is failing to execute the following command:
/sbin/gluster --mode=script --xml volume info mgmttank 
--remote-host=storage1.nullaxiom.com


When I run the command manually, I get a blank line as output and 
checking in /var/log/glusterfs/cli.log, it seems to be exiting with 
error code -2.


I have tried disabling the firewall on both host and gluster server, 
but it did not make a difference. I am able to manually mount the 
gluster volume on the host, and I had a working oVirt 3.6 
installation using the same exact gluster server.


Console output below:

[ INFO  ] Stage: Initializing
[ INFO  ] Generating a temporary VNC password.
[ INFO  ] Stage: Environment setup
  During customization use CTRL-D to abort.
  Continuing will configure this host for serving as 
hypervisor and create a VM where you have to install the engine 
afterwards.

  Are you sure you want to continue? (Yes, No)[Yes]:
  It has been detected that this program is executed through 
an SSH connection without using screen.
  Continuing with the installation may lead to broken 
installation if the network connection fails.
  It is highly recommended to abort the installation and run 
it inside a screen session using command "screen".

  Do you want to continue anyway? (Yes, No)[No]: yes
[ INFO  ] Hardware supports virtualization
  Configuration files: []
  Log file: 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160630225930-ef5wd4.log

  Version: otopi-1.5.0 (otopi-1.5.0-1.el7.centos)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== STORAGE CONFIGURATION ==--

  Please specify the storage you would like to use 
(glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the 
shared storage.
  Please specify the full shared storage connection path to 
use (example: host:/path): storage1.nullaxiom.com:/mgmttank
[ ERROR ] Cannot access storage connection 
storage1.nullaxiom.com:/mgmttank: Command '/sbin/gluster' failed to 
execute
  Please specify the full shared storage connection path to 
use (example: host:/path):

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users






___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Kevin Hung]

The same as the other command, two blank lines.

On 7/1/2016 12:41 AM, Sahina Bose wrote:

What's the output of below from the node?
# gluster volume info mgmttank --remote-host=storage1.nullaxiom.com

On 07/01/2016 08:52 AM, Kevin Hung wrote:

Hello,

I thought I would ask the list if anyone is aware of this issue (or 
if I am doing something obviously wrong) before I submit a bug report.


It looks like I am not able to choose glusterfs as a storage option 
for deploying a Hosted Engine in oVirt 4.0 Node Next. I believe it is 
failing to execute the following command:
/sbin/gluster --mode=script --xml volume info mgmttank 
--remote-host=storage1.nullaxiom.com


When I run the command manually, I get a blank line as output and 
checking in /var/log/glusterfs/cli.log, it seems to be exiting with 
error code -2.


I have tried disabling the firewall on both host and gluster server, 
but it did not make a difference. I am able to manually mount the 
gluster volume on the host, and I had a working oVirt 3.6 
installation using the same exact gluster server.


Console output below:

[ INFO  ] Stage: Initializing
[ INFO  ] Generating a temporary VNC password.
[ INFO  ] Stage: Environment setup
  During customization use CTRL-D to abort.
  Continuing will configure this host for serving as 
hypervisor and create a VM where you have to install the engine 
afterwards.

  Are you sure you want to continue? (Yes, No)[Yes]:
  It has been detected that this program is executed through 
an SSH connection without using screen.
  Continuing with the installation may lead to broken 
installation if the network connection fails.
  It is highly recommended to abort the installation and run 
it inside a screen session using command "screen".

  Do you want to continue anyway? (Yes, No)[No]: yes
[ INFO  ] Hardware supports virtualization
  Configuration files: []
  Log file: 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160630225930-ef5wd4.log

  Version: otopi-1.5.0 (otopi-1.5.0-1.el7.centos)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== STORAGE CONFIGURATION ==--

  Please specify the storage you would like to use 
(glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the 
shared storage.
  Please specify the full shared storage connection path to 
use (example: host:/path): storage1.nullaxiom.com:/mgmttank
[ ERROR ] Cannot access storage connection 
storage1.nullaxiom.com:/mgmttank: Command '/sbin/gluster' failed to 
execute
  Please specify the full shared storage connection path to 
use (example: host:/path):

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Sahina Bose]

What's the output of below from the node?
# gluster volume info mgmttank --remote-host=storage1.nullaxiom.com

On 07/01/2016 08:52 AM, Kevin Hung wrote:

Hello,

I thought I would ask the list if anyone is aware of this issue (or if 
I am doing something obviously wrong) before I submit a bug report.


It looks like I am not able to choose glusterfs as a storage option 
for deploying a Hosted Engine in oVirt 4.0 Node Next. I believe it is 
failing to execute the following command:
/sbin/gluster --mode=script --xml volume info mgmttank 
--remote-host=storage1.nullaxiom.com


When I run the command manually, I get a blank line as output and 
checking in /var/log/glusterfs/cli.log, it seems to be exiting with 
error code -2.


I have tried disabling the firewall on both host and gluster server, 
but it did not make a difference. I am able to manually mount the 
gluster volume on the host, and I had a working oVirt 3.6 installation 
using the same exact gluster server.


Console output below:

[ INFO  ] Stage: Initializing
[ INFO  ] Generating a temporary VNC password.
[ INFO  ] Stage: Environment setup
  During customization use CTRL-D to abort.
  Continuing will configure this host for serving as 
hypervisor and create a VM where you have to install the engine 
afterwards.

  Are you sure you want to continue? (Yes, No)[Yes]:
  It has been detected that this program is executed through 
an SSH connection without using screen.
  Continuing with the installation may lead to broken 
installation if the network connection fails.
  It is highly recommended to abort the installation and run 
it inside a screen session using command "screen".

  Do you want to continue anyway? (Yes, No)[No]: yes
[ INFO  ] Hardware supports virtualization
  Configuration files: []
  Log file: 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160630225930-ef5wd4.log

  Version: otopi-1.5.0 (otopi-1.5.0-1.el7.centos)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== STORAGE CONFIGURATION ==--

  Please specify the storage you would like to use (glusterfs, 
iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the 
shared storage.
  Please specify the full shared storage connection path to 
use (example: host:/path): storage1.nullaxiom.com:/mgmttank
[ ERROR ] Cannot access storage connection 
storage1.nullaxiom.com:/mgmttank: Command '/sbin/gluster' failed to 
execute
  Please specify the full shared storage connection path to 
use (example: host:/path):

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Unable to set up oVirt 4.0 HE using glusterfs storage

[Kevin Hung]

Hello,

I thought I would ask the list if anyone is aware of this issue (or if I 
am doing something obviously wrong) before I submit a bug report.


It looks like I am not able to choose glusterfs as a storage option for 
deploying a Hosted Engine in oVirt 4.0 Node Next. I believe it is 
failing to execute the following command:
/sbin/gluster --mode=script --xml volume info mgmttank 
--remote-host=storage1.nullaxiom.com


When I run the command manually, I get a blank line as output and 
checking in /var/log/glusterfs/cli.log, it seems to be exiting with 
error code -2.


I have tried disabling the firewall on both host and gluster server, but 
it did not make a difference. I am able to manually mount the gluster 
volume on the host, and I had a working oVirt 3.6 installation using the 
same exact gluster server.


Console output below:

[ INFO  ] Stage: Initializing
[ INFO  ] Generating a temporary VNC password.
[ INFO  ] Stage: Environment setup
  During customization use CTRL-D to abort.
  Continuing will configure this host for serving as hypervisor 
and create a VM where you have to install the engine afterwards.

  Are you sure you want to continue? (Yes, No)[Yes]:
  It has been detected that this program is executed through an 
SSH connection without using screen.
  Continuing with the installation may lead to broken 
installation if the network connection fails.
  It is highly recommended to abort the installation and run it 
inside a screen session using command "screen".

  Do you want to continue anyway? (Yes, No)[No]: yes
[ INFO  ] Hardware supports virtualization
  Configuration files: []
  Log file: 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160630225930-ef5wd4.log

  Version: otopi-1.5.0 (otopi-1.5.0-1.el7.centos)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== STORAGE CONFIGURATION ==--

  Please specify the storage you would like to use (glusterfs, 
iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the shared 
storage.
  Please specify the full shared storage connection path to use 
(example: host:/path): storage1.nullaxiom.com:/mgmttank
[ ERROR ] Cannot access storage connection 
storage1.nullaxiom.com:/mgmttank: Command '/sbin/gluster' failed to execute
  Please specify the full shared storage connection path to use 
(example: host:/path):

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mantenance mode error

[Краснобаев Михаил]

Hi, it was alr3eady answered in previous emails  http://lists.ovirt.org/pipermail/users/2014-November/028985.html > > login to your SPM host and run the following
> >
> > vdsClient -s 0 getAllTasksStatuses
> >
> > You can than use
> >
> > stopTask
> > 
> > stop async task
> >
> > and then
> >
> > clearTask
> > 
> > clear async task  30.06.2016, 15:21, "nicola.gentile.to" :hello,I must put in maintenance mode the node of ovirt but returns the following error (by admin web page):Error while executing action: Cannot switch Host to Maintenance mode. Host has asynchronous running tasks,wait for operation to complete and retry.I have checked the log file engine.log and returns the following errors:2016-06-30 13:31:35,688 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47) [5f3d36f7] Lock Acquired to object 'EngineLock:{exclusiveLocks='null', sharedLocks='[0001-0001-0001-0001-037d=]'}'2016-06-30 13:31:35,692 WARN [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47) [5f3d36f7] CanDoAction of action 'MaintenanceNumberOfVdss' failed for user admin@internal. Reasons: VAR__TYPE__HOST,VAR__ACTION__MAINTENANCE,VDS_CANNOT_MAINTENANCE_SPM_WITH_RUNNING_TASKS2016-06-30 13:31:35,692 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47) [5f3d36f7] Lock freed to object 'EngineLock:{exclusiveLocks='null', sharedLocks='[0001-0001-0001-0001-037d=]'}'how can I do to see if there are tasks?What can i do for resolve the problem?Thanks in advanceNicola___Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users  -- С уважением, Краснобаев Михаил.  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] moving disk from nfs to iscsi

[Fernando Fuentes]

Solved my own issue. :)

Thanks guys!

-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org

On Thu, Jun 30, 2016, at 02:40 PM, Fernando Fuentes wrote:
> Team, I am trying to move my vms from one storage domain (NFS Shared) to
> another (iSCSI Shared)...
> 
> Same DC. Two clusters. NFS is on cluser a and iscsi iss on cluster b.
> 
> When I try to move the disk in "cluster a" I am not getting the option
> to move it the iscsi data domain on cluster b.
> 
> Ovirt 3.6.6 all centos 6.6 x86_64 hosts
> 
> Any ideas why?
> 
> Regards,
> 
> 
> -- 
> Fernando Fuentes
> ffuen...@txweather.org
> http://www.txweather.org
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Paul Groeneweg | Pazion]

Op do 30 jun. 2016 om 21:55 schreef Yedidyah Bar David :

> On Thu, Jun 30, 2016 at 10:43 PM, Paul Groeneweg | Pazion
>  wrote:
> >
> >
> > Op do 30 jun. 2016 om 21:17 schreef Yedidyah Bar David  >:
> >>
> >> On Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion <
> p...@pazion.nl>
> >> wrote:
> >> > Things are getting more clear to me, thanks!
> >> > And this whole upgrade is something I should prepare well and not try
> to
> >> > do
> >> > in a few hours at night :)
> >> >
> >> > Resuming, there are multiple solutions:
> >> >
> >> > 1. upgrade el6 to el7
> >> > no go => I need to upgrade postgresql and redhat warns about upgrading
> >> > 6.6
> >> > to 7 because of newer packages
> >> > 2. install a new HE on new Host new storage domain
> >> > a lot of work  => I have to turn off VMs, import storage domain into
> new
> >> > setup and reinstall hosts.
> >> > 3. install a new HE on new Host existing storage domain
> >> > possibly not without issues => I have to manually update references to
> >> > the
> >> > hosted storage or better wait till there is an upgrade tool.
> >> > 4. (re)install HE in current VMS container.
> >> > => I can keep my Hosts and reference to the storage domain.
> >> >
> >> > So I guess my best bet is to go for option 4.
> >> >
> >> > The flow I am planning to follow would be:
> >> >
> >> > 1. Move to global maintenance ( keep VMs running )
> >> > 2. backup ( I have also a complete disk install of old hosted-engine )
> >> > 3. reboot with different conf, to boot from cd
> >> > 4. acces console and run install + import the backup in the engine vm
> >> > ? 5. run engine-setup to configure new install with engine restore
> data
> >> > 6. reboot hosted-engine
> >> > 7. Remove from global maintenance
> >> > 8. launch web gui and I should be able to manage all still running VMs
> >> > again.
> >> >
> >> > Would above be working or am I missing something and I  doubt step 5.
> Is
> >> > this needed?
> >>
> >> Yes.
> >>
> >> In a normal backup/restore flow, it's less important, although
> officially
> >> it's mandatory. But in above flow, it's not just backup/restore, but
> also
> >> upgrade from 3.6 to 4.0.
> >>
> >> In principle you can also do all of the above with 3.6, at least inside
> >> the engine, verify that all seems good, then upgrade to 4.0 later. See
> >> also:
> >>
> >> https://bugzilla.redhat.com/1332463
> >>
> >> But I do not remember reports from people trying it.
> >>
> > Good point, I planned to first get 3.6 running on el7 and from there
> upgrade
> > hosted-engine to 4.0 ( between step 6 and 7 ). Altough this way I keep
> old
> > 3.6 files on my fresh installl...what would you advice? directly install
> 4.0
> > on new el7 host? ( I am running 3.6.7, so above bug is probably fixed ).
>
> If you look at the bug page you see it's fixed in 3.6.6. And even if you
> had
> something earlier you should have been fine, as the fix works also for
> earlier
> 3.6 upgraded to 3.6.6 (or later).
>
> The question whether to first migrate from el6/3.6 to el7/3.6 and later to
> 4.0
> or do this in a single jump is a matter of your motivation and your style.
>
> Do you prefer to do large changes at once, or gradually?
>
> I want to be able do a roll back when thing don't work, so I think I start
with upgrade to el7 with 3.6.
Not sure if it would happen, but this way I don't change anything version
related stuff on the storage side where the VMs reside.



> Do you have some specific new features you want in 4.0?
>
>
Currently I have some issues where my OVF image files of the hosted engine
storage is not updated ( timestamp on hosts folders/ files stay the same )
I am hoping this broken thing is fixed once I have upgraded.
There are further no specific issues I want to upgrade, just to stay
current.
I am running oVirt since 3.4 and it took ( and still takes ) time to learn
about the different components, but overall I love how stable it functions
ov.


> >
> >
> >
> >>
> >> One very important thing you did not mention: Try this on a test system,
> >> including rollback to your backup, after you finished everything and
> >> (supposedly) found out something broken. Better safe than sorry :-)
> >
> >
> > A test setup might provide a good practice. But requires extra spare
> > hosts...
>
> You can test using nested-kvm.
>
> That might be a good idea, will certainly review!


> >I do have a bare metal restore option. So I am able ( with cd boot
> > and console mode) to restore hosted engine within an hour to previous
> state
> > :-)
>
> Including the shared storage? Just mentioning. With decent shared storage
> you probably just revert to a snapshot.
>
>
My Hostedengine storage is mounted as NFS, so backingup/restoring nfs
folder on server might be even easier :)

Hey, these are you own systems, you know how much you trust your tools etc.
> Just pointing out. Also, mainly, for other potential readers of this
> thread...
>
> Thanks!




> >
> 

Re: [ovirt-users] mantenance mode error

[Nir Soffer]

On Thu, Jun 30, 2016 at 4:08 PM, nicola.gentile.to
 wrote:
> I run what you have told me and now I put in maintenance mode the node
> successfully
>
> This is the results of command "vdsClient -s 0 getAllTasksStatuses":
>
> {'status': {'message': 'OK', 'code': 0}, 'allTasksStatus':
> {'19d51354-0add-4c88-a9cf-be660146af6d': {'message': '1 jobs completed
> successfully', 'code': 0, 'taskID': '19d51354-0add-4c88-a9cf-be660146af6d',
> 'taskResult': 'success', 'taskState': 'finished'},
> '355a6da4-be07-4fed-b424-99aa4e3321aa': {'message': '1 jobs completed
> successfully', 'code': 0, 'taskID': '355a6da4-be07-4fed-b424-99aa4e3321aa',
> 'taskResult': 'success', 'taskState': 'finished'},
> 'a0f1551a-f23c-4b89-84c4-43dadbc7c772': {'message': '1 jobs completed
> successfully', 'code': 0, 'taskID': 'a0f1551a-f23c-4b89-84c4-43dadbc7c772',
> 'taskResult': 'success', 'taskState': 'finished'}}}
>
> I attach the request file vdsm.log and engine.log

Would you open a bug for this?
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

We need one place with all the information so we can track this issue.

Thanks,
Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 10:43 PM, Paul Groeneweg | Pazion
 wrote:
>
>
> Op do 30 jun. 2016 om 21:17 schreef Yedidyah Bar David :
>>
>> On Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion 
>> wrote:
>> > Things are getting more clear to me, thanks!
>> > And this whole upgrade is something I should prepare well and not try to
>> > do
>> > in a few hours at night :)
>> >
>> > Resuming, there are multiple solutions:
>> >
>> > 1. upgrade el6 to el7
>> > no go => I need to upgrade postgresql and redhat warns about upgrading
>> > 6.6
>> > to 7 because of newer packages
>> > 2. install a new HE on new Host new storage domain
>> > a lot of work  => I have to turn off VMs, import storage domain into new
>> > setup and reinstall hosts.
>> > 3. install a new HE on new Host existing storage domain
>> > possibly not without issues => I have to manually update references to
>> > the
>> > hosted storage or better wait till there is an upgrade tool.
>> > 4. (re)install HE in current VMS container.
>> > => I can keep my Hosts and reference to the storage domain.
>> >
>> > So I guess my best bet is to go for option 4.
>> >
>> > The flow I am planning to follow would be:
>> >
>> > 1. Move to global maintenance ( keep VMs running )
>> > 2. backup ( I have also a complete disk install of old hosted-engine )
>> > 3. reboot with different conf, to boot from cd
>> > 4. acces console and run install + import the backup in the engine vm
>> > ? 5. run engine-setup to configure new install with engine restore data
>> > 6. reboot hosted-engine
>> > 7. Remove from global maintenance
>> > 8. launch web gui and I should be able to manage all still running VMs
>> > again.
>> >
>> > Would above be working or am I missing something and I  doubt step 5. Is
>> > this needed?
>>
>> Yes.
>>
>> In a normal backup/restore flow, it's less important, although officially
>> it's mandatory. But in above flow, it's not just backup/restore, but also
>> upgrade from 3.6 to 4.0.
>>
>> In principle you can also do all of the above with 3.6, at least inside
>> the engine, verify that all seems good, then upgrade to 4.0 later. See
>> also:
>>
>> https://bugzilla.redhat.com/1332463
>>
>> But I do not remember reports from people trying it.
>>
> Good point, I planned to first get 3.6 running on el7 and from there upgrade
> hosted-engine to 4.0 ( between step 6 and 7 ). Altough this way I keep old
> 3.6 files on my fresh installl...what would you advice? directly install 4.0
> on new el7 host? ( I am running 3.6.7, so above bug is probably fixed ).

If you look at the bug page you see it's fixed in 3.6.6. And even if you had
something earlier you should have been fine, as the fix works also for earlier
3.6 upgraded to 3.6.6 (or later).

The question whether to first migrate from el6/3.6 to el7/3.6 and later to 4.0
or do this in a single jump is a matter of your motivation and your style.

Do you prefer to do large changes at once, or gradually?

Do you have some specific new features you want in 4.0?

>
>
>
>>
>> One very important thing you did not mention: Try this on a test system,
>> including rollback to your backup, after you finished everything and
>> (supposedly) found out something broken. Better safe than sorry :-)
>
>
> A test setup might provide a good practice. But requires extra spare
> hosts...

You can test using nested-kvm.

>I do have a bare metal restore option. So I am able ( with cd boot
> and console mode) to restore hosted engine within an hour to previous state
> :-)

Including the shared storage? Just mentioning. With decent shared storage
you probably just revert to a snapshot.

Hey, these are you own systems, you know how much you trust your tools etc.
Just pointing out. Also, mainly, for other potential readers of this thread...

>
> Thanks a lot for all info!
>
>>
>> Best,
>>
>> >
>> > Best Regards,
>> > Paul
>> >
>> >
>> >
>> > Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi
>> > :
>> >>
>> >> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion
>> >> 
>> >> wrote:
>> >> > Hi Yedidyah,
>> >> >
>> >> > Thank you for the comprehensive answers.
>> >> >
>> >> > I think I go for a complete reinstall ( read also OS upgrade tool is
>> >> > not
>> >> > adviced on 6.6 or higher as there might be newer packages as on 7 ).
>> >> > No
>> >> > doubting to re-use current VM or setup from scratch ( fresh host with
>> >> > new
>> >> > hosted-engine and existing storage domein ).
>> >>
>> >> If you are planning to redeploy hosted-engien from scratch and
>> >> restoring on the new engine DB a backup of the previous one, please
>> >> carefully consider this:
>> >> https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21
>> >>
>> >> So, if you choose that path you'll have also to manually remove any
>> >> reference to the previous hosted-engine from the restored DB.
>> >> I'd strongly suggest you to wait for the upgrade tool to be fixed
>> >> since 

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Paul Groeneweg | Pazion]

Op do 30 jun. 2016 om 21:17 schreef Yedidyah Bar David :

> On Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion 
> wrote:
> > Things are getting more clear to me, thanks!
> > And this whole upgrade is something I should prepare well and not try to
> do
> > in a few hours at night :)
> >
> > Resuming, there are multiple solutions:
> >
> > 1. upgrade el6 to el7
> > no go => I need to upgrade postgresql and redhat warns about upgrading
> 6.6
> > to 7 because of newer packages
> > 2. install a new HE on new Host new storage domain
> > a lot of work  => I have to turn off VMs, import storage domain into new
> > setup and reinstall hosts.
> > 3. install a new HE on new Host existing storage domain
> > possibly not without issues => I have to manually update references to
> the
> > hosted storage or better wait till there is an upgrade tool.
> > 4. (re)install HE in current VMS container.
> > => I can keep my Hosts and reference to the storage domain.
> >
> > So I guess my best bet is to go for option 4.
> >
> > The flow I am planning to follow would be:
> >
> > 1. Move to global maintenance ( keep VMs running )
> > 2. backup ( I have also a complete disk install of old hosted-engine )
> > 3. reboot with different conf, to boot from cd
> > 4. acces console and run install + import the backup in the engine vm
> > ? 5. run engine-setup to configure new install with engine restore data
> > 6. reboot hosted-engine
> > 7. Remove from global maintenance
> > 8. launch web gui and I should be able to manage all still running VMs
> > again.
> >
> > Would above be working or am I missing something and I  doubt step 5. Is
> > this needed?
>
> Yes.
>
> In a normal backup/restore flow, it's less important, although officially
> it's mandatory. But in above flow, it's not just backup/restore, but also
> upgrade from 3.6 to 4.0.
>
> In principle you can also do all of the above with 3.6, at least inside
> the engine, verify that all seems good, then upgrade to 4.0 later. See
> also:
>
> https://bugzilla.redhat.com/1332463
>
> But I do not remember reports from people trying it.
>
> Good point, I planned to first get 3.6 running on el7 and from there
upgrade hosted-engine to 4.0 ( between step 6 and 7 ). Altough this way I
keep old 3.6 files on my fresh installl...what would you advice? directly
install 4.0 on new el7 host? ( I am running 3.6.7, so above bug is probably
fixed ).




> One very important thing you did not mention: Try this on a test system,
> including rollback to your backup, after you finished everything and
> (supposedly) found out something broken. Better safe than sorry :-)
>

A test setup might provide a good practice. But requires extra spare
hosts...I do have a bare metal restore option. So I am able ( with cd boot
and console mode) to restore hosted engine within an hour to previous state
:-)

Thanks a lot for all info!


> Best,
>
> >
> > Best Regards,
> > Paul
> >
> >
> >
> > Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi <
> stira...@redhat.com>:
> >>
> >> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion <
> p...@pazion.nl>
> >> wrote:
> >> > Hi Yedidyah,
> >> >
> >> > Thank you for the comprehensive answers.
> >> >
> >> > I think I go for a complete reinstall ( read also OS upgrade tool is
> not
> >> > adviced on 6.6 or higher as there might be newer packages as on 7 ).
> No
> >> > doubting to re-use current VM or setup from scratch ( fresh host with
> >> > new
> >> > hosted-engine and existing storage domein ).
> >>
> >> If you are planning to redeploy hosted-engien from scratch and
> >> restoring on the new engine DB a backup of the previous one, please
> >> carefully consider this:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21
> >>
> >> So, if you choose that path you'll have also to manually remove any
> >> reference to the previous hosted-engine from the restored DB.
> >> I'd strongly suggest you to wait for the upgrade tool to be fixed
> >> since manually doing this upgrade can be really error prone.
> >>
> >> > You explain the steps ( 1 to 6 ), but then don't talk about storage
> >> > domain
> >> > import.
> >> > Does it mean, when I reinstall the hosted-engine in the current he VM
> >> > and
> >> > restore an engine-backup ( step 5 ) I am able to start vm from Host
> and
> >> > it
> >> > is still connected to the master storage ( so no need for storage
> >> > import) ?
> >> >
> >> > Best Regards,
> >> > Paul Groeneweg
> >> >
> >> >
> >> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David
> >> > :
> >> >>
> >> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
> >> >>  wrote:
> >> >> >
> >> >> > I am looking for a way to get my hosted-engine running on el7 so I
> >> >> > can
> >> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
> >> >> > hosted-engine is still el6.
> >> >> >
> >> >> > I read
> >> >> >
> >> >> >
> >> >> >
> 

[ovirt-users] moving disk from nfs to iscsi

[Fernando Fuentes]

Team, I am trying to move my vms from one storage domain (NFS Shared) to
another (iSCSI Shared)...

Same DC. Two clusters. NFS is on cluser a and iscsi iss on cluster b.

When I try to move the disk in "cluster a" I am not getting the option
to move it the iscsi data domain on cluster b.

Ovirt 3.6.6 all centos 6.6 x86_64 hosts

Any ideas why?

Regards,


-- 
Fernando Fuentes
ffuen...@txweather.org
http://www.txweather.org
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 10:28 PM, Ariel Pérez Rodríguez
 wrote:
> Hi everyone!,
> I've been running into this error every time I try to upgrade to version 4.0
> ([ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade
> from unsupported versions: 3.5). There's an excerpt below of the engine-
> setup output:
>
>  INFO  ] Stage: Setup validation
> [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from
> unsupported versions: 3.5

This is most likely due to having clusters at compatibility level 3.5.

> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20160630150931-ahkjnm.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20160630151045-setup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of setup failed
>
> I've been googling about this issue but this is one vague reference only.
> Then if I tried to downgrade to my current version
> ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch" doesn't allow me:
>
> Resolving Dependencies
> --> Running transaction check
> ---> Package ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos will be a
> downgrade
> --> Processing Dependency: ovirt-engine-setup-plugin-ovirt-engine =
> 3.6.7.5-1.el7.centos for package:
> ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch
> ---> Package ovirt-engine-setup.noarch 0:4.0.0.6-1.el7.centos will be erased
> --> Finished Dependency Resolution
> Error: Package: ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch (ovirt-3.6)
>Requires: ovirt-engine-setup-plugin-ovirt-engine =
> 3.6.7.5-1.el7.centos
>Installed:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.0.6-1.el7.centos.noarch

So downgrade that one as well to 3.6. You can check also 'yum transaction'
to see how to undo the entire last transaction (assuming it was just to
upgrade the setup packages).

>
> Currently I'm not able to start the ovirt-engine service nor go back to
> version 3.6.

But you only upgraded the setup packages, right? The engine should still
be startable. If it's not, please check/post:
1. rpm -qa | grep ovirt
2. links to engine logs (from /var/log/ovirt-engine)

Best,

> Any helps are more than welcome,
> Ariel
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5

[Ariel Pérez Rodríguez]

Hi everyone!,
I've been running into this error every time I try to upgrade to version
4.0 ([ ERROR ] Failed to execute stage 'Setup validation': Trying to
upgrade from unsupported versions: 3.5). There's an excerpt below of the
engine- setup output:

 INFO  ] Stage: Setup validation
[ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade
from unsupported versions: 3.5
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20160630150931-ahkjnm.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20160630151045-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

I've been googling about this issue but this is one vague reference only.
Then if I tried to downgrade to my current version
ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch" doesn't allow me:

Resolving Dependencies
--> Running transaction check
---> Package ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos will be a
downgrade
--> Processing Dependency: ovirt-engine-setup-plugin-ovirt-engine =
3.6.7.5-1.el7.centos for package:
ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch
---> Package ovirt-engine-setup.noarch 0:4.0.0.6-1.el7.centos will be erased
--> Finished Dependency Resolution
Error: Package: ovirt-engine-setup-3.6.7.5-1.el7.centos.noarch (ovirt-3.6)
   Requires: ovirt-engine-setup-plugin-ovirt-engine =
3.6.7.5-1.el7.centos
   Installed:
ovirt-engine-setup-plugin-ovirt-engine-4.0.0.6-1.el7.centos.noarch

Currently I'm not able to start the ovirt-engine service nor go back to
version 3.6.
Any helps are more than welcome,
Ariel
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion  wrote:
> Things are getting more clear to me, thanks!
> And this whole upgrade is something I should prepare well and not try to do
> in a few hours at night :)
>
> Resuming, there are multiple solutions:
>
> 1. upgrade el6 to el7
> no go => I need to upgrade postgresql and redhat warns about upgrading 6.6
> to 7 because of newer packages
> 2. install a new HE on new Host new storage domain
> a lot of work  => I have to turn off VMs, import storage domain into new
> setup and reinstall hosts.
> 3. install a new HE on new Host existing storage domain
> possibly not without issues => I have to manually update references to the
> hosted storage or better wait till there is an upgrade tool.
> 4. (re)install HE in current VMS container.
> => I can keep my Hosts and reference to the storage domain.
>
> So I guess my best bet is to go for option 4.
>
> The flow I am planning to follow would be:
>
> 1. Move to global maintenance ( keep VMs running )
> 2. backup ( I have also a complete disk install of old hosted-engine )
> 3. reboot with different conf, to boot from cd
> 4. acces console and run install + import the backup in the engine vm
> ? 5. run engine-setup to configure new install with engine restore data
> 6. reboot hosted-engine
> 7. Remove from global maintenance
> 8. launch web gui and I should be able to manage all still running VMs
> again.
>
> Would above be working or am I missing something and I  doubt step 5. Is
> this needed?

Yes.

In a normal backup/restore flow, it's less important, although officially
it's mandatory. But in above flow, it's not just backup/restore, but also
upgrade from 3.6 to 4.0.

In principle you can also do all of the above with 3.6, at least inside
the engine, verify that all seems good, then upgrade to 4.0 later. See
also:

https://bugzilla.redhat.com/1332463

But I do not remember reports from people trying it.

One very important thing you did not mention: Try this on a test system,
including rollback to your backup, after you finished everything and
(supposedly) found out something broken. Better safe than sorry :-)

Best,

>
> Best Regards,
> Paul
>
>
>
> Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi :
>>
>> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion 
>> wrote:
>> > Hi Yedidyah,
>> >
>> > Thank you for the comprehensive answers.
>> >
>> > I think I go for a complete reinstall ( read also OS upgrade tool is not
>> > adviced on 6.6 or higher as there might be newer packages as on 7 ). No
>> > doubting to re-use current VM or setup from scratch ( fresh host with
>> > new
>> > hosted-engine and existing storage domein ).
>>
>> If you are planning to redeploy hosted-engien from scratch and
>> restoring on the new engine DB a backup of the previous one, please
>> carefully consider this:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21
>>
>> So, if you choose that path you'll have also to manually remove any
>> reference to the previous hosted-engine from the restored DB.
>> I'd strongly suggest you to wait for the upgrade tool to be fixed
>> since manually doing this upgrade can be really error prone.
>>
>> > You explain the steps ( 1 to 6 ), but then don't talk about storage
>> > domain
>> > import.
>> > Does it mean, when I reinstall the hosted-engine in the current he VM
>> > and
>> > restore an engine-backup ( step 5 ) I am able to start vm from Host and
>> > it
>> > is still connected to the master storage ( so no need for storage
>> > import) ?
>> >
>> > Best Regards,
>> > Paul Groeneweg
>> >
>> >
>> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David
>> > :
>> >>
>> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
>> >>  wrote:
>> >> >
>> >> > I am looking for a way to get my hosted-engine running on el7 so I
>> >> > can
>> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
>> >> > hosted-engine is still el6.
>> >> >
>> >> > I read
>> >> >
>> >> >
>> >> > https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
>> >> > but this is only about the hosts.
>> >> >
>> >> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but
>> >> > it
>> >> > only mentions upgrade of the hosted-engine software, not the OS.
>> >> >
>> >> > I understood I can do a fresh hosted-engine install, and then import
>> >> > my
>> >> > storage domain to the new hosted engine, but:
>> >> >
>> >> > - Do I need to restore my hosted engine database? ( like described
>> >> > here:
>> >> >
>> >> >
>> >> > http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
>> >> > )
>> >>
>> >> You might not have to, if you only care about the imported VMs from
>> >> your
>> >> storage. This will not keep other configuration, such as
>> >> users/roles/permissions
>> >> etc.
>> >>
>> >> > - Can I directly install hosted-engine 4.0 and then import the

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Paul Groeneweg | Pazion]

Things are getting more clear to me, thanks!
And this whole upgrade is something I should prepare well and not try to do
in a few hours at night :)

Resuming, there are multiple solutions:

1. upgrade el6 to el7
no go => I need to upgrade postgresql and redhat warns about upgrading 6.6
to 7 because of newer packages
2. install a new HE on new Host new storage domain
a lot of work  => I have to turn off VMs, import storage domain into new
setup and reinstall hosts.
3. install a new HE on new Host existing storage domain
possibly not without issues => I have to manually update references to the
hosted storage or better wait till there is an upgrade tool.
4. (re)install HE in current VMS container.
=> I can keep my Hosts and reference to the storage domain.

So I guess my best bet is to go for option 4.

The flow I am planning to follow would be:

1. Move to global maintenance ( keep VMs running )
2. backup ( I have also a complete disk install of old hosted-engine )
3. reboot with different conf, to boot from cd
4. acces console and run install + import the backup in the engine vm
? 5. run engine-setup to configure new install with engine restore data
6. reboot hosted-engine
7. Remove from global maintenance
8. launch web gui and I should be able to manage all still running VMs
again.

Would above be working or am I missing something and I  doubt step 5. Is
this needed?

Best Regards,
Paul



Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi :

> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion 
> wrote:
> > Hi Yedidyah,
> >
> > Thank you for the comprehensive answers.
> >
> > I think I go for a complete reinstall ( read also OS upgrade tool is not
> > adviced on 6.6 or higher as there might be newer packages as on 7 ). No
> > doubting to re-use current VM or setup from scratch ( fresh host with new
> > hosted-engine and existing storage domein ).
>
> If you are planning to redeploy hosted-engien from scratch and
> restoring on the new engine DB a backup of the previous one, please
> carefully consider this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21
>
> So, if you choose that path you'll have also to manually remove any
> reference to the previous hosted-engine from the restored DB.
> I'd strongly suggest you to wait for the upgrade tool to be fixed
> since manually doing this upgrade can be really error prone.
>
> > You explain the steps ( 1 to 6 ), but then don't talk about storage
> domain
> > import.
> > Does it mean, when I reinstall the hosted-engine in the current he VM and
> > restore an engine-backup ( step 5 ) I am able to start vm from Host and
> it
> > is still connected to the master storage ( so no need for storage
> import) ?
> >
> > Best Regards,
> > Paul Groeneweg
> >
> >
> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David  >:
> >>
> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
> >>  wrote:
> >> >
> >> > I am looking for a way to get my hosted-engine running on el7 so I can
> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
> >> > hosted-engine is still el6.
> >> >
> >> > I read
> >> >
> >> >
> https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
> >> > but this is only about the hosts.
> >> >
> >> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/,
> but it
> >> > only mentions upgrade of the hosted-engine software, not the OS.
> >> >
> >> > I understood I can do a fresh hosted-engine install, and then import
> my
> >> > storage domain to the new hosted engine, but:
> >> >
> >> > - Do I need to restore my hosted engine database? ( like described
> here:
> >> >
> >> >
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> >> > )
> >>
> >> You might not have to, if you only care about the imported VMs from your
> >> storage. This will not keep other configuration, such as
> >> users/roles/permissions
> >> etc.
> >>
> >> > - Can I directly install hosted-engine 4.0 and then import the storage
> >> > domain? Or should I install same hosted-engine version?
> >>
> >> AFAIK 4.0 engine can import 3.6 storage domains without problem.
> >>
> >> > - Do I first need another master storage domain or can I directly
> import
> >> > my
> >> > old master storage domain?
> >>
> >> No idea. Even if you do, you can create a small empty one and later
> remove
> >> it.
> >>
> >> > - When importing the storage domain what is the risk it fails ( I have
> >> > backups, but it would cost a day to restore all )
> >>
> >> No idea, but IIRC we got many successful reports and at most few
> failures
> >> for this.
> >>
> >> > - How long would import take? few minutes or hours? ( I want to keep
> >> > down
> >> > time as low as possible ).
> >>
> >> Again no idea. Perhaps do some test?
> >>
> >> >
> >> > Another option would be upgrade the OS ( with redhat-upgrade-tool ) or
> >> > is
> >> > this a path for disaster?
> 

[ovirt-users] [oVirt 4.0] Is it possible to access oVirt through a reverse proxy

[COUSIN Kevin]

Hi list,

I upgraded to oVirt 4.0 and it works fine. However, I used HAProxy to
access oVirt outside my LAN. It doesn't work anymore since I upgraded
to 4.0. It seems the oVirt Manager URL is rewritten by the SSO engine.
eg: ovirt.externaldomain.tld -> ovirtmanager.internaldomain.tld. 

Is it possible to disable this  behaviour and stay with
ovirt.externaldomain.tld ?

Regards

-- 
COUSIN Kevin 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] correct repo

[Martin Perina]

On Thu, Jun 30, 2016 at 3:28 PM, Rafael Almeida <
ralme...@prefecturaloja.gob.ec> wrote:

> Hello, what is the correct repo to upgrade ovirt from 3.6 to 4.0 in my
> centos 7.2 x64
>
> yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm


​This one should be used for 4.0 installations.
​


>
> or
> yum install
> http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm


​This one should be used only for development and testing of latest sources.
​


>
>
> thnx.
> greetings
> Rafhael Almeida.
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] correct repo

[Rafael Almeida]

Hello, what is the correct repo to upgrade ovirt from 3.6 to 4.0 in my 
centos 7.2 x64


yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
or
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

thnx.
greetings
Rafhael Almeida.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Simone Tiraboschi]

On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion  wrote:
> Hi Yedidyah,
>
> Thank you for the comprehensive answers.
>
> I think I go for a complete reinstall ( read also OS upgrade tool is not
> adviced on 6.6 or higher as there might be newer packages as on 7 ). No
> doubting to re-use current VM or setup from scratch ( fresh host with new
> hosted-engine and existing storage domein ).

If you are planning to redeploy hosted-engien from scratch and
restoring on the new engine DB a backup of the previous one, please
carefully consider this:
https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21

So, if you choose that path you'll have also to manually remove any
reference to the previous hosted-engine from the restored DB.
I'd strongly suggest you to wait for the upgrade tool to be fixed
since manually doing this upgrade can be really error prone.

> You explain the steps ( 1 to 6 ), but then don't talk about storage domain
> import.
> Does it mean, when I reinstall the hosted-engine in the current he VM and
> restore an engine-backup ( step 5 ) I am able to start vm from Host and it
> is still connected to the master storage ( so no need for storage import) ?
>
> Best Regards,
> Paul Groeneweg
>
>
> Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David :
>>
>> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
>>  wrote:
>> >
>> > I am looking for a way to get my hosted-engine running on el7 so I can
>> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
>> > hosted-engine is still el6.
>> >
>> > I read
>> >
>> > https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
>> > but this is only about the hosts.
>> >
>> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but it
>> > only mentions upgrade of the hosted-engine software, not the OS.
>> >
>> > I understood I can do a fresh hosted-engine install, and then import my
>> > storage domain to the new hosted engine, but:
>> >
>> > - Do I need to restore my hosted engine database? ( like described here:
>> >
>> > http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
>> > )
>>
>> You might not have to, if you only care about the imported VMs from your
>> storage. This will not keep other configuration, such as
>> users/roles/permissions
>> etc.
>>
>> > - Can I directly install hosted-engine 4.0 and then import the storage
>> > domain? Or should I install same hosted-engine version?
>>
>> AFAIK 4.0 engine can import 3.6 storage domains without problem.
>>
>> > - Do I first need another master storage domain or can I directly import
>> > my
>> > old master storage domain?
>>
>> No idea. Even if you do, you can create a small empty one and later remove
>> it.
>>
>> > - When importing the storage domain what is the risk it fails ( I have
>> > backups, but it would cost a day to restore all )
>>
>> No idea, but IIRC we got many successful reports and at most few failures
>> for this.
>>
>> > - How long would import take? few minutes or hours? ( I want to keep
>> > down
>> > time as low as possible ).
>>
>> Again no idea. Perhaps do some test?
>>
>> >
>> > Another option would be upgrade the OS ( with redhat-upgrade-tool ) or
>> > is
>> > this a path for disaster?
>>
>> Didn't work for us well, so we decided to not support it. If you decide to
>> try,
>> make sure you test carefully beforehand. From ovirt's POV:
>> 1. You'll need to handle postgresql upgrade.
>> 2. Right after OS upgrade, you'll still have (I think) el6 packages
>> of the engine. It will hopefully be in a good-enough state for upgrade
>> to 4.0, but we didn't test this.
>> 3. Specifically, if upgrade fails, rollback will most likely not work,
>> so you'll have to manually handle this - take a full vm backup and make
>> sure you can restore it.
>>
>> >
>> > I hope someone can tell me how I can smoothly upgrade my hosted-engine
>> > up to
>> > el7 and run oVirt 4.
>>
>> We are working on a tool/wizard to help with this process. It used to
>> work,
>> but at some point it was decided that one of the actions it does is risky
>> and was blocked, thus the tool is broken currently.
>>
>> You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.
>> As noted above, this is currently broken.
>>
>> There are several open bugs about it, e.g.:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1319457
>> https://bugzilla.redhat.com/show_bug.cgi?id=1343425
>> https://bugzilla.redhat.com/show_bug.cgi?id=1343593 (closed, this is
>> what broke the tool)
>>
>> Basically, you can manually do what the tool is supposed to do:
>> 1. Make sure state is clean and stable (no running/pending storage
>> actions,
>> no VMs in the middle of migration etc), all clusters are compat level 3.6,
>> etc.
>> 2. Move to global maintenance
>> 3. backup the engine using engine-backup and keep the backup elsewhere
>> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use 

Re: [ovirt-users] mantenance mode error

[Nir Soffer]

On Thu, Jun 30, 2016 at 3:20 PM, nicola.gentile.to
 wrote:
> hello,
> I must put in maintenance mode the node of ovirt but returns the following
> error (by admin web page):
>
> Error while executing action: Cannot switch Host to Maintenance mode. Host
> has asynchronous running tasks,
> wait for operation to complete and retry.
>
> I have checked the log file engine.log and returns the following errors:
>
> 2016-06-30 13:31:35,688 INFO
> [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47)
> [5f3d36f7] Lock Acquired to object 'EngineLock:{exclusiveLocks='null',
> sharedLocks='[0001-0001-0001-0001-037d= ACTION_TYPE_FAILED_OBJECT_LOCKED>]'}'
> 2016-06-30 13:31:35,692 WARN
> [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47)
> [5f3d36f7] CanDoAction of action 'MaintenanceNumberOfVdss' failed for user
> admin@internal. Reasons:
> VAR__TYPE__HOST,VAR__ACTION__MAINTENANCE,VDS_CANNOT_MAINTENANCE_SPM_WITH_RUNNING_TASKS
> 2016-06-30 13:31:35,692 INFO
> [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default task-47)
> [5f3d36f7] Lock freed to object 'EngineLock:{exclusiveLocks='null',
> sharedLocks='[0001-0001-0001-0001-037d= ACTION_TYPE_FAILED_OBJECT_LOCKED>]'}'
>
> how can I do to see if there are tasks?

You can run this on the host:

vdsClient -s 0 getAllTasksStatuses

And share the output.

>
> What can i do for resolve the problem?

You should see the status of each task - if you have a finished task,
and engine is not
clearing it, this is a bug in engine - please file a bug and attached
vdsm and engine logs.

To clear the a finished task not cleared by the engine, try to restart
the engine.

If engine is not clearing finished tasks after restart, you can clear
it yourself:

vdsClient -s 0 clearTask 

Nir

>
> Thanks in advance
>
> Nicola
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] mantenance mode error

[nicola.gentile.to]

hello,
I must put in maintenance mode the node of ovirt but returns the 
following error (by admin web page):


Error while executing action: Cannot switch Host to Maintenance mode. 
Host has asynchronous running tasks,

wait for operation to complete and retry.

I have checked the log file engine.log and returns the following errors:

2016-06-30 13:31:35,688 INFO 
[org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default 
task-47) [5f3d36f7] Lock Acquired to object 
'EngineLock:{exclusiveLocks='null', 
sharedLocks='[0001-0001-0001-0001-037d=]'}'
2016-06-30 13:31:35,692 WARN 
[org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default 
task-47) [5f3d36f7] CanDoAction of action 'MaintenanceNumberOfVdss' 
failed for user admin@internal. Reasons: 
VAR__TYPE__HOST,VAR__ACTION__MAINTENANCE,VDS_CANNOT_MAINTENANCE_SPM_WITH_RUNNING_TASKS
2016-06-30 13:31:35,692 INFO 
[org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (default 
task-47) [5f3d36f7] Lock freed to object 
'EngineLock:{exclusiveLocks='null', 
sharedLocks='[0001-0001-0001-0001-037d=]'}'


how can I do to see if there are tasks?

What can i do for resolve the problem?

Thanks in advance

Nicola
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 12:33 PM, Gianluca Cecchi
 wrote:
> On Thu, Jun 30, 2016 at 11:20 AM, Yedidyah Bar David 
> wrote:
>>
>>
>>
>> My suggestion above was to reinstall the same existing VM.
>>
>> If you want to have a new VM, you'll have to configure the HA daemons
>> to know this is the one they should handle, which is currently not
>> supported.
>> --
>> Didi
>
>
> Ah, ok.
> So after you see what is the host containing the VM, you connect to it and
> run something like
>
> hosted-engine --add-console-password
> set the password for engine vm and can connect to its console
> but then how do you connect for example an iso to install CentOS 7 on it?

You can pass a custom conf file, see this:

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

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 3.6.x upgrade to 4.0: HE VM not shutdownable - hyperkonverged r3a1 setup

[Roy Golan]

On Wed, Jun 29, 2016 at 10:25 AM,  wrote:

> Hello all,
>
> yesterday I upgraded my 3.6.x to 4.0 and got stuck with obviously not
> being able to shutdown HE VM itself ("shutdown all VMs" required for
> increasing the compatibility level to 4.0). As I luckily already had a 4th
> pure computing node, rgolan friendly walked me through the process of
> creating a new V4 cluster and moving that 4th node to it. The purpose was
> to free up the default cluster, to be prepared to increase to V4.
>
> The next step was to migrate the HE VM to the new cluster ("automatically
> chose host", as there is only one host for that new cluster). Everything
> went well, but (as rgolan asked to check) the cluster assignment for the HE
> VM in the edit VM dialogue still shows "Default" and an attempt to increase
> the compatibility of "Default" cluster of course didn't work ("first shut
> down all VMs!"). The migration of another VM to that new cluster on the
> other hand worked without a glitch.
>
> Attached is the engine.log. Relevant entries should start at around "
> 2016-06-29 00:53:20 ", it should be the time I created the new cluster and
> moved pure computing node " slp-ovirtnode-04 " to it. Please ignore the
> glusterfs brick entries, I have additional disks ready to be added, but
> this is another story ;)
>
> Hopefully there is a way to entirely move the HE VM to the new cluster.
>
> Thanks and regards
> mikelupe
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
At the end of the migration we prevent that action on the hosted engine vm
specifically

2016-06-28 21:55:20,734 WARN
 [org.ovirt.engine.core.bll.ChangeVMClusterCommand]
(ForkJoinPool-1-worker-0) [3ce2a3ad] Validation of action 'ChangeVMCluster'
failed for user SYSTEM. Reasons:
VAR__ACTION__UPDATE,VAR__TYPE__VM__CLUSTER,ACTION_TYPE_FAILED_CANNOT_RUN_ACTION_ON_NON_MANAGED_VM

I opened https://bugzilla.redhat.com/show_bug.cgi?id=1351533

Mike if you want meanwhile I can supply a script to help you with that.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Gianluca Cecchi]

On Thu, Jun 30, 2016 at 11:20 AM, Yedidyah Bar David 
wrote:

>
>
> My suggestion above was to reinstall the same existing VM.
>
> If you want to have a new VM, you'll have to configure the HA daemons
> to know this is the one they should handle, which is currently not
> supported.
> --
> Didi
>

Ah, ok.
So after you see what is the host containing the VM, you connect to it and
run something like

hosted-engine --add-console-password
set the password for engine vm and can connect to its console
but then how do you connect for example an iso to install CentOS 7 on it?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.0.0 - Cluster Compatibility Version

[Roy Golan]

On Fri, Jun 24, 2016 at 9:19 AM, Michal Skrivanek 
wrote:

>
> On 24 Jun 2016, at 08:15, Sandro Bonazzola  wrote:
>
>
>
> On Fri, Jun 24, 2016 at 12:08 AM, Scott  wrote:
>
>> Hello list,
>>
>> I've successfully upgraded oVirt to 4.0 from 3.6 on my engine and three
>> hosts.  However, it doesn't look like I can change the Cluster
>> Compatibility Version to 4.0.  It tells me I need to shut down all the VMs
>> in the cluster.  Except I use Hosted Engine.  How do I change the cluster
>> compatibility version when the engine is down?
>>
>
> We're on it, tracked by
> https://bugzilla.redhat.com/show_bug.cgi?id=1348907 (During cluster level
> upgrade - warn and mark VMs as pending a configuration change when they are
> running)
>
>
> While that’s in progress, I’m still not clear whether that is a real
> blocker for this flow or not as Roy/Didi was saying due to HE having it’s
> own separate configuration the set of hosts it runs on does not necessarily
> have to follow the engine’s view of the cluster. So I don’t really know
> what’s required for HE to change its cluster
>
>
We need a fix for the engine to allow migrating HE 3.6 to 4.0 and upgarfde
of that cluster compat level - If we want to upgrade the HE cluster version
the HE-VM itself must move away to a new  cluster. Migrating to a new
cluster is supported, but not the ChangeVmCluster action on hosted engine
vm.  The VM will effectively run on another host (and cluster) but the ID
will remain of the old cluster.

See bug https://bugzilla.redhat.com/show_bug.cgi?id=1351533

BTW, 1348907 fix won't help, cause the engine vm itself won't leave to
perform this change. The engine never sees itself as starting or stopping.


Thanks,
> michal
>
>
>
>
>
>>
>> Thanks in advance,
>> Scott
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 11:53 AM, Gianluca Cecchi
 wrote:
> On Thu, Jun 30, 2016 at 8:00 AM, Yedidyah Bar David  wrote:
>>
>>
>>
>> Basically, you can manually do what the tool is supposed to do:
>> 1. Make sure state is clean and stable (no running/pending storage
>> actions,
>> no VMs in the middle of migration etc), all clusters are compat level 3.6,
>> etc.
>> 2. Move to global maintenance
>> 3. backup the engine using engine-backup and keep the backup elsewhere
>> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the
>> engine
>> appliance, you might too but not sure how exactly).
>> 5. Restore the backup and run engine-setup.
>> 6. If all looks ok, leave global maintenance.
>>
>> If you manually keep a full backup of the engine vm before step 4,
>> you might be able to restore this backup if there are problems.
>> Doing this in the provided tool is currently the main blocking issue
>> for it. Hopefully will be provided in 4.0.1.
>>
>> Best,
>> --
>> Didi
>> _
>
>
> Hello,
> coming back to this proposed steps, do you think it could be applied also to
> single host environment with hosted engine?
> In that case a few clarifications needed
>
> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the engine
> appliance, you might too but not sure how exactly).
> --> so in my still working 3.6 environment I will install a clean VM with
> el7 and at least at the beginning while I provision it, it should have
> different hostname and ip from previous engine vm, correct?
> And then? Can I shutdown previous engine vm and after that, give the same
> hostname and ip to the new el7 vm ?

My suggestion above was to reinstall the same existing VM.

If you want to have a new VM, you'll have to configure the HA daemons
to know this is the one they should handle, which is currently not
supported.
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 9:47 AM, Paul Groeneweg | Pazion  wrote:
> Ok that sounds good.
>
> And if I deploy a new hosted-engine on a fresh host I need to do a storage
> domain import after restore?

Please describe exact flow you plan.

In principle you can use a flow similar to the one described in the "migrate
to hosted-engine" doc you mentioned before. Run engine-backup backup on the
existing engine, deploy new hosted-engine on a new host and new storage,
then restore the backup and engine-setup.

You'll keep all your existing VMs and hosts/storage/etc.

The main issue will be about HE shared storage, from the POV of the HA daemons
on the existing HE hosts. They'll look at the old storage configured, and we
do not supply a tool to change that. So in principle, you can try
something like:

1. Move to global maintenance
2. backup
3. deploy hosted-engine on a new host and storage, import the backup in the
engine vm and engine-setup.
4. Migrate all running VMs from one of the old HE hosts to the new HE host.
5. Move this old host to maint and remove it.
6. Clean this old host somehow (simplest is OS reinstall) and deploy it again
as an additional HE host of the new hosted-engine setup (that is, when asked
for hosted storage, supply the new storage).
7. Repeat steps 4-6 for all the remaining old hosts.

This is obviously somewhat more complex than just setting up a completely new
engine (no backup/restore) and only import the VMs, but in principle might
allow no downtime at all for the other VMs.

> Or is my config including master storage domain restored and I can use the
> old storage domain with need to import?

Your config is not restored unless you restore it manually.
Unless you use the tool when it's ready, and it will do that for you :-)

Best,

>
>
>
> Op do 30 jun. 2016 om 08:41 schreef Yedidyah Bar David :
>>
>> On Thu, Jun 30, 2016 at 9:34 AM, Paul Groeneweg | Pazion 
>> wrote:
>> > Hi Yedidyah,
>> >
>> > Thank you for the comprehensive answers.
>> >
>> > I think I go for a complete reinstall ( read also OS upgrade tool is not
>> > adviced on 6.6 or higher as there might be newer packages as on 7 ). No
>> > doubting to re-use current VM or setup from scratch ( fresh host with
>> > new
>> > hosted-engine and existing storage domein ).
>> >
>> > You explain the steps ( 1 to 6 ), but then don't talk about storage
>> > domain
>> > import.
>> > Does it mean, when I reinstall the hosted-engine in the current he VM
>> > and
>> > restore an engine-backup ( step 5 ) I am able to start vm from Host and
>> > it
>> > is still connected to the master storage ( so no need for storage
>> > import) ?
>>
>> Indeed - if you didn't touch the storage, the restored engine should
>> already
>> knows all it needs to know.
>>
>> Best,
>>
>> >
>> > Best Regards,
>> > Paul Groeneweg
>> >
>> >
>> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David
>> > :
>> >>
>> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
>> >>  wrote:
>> >> >
>> >> > I am looking for a way to get my hosted-engine running on el7 so I
>> >> > can
>> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
>> >> > hosted-engine is still el6.
>> >> >
>> >> > I read
>> >> >
>> >> >
>> >> > https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
>> >> > but this is only about the hosts.
>> >> >
>> >> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but
>> >> > it
>> >> > only mentions upgrade of the hosted-engine software, not the OS.
>> >> >
>> >> > I understood I can do a fresh hosted-engine install, and then import
>> >> > my
>> >> > storage domain to the new hosted engine, but:
>> >> >
>> >> > - Do I need to restore my hosted engine database? ( like described
>> >> > here:
>> >> >
>> >> >
>> >> > http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
>> >> > )
>> >>
>> >> You might not have to, if you only care about the imported VMs from
>> >> your
>> >> storage. This will not keep other configuration, such as
>> >> users/roles/permissions
>> >> etc.
>> >>
>> >> > - Can I directly install hosted-engine 4.0 and then import the
>> >> > storage
>> >> > domain? Or should I install same hosted-engine version?
>> >>
>> >> AFAIK 4.0 engine can import 3.6 storage domains without problem.
>> >>
>> >> > - Do I first need another master storage domain or can I directly
>> >> > import
>> >> > my
>> >> > old master storage domain?
>> >>
>> >> No idea. Even if you do, you can create a small empty one and later
>> >> remove
>> >> it.
>> >>
>> >> > - When importing the storage domain what is the risk it fails ( I
>> >> > have
>> >> > backups, but it would cost a day to restore all )
>> >>
>> >> No idea, but IIRC we got many successful reports and at most few
>> >> failures
>> >> for this.
>> >>
>> >> > - How long would import take? few minutes or hours? ( I want to keep
>> >> > down
>> >> > time 

Re: [ovirt-users] Windows 7 to 10 Upgrade fails

[Vinzenz Feenstra]

> On Jun 29, 2016, at 9:40 PM, Blaster  wrote:
> 
> I'm trying to update some Windows 7 VMs before the free upgrade period ends.
> 
> It appears Windows 10 has an issue with KVM during the upgrade, and according 
> to this thread, 
> http://ubuntuforums.org/showthread.php?t=2289210=13334367#post13334367 , 
> you need to specify the CPU type as core2duo for the VM, perform the upgrade, 
> then switch it back.
> 
> Is there anyway with ovirt to set the CPU type to core2duo for a single VM 
> without having to shutdown the entire cluster, change it for the cluster, do 
> the upgrades, then change it all back?

Core2Duo corresponds to the Intel Penryn Family - If you have your cluster on 
Conroe you’d have to create a new cluster with the Intel Penryn Family CPU 
Type, add a host to that new cluster and then change the VM you would like to 
upgrade to that new cluster.

Otherwise that shouldn’t be a big problem, except that you might want to also 
change already the OS type in the VM Configuration to Windows 10 (With the 
correct architecture)

HTH,

> 
> Thank you
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Paul Groeneweg | Pazion]

Ok that sounds good.

And if I deploy a new hosted-engine on a fresh host I need to do a storage
domain import after restore?
Or is my config including master storage domain restored and I can use the
old storage domain with need to import?



Op do 30 jun. 2016 om 08:41 schreef Yedidyah Bar David :

> On Thu, Jun 30, 2016 at 9:34 AM, Paul Groeneweg | Pazion 
> wrote:
> > Hi Yedidyah,
> >
> > Thank you for the comprehensive answers.
> >
> > I think I go for a complete reinstall ( read also OS upgrade tool is not
> > adviced on 6.6 or higher as there might be newer packages as on 7 ). No
> > doubting to re-use current VM or setup from scratch ( fresh host with new
> > hosted-engine and existing storage domein ).
> >
> > You explain the steps ( 1 to 6 ), but then don't talk about storage
> domain
> > import.
> > Does it mean, when I reinstall the hosted-engine in the current he VM and
> > restore an engine-backup ( step 5 ) I am able to start vm from Host and
> it
> > is still connected to the master storage ( so no need for storage
> import) ?
>
> Indeed - if you didn't touch the storage, the restored engine should
> already
> knows all it needs to know.
>
> Best,
>
> >
> > Best Regards,
> > Paul Groeneweg
> >
> >
> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David  >:
> >>
> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
> >>  wrote:
> >> >
> >> > I am looking for a way to get my hosted-engine running on el7 so I can
> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
> >> > hosted-engine is still el6.
> >> >
> >> > I read
> >> >
> >> >
> https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
> >> > but this is only about the hosts.
> >> >
> >> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/,
> but it
> >> > only mentions upgrade of the hosted-engine software, not the OS.
> >> >
> >> > I understood I can do a fresh hosted-engine install, and then import
> my
> >> > storage domain to the new hosted engine, but:
> >> >
> >> > - Do I need to restore my hosted engine database? ( like described
> here:
> >> >
> >> >
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> >> > )
> >>
> >> You might not have to, if you only care about the imported VMs from your
> >> storage. This will not keep other configuration, such as
> >> users/roles/permissions
> >> etc.
> >>
> >> > - Can I directly install hosted-engine 4.0 and then import the storage
> >> > domain? Or should I install same hosted-engine version?
> >>
> >> AFAIK 4.0 engine can import 3.6 storage domains without problem.
> >>
> >> > - Do I first need another master storage domain or can I directly
> import
> >> > my
> >> > old master storage domain?
> >>
> >> No idea. Even if you do, you can create a small empty one and later
> remove
> >> it.
> >>
> >> > - When importing the storage domain what is the risk it fails ( I have
> >> > backups, but it would cost a day to restore all )
> >>
> >> No idea, but IIRC we got many successful reports and at most few
> failures
> >> for this.
> >>
> >> > - How long would import take? few minutes or hours? ( I want to keep
> >> > down
> >> > time as low as possible ).
> >>
> >> Again no idea. Perhaps do some test?
> >>
> >> >
> >> > Another option would be upgrade the OS ( with redhat-upgrade-tool ) or
> >> > is
> >> > this a path for disaster?
> >>
> >> Didn't work for us well, so we decided to not support it. If you decide
> to
> >> try,
> >> make sure you test carefully beforehand. From ovirt's POV:
> >> 1. You'll need to handle postgresql upgrade.
> >> 2. Right after OS upgrade, you'll still have (I think) el6 packages
> >> of the engine. It will hopefully be in a good-enough state for upgrade
> >> to 4.0, but we didn't test this.
> >> 3. Specifically, if upgrade fails, rollback will most likely not work,
> >> so you'll have to manually handle this - take a full vm backup and make
> >> sure you can restore it.
> >>
> >> >
> >> > I hope someone can tell me how I can smoothly upgrade my hosted-engine
> >> > up to
> >> > el7 and run oVirt 4.
> >>
> >> We are working on a tool/wizard to help with this process. It used to
> >> work,
> >> but at some point it was decided that one of the actions it does is
> risky
> >> and was blocked, thus the tool is broken currently.
> >>
> >> You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.
> >> As noted above, this is currently broken.
> >>
> >> There are several open bugs about it, e.g.:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1319457
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1343425
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1343593 (closed, this is
> >> what broke the tool)
> >>
> >> Basically, you can manually do what the tool is supposed to do:
> >> 1. Make sure state is clean and stable (no running/pending storage
> >> actions,
> >> no VMs in the middle of 

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Thu, Jun 30, 2016 at 9:34 AM, Paul Groeneweg | Pazion  wrote:
> Hi Yedidyah,
>
> Thank you for the comprehensive answers.
>
> I think I go for a complete reinstall ( read also OS upgrade tool is not
> adviced on 6.6 or higher as there might be newer packages as on 7 ). No
> doubting to re-use current VM or setup from scratch ( fresh host with new
> hosted-engine and existing storage domein ).
>
> You explain the steps ( 1 to 6 ), but then don't talk about storage domain
> import.
> Does it mean, when I reinstall the hosted-engine in the current he VM and
> restore an engine-backup ( step 5 ) I am able to start vm from Host and it
> is still connected to the master storage ( so no need for storage import) ?

Indeed - if you didn't touch the storage, the restored engine should already
knows all it needs to know.

Best,

>
> Best Regards,
> Paul Groeneweg
>
>
> Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David :
>>
>> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
>>  wrote:
>> >
>> > I am looking for a way to get my hosted-engine running on el7 so I can
>> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
>> > hosted-engine is still el6.
>> >
>> > I read
>> >
>> > https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
>> > but this is only about the hosts.
>> >
>> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but it
>> > only mentions upgrade of the hosted-engine software, not the OS.
>> >
>> > I understood I can do a fresh hosted-engine install, and then import my
>> > storage domain to the new hosted engine, but:
>> >
>> > - Do I need to restore my hosted engine database? ( like described here:
>> >
>> > http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
>> > )
>>
>> You might not have to, if you only care about the imported VMs from your
>> storage. This will not keep other configuration, such as
>> users/roles/permissions
>> etc.
>>
>> > - Can I directly install hosted-engine 4.0 and then import the storage
>> > domain? Or should I install same hosted-engine version?
>>
>> AFAIK 4.0 engine can import 3.6 storage domains without problem.
>>
>> > - Do I first need another master storage domain or can I directly import
>> > my
>> > old master storage domain?
>>
>> No idea. Even if you do, you can create a small empty one and later remove
>> it.
>>
>> > - When importing the storage domain what is the risk it fails ( I have
>> > backups, but it would cost a day to restore all )
>>
>> No idea, but IIRC we got many successful reports and at most few failures
>> for this.
>>
>> > - How long would import take? few minutes or hours? ( I want to keep
>> > down
>> > time as low as possible ).
>>
>> Again no idea. Perhaps do some test?
>>
>> >
>> > Another option would be upgrade the OS ( with redhat-upgrade-tool ) or
>> > is
>> > this a path for disaster?
>>
>> Didn't work for us well, so we decided to not support it. If you decide to
>> try,
>> make sure you test carefully beforehand. From ovirt's POV:
>> 1. You'll need to handle postgresql upgrade.
>> 2. Right after OS upgrade, you'll still have (I think) el6 packages
>> of the engine. It will hopefully be in a good-enough state for upgrade
>> to 4.0, but we didn't test this.
>> 3. Specifically, if upgrade fails, rollback will most likely not work,
>> so you'll have to manually handle this - take a full vm backup and make
>> sure you can restore it.
>>
>> >
>> > I hope someone can tell me how I can smoothly upgrade my hosted-engine
>> > up to
>> > el7 and run oVirt 4.
>>
>> We are working on a tool/wizard to help with this process. It used to
>> work,
>> but at some point it was decided that one of the actions it does is risky
>> and was blocked, thus the tool is broken currently.
>>
>> You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.
>> As noted above, this is currently broken.
>>
>> There are several open bugs about it, e.g.:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1319457
>> https://bugzilla.redhat.com/show_bug.cgi?id=1343425
>> https://bugzilla.redhat.com/show_bug.cgi?id=1343593 (closed, this is
>> what broke the tool)
>>
>> Basically, you can manually do what the tool is supposed to do:
>> 1. Make sure state is clean and stable (no running/pending storage
>> actions,
>> no VMs in the middle of migration etc), all clusters are compat level 3.6,
>> etc.
>> 2. Move to global maintenance
>> 3. backup the engine using engine-backup and keep the backup elsewhere
>> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the
>> engine
>> appliance, you might too but not sure how exactly).
>> 5. Restore the backup and run engine-setup.
>> 6. If all looks ok, leave global maintenance.
>>
>> If you manually keep a full backup of the engine vm before step 4,
>> you might be able to restore this backup if there are problems.
>> Doing this in the provided tool is currently the 

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Paul Groeneweg | Pazion]

Hi Yedidyah,

Thank you for the comprehensive answers.

I think I go for a complete reinstall ( read also OS upgrade tool is not
adviced on 6.6 or higher as there might be newer packages as on 7 ). No
doubting to re-use current VM or setup from scratch ( fresh host with new
hosted-engine and existing storage domein ).

You explain the steps ( 1 to 6 ), but then don't talk about storage domain
import.
Does it mean, when I reinstall the hosted-engine in the current he VM
and restore
an engine-backup ( step 5 ) I am able to start vm from Host and it is still
connected to the master storage ( so no need for storage import) ?

Best Regards,
Paul Groeneweg


Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David :

> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
>  wrote:
> >
> > I am looking for a way to get my hosted-engine running on el7 so I can
> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my
> > hosted-engine is still el6.
> >
> > I read
> >
> https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
> > but this is only about the hosts.
> >
> > I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but it
> > only mentions upgrade of the hosted-engine software, not the OS.
> >
> > I understood I can do a fresh hosted-engine install, and then import my
> > storage domain to the new hosted engine, but:
> >
> > - Do I need to restore my hosted engine database? ( like described here:
> >
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> > )
>
> You might not have to, if you only care about the imported VMs from your
> storage. This will not keep other configuration, such as
> users/roles/permissions
> etc.
>
> > - Can I directly install hosted-engine 4.0 and then import the storage
> > domain? Or should I install same hosted-engine version?
>
> AFAIK 4.0 engine can import 3.6 storage domains without problem.
>
> > - Do I first need another master storage domain or can I directly import
> my
> > old master storage domain?
>
> No idea. Even if you do, you can create a small empty one and later remove
> it.
>
> > - When importing the storage domain what is the risk it fails ( I have
> > backups, but it would cost a day to restore all )
>
> No idea, but IIRC we got many successful reports and at most few failures
> for this.
>
> > - How long would import take? few minutes or hours? ( I want to keep down
> > time as low as possible ).
>
> Again no idea. Perhaps do some test?
>
> >
> > Another option would be upgrade the OS ( with redhat-upgrade-tool ) or is
> > this a path for disaster?
>
> Didn't work for us well, so we decided to not support it. If you decide to
> try,
> make sure you test carefully beforehand. From ovirt's POV:
> 1. You'll need to handle postgresql upgrade.
> 2. Right after OS upgrade, you'll still have (I think) el6 packages
> of the engine. It will hopefully be in a good-enough state for upgrade
> to 4.0, but we didn't test this.
> 3. Specifically, if upgrade fails, rollback will most likely not work,
> so you'll have to manually handle this - take a full vm backup and make
> sure you can restore it.
>
> >
> > I hope someone can tell me how I can smoothly upgrade my hosted-engine
> up to
> > el7 and run oVirt 4.
>
> We are working on a tool/wizard to help with this process. It used to work,
> but at some point it was decided that one of the actions it does is risky
> and was blocked, thus the tool is broken currently.
>
> You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.
> As noted above, this is currently broken.
>
> There are several open bugs about it, e.g.:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1319457
> https://bugzilla.redhat.com/show_bug.cgi?id=1343425
> https://bugzilla.redhat.com/show_bug.cgi?id=1343593 (closed, this is
> what broke the tool)
>
> Basically, you can manually do what the tool is supposed to do:
> 1. Make sure state is clean and stable (no running/pending storage actions,
> no VMs in the middle of migration etc), all clusters are compat level 3.6,
> etc.
> 2. Move to global maintenance
> 3. backup the engine using engine-backup and keep the backup elsewhere
> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the
> engine
> appliance, you might too but not sure how exactly).
> 5. Restore the backup and run engine-setup.
> 6. If all looks ok, leave global maintenance.
>
> If you manually keep a full backup of the engine vm before step 4,
> you might be able to restore this backup if there are problems.
> Doing this in the provided tool is currently the main blocking issue
> for it. Hopefully will be provided in 4.0.1.
>
> Best,
> --
> Didi
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] upgrade hosted-engine os ( not hosts )

[Yedidyah Bar David]

On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion
 wrote:
>
> I am looking for a way to get my hosted-engine running on el7 so I can
> upgrade to oVirt 4.0. Currently my hosts already run el7, but my
> hosted-engine is still el6.
>
> I read
> https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/
> but this is only about the hosts.
>
> I read https://www.ovirt.org/documentation/how-to/hosted-engine/, but it
> only mentions upgrade of the hosted-engine software, not the OS.
>
> I understood I can do a fresh hosted-engine install, and then import my
> storage domain to the new hosted engine, but:
>
> - Do I need to restore my hosted engine database? ( like described here:
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> )

You might not have to, if you only care about the imported VMs from your
storage. This will not keep other configuration, such as users/roles/permissions
etc.

> - Can I directly install hosted-engine 4.0 and then import the storage
> domain? Or should I install same hosted-engine version?

AFAIK 4.0 engine can import 3.6 storage domains without problem.

> - Do I first need another master storage domain or can I directly import my
> old master storage domain?

No idea. Even if you do, you can create a small empty one and later remove it.

> - When importing the storage domain what is the risk it fails ( I have
> backups, but it would cost a day to restore all )

No idea, but IIRC we got many successful reports and at most few failures
for this.

> - How long would import take? few minutes or hours? ( I want to keep down
> time as low as possible ).

Again no idea. Perhaps do some test?

>
> Another option would be upgrade the OS ( with redhat-upgrade-tool ) or is
> this a path for disaster?

Didn't work for us well, so we decided to not support it. If you decide to try,
make sure you test carefully beforehand. From ovirt's POV:
1. You'll need to handle postgresql upgrade.
2. Right after OS upgrade, you'll still have (I think) el6 packages
of the engine. It will hopefully be in a good-enough state for upgrade
to 4.0, but we didn't test this.
3. Specifically, if upgrade fails, rollback will most likely not work,
so you'll have to manually handle this - take a full vm backup and make
sure you can restore it.

>
> I hope someone can tell me how I can smoothly upgrade my hosted-engine up to
> el7 and run oVirt 4.

We are working on a tool/wizard to help with this process. It used to work,
but at some point it was decided that one of the actions it does is risky
and was blocked, thus the tool is broken currently.

You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.
As noted above, this is currently broken.

There are several open bugs about it, e.g.:

https://bugzilla.redhat.com/show_bug.cgi?id=1319457
https://bugzilla.redhat.com/show_bug.cgi?id=1343425
https://bugzilla.redhat.com/show_bug.cgi?id=1343593 (closed, this is
what broke the tool)

Basically, you can manually do what the tool is supposed to do:
1. Make sure state is clean and stable (no running/pending storage actions,
no VMs in the middle of migration etc), all clusters are compat level 3.6, etc.
2. Move to global maintenance
3. backup the engine using engine-backup and keep the backup elsewhere
4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the engine
appliance, you might too but not sure how exactly).
5. Restore the backup and run engine-setup.
6. If all looks ok, leave global maintenance.

If you manually keep a full backup of the engine vm before step 4,
you might be able to restore this backup if there are problems.
Doing this in the provided tool is currently the main blocking issue
for it. Hopefully will be provided in 4.0.1.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users