You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/04/05 15:49:41 UTC

[jira] [Commented] (MESOS-7316) Upgrading Mesos to 1.2.0 results in some information missing from the `/flags` endpoint.

    [ https://issues.apache.org/jira/browse/MESOS-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957090#comment-15957090 ] 

Adam B commented on MESOS-7316:
-------------------------------

[~bbannier], [~mcypark], can you baackport this fix to the 1.2.x branch so we can include it in 1.2.1 for the community user's upgrade scenario?

> Upgrading Mesos to 1.2.0 results in some information missing from the `/flags` endpoint.
> ----------------------------------------------------------------------------------------
>
>                 Key: MESOS-7316
>                 URL: https://issues.apache.org/jira/browse/MESOS-7316
>             Project: Mesos
>          Issue Type: Bug
>          Components: HTTP API
>    Affects Versions: 1.2.0
>            Reporter: Anand Mazumdar
>            Assignee: Benjamin Bannier
>            Priority: Critical
>              Labels: mesosphere
>             Fix For: 1.3.0
>
>
> From OSS Mesos Slack:
> I recently tried upgrading one of our Mesos clusters from 1.1.0 to 1.2.0. After doing this, it looks like the {{zk}} field on the {{/master/flags}} endpoint is no longer present. 
> This looks related to the recent {{Flags}} refactoring that was done which resulted in some flags no longer being populated since they were not part of {{master::Flags}} in {{src/master/flags.hpp}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)