Bug 1001223
Summary: | calling app-destroy on already deleted gear throws error | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Rajat Chopra <rchopra> |
Component: | Containers | Assignee: | Dan Mace <dmace> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.x | CC: | bmeng, xtian, yadu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-19 16:48:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rajat Chopra
2013-08-26 19:26:55 UTC
Its debatable whether the 'node' should return a zero exitcode on 'not found' situations. For our case here, though, its probably ok to have an warning message with a zero exitcode. The node already behaves as desired; turns out there was a regression corrected by: https://github.com/openshift/origin-server/commit/1adf4900493e378f2df567762cb11bc1e9f1fd4e Should be fixed in master. If it crops up again, be sure to attach logs. Thanks! Checked on devenv_3762, 1.Create app 2.Add "return 1" to the middle of "def oo-app-destroy" in mcollective/agent/openshift.rb 3.Restart mcollective and broker 4.Delete the app from rhc client Will meet Node execution failure here. 5.Check the app on node Should be deleted 6.Check the app on broker Should be still existed 7.Remove the change in openshift.rb 8.Restart mcollective and broker 9.Try to destroy the app again via oo-admin-ctl-app App is deleted successfully. Move bug to verified. |