Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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
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: