yahoo-eng-team team mailing list archive

[Manish <manish.upadhyay@xxxxxxx>]

To be more specific. We have created 2 networks (public, private) public
is external network. If we launch any VM in public network vm are
getting launched and getting IP's and ping able however if we launch a
VM in private network using router with public netwotk and launch a VM
it is getting private ip assigned and associate a floating up to it.
When we try to ping floating ip it says "destination host not reachable"
upon further checking when we login to vm using console and do "ip addr
list" instance does not get a private ip. All the settings are similar
like we did in Liberty and there it works fine but here it's giving
problem.

** Changed in: neutron
       Status: Invalid => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1591048

Title:
  VM in self Service Networks aren't getting IP

Status in neutron:
  In Progress

Bug description:
  Hello Team,

  I have setup openstack mitaka distribution on RHEL 7 box. I setup One
  Controller node and one compute node with Networking 2 option (Self
  Service Networks). I can spin up VM in both subnets but VM in private
  self-service network is not getting IP assigned where as VM in
  provider networks are getting IP . Is this kind of bug in Mitaka
  version.

  I had setup openstack-liberty also where VM's in self service networks
  are getting IP's.

  I found i am not the only one who coming across this issue.
  http://stackoverflow.com/questions/37426821/why-the-vm-in-selfservice-
  network-can-not-get-ip

  Thanks,
  Rajiv Sharma

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1591048/+subscriptions