Red Hat Bugzilla – Bug 1303796
Python cartridge doesn't stop deploy process when it failed to install packages (It is different from behavior of other cartridges)
Last modified: 2017-05-31 14:22:11 EDT
Description of problem:
- Python cartridge doesn't stop deploy process when it failed to install packages (It is different from the behavior of other packages)
Version-Release number of selected component (if applicable):
- OpenShift Online
- OpenShift Enterprise 2.x
- OpenShift origin-server
Steps to Reproduce:
1. Put *wrong* package down requirements.txt.
e.g: foo==1.1.1 (the package 'foo' doesn't exist)
2. Deploy test
$ git commit -am "package test" && git push
3. Pacakge installation failed (output the pip installation failed error), but the deploy result is "success"
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success
9765ac3..9a4a2cf master -> master
- The deploy process stopped due to the package installation failure
- Here is the proposal patch - https://github.com/openshift/origin-server/pull/6357
- However, it has been removed purposely before - https://github.com/openshift/origin-server/pull/3542
So, it might cause another side effect.
Regarding the customer case attached, it's clear that the package pybing is not longer available and in fact, the Bing API version it currently uses will be deprecated soon. So, it will be broken in the near future if it's not getting updates for that matter. There is an alternative package "py-bing-search" that may work for the customer. I just want to put it here for the record in case the customer requires further assistant in the future.
Current PR in review for merge: https://github.com/openshift/origin-server/pull/6357
Yes, I've covered with the Python cartridges 2.7 and 3.3.
Thank you for confirmation.
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.