Bug 1810122 - [RHV] VM ip address is not displayed in CFME UI
Summary: [RHV] VM ip address is not displayed in CFME UI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: GA
: cfme-future
Assignee: Roberto Ciatti
QA Contact: Ilanit Stein
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1811523
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-04 15:18 UTC by Ilanit Stein
Modified: 2020-05-27 13:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-27 09:10:14 UTC
Category: Bug
Cloudforms Team: RHEVM
Target Upstream Version:
Embargoed:
istein: needinfo+


Attachments (Terms of Use)

Description Ilanit Stein 2020-03-04 15:18:16 UTC
Description of problem:
After creating a VM in RHV, and have it's IP address displayed in RHV UI,
CFME for long minutes (at least) do not display it's ip addresses in the VM page.

This is affecting v2v, since when we configure a conversion host VM from RHV,
it uses the VM's ip address reported by CFME, and if this is missing it can fail the conversion host functionality.

Version-Release number of selected component (if applicable):
CFME-5.11.4.1
RHV-4.3.7

How reproducible:
Happened for several different VMs on the same RHV.

Additional info:
VM refresh makes the ip addresses visible on VM page.

Comment 2 Adam Grare 2020-03-05 13:43:04 UTC
> CFME for long minutes (at least) do not display it's ip addresses in the VM page.

Aprox how long does it take?  I assume it is less about the time and more about when a refresh runs.

Is it only visible after a full refresh or just the next targeted refresh?  I assume the VM doesn't have an IP address immediately upon creation so is it something that isn't available when we first discover the VM?  At what point is the IP address visible on the underlying RHV system?

Do you have any logs?  We need the evm.log for the system with the ems_inventory role and the vm name and times that this happened to start looking at this.

Comment 10 Ilanit Stein 2020-03-08 11:12:49 UTC
Martin, Roberto,

Thanks for your inputs.
We have a separate bug for v2v:
Bug 1810135 - [v2v] Add a check that conversion host VM has least one IP address in the inventory
which will fail the v2v configure conversion host VM, in case VM has no ip address in the CFME inventory.

Fabien,
Can we expand this v2v bug, to not just fail, if the VM has no ip address,
but also to run VM refresh VM?

Thanks.

Comment 11 Fabien Dupont 2020-03-08 14:32:53 UTC
The current implementation of the conversion host configuration is synchronous, so waiting for the targeted refresh task would require a big change in ConversionHost class.
Also, what would be the limit otherwise? How many times should it check and re-queue a targeted refresh? Potentially, the IP is not reported by the guest-agent, and that's not an IMS thing.
All in al, I'm not sure it's an IMS problem. Users should ensure that the IP address is reported in the CloudForms inventory, before configuring the VM as a conversion host.

Comment 12 Ilanit Stein 2020-03-09 06:39:53 UTC
This bug has been marked as blocked by this RHV RFE:
Bug 1811523 - [RFE] Add audit log message when VM information (like IP address) changes

Comment 13 Fabien Dupont 2020-03-09 07:03:53 UTC
Lowering severity to medium and priority to low. Also moving the target release to cfme-future.
There's an error generated when the VM IP is not available, and we add a note in the IMS Guide.
And the blocking BZ (Bug 1811523) is unlikely to be fixed on the short term.


Note You need to log in before you can comment on or make changes to this bug.