Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

[ipam][docs] document prohibition to manually allocate in ipam range #681

Closed
rade opened this issue May 17, 2015 · 1 comment
Closed

[ipam][docs] document prohibition to manually allocate in ipam range #681

rade opened this issue May 17, 2015 · 1 comment

Comments

@rade
Copy link
Member

rade commented May 17, 2015

AFAIK bad things can happen when a user manually assigns an IP in the range given to IPAM, until we address #598. The docs do not mention this prohibition. They should. And they should also state what happens when a user doesn't follow it. (I'm guessing the IP might get allocated by IPAM, but can any other badness occur? some assertions getting triggered?)

@bboreham
Copy link
Contributor

The allocator isn't told about this address on first usage, so cannot trigger any assertions at that time. However, if you restart weave, then the script will try to claim that address, and you can get a message like Unable to claim IP address 10.2.1.5: Claimed address 10.2.1.5 is already owned by 4b9f69c5a48b

Raised #687 to inform the user straight away.

rade added a commit that referenced this issue May 18, 2015
Expand documentation of 'weave launch' parameters for IPAM

Closes #669 and #681.
@rade rade closed this as completed May 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants