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

Upgrading mesos should not (re)enable mesos master or slave #70

Open
albundy83 opened this issue Mar 18, 2016 · 1 comment
Open

Upgrading mesos should not (re)enable mesos master or slave #70

albundy83 opened this issue Mar 18, 2016 · 1 comment

Comments

@albundy83
Copy link

Hello,
I'm under debian 8 and I use official repository to install mesos (and the deb files) :
deb http://repos.mesosphere.io/debian jessie main
I have 3 mesos masters and 3 mesos slaves.
On masters, mesos slaves are not started (and must not be started), same for mesos slaves, mesos masters must not be started.
During each upgrade, I have to disable manually after the upgrade the "not installed component".
Here the log on a mesos slave for example :
....
Setting up mesos (0.27.0-0.2.190.debian81) ...
Created symlink from /etc/systemd/system/multi-user.target.wants/mesos-master.service to /lib/systemd/system/mesos-master.service.
Processing triggers for libc-bin (2.19-18+deb8u2) ...
...
So, once upgrade is done, I have to issue the following command :
systemctl disable mesos-master.service
It should not be necessary I think.
(For reference : https://issues.apache.org/jira/browse/MESOS-4605)

@albundy83
Copy link
Author

This issue join the pull request :
#65

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant