further once I determine what port a troubled instance is using I can fix it with:
neutron port-update <port-id> --device-id='' nova interface-attach --port-id <port-id> <instance-id> I don't want to do this for all ports and most are OK but there are about 100 in the working but invisible state. I could iterate through all active ports and for each look up if the device-id is and nova instance and if that instace reports correctly or not then fix it if need, but there must be a *much* simpler way to do this directly in the database. -Jon On Wed, Jan 15, 2014 at 10:08 AM, Jonathan Proulx <[email protected]> wrote: > How does the nova api map fixed-ips from neutron to running instances? > I've been poking around the nova database but cant seem to guess > where it is. > > My issue is that after upgrading to Havana *some* instances no longer > show their network and fixed-ip in the output of 'nova' cli commands > or in the horizon dashboard, though others do show up properly. > > The neutron ports still exist as shown in neutron ports-list. The > instances also still have network and function properly, but it's > difficult for my users to pragmatically determine what IP their system > has. > > I suspect if I knew what to mangle I could just iterate through the > existing neutron ports (which correctly show the instance uuid they > are associated with) and stuff the relation in the right place > somewhere else and all would be well. If someone could point me in > the right direction I'd be much obliged. > > Thanks, > -Jon _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
