Bug 1264312
| Summary: | Deprecation warning when initializing database | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Milan Falešník <mfalesni> |
| Component: | Appliance | Assignee: | Nick Carboni <ncarboni> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.5.0 | CC: | abellott, jhardy, mfeifer, ncarboni, obarenbo, tcarlin |
| Target Milestone: | GA | ||
| Target Release: | 5.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.5.0.8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-08 13:31:17 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
Milan Falešník
2015-09-18 07:16:38 UTC
*** Bug 1270595 has been marked as a duplicate of this bug. *** New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/0ebf39247ff556c726f7683539f16b24a968422f commit 0ebf39247ff556c726f7683539f16b24a968422f Author: Nick Carboni <ncarboni> AuthorDate: Tue Oct 20 09:47:38 2015 -0400 Commit: Nick Carboni <ncarboni> CommitDate: Tue Oct 20 09:47:38 2015 -0400 Using .remove_connection to remove test connection from the pool This removes a deprecation warning and also corrects the behavior as the hash returned from .connection_pools has a connection spec as the key rather than the owner class name, so the previous implementation was never deleting the connection anyway. https://bugzilla.redhat.com/show_bug.cgi?id=1264312 gems/pending/appliance_console/database_configuration.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) The warning no longer show up in 5.5.0.9 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://access.redhat.com/errata/RHSA-2015:2551 |