*** Bug 881569 has been marked as a duplicate of this bug. ***
Created attachment 654004 [details] Unexpected error: Couldn't find Organization with ID=1
Moving out as not a blocker. Could be result of slow-running background tasks during org deletion. Waiting a few minutes, the error message did not reappear.
Clearing needinfo
@Marek - taking as I am alrady working on the same one: https://bugzilla.redhat.com/show_bug.cgi?id=885261
So I can confirm your katello-jobs service had not to be running or you just did it too fast. Sometimes org deletion can be put on hold for some time and you need to wait - the error will disappear once organization is deleted. Current organization deletion code is not good and I hesitate to implement a workaround for it as we will refactor our orchestration shortly. This looks like a Release Note for both SE and SAM releases just to wait until org is deleted.
Created attachment 666495 [details] kateloo-debug tarball
The patch was finally merged upstream, please test accordingly as it completely change the way how we dealing with orgs being deleted: https://github.com/Katello/katello/pull/1358
Moving all POST / MODIFIED bugs to ON_QA due to the new builds.
Created attachment 783747 [details] Delete ACME_Corporation # rpm -qa | grep katello katello-selinux-1.4.4-2.el6sat.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-certs-tools-1.4.2-2.el6sat.noarch katello-common-1.4.3-5.el6sam_splice.noarch katello-configure-1.4.4-2.el6sat.noarch katello-cli-common-1.4.3-4.el6sat.noarch katello-glue-elasticsearch-1.4.3-5.el6sam_splice.noarch katello-headpin-all-1.4.3-5.el6sam_splice.noarch katello-cli-1.4.3-4.el6sat.noarch katello-glue-candlepin-1.4.3-5.el6sam_splice.noarch signo-katello-0.0.10-2.el6sat.noarch katello-headpin-1.4.3-5.el6sam_splice.noarch # headpin -u admin -p admin org list -------------------------------------------------------------------------------- Organization List ID Name Label Description -------------------------------------------------------------------------------- 3 Red Hat Red_Hat 2 test test Here,if you see a newly created org has got the ID -2,3
This code appears to be to in the delivery.
Failed. Attempted to delete ACME_Corporation and got a user message that the org is scheduled to be deleted. I waited for few minkutes and attempted to create ACME_Corporation again, but it wouldn't let me do it. (UI Screenshot attached) Version tested: * candlepin-0.8.20-1.el6sam.noarch * candlepin-cert-consumer-cloud-qe-21.idm.lab.bos.redhat.com-1.0-1.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.8.20-1.el6sam.noarch * candlepin-tomcat6-0.8.20-1.el6sam.noarch * elasticsearch-0.19.9-8.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.2-2.el6sat.noarch * katello-cli-1.4.3-7.el6sat.noarch * katello-cli-common-1.4.3-7.el6sat.noarch * katello-common-1.4.3-8.el6sam_splice.noarch * katello-configure-1.4.4-2.el6sat.noarch * katello-glue-candlepin-1.4.3-8.el6sam_splice.noarch * katello-glue-elasticsearch-1.4.3-8.el6sam_splice.noarch * katello-headpin-1.4.3-8.el6sam_splice.noarch * katello-headpin-all-1.4.3-8.el6sam_splice.noarch * katello-selinux-1.4.4-2.el6sat.noarch * thumbslug-0.0.32-1.el6sam.noarch * thumbslug-selinux-0.0.32-1.el6sam.noarch
Created attachment 787455 [details] Error on trying to add ACME_Corporation after it is deleted
My patch can be considered as verified, because it works. This is different error introduced when foreign keys were implemented. Open a bug with this topic: Foreign key is preventing an org from being deleted. The error message is: 2013-08-16T14:04:01-0400: [Worker(delayed_job host:cloud-qe-21.idm.lab.bos.redhat.com pid:7267)] 1 jobs processed at 8.4682 j/s, 1 failed ... 2013-08-16T15:57:10-0400: [Worker(delayed_job host:cloud-qe-21.idm.lab.bos.redhat.com pid:7267)] OrganizationDestroyer#run failed with ActiveRecord:: +InvalidForeignKey: PGError: ERROR: update or delete on table "organizations" violates foreign key constraint "notices_organization_id_fk" on table "notices" DETAIL: Key (id)=(1) is still referenced from table "notices". : COMMIT - 0 failed attempts 2013-08-16T15:57:10-0400: [Worker(delayed_job host:cloud-qe-21.idm.lab.bos.redhat.com pid:7267)] PERMANENTLY removing OrganizationDestroyer#run because of 1 +consecutive failures. PGError: ERROR: update or delete on table "organizations" violates foreign key constraint "notices_organization_id_fk" on table "notices" DETAIL: Key (id)=(1) is still referenced from table "notices". : COMMIT
An other bug is created https://bugzilla.redhat.com/show_bug.cgi?id=1001609 to track the foreign key error.
This should be re-investigated, not sure if this is relevant due to dynflow change.
The release of Satellite 5.8 we are deprecating the support of Subscription Asset Manager. The release notes for 5.8 can be found at https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/pdf/release_notes/Red_Hat_Satellite-5.8-Release_Notes-en-US.pdf. I am therefore closing out this bug as WONTFIX. If you believe this to be an error, please feel free tor each out to either Rich Jerrido or Bryan Kearney. Thank you!