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

[ipam] misleading status when in virgin state #787

Closed
rade opened this issue May 28, 2015 · 0 comments
Closed

[ipam] misleading status when in virgin state #787

rade opened this issue May 28, 2015 · 0 comments
Assignees
@bboreham
Labels
bug
Milestone
0.11.1

Comments

@rade
Copy link
Member

rade commented May 28, 2015

When no IP address allocation requests have been made yet, the weave status output shows something like

Allocator subnet 10.0.0.0/16
Awaiting consensus: Nodes known: 0, Quorum size: 1

which does rather convey a sense of something being not quite right.

This alarmed and mislead at least one user - see #786.
@rade rade added the chore label May 28, 2015
@rade rade added this to the next milestone May 28, 2015
@rade rade added bug and removed chore labels May 29, 2015
@rade rade modified the milestones: 0.11.1, next May 29, 2015
@bboreham bboreham mentioned this issue May 29, 2015
Merged
@bboreham bboreham self-assigned this May 29, 2015
@rade rade closed this as completed in 3332f94 Jun 1, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bboreham bboreham

Labels
bug
Projects
None yet
Milestone
0.11.1
Development

No branches or pull requests
2 participants
@rade @bboreham