Skip to content
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.

Move iptables configuration variables to consul #1350

Merged
merged 2 commits into from Apr 27, 2016
Merged

Move iptables configuration variables to consul #1350

merged 2 commits into from Apr 27, 2016

Conversation

ChrisAubuchon
Copy link
Contributor

@ChrisAubuchon ChrisAubuchon commented Apr 13, 2016 •
edited by ryane

  • Installs cleanly on a fresh build of most recent master branch
  • Upgrades cleanly from the most recent release
  • Updates documentation relevant to the changes

@BrianHicks
Copy link
Contributor

What are the things upgrading this would break?

@BrianHicks BrianHicks added this to the 1.1 milestone Apr 20, 2016
@ryane
Copy link
Contributor

ryane commented Apr 27, 2016

clean install on AWS

but upgrade from 1.0.3 failed on GCE.

Post-upgrade, none of the mesos-agents are registered with mesos b/c they are getting Authentication timed out. they cannot connect to the mesos leader.

curl 10.0.0.9:15050
curl: (7) Failed connect to 10.0.0.9:15050; Connection timed out

The iptables script on the control nodes do not have rules for the agents b/c there are no agents registered with the follower tag in Consul. mesos-consul cannot launch b/c there are no agents for it to run on in Mesos.

@ryane
Copy link
Contributor

ryane commented Apr 27, 2016

with 2db380d, the upgrade is successful. lgtm

@ryane ryane merged commit 92d4662 into master Apr 27, 2016
@ryane ryane deleted the feature/iptables-consul branch April 27, 2016 21:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.1
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@ChrisAubuchon @BrianHicks @ryane @metahertz