| Summary: | Orchestration template : Adding a VNF template shows error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Shveta <sshveta> | ||||
| Component: | Providers | Assignee: | Ladislav Smola <lsmola> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Shveta <sshveta> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.7.0 | CC: | cpelland, hkataria, jfrey, jhardy, mpovolny, obarenbo, sshveta | ||||
| Target Milestone: | GA | ||||||
| Target Release: | cfme-future | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | stack | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-10-02 14:29:48 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | Bug | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Ladas, Looks like a back-end issue, can you please take a look. Let me know if you have questions. Thanks, ~Harpreet That behavior is expected, for vnf template, you need a provider that supports the service. Which is right now a tacker service in OpenStack. I think in that case , proper validation message should be shown instead of exception. Like "The provider does not support this service" Yeah it would deserve a better exception, stating the name of a needed service. right now it shows exception it got from Fog Shveta, after reviewing this, looks to me the message is ok. ServiceNotAvailable is what it should say. It would not be good to modify that generic code to print a specific message. Can we turn this into documentation BZ, to state VNF template and stack need OpenStack Tacker service? Sure .. can be converted to a doc BZ. Dear customer, The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. If you have any concerns about this, please let us know. Thanks and regards! Dear customer, The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. If you have any concerns about this, please let us know. Thanks and regards! |
Created attachment 1214474 [details] vnf exception Description of problem: Version-Release number of selected component (if applicable): 5.7.0.7-beta1.20161025153249_9376fbd How reproducible: Steps to Reproduce: 1. Orchestration template - Add a VNF Template 2. Fill some data and add 3. Actual results: Expected results: Additional info: