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.

Bug 1682992

Summary: Blueprint configuration file (.toml) cannot get deleted
Product: Red Hat Enterprise Linux 8 Reporter: Xiaofeng Wang <xiaofwan>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact: Vladimír Slávik <vslavik>
Priority: medium    
Version: 8.0CC: atodorov, tbowling, toneata
Target Milestone: rcKeywords: ZStream
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-28.14.23-7.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1714103 (view as bug list) Environment:
Last Closed: 2019-06-18 17:19:59 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: 1714103    

Description Xiaofeng Wang 2019-02-26 03:36:22 UTC
Description of problem:
After deleted blueprint from UI, the configuration file in /var/lib/lorax/composer/blueprints/git/workspace/master/ folder cannot get deleted accordingly.


How reproducible:
100%

Steps to Reproduce:
1. Create a blueprint with name "myblueprint" from cockpit-composer UI.
2. Check for "myblueprint.toml" file existing in folder /var/lib/lorax/composer/blueprints/git/workspace/master/
2. Delete blueprint created in step 1 from UI.
3. Check for "myblueprint.toml" file in folder /var/lib/lorax/composer/blueprints/git/workspace/master/

Actual results:
"myblueprint.toml" should be removed from master folder.

Expected results:
"myblueprint.toml" still exists.

Comment 2 Brian Lane 2019-03-01 21:39:17 UTC
https://github.com/weldr/lorax/pull/626

Comment 6 Alexander Todorov 2019-06-10 20:36:21 UTC
verified with lorax-composer-28.14.23-7.el8_0.x86_64

Comment 8 errata-xmlrpc 2019-06-18 17:19:59 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/RHBA-2019:1520