Re: [ovirt-users] disk not bootable

2016-07-10 Thread Fernando Fuentes 
Nir,

I am on it and will reply with the requested info asap.

Regards,

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

On Sun, Jul 10, 2016, at 02:15 PM, Nir Soffer wrote:
> On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler 
> wrote:
> > All, I did a test for Fernando in our ovirt environment. I created a vm
> > called win7melly in the nfs domain. I then migrated it to the iscsi
> > domain. It booted without any issue. So it has to be something with the
> > templates. I have attached the vdsm log for the host the vm resides on.
> 
> The log show a working vm, so it does not help much.
> 
> I think that the template you copied from the nfs domain to the block
> domain is
> corrupted, or the volume metadata are incorrect.
> 
> If I understand this correctly, this started when Fernando could not copy
> the vm
> disk to the block storage, and I guess the issue was that the template
> was missing
> on that storage domain. I assume that he copied the template to the
> block storage
> domain by opening the templates tab, selecting the template, and choosing
> copy
> from the menu.
> 
> Lets compare the template on both nfs and block storage domain.
> 
> 1. Find the template on the nfs storage domain, using the image uuid in
> engine.
> 
> It should be at
> 
> 
> /rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid
> 
> 2. Please share the output of:
> 
> cat /path/to/volume.meta
> qemu-img info /path/to/volume
> qemu-img check /path/to/volume
> 
> 4. Find the template on the block storage domain
> 
> You should have an lv using the same volume uuid and the image-uuid
> should be in the lv tag.
> 
> Find it using:
> 
> lvs -o vg_name,lv_name,tags | grep volume-uuid
> 
> 5. Activate the lv
> 
> lvchange -ay vg_name/lv_name
> 
> 6. Share the output of
> 
> qemu-img info /dev/vg_name/lv_name
> qemu-img check /dev/vg_name/lv_name
> 
> 7. Deactivate the lv
> 
> lvchange -an vg_name/lv_name
> 
> 8. Find the lv metadata
> 
> The metadata is stored in /dev/vg_name/metadata. To find the correct
> block,
> find the tag named MD_N in the lv tags you found in step 4
> 
> The block we need is located at offset N from start of volume.
> 
> 9. Share the output of:
> 
> dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct
> 
> The output of this command should show the image-uuid.
> 
> Nir
> 
> >
> > - MeLLy
> >
> > On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
> >> Nir,
> >>
> >> That's exactly how I did it Nir.
> >> I will test tomorrow with a new Windows VM and report back.
> >>
> >> Regards,
> >>
> >> --
> >> Fernando Fuentes
> >> ffuen...@txweather.org
> >> http://www.txweather.org
> >>
> >> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
> >> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
> >> > wrote:
> >> > > - Original Message -
> >> > >> From: "Nir Soffer" 
> >> > >> To: "Fernando Fuentes" 
> >> > >> Cc: "Francesco Romani" , "users" 
> >> > >> Sent: Saturday, July 2, 2016 11:18:01 AM
> >> > >> Subject: Re: [ovirt-users] disk not bootable
> >> > >>
> >> > >> On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes 
> >> > >> 
> >> > >> wrote:
> >> > >> > Nir,
> >> > >> >
> >> > >> > Ok I ran another test and this one I moved from NFS domain to iSCSI 
> >> > >> > and
> >> > >> > stop working than I moved it back and still unable to run... 
> >> > >> > Windows VM
> >> > >> > is saying "no available boot disk"
> >> > >> > VM: Win7-Test
> >> > >> > Host: Zeta
> >> > >> > Info as requested:  http://pastebin.com/1fSi3auz
> >> > >>
> >> > >> We need a working xml to compare to.
> >> > >
> >> > > [snip expected changes]
> >> > >
> >> > >
> >> > >>   oVirt
> >> > >>   oVirt Node
> >> > >>   6-5.el6.centos.11.2
> >> > >> - C938F077-55E2-3E50-A694-9FCB7661FD89
> >> > >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> >> > >>
> >> > >> Not expected - maybe this is confusing windows?
> >> > >>
> >> > >> Francesco, why vm serial has changed after moving disks from one 
> >> > >> storage
> >> > >> domain
> >> > >> to another?
> >> > >
> >> > > We put in serial either
> >> > > 1. the UUID Engine send to us
> >> > > 2. the host UUID as returned by our getHostUUID utility function
> >> > >
> >> > > the latter is unlikely to change, even after this disk move.
> >> >
> >> > Fernando, can you describe exactly how you moved the disk?
> >> >
> >> > I assume that you selected the vm in the virtual machines tab, then
> >> > selected
> >> > disks from the sub tab, then selected move, and selected the target
> >> > storage domain.
> >> >
> >> > Also, can you reproduce this with a new vm? (create vm with disk nfs,
> >> > stop vm,
> >> > move disk to iscsi, start vm).
> >> >
> >> > > So the first suspect in line is Engine
> >> > >
> >> > > Arik, do you know if Engine is indeed supposed to change the

Re: [ovirt-users] disk not bootable

2016-07-10 Thread Nir Soffer 
On Thu, Jul 7, 2016 at 7:46 PM, Melissa Mesler  wrote:
> All, I did a test for Fernando in our ovirt environment. I created a vm
> called win7melly in the nfs domain. I then migrated it to the iscsi
> domain. It booted without any issue. So it has to be something with the
> templates. I have attached the vdsm log for the host the vm resides on.

The log show a working vm, so it does not help much.

I think that the template you copied from the nfs domain to the block domain is
corrupted, or the volume metadata are incorrect.

If I understand this correctly, this started when Fernando could not copy the vm
disk to the block storage, and I guess the issue was that the template
was missing
on that storage domain. I assume that he copied the template to the
block storage
domain by opening the templates tab, selecting the template, and choosing copy
from the menu.

Lets compare the template on both nfs and block storage domain.

1. Find the template on the nfs storage domain, using the image uuid in engine.

It should be at

/rhev/data-center/mnt/server:_path/domain-uuid/images/image-uuid/volume-uuid

2. Please share the output of:

cat /path/to/volume.meta
qemu-img info /path/to/volume
qemu-img check /path/to/volume

4. Find the template on the block storage domain

You should have an lv using the same volume uuid and the image-uuid
should be in the lv tag.

Find it using:

lvs -o vg_name,lv_name,tags | grep volume-uuid

5. Activate the lv

lvchange -ay vg_name/lv_name

6. Share the output of

qemu-img info /dev/vg_name/lv_name
qemu-img check /dev/vg_name/lv_name

7. Deactivate the lv

lvchange -an vg_name/lv_name

8. Find the lv metadata

The metadata is stored in /dev/vg_name/metadata. To find the correct block,
find the tag named MD_N in the lv tags you found in step 4

The block we need is located at offset N from start of volume.

9. Share the output of:

dd if=/dev/vg_name/metadata bs=512 skip=N count=1 iflag=direct

The output of this command should show the image-uuid.

Nir

>
> - MeLLy
>
> On Mon, Jul 4, 2016, at 11:52 PM, Fernando Fuentes wrote:
>> Nir,
>>
>> That's exactly how I did it Nir.
>> I will test tomorrow with a new Windows VM and report back.
>>
>> Regards,
>>
>> --
>> Fernando Fuentes
>> ffuen...@txweather.org
>> http://www.txweather.org
>>
>> On Mon, Jul 4, 2016, at 10:48 AM, Nir Soffer wrote:
>> > On Mon, Jul 4, 2016 at 6:43 PM, Francesco Romani 
>> > wrote:
>> > > - Original Message -
>> > >> From: "Nir Soffer" 
>> > >> To: "Fernando Fuentes" 
>> > >> Cc: "Francesco Romani" , "users" 
>> > >> Sent: Saturday, July 2, 2016 11:18:01 AM
>> > >> Subject: Re: [ovirt-users] disk not bootable
>> > >>
>> > >> On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes 
>> > >> wrote:
>> > >> > Nir,
>> > >> >
>> > >> > Ok I ran another test and this one I moved from NFS domain to iSCSI 
>> > >> > and
>> > >> > stop working than I moved it back and still unable to run... Windows 
>> > >> > VM
>> > >> > is saying "no available boot disk"
>> > >> > VM: Win7-Test
>> > >> > Host: Zeta
>> > >> > Info as requested:  http://pastebin.com/1fSi3auz
>> > >>
>> > >> We need a working xml to compare to.
>> > >
>> > > [snip expected changes]
>> > >
>> > >
>> > >>   oVirt
>> > >>   oVirt Node
>> > >>   6-5.el6.centos.11.2
>> > >> - C938F077-55E2-3E50-A694-9FCB7661FD89
>> > >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
>> > >>
>> > >> Not expected - maybe this is confusing windows?
>> > >>
>> > >> Francesco, why vm serial has changed after moving disks from one storage
>> > >> domain
>> > >> to another?
>> > >
>> > > We put in serial either
>> > > 1. the UUID Engine send to us
>> > > 2. the host UUID as returned by our getHostUUID utility function
>> > >
>> > > the latter is unlikely to change, even after this disk move.
>> >
>> > Fernando, can you describe exactly how you moved the disk?
>> >
>> > I assume that you selected the vm in the virtual machines tab, then
>> > selected
>> > disks from the sub tab, then selected move, and selected the target
>> > storage domain.
>> >
>> > Also, can you reproduce this with a new vm? (create vm with disk nfs,
>> > stop vm,
>> > move disk to iscsi, start vm).
>> >
>> > > So the first suspect in line is Engine
>> > >
>> > > Arik, do you know if Engine is indeed supposed to change the UUID in 
>> > > this flow?
>> > > That seems very surprising.
>> > >
>> > > Thanks and bests,
>> > >
>> > > --
>> > > Francesco Romani
>> > > RedHat Engineering Virtualization R & D
>> > > Phone: 8261328
>> > > IRC: fromani
>> ___
>> 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] No hosted Engine VM in portal after migrating

2016-07-10 Thread Matt . 
Or add a new cluster it seems.

2016-07-10 11:25 GMT+02:00 Yaniv Dary :
> You need to add one storage to make the import trigger.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Fri, Jul 8, 2016 at 8:43 PM, Matt .  wrote:
>>
>> By adding a new cluster the Hosted Engine was imported also...
>>
>> There seem to be some issues with changing the clusters from 3.6 to
>> 4.0 and adding new cluster to make that happen the HostedEngine was
>> added also.
>>
>> 2016-07-08 9:43 GMT+02:00 Simone Tiraboschi :
>> > On Fri, Jul 8, 2016 at 9:25 AM, Matt .  wrote:
>> >> Hi,
>> >>
>> >> I see on the engine gthe following message:
>> >>
>> >> 2016-07-08 09:24:24,986 INFO
>> >> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
>> >> (org.ovirt.thread.pool-8-thread-5) [49c1c8c1] Lock Acquired to object
>> >> 'EngineLock:{exclusiveLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a=> >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
>> >> HostedEngine=]',
>> >> sharedLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a=> >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
>> >>
>> >> The issue is that there is no entry as VM in the database.
>> >
>> > Adding Roy here.
>> >
>> >> What should I check more ?
>> >>
>> >> Thanks,
>> >>
>> >> Matt
>> >>
>> >> 2016-07-07 23:26 GMT+02:00 Matt . :
>> >>> The storage domain is there, the host-engine is just not being added,
>> >>> also not after some time waiting.
>> >>>
>> >>> 2016-07-07 14:15 GMT+02:00 Simone Tiraboschi :
>>  On Thu, Jul 7, 2016 at 1:34 PM, Matt . 
>>  wrote:
>> > Hi,
>> >
>> > I did a successfull migration to hosted engine and noticed there is
>> > no
>> > HostedEngine VM in the portal.
>> 
>>  Do you just miss the hosted-engine VM or also the whole hosted-engine
>>  storage domain?
>> 
>> > In earlier tests it showed up so I wonder if I can import it in some
>> > way so it exists in the portal.
>> >
>> > I used this migration way which earlier added the hosted engine and
>> > stayed in the portal also after restoring the old backup.
>> >
>> >
>> > http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
>> >
>> > Thanks,
>> >
>> > Matt
>> > ___
>> > 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
>> ___
>> 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] disk not bootable

2016-07-10 Thread Fernando Fuentes 
Team,

Any more ideas? :(

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

On Fri, Jul 8, 2016, at 09:36 AM, Melissa Mesler wrote:
> Michal, given what you said, then it has to be template related. We were
> able to create a new vm from scratch and move from the nfs domain to the
> iscsi domain. So where do we go from here?
> 
> On Fri, Jul 8, 2016, at 04:24 AM, Michal Skrivanek wrote:
> > 
> > > On 04 Jul 2016, at 17:43, Francesco Romani  wrote:
> > > 
> > > - Original Message -
> > >> From: "Nir Soffer" 
> > >> To: "Fernando Fuentes" 
> > >> Cc: "Francesco Romani" , "users" 
> > >> Sent: Saturday, July 2, 2016 11:18:01 AM
> > >> Subject: Re: [ovirt-users] disk not bootable
> > >> 
> > >> On Sat, Jul 2, 2016 at 1:33 AM, Fernando Fuentes 
> > >> wrote:
> > >>> Nir,
> > >>> 
> > >>> Ok I ran another test and this one I moved from NFS domain to iSCSI and
> > >>> stop working than I moved it back and still unable to run... Windows VM
> > >>> is saying "no available boot disk"
> > >>> VM: Win7-Test
> > >>> Host: Zeta
> > >>> Info as requested:  http://pastebin.com/1fSi3auz
> > >> 
> > >> We need a working xml to compare to.
> > > 
> > > [snip expected changes]
> > > 
> > > 
> > >>  oVirt
> > >>  oVirt Node
> > >>  6-5.el6.centos.11.2
> > >> - C938F077-55E2-3E50-A694-9FCB7661FD89
> > >> + 735C7A01-1F16-3CF0-AF8C-A99823E95AC0
> > >> 
> > >> Not expected - maybe this is confusing windows?
> > 
> > Nope, only specific licensing software seem to be checking this
> > 
> > >> 
> > >> Francesco, why vm serial has changed after moving disks from one storage
> > >> domain
> > >> to another?
> > > 
> > > We put in serial either
> > > 1. the UUID Engine send to us
> > > 2. the host UUID as returned by our getHostUUID utility function
> > > 
> > > the latter is unlikely to change, even after this disk move.
> > 
> > depends on which host the VM is started. It’s the host-derived ID so it’s
> > often different every time you run a VM.
> > So I suppose here it just means the VM was launched on a different host.
> > It shouldn’t be significant to the boot issue.
> > 
> > > 
> > > So the first suspect in line is Engine
> > > 
> > > Arik, do you know if Engine is indeed supposed to change the UUID in this 
> > > flow?
> > > That seems very surprising.
> > > 
> > > Thanks and bests,
> > > 
> > > -- 
> > > Francesco Romani
> > > RedHat Engineering Virtualization R & D
> > > Phone: 8261328
> > > IRC: fromani
> > > ___
> > > 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
> ___
> 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] Removing old images from glance.ovirt.org

2016-07-10 Thread Barak Korren 
Hi all,

We've recently updated many of the OS images in glance.ovirt.org
(Available as the 'ovirt-image-repository' in oVirt).

We have also slightly modified the image naming convention to include
a little more information about where the images came from. For
example we now use 'Fedora 22 Cloud Base Image v20150521 for x86_64'
rather then 'Fedora 22 Base Cloud Image'.

My question is, is anyone using/relying on the old image names in any
way? If not, we will go ahead and remove them.


-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] 3.6 -> 4.0 upgrade fails on schema refresh

2016-07-10 Thread Michal Skrivanek 


> On 06 Jul 2016, at 23:15, Matt .  wrote:
> 
> OK, due some not having done PgSQL for a long time I didn't select the
> engine DB that well.
> 
> Thanks, this is a good fix where I already noticed the same snapshot
> ID already by searching through the tables and looking what's going on
> there.
> 
> 
> 
> 2016-07-06 14:41 GMT+02:00 Matt . :
>> HI,
>> 
>> Thanks for the solution, I actually get:
>> 
>> postgres=# select vm_name, snapshots.description as snapshot_name,
>> snapshot_id from snapshots join vm_static on vm_id=vm_guid where
>> CAST(split_part(memory_volume, ',', 1) AS UUID) not in (select id from
>> storage_domain_static);
>> ERROR:  relation "snapshots" does not exist
>> LINE 1: ...ts.description as snapshot_name, snapshot_id from snapshots ..
>> 
>> 2016-07-06 12:11 GMT+02:00  :
>>> Hi Arik,
>>> 
>>> El 2016-07-06 10:27, Arik Hadas escribió:
 
 Hi,
 
 This is a bit aggressive solution to remove all snapshots with the memory.
 
 Can you confirm that a storage domain that was active while creating
 the snapshot with memory was removed from the system?
 This is something that was not covered and could lead to the reported
 issue.
>>> 
>>> Some of them were available when we did remove a storage backend, indeed.
>>> Some were newer, the problem is that I don't know which one actually failed
>>> since when this happened we were in a hurry and needed to upgrade ASAP.
>>> 
 Until we come up with a proper solution, you can use the following

tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1353219

 query to identify the exact problematic snapshots and remove them
 before upgrading:
 select vm_name, snapshots.description as snapshot_name, snapshot_id
 from snapshots join vm_static on vm_id=vm_guid where
 CAST(split_part(memory_volume, ',', 1) AS UUID) not in (select id from
 storage_domain_static);
>>> 
>>> Thanks. We have another oVirt infrastructure and I see this query is
>>> returning one row. I'll report back when we upgrade this second
>>> infrastructure and provide some details.
>>> 
>>> Regards.
>>> 
>>> 
 Regards,
 Arik
 
 - Original Message -
> 
> Hi,
> 
> We have had a similar issue when upgrading, digging into it we found out
> that this was caused by snapshots that had the "Save memory" option
> enabled. We finally ended up deleting any snapshot that had this option
> enabled and then we tried to upgrade, this time the process went smooth.
> 
> Hope this helps.
> 
> Regards.
> 
> El 2016-07-05 18:49, Matt . escribió:
>> OK some update on this.
>> 
>> Removed the db-migrate-script package and reinstalled ovirt-engine and
>> ovirt-engine-setup.
>> 
>> I still have that error and this is the loggingpart:
>> 
>> CONTEXT:  SQL statement "DROP INDEX  IF EXISTS
>> idx_vm_static_template_version_name; CREATE INDEX
>> idx_vm_static_template_version_nam$
>> PL/pgSQL function fn_db_create_index(character varying,character
>> varying,text,text) line 12 at EXECUTE statement
>> 
>> psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql:93:
>> ERROR:
>> insert or update on table "image_storage_domain_map" violates foreign
>> key constraint
>> "fk_image_storage_domain_map_storage_domain_static"
>> DETAIL:  Key (storage_domain_id)=(006552b0-cae3-4ccb-9baa-ee8c3b8e42cf)
>> is not present in table "storage_domain_static".
>> FATAL: Cannot execute sql command:
>> 
>> --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
>> 
>> 2016-07-05 19:40:29 ERROR
>> otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema
>> schema._misc:313 schema.sh: FATAL:
>> sql command:
>> 
>> --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
>> 2016-07-05 19:40:29 DEBUG otopi.context context._executeMethod:142
>> method exception
>> Traceback (most recent call last):
>>  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132,
>> in _executeMethod
>>method['method']()
>>  File
>> 
>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py",
>> line 315, in _misc
>>raise RuntimeError(_('Engine schema refresh failed'))
>> RuntimeError: Engine schema refresh failed
>> 
>> Any idea ?
>> 
>> 2016-07-05 15:25 GMT+02:00 Matt . :
>>> I just found out that the file
>>> 
>>> 04_00_0140_convert_memory_snapshots_to_disks.sql
>>> 
>>> is not located in:
>>> 
>>> /usr/share/ovirt-engine/dbscripts/upgrade/
>> ___
>> Users mailing list
>> Users@ovirt.org
>>

Re: [ovirt-users] No hosted Engine VM in portal after migrating

2016-07-10 Thread Yaniv Dary 
You need to add one storage to make the import trigger.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Fri, Jul 8, 2016 at 8:43 PM, Matt .  wrote:

> By adding a new cluster the Hosted Engine was imported also...
>
> There seem to be some issues with changing the clusters from 3.6 to
> 4.0 and adding new cluster to make that happen the HostedEngine was
> added also.
>
> 2016-07-08 9:43 GMT+02:00 Simone Tiraboschi :
> > On Fri, Jul 8, 2016 at 9:25 AM, Matt .  wrote:
> >> Hi,
> >>
> >> I see on the engine gthe following message:
> >>
> >> 2016-07-08 09:24:24,986 INFO
> >> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand]
> >> (org.ovirt.thread.pool-8-thread-5) [49c1c8c1] Lock Acquired to object
> >> 'EngineLock:{exclusiveLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a= >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>,
> >> HostedEngine=]',
> >> sharedLocks='[5576ec24-112e-4995-89f8-57e40c43cc5a= >> ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName HostedEngine>]'}'
> >>
> >> The issue is that there is no entry as VM in the database.
> >
> > Adding Roy here.
> >
> >> What should I check more ?
> >>
> >> Thanks,
> >>
> >> Matt
> >>
> >> 2016-07-07 23:26 GMT+02:00 Matt . :
> >>> The storage domain is there, the host-engine is just not being added,
> >>> also not after some time waiting.
> >>>
> >>> 2016-07-07 14:15 GMT+02:00 Simone Tiraboschi :
>  On Thu, Jul 7, 2016 at 1:34 PM, Matt . 
> wrote:
> > Hi,
> >
> > I did a successfull migration to hosted engine and noticed there is
> no
> > HostedEngine VM in the portal.
> 
>  Do you just miss the hosted-engine VM or also the whole hosted-engine
>  storage domain?
> 
> > In earlier tests it showed up so I wonder if I can import it in some
> > way so it exists in the portal.
> >
> > I used this migration way which earlier added the hosted engine and
> > stayed in the portal also after restoring the old backup.
> >
> >
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
> >
> > Thanks,
> >
> > Matt
> > ___
> > 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
> ___
> 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