IPs not showing up after Upgrade from 5.6.0 to 5.8.1

This was working fine in the older version, but since upgrading to 5.8.1, we do not see the IP of a VM in the table list. Clicking through to the VM itself DOES show the IP. This happens whether the VM is on or off, newly created or pre-existing.

This happens in all views, we are using vCenter.

Admin view:

Click through to VM:
image

Cloud view:

image

Click through to VM:
image

Hello @rmurciano,

Could you share the output of onevm list -x?

<VM>
  <ID>2755</ID>
  <UID>117</UID>
  <GID>103</GID>
  <UNAME>a******@*****.com</UNAME>
  <GNAME>Support</GNAME>
  <NAME>LUNDIN CLOUD 04.30.2019</NAME>
  <LAST_POLL>1556636570</LAST_POLL>
  <STATE>3</STATE>
  <LCM_STATE>3</LCM_STATE>
  <RESCHED>0</RESCHED>
  <STIME>1556633213</STIME>
  <ETIME>0</ETIME>
  <DEPLOY_ID>vm-49201</DEPLOY_ID>
  <TEMPLATE>
    <CPU>2</CPU>
    <MEMORY>4096</MEMORY>
    <DISK>
      <DISK_ID><![CDATA[0]]></DISK_ID>
      <DATASTORE><![CDATA[R*****-San-Clouds-02 [vcenter-02.*******.com - P*******s] (IMG)]]></DATASTORE>
      <DATASTORE_ID><![CDATA[108]]></DATASTORE_ID>
      <IMAGE><![CDATA[Template_X07_2018-06-11 - R*****-San-Clouds-02 [template 63]]]></IMAGE>
      <IMAGE_ID><![CDATA[64]]></IMAGE_ID>
      <SIZE><![CDATA[61440]]></SIZE>
      <TYPE><![CDATA[FILE]]></TYPE>
      <CLONE><![CDATA[YES]]></CLONE>
      <CLONE_TARGET><![CDATA[SYSTEM]]></CLONE_TARGET>
      <LN_TARGET><![CDATA[NONE]]></LN_TARGET>
      <DISK_SNAPSHOT_TOTAL_SIZE><![CDATA[0]]></DISK_SNAPSHOT_TOTAL_SIZE>
    </DISK>
    <DISK>
      <DISK_ID><![CDATA[1]]></DISK_ID>
      <DATASTORE><![CDATA[R*****-San-Clouds-02 [vcenter-02.*******.com - P*********s] (IMG)]]></DATASTORE>
      <DATASTORE_ID><![CDATA[108]]></DATASTORE_ID>
      <IMAGE><![CDATA[Template_X07_2018-06-11_1 - R*******-San-Clouds-02 [template 63]]]></IMAGE>
      <IMAGE_ID><![CDATA[65]]></IMAGE_ID>
      <SIZE><![CDATA[512000]]></SIZE>
      <TYPE><![CDATA[FILE]]></TYPE>
      <CLONE><![CDATA[YES]]></CLONE>
      <CLONE_TARGET><![CDATA[SYSTEM]]></CLONE_TARGET>
      <LN_TARGET><![CDATA[NONE]]></LN_TARGET>
      <DISK_SNAPSHOT_TOTAL_SIZE><![CDATA[0]]></DISK_SNAPSHOT_TOTAL_SIZE>
    </DISK>
    <NIC>
      <MAC><![CDATA[02:00:35:3c:18:94]]></MAC>
      <NETWORK><![CDATA[240]]></NETWORK>
      <NETWORK_ID><![CDATA[4]]></NETWORK_ID>
      <NIC_ID><![CDATA[0]]></NIC_ID>
      <SECURITY_GROUPS><![CDATA[0]]></SECURITY_GROUPS>
    </NIC>
    <GRAPHICS>
      <LISTEN><![CDATA[0.0.0.0]]></LISTEN>
      <PORT><![CDATA[8655]]></PORT>
      <TYPE><![CDATA[VNC]]></TYPE>
    </GRAPHICS>
    <AUTOMATIC_REQUIREMENTS><![CDATA[(CLUSTER_ID = 106) & !(PUBLIC_CLOUD = YES)]]></AUTOMATIC_REQUIREMENTS>
    <AUTOMATIC_DS_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 106)]]></AUTOMATIC_DS_REQUIREMENTS>
    <AUTOMATIC_NIC_REQUIREMENTS><![CDATA[("CLUSTERS/ID" @> 106)]]></AUTOMATIC_NIC_REQUIREMENTS>
  </TEMPLATE>
  <MONITORING>
    <CPU><![CDATA[102.96]]></CPU>
    <MEMORY><![CDATA[4240384]]></MEMORY>
    <STATE><![CDATA[a]]></STATE>
  </MONITORING>
  <USER_TEMPLATE>
    <SCHED_REQUIREMENTS><![CDATA[ID="5" | CLUSTER_ID="106"]]></SCHED_REQUIREMENTS>
    <SCHED_DS_REQUIREMENTS><![CDATA[ID="104" | ID="105"]]></SCHED_DS_REQUIREMENTS>
  </USER_TEMPLATE>
  <HISTORY_RECORDS>
    <HISTORY>
      <OID>2755</OID>
      <SEQ>0</SEQ>
      <HOSTNAME><![CDATA[R******-Colo]]></HOSTNAME>
      <HID>5</HID>
      <CID>106</CID>
      <DS_ID>104</DS_ID>
      <ACTION><![CDATA[0]]></ACTION>
    </HISTORY>
  </HISTORY_RECORDS>
</VM>

This is just an excerpt from one VM from the list, but it does list all of them in the output

It seems that the VM you take as excerpt does not have an IP address. Could you check the type of the AR which owns the lease used by the VM? It is Ethernet type?

Hi, yes, the AR ID assigned to this VM (and most VMs) is 0, and here are the details for that AR:

Thanks

Which hypervisor are you using? vCenter?

Correct, we are using vCenter

We are having this same issue. just as rmurcianoRaul

Are there any updates on this?

Kind Regards,
Jeremy

Hello @jmccourt and @rmurciano,

I forgot to update the thread, there was an issue with some changes in the XMLRPC API (https://github.com/OpenNebula/one/issues/3308)

A workaround was included in ONE 5.8.2, you can find the documentation here: