You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Further, when copying the Active Framework ID manually out of the Mesos UI and attempting to delete the framework using that ID via the API, this fails as the framework corresponding to the ID is reported as 'not found'.
curl -X DELETE -sku username:password https://<my-mantl-control-01/api/1/frameworks/{My_Framework_ID} Cloud not shutdown framework {ID}: 400 No framework found with specified ID
Is this a real issue, or user error in some way?
I'm running Mantl 1.1.0 on Openstack.
The text was updated successfully, but these errors were encountered:
can you check the stderr logs in mantl-api while you run curl -sku username:password https://<my-mantl-control-01/api/1/frameworks? assuming you are in debug mode (the default until mantl/mantl#1531), you should see a line that looks like this: GET http://mantl-control-01:15050/master/state.json. can you check to see if the host in that line matches the leader that you see in the mesos UI (labeled Server on the left sidebar of the mesos ui home page)?
you may have to translate between hostname and ip (mantl-api will report the hostname but mesos ui will report the ip addr).
When cleaning up a Cassandra un-install, the framework ID in Mesos is required.
But, using the Mantl-API, an empty JSON is returned, though I can see four active frameworks in the Mesos UI.
curl -sku username:password https://<my-mantl-control-01/api/1/frameworks
Further, when copying the Active Framework ID manually out of the Mesos UI and attempting to delete the framework using that ID via the API, this fails as the framework corresponding to the ID is reported as 'not found'.
curl -X DELETE -sku username:password https://<my-mantl-control-01/api/1/frameworks/{My_Framework_ID}
Cloud not shutdown framework {ID}: 400 No framework found with specified ID
Is this a real issue, or user error in some way?
I'm running Mantl 1.1.0 on Openstack.
The text was updated successfully, but these errors were encountered: