VMs attached to newly created tenant networks can no longer access outside networks via NAT.
This was working last week. We first noticed a problem when a 2nd router was created under the same project (to serve a different network). As we were doing additional testing to gather additional information on this behavior, we watched the situation deteriorate. Currently, newly created tenant networks can not use NAT.
When rebooting one of the controllers, connectivity works for those broken VMs but as soon as the rebooting controller comes back up, connectivity breaks again.
- Red Hat OpenStack Platform 16.2 (RHOSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.