Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Version-Release number of selected component (if applicable):
1.4.2-1.git.837.d2ca1b8.el6
How reproducible:
Steps to Reproduce:
1. Create org with initial env "Library"
2.
3.
Actual results:
ERROR: update or delete on table "organizations" violates foreign key constraint "environments_organization_id_fk" on table "environments" DETAIL: Key (id)=(44) is still referenced from table "environments". (PGError)
Expected results:
Something about name already taken or "Library is not a valid environment name".
Additional info:
Comment 1RHEL Program Management
2013-09-17 04:23:06 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I was able to reproduce. I get this error:
[FATAL 2013-10-10 10:33:45 app]
| PG::ForeignKeyViolation (ERROR: update or delete on table "organizations" violates foreign key constraint "environments_organization_id_fk" on table "environments"
| DETAIL: Key (id)=(27) is still referenced from table "environments".
| ):
| app/models/glue.rb:93:in `destroy'
| app/controllers/organizations_controller.rb:130:in `ensure in create'
| app/controllers/organizations_controller.rb:130:in `create'
| app/lib/util/thread_session.rb:110:in `thread_locals'
| config/initializers/quiet_paths.rb:11:in `call_with_quiet'
| lib/katello/middleware/log_request_uuid.rb:22:in `call'
| app/controllers/organizations_controller.rb:108:in `create'
|
I've opened a PR to address this:
https://github.com/Katello/katello/pull/3156
katello SHA 6e204be06eb836faf2b59139ec09b8847b842b59
983994: Fixing organization create with bad environment
Bug where organization was not getting deleted due to the library not being
deletable. The library is only deletable if the org is being destroyed (and has
a deletion task), therefore this was trigging a foreign key error.