Comment 1 for bug 1323965
Revision history for this message
| Sergii Golovatiuk (sgolovatiuk) wrote Re: Instances created with wrong IP range on second cluster | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
The problem is in mask you used. It overlaps the range from first and second cluster. /16 means 10.0.X.X thus you had a problem. Please use /24 instead. If you still want /16 please use second octet as distinguishing attribute. 10.0.0.0/16 and 10.X.0.0/16 should work fine.