Bug 1696415

Summary: Blueprints with " " spaces in the name cause failures
Product: Red Hat Enterprise Linux 8 Reporter: Kyle Walker <kwalker>
Component: cockpit-composerAssignee: jgiardin <jgiardin>
Status: CLOSED ERRATA QA Contact: Xiaofeng Wang <xiaofwan>
Severity: high Docs Contact: Eliane Ramos Pereira <elpereir>
Priority: unspecified    
Version: 8.0CC: atodorov, elpereir, jrusz, mpitt
Target Milestone: rcKeywords: Rebase
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1775106 (view as bug list) Environment:
Last Closed: 2019-11-05 20:43:35 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:
Bug Depends On:    
Bug Blocks: 1775106    

Description Kyle Walker 2019-04-04 19:46:22 UTC
Description of problem:
 When creating blueprints with " " spaces in the name, attempts to access that blueprint result in a blank screen and lorax-composer returning the following in the system logs:

    lorax-composer[<pid>]: 2019-04-04 15:00:33,849: (v0_blueprints_depsolve) No commits for Name-with-Spaces.toml on the master branch.

Stopping the cockpit service results in the blueprint disappearing. It seems that the blueprint is never actually created on the lorax-composer side, but cockpit-composer doesn't recognize that the image was not created.


Version-Release number of selected component (if applicable):
    cockpit-composer-0.2.0-1.el8


How reproducible:
    Easily

Steps to Reproduce:
1. Navigate to https://<hostname>:9090/welder/
2. Click "Create Blueprint"
3. Name the Blueprint "Name with Spaces"
4. Click "Create"
5. Click on the Blueprint now created

Actual results:
 A blank screen is displayed

Expected results:
 An error indicating that a name cannot have spaces is returned, or the blueprint is created with spaces.

Additional info:

Comment 1 Martin Pitt 2019-07-31 11:02:57 UTC
This was fixed in cockpit-composer 3 with https://github.com/weldr/cockpit-composer/commit/9258d8404ac41d

Comment 5 errata-xmlrpc 2019-11-05 20:43:35 UTC
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/RHEA-2019:3333