[ https://issues.apache.org/jira/browse/MESOS-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201456#comment-15201456 ]
Grégoire Bellon-Gervais commented on MESOS-4605: ------------------------------------------------ Just for your information, I have created the following issue : https://github.com/mesosphere/mesos-deb-packaging/issues/70 Thanks for your help. > Upgrading mesos should not (re)enable mesos master or slave > ----------------------------------------------------------- > > Key: MESOS-4605 > URL: https://issues.apache.org/jira/browse/MESOS-4605 > Project: Mesos > Issue Type: Bug > Components: general > Affects Versions: 0.27.0 > Environment: debian8 > Reporter: Grégoire Bellon-Gervais > Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)