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

DCOS CLI VERSION Issue to Cosmos

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: DC/OS 1.10.0
    • Component/s: dcos-cli
    • Labels:
      None

      Description

      there is a regress on `testing/master` caught by our SI tests... this is an issue I was able to track back a few weeks ago (found comments in slack from jun 23 timefrawe): https://mesosphere.slack.com/archives/C0PQL46QJ/p1499708240150092

      Jesus says it will be fixed in the next CLI release.. however all of our shakedown SI tests are broken until we resolve this. The issue manifests with the following error:

      ┍┈┈ ✕: tests/system/test_chronos.py::test_job 
      ┊ error: /Users/kensipe/.pyenv/versions/3.5.3/lib/python3.5/site-packages/dcos/packagemanager.py:42: dcos.errors.DCOSException: Item header 'Accept' deemed invalid by rule: Media type was [application/vnd.dcos.package.describe-response+json;charset=utf-8;version=v1] but should be one of [application/vnd.dcos.package.describe-response+json;charset=utf-8;version=v3, application/vnd.dcos.package.describe-response+json;charset=utf-8;version=v2]

      This issue is shakedown 1.4.3 uses 0.4.16 and it doesn't work with this version of DCOS.   I'm not sure another the release of  new CLI is the right fix. 

        Attachments

          Activity

            People

            • Assignee:
              klueska Kevin Klues (Inactive)
              Reporter:
              ken Ken Sipe (Inactive)
              Watchers:
              Cathy Daw, José Armando García Sancio (Inactive), Ken Sipe (Inactive), Kevin Klues (Inactive), Scott Schneider, Senthil Kumaran (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.