Bug 1534039
| Summary: | [Embedded Ansible] Standard Output throws error if Hostname has Non-ASCII Characters | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Kedar Kulkarni <kkulkarn> | ||||
| Component: | UI - OPS | Assignee: | lgalis | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kedar Kulkarni <kkulkarn> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.9.0 | CC: | cpelland, hkataria, lavenel, mpovolny, obarenbo | ||||
| Target Milestone: | GA | Keywords: | TestOnly, ZStream | ||||
| Target Release: | 5.10.0 | Flags: | kkulkarn:
automate_bug-
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 5.10.0.0 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1568023 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-02-11 14:06:51 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: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1568023 | ||||||
| Attachments: |
|
||||||
This error is still present in latest 5.9.0.20 build. On 5.10.0.2 there were no errors on OPS UI standard output screen when I had non-ascii characters in hostname. |
Created attachment 1380553 [details] Screenshot Description of problem: Standard output of Ansible Playbook Service throws error if hostname contains special characters. Version-Release number of selected component (if applicable): 5.9.0.16 How reproducible: Believe 100% Steps to Reproduce: 1.Enable Embedded Ansible Role 2.Add repository, credentials 3.Create a Catalog and add Catalog Item of Ansible Playbook type 4.Make sure to use Non-ASCII Character in Hostname field 5.Order Service for this catalog item 6.Navigate to My Services and click on service you just ordered 7.Click on provisioning tab Actual results: See Screenshot Expected results: Should not throw errors Additional info: