[DCOS_OSS-2162] Enable Mesos Modules to accept ZooKeeper configuration stored in files. Created: 13/Feb/18  Updated: 09/Nov/18  Resolved: 13/Mar/18

Status: Resolved
Project: DC/OS
Component/s: mesos
Affects Version/s: DC/OS 1.11.0, DC/OS 1.12
Fix Version/s: DC/OS 1.11.1, DC/OS 1.12.0

Type: Bug Priority: Medium
Reporter: Alexander Rojas (Inactive) Assignee: Alexander Rojas (Inactive)
Resolution: Done  
Labels: cs_updated_fixVersion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Team: DELETE Security Team
Sprint: Core Sprint 74, Security Team Sprint 24, Security Team Sprint 25, Security Team Sprint 26, Security Team Sprint 27, Security Team Sprint 28, Security Team Sprint 29


ZooKeeper configuration is passed to the Mesos modules as the environment variables MESOS_ZK and MESOS_MASTER for masters and agents respectively. This variables expect ZooKeeper configuration to be stored in the environment variable following the pattern zk://user:password@zk1:port,zk2:port. However, mesos has always allowed this configuration to be stored in files.

With MESOS-8413 an issue was resolved in which the contents of the files were shown instead of the path of the file, thus preventing accidental leak of ZooKeeper credentials.

While the issue of Mesos is fixed, using ZooKeeper file based configuration cannot yet be used since the mesos-modules do not yet support this feature.

Comment by Alexander Rojas (Inactive) [ 14/Feb/18 ]

PRs for master:

Comment by Alexander Rojas (Inactive) [ 14/Feb/18 ]

PRs for 1.11:

Comment by Senthil Kumaran (Inactive) [ 14/Feb/18 ]

Hello Alexander Rojas - Is this determined to be included in 1.11.0-GA ? 

Comment by Alexander Rojas (Inactive) [ 15/Feb/18 ]

Senthil Kumaran I doubt so, It was originally planned to be released in 1.12, then we wanted to backport it to 1.11, however it was never considered a blocker and it depends on a mesos bump which as of yesterday evening GMT+1 time hadn't happened.

Comment by Catherine Southard [ 04/Sep/18 ]

Updating the fixVersion from 1.12 to 1.12.0 since the ticket has been marked as Resolved - Done

Generated at Wed May 18 08:17:40 CDT 2022 using JIRA 7.8.4#78004-sha1:5704c55c9196a87d91490cbb295eb482fa3e65cf.