Uploaded image for project: 'DC/OS'
  1. DC/OS
  2. DCOS_OSS-720

Cryptographic Cluster ID is longer than ~50chars

    Details

    • Sprint:
      Networking Team 1.9 Sprint 8

      Description

      Hi,
      we're having some issues with the Mesos Zone Exposing ( https://docs.mesosphere.com/1.8/usage/service-discovery/mesos-dns/expose-mesos-zone/ ).

      We did a fresh install of a DC/OS 1.8.8 cluster on CentOS 7.3.1611 , with 3x master and 3x agents.

      The cryptographic cluster ID we obtained was ~80 chars:

      kdz59xxxz66s7579zi8zp3feudz59xenpzz59xeukdz59xjq76954jeqyapp7ykwdtblo4xxz6669x77

      and this caused issues because the obtained zone name was too long.

      Since we needed the cluster operational, we reinstalled the masters (keeping the agents down) using the same generated bootstrap configuration (this didn't cause any troubles in our previous experiments using 1.8.7).

      Now the Cryptographic Cluster ID is even longer:

      dww69x7776955579zwmtow8xz66o6a8xz6669x77qmz59xxxz66wkqxxz6669x77n5z59xmp76955lhg7695499xz6669x77

      Here is the /navstar_key binary found in http://{master-ip}/exhibitor/ - Config:

      7b 22 70 75 62 6c 69 63 22 3a 22 5c 75 30 30 31 64 29 ef bf bd ef bf bd ef bf bd 5c 75 30 30 31 37 5c 75 30 30 31 38 50 ef bf bd 5c 75 30 30 30 66 60 ef bf bd ef bf bd 72 ef bf bd ef bf bd 45 39 ef bf bd ef bf bd 5c 75 30 30 31 36 ef bf bd 6d ef bf bd cb 86 ef bf bd 7f ef bf bd ef bf bd 22 2c 22 73 65 63 72 65 74 22 3a 22 62 ef bf bd ef bf bd ef bf bd 37 ef bf bd ef bf bd 49 5c 75 30 30 31 37 ef bf bd 68 5c 75 30 30 30 36 ef bf bd cb 8d ef bf bd 3d 4a 69 ef bf bd 7a ef bf bd 78 ef bf bd 37 49 5f ef bf bd 69 61 5c 75 30 30 31 66 4e 5c 75 30 30 31 64 29 ef bf bd ef bf bd ef bf bd 5c 75 30 30 31 37 5c 75 30 30 31 38 50 ef bf bd 5c 75 30 30 30 66 60 ef bf bd ef bf bd 72 ef bf bd ef bf bd 45 39 ef bf bd ef bf bd 5c 75 30 30 31 36 ef bf bd 6d ef bf bd cb 86 ef bf bd 7f ef bf bd ef bf bd 22 7d

       

      I've attached the payload of http://localhost:62080/lashup/key (lashup-key.json) and http://localhost:62080/lashup/kv/navstar/key (lashup-kv-navstar-key.json) from one of the masters.

      I'm available for further debugging, if needed.
      Marco

        Attachments

          Activity

            People

            • Assignee:
              dgoel Deepak Goel
              Reporter:
              marco.reni Marco Reni
              Team:
              DELETE Networking Team
              Watchers:
              Adam Bordelon (Inactive), Albert Strasheim (Inactive), Deepak Goel, Jeremy Lingmann (Inactive), Marco Reni, Nicholas Sun (Inactive)
            • Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your JIRA administrators.