Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1443641

Summary:	Unregistered external VMs should not be candidates for register once storage domain is being attached
Product:	[oVirt] ovirt-engine	Reporter:	Maor <mlipchuk>
Component:	Backend.Core	Assignee:	Maor <mlipchuk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Carlos Mestre González <cmestreg>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	amureini, bugs, mlipchuk, ratamir, stirabos, tnisan
Target Milestone:	ovirt-4.1.3	Flags:	rule-engine: ovirt-4.1+
Target Release:	4.1.3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-06 13:22:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2017-04-19 15:25:43 UTC

Description of problem:
Have a setup with external VM without disks will set the OVF_STORE disk with this VM OVF.
The user should not see this VM as part of the unregistered candidates to be registered to the setup.
The engine should filter all external entities once the storage domain is being attached.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run an external VM
2. Make sure the storage domain's OVF is being updated
3. Destroy the environment.
4. Restore the env and import and attach the storage domain
5. go to the "import VM" sub tab and check the entities for register there

Actual results:
the External VM exists in this sub tab as an entity to register

Expected results:
the External VM should be filtered out

Additional info:

Comment 3 Allon Mureinik 2017-06-20 09:58:06 UTC

All these patches are contained in the ovirt-engine-4.1.3.3 tag.

Comment 4 Carlos Mestre González 2017-06-27 13:12:36 UTC

Have some questions for verifying this:

> 1. Run an external VM
is there a consistent way to create the external vms? I've only seen them in some bugs that I've encountered some-times but not really know the flow for it.

> 3. Destroy the environment.
What is this exactly? Remove the DC, the storage domain, uninstall ovirt? 

Thanks

Comment 5 Maor 2017-06-27 19:57:18 UTC

(In reply to Carlos Mestre González from comment #4)
> Have some questions for verifying this:
> 
> > 1. Run an external VM
> is there a consistent way to create the external vms? I've only seen them in
> some bugs that I've encountered some-times but not really know the flow for
> it.

You should have running qemu process.
maybe try to use a Host on one setup and run a VM on it, then try to use that same host on another setup, that way the VM will still be running on the host and you should see an external VM on your setup.
What I've done to verify this is to run a VM on that Host and then remove that VM from the DB, so it will be external-VM

> 
> > 3. Destroy the environment.
> What is this exactly? Remove the DC, the storage domain, uninstall ovirt? 

Simply kill the engine process, and reinstall it again from scratch.

> 
> Thanks

Comment 6 Maor 2017-06-27 19:58:21 UTC

(In reply to Maor from comment #5)
> (In reply to Carlos Mestre González from comment #4)
> > Have some questions for verifying this:
> > 
> > > 1. Run an external VM
> > is there a consistent way to create the external vms? I've only seen them in
> > some bugs that I've encountered some-times but not really know the flow for
> > it.
> 
> You should have running qemu process.
> maybe try to use a Host on one setup and run a VM on it, then try to use
> that same host on another setup, that way the VM will still be running on
> the host and you should see an external VM on your setup.
> What I've done to verify this is to run a VM on that Host and then remove
> that VM from the DB, so it will be external-VM
> 
> > 
> > > 3. Destroy the environment.
> > What is this exactly? Remove the DC, the storage domain, uninstall ovirt? 
> 
> Simply kill the engine process, and reinstall it again from scratch.
> 
> > 
> > Thanks

If you need any help with verifying this, try to ping me on IRC

Comment 7 Carlos Mestre González 2017-07-03 16:13:19 UTC

tested on rhevm-4.1.3.5-0.1.el7.noarch with RHEL 7.4 hosts and using glusterfs domains