Bug 1672937
| Summary: | [RFE] Remove OpenShift Deployment in Automate | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Loic Avenel <lavenel> |
| Component: | Automate | Assignee: | drew uhlmann <duhlmann> |
| Status: | CLOSED ERRATA | QA Contact: | Ganesh Hubale <ghubale> |
| Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | high | ||
| Version: | unspecified | CC: | duhlmann, ghubale, jprause, mkanoor, obarenbo, simaishi, smallamp, tfitzger |
| Target Milestone: | GA | Keywords: | FutureFeature |
| Target Release: | 5.11.0 | Flags: | mfeifer:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.11.0.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-12-12 13:35:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Feature | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Loic Avenel
2019-02-06 09:35:44 UTC
https://github.com/ManageIQ/manageiq-content/pull/511 https://github.com/ManageIQ/manageiq-automation_engine/pull/301 https://github.com/ManageIQ/manageiq-api/pull/560 https://github.com/ManageIQ/manageiq/pull/18515 There's additionally UI work that will be necessary. Sorry Satoe, I lied about that, the UI work I think is finished. Milan confirmed in https://github.com/ManageIQ/manageiq/pull/18515#issuecomment-469619344 Hey Ganesh, sorry, but https://github.com/ManageIQ/manageiq-automation_engine/pull/311 was merged after this got changed to POST. The idea was that after all the PRs above this got merged on upstream, we'd see what broke, and 311 is a fix for one of the issues. I guess maybe 311 should be the PR for a new bug about the original? I'm not sure of what the correct process is, in this case, sorry. 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/RHBA-2019:4199 |