Hi Paul,

Thanks for looking into that!

I was just spinning up a VM in a Basic Zone using VMware and NFS…nothing really 
out of the ordinary.

I’m traveling today, but should be able to re-try this use case again tomorrow.

Thanks again!
Mike

On 1/11/18, 2:12 AM, "Paul Angus" <paul.an...@shapeblue.com> wrote:

    Hey Mike, were you doing anything specific/special?  I haven't yet managed 
to get the wrong IP address.
    how does the config for dhcp leases look on the VR?
    
    
    Kind regards,
    
    Paul Angus
    
    paul.an...@shapeblue.com 
    www.shapeblue.com
    53 Chandos Place, Covent Garden, London  WC2N 4HSUK
    @shapeblue
      
     
    
    
    -----Original Message-----
    From: Tutkowski, Mike [mailto:mike.tutkow...@netapp.com] 
    Sent: 11 January 2018 07:52
    To: dev@cloudstack.apache.org
    Subject: Re: IP Address Discrepancy with VMware
    
    Thanks, Paul!
    
    > On Jan 11, 2018, at 12:49 AM, Paul Angus <paul.an...@shapeblue.com> wrote:
    > 
    > I'll have a look @ mike
    > 
    > 
    > 
    > Kind regards,
    > 
    > Paul Angus
    > 
    > paul.an...@shapeblue.com
    > www.shapeblue.com
    > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
    > 
    > 
    > 
    > 
    > -----Original Message-----
    > From: Tutkowski, Mike [mailto:mike.tutkow...@netapp.com] 
    > Sent: 11 January 2018 07:31
    > To: dev@cloudstack.apache.org
    > Subject: IP Address Discrepancy with VMware
    > 
    > Hi,
    > 
    > While I was running some tests related to 4.11 tonight, I noticed the 
following discrepancy with regards to the IP address given to a VM of mine:
    > 
    > https://imgur.com/3ODXHNe
    > 
    > According to CloudStack, the IP address should be 10.117.40.28. However, 
when I run ifconfig, I get 10.117.40.115.
    > 
    > In this situation, I’m running only with VMware (no other hypervisor type 
in use) in a Basic Zone where the root disk of the VM is on NFS.
    > 
    > Anyone else able to reproduce this issue?
    > 
    > Thanks,
    > Mike
    

Reply via email to