[
https://issues.apache.org/jira/browse/MESOS-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939753#comment-15939753
]
Avinash Sridharan edited comment on MESOS-7281 at 3/24/17 4:00 AM:
-------------------------------------------------------------------
[~mcypark] is this because of the multi-role changes. I am assuming it won't
effect 1.2 ?
Nevermind this is only on the master.
was (Author: [email protected]):
[~mcypark] is this because of the multi-role changes. I am assuming it won't
effect 1.2 ?
> Backwards incompatible UpdateFrameworkMessage handling
> ------------------------------------------------------
>
> Key: MESOS-7281
> URL: https://issues.apache.org/jira/browse/MESOS-7281
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Reporter: Ilya Pronin
> Assignee: Ilya Pronin
> Priority: Blocker
>
> Patch in [r/57108|https://reviews.apache.org/r/57108/] introduced framework
> info updates. Agents are using a new {{framework_info}} field without
> checking that it's present. If a patched agent is used with not patched
> master it will get a default-initialized {{framework_info}}. This will cause
> agent failures later. E.g abort on framework ID validation when it tries to
> launch a new task for the updated framework.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
