Bug 1199903
Summary: | Cannot delete monitor (also pool and member), when deleting scalable application with openshift-routing-daemon | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Kenjiro Nakayama <knakayam> |
Component: | Unknown | Assignee: | chris alfonso <calfonso> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 2.2.0 | CC: | adellape, bleanhar, calfonso, hbrock, jialiu, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-routing-daemon-0.22.2.2-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously if the routing daemon was configured for use with F5 BIG-IP LTMĀ® and was configured to create monitors or assign an existing monitor to new pools, errors occurred while deleting a scalable application when the process attempted to delete the associated monitor. This was due to a bug in the routing daemon. This bug fix updates the routing daemon to address these issues, and as a result these errors no longer occur. Additionally, the routing daemon now reports error messages from F5 in more situations rather than generic failure messages.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-04-06 17:06:29 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
Kenjiro Nakayama
2015-03-09 08:28:34 UTC
PR opened upstream for origin-server https://github.com/openshift/origin-server/pull/6092 Verified this bug with rubygem-openshift-origin-routing-daemon-0.22.2.2-1.el6op.noarch, and PASS. After upgrade it to rubygem-openshift-origin-routing-daemon-0.22.2.2-1.el6op.noarch, the error disappeared. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0779.html |