Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improper Deployment Status #49

Open
meghdeep-basu opened this issue Jun 28, 2016 · 0 comments
Open

Improper Deployment Status #49

meghdeep-basu opened this issue Jun 28, 2016 · 0 comments

Comments

@meghdeep-basu
Copy link

During deployment of the API Proxy using the apigee deploy maven plugin, we realised that one of the MPs in the env was down. The api proxy activation response shows the state as error, but still the build response is "Build Success".
From a layman point of view this is not correct, as the response of deployment is success, but when the APIX Proxy is retrieved on Edge UI, it shows Error Marks in it.
Therefore, would it be possible to read the State Parameter at the body of the activation response and based on that decide the final status of deployment. May be we can add something like "Partial Success".
Due to proprietary commitments, I can't attach the logs here, but here is the snap with masked values.

build 23-Jun-2016 22:11:27 POST https://api.enterprise.apigee.com/v1/organizations/XXX/environments/prod/apis/XXX/revisions/35/deployments
build 23-Jun-2016 22:11:27 accept: application/json
build 23-Jun-2016 22:11:27 accept-encoding: gzip
build 23-Jun-2016 22:11:27 authorization: Basic [Not shown in log]
build 23-Jun-2016 22:11:53 [INFO]
build 23-Jun-2016 22:11:53
build 23-Jun-2016 22:11:53
build 23-Jun-2016 22:11:53 Response returned by the server
build 23-Jun-2016 22:11:53 **************************
build 23-Jun-2016 22:11:53 200 OK
build 23-Jun-2016 22:11:53 accept-encoding: gzip
build 23-Jun-2016 22:11:53 content-encoding: gzip
build 23-Jun-2016 22:11:53 content-length: 457
build 23-Jun-2016 22:11:53 content-type: application/json
build 23-Jun-2016 22:11:53 date: Fri, 24 Jun 2016 02:11:53 GMT
build 23-Jun-2016 22:11:53 server: [Apigee Router]
build 23-Jun-2016 22:11:53 access-control-allow-origin: [*]
build 23-Jun-2016 22:11:53 access-control-allow-methods: [GET, PUT, POST, DELETE]
build 23-Jun-2016 22:11:53 connection: [keep-alive]
build 23-Jun-2016 22:11:53 access-control-max-age: [3628800]
build 23-Jun-2016 22:11:53 access-control-allow-headers: [origin, x-requested-with, accept]
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "aPIProxy": "XXX",
build 23-Jun-2016 22:11:53 "configuration": {
build 23-Jun-2016 22:11:53 "basePath": "/",
build 23-Jun-2016 22:11:53 "steps": []
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 "environment": "prod",
build 23-Jun-2016 22:11:53 "name": "35",
build 23-Jun-2016 22:11:53 "organization": "XXX",
build 23-Jun-2016 22:11:53 "revision": "35",
build 23-Jun-2016 22:11:53 "state": "error",
build 23-Jun-2016 22:11:53 "server": [
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "error",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "message-processor"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "XXX"
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "message-processor"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "6XXX"
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "router"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "XXX"
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "router"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "XXX"
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "router"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "XXX"
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "router"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": “XXX”
build 23-Jun-2016 22:11:53 },
build 23-Jun-2016 22:11:53 {
build 23-Jun-2016 22:11:53 "status": "deployed",
build 23-Jun-2016 22:11:53 "type": [
build 23-Jun-2016 22:11:53 "router"
build 23-Jun-2016 22:11:53 ],
build 23-Jun-2016 22:11:53 "uUID": "XXX"
build 23-Jun-2016 22:11:53 }
build 23-Jun-2016 22:11:53 ]
build 23-Jun-2016 22:11:53 }
build 23-Jun-2016 22:11:53 [INFO]
build 23-Jun-2016 22:11:53 Deployed revision is: 35
build 23-Jun-2016 22:11:53 [INFO] ------------------------------------------------------------------------
build 23-Jun-2016 22:11:53 [INFO] BUILD SUCCESS
build 23-Jun-2016 22:11:53 [INFO] ------------------------------------------------------------------------
build 23-Jun-2016 22:11:53 [INFO] Total time: 55.753 s
build 23-Jun-2016 22:11:53 [INFO] Finished at: 2016-06-23T22:11:53-04:00
build 23-Jun-2016 22:11:53 [INFO] Final Memory: 14M/170M
build 23-Jun-2016 22:11:53 [INFO] ------------------------------------------------------------------------
simple 23-Jun-2016 22:11:53 Finished task 'deploy apigee enterprise service' with result: Success
simple 23-Jun-2016 22:11:53 Starting task 'mvn clean' of type 'XXX'
simple 23-Jun-2016 22:11:53 Cleaning working directory ‘XXX’
simple 23-Jun-2016 22:11:53 Finished task 'mvn clean' with result: Success
simple 23-Jun-2016 22:11:53 Finalising the build...
simple 23-Jun-2016 22:11:53 Stopping timer.
simple 23-Jun-2016 22:11:53 Build XXX completed.
simple 23-Jun-2016 22:11:53 Finished processing deployment result Deployment of XXX on 'Prod'

@meghdeep-basu meghdeep-basu changed the title Improper Deployment Statys Improper Deployment Status Jun 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant