Created attachment 1030740 [details] Failed task info Description of problem: Organization delete failed Version-Release number of selected component (if applicable): Sat 6.1 GA Snap 5 How reproducible: Always Steps to Reproduce: 1. Create an Org 2. Create Lifecycle enviroments DEV,QE 3. Importing Red Hat Manifest (containing Employee SKU) 4. Attempt to delete the Org in UI Actual results: Failed (see foreman-debug) Expected results: Organization should be deleted without errors Additional info: Failed task info attached Foreman debug attached
It happened an other time for me - this time error is different - attaching newerror.log
Created attachment 1030745 [details] newerror.log
Created redmine issue http://projects.theforeman.org/issues/10655 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/10655 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|63bf81f35261b658832b18e46a9bca7fa35a8ed3.
Something isn't getting cleaned up in Candlepin: 1) run this demo script that creates orgs+products: http://file.rdu.redhat.com/~mmccune/s6-demo.bash 2) delete the 'Demo Org Auto' via the UI 3) Re-run above script and get: Could not create the repository: Task 2883a776-8999-4d97-b7ce-f25cb26cf93a: Katello::Errors::CandlepinError: Runtime Error ERROR: duplicate key value violates unique constraint "cp_content_label_key" Detail: Key (label)=(The_Demo_Org_Auto_Demo_Product_A_Demo_Internal_Product) already exists. at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse:2,157
NEW PR: https://github.com/Katello/katello/pull/5272/
VERIFIED: rpm -qa | grep foreman ruby193-rubygem-foreman_discovery-2.0.0.15-1.el7sat.noarch foreman-libvirt-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch foreman-compute-1.7.2.27-1.el7sat.noarch foreman-gce-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch foreman-debug-1.7.2.27-1.el7sat.noarch foreman-vmware-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.7-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch foreman-ovirt-1.7.2.27-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch foreman-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-postgresql-1.7.2.27-1.el7sat.noarch steps: 1. Create an Org 2. Create Lifecycle enviroments DEV,QE 3. Importing Red Hat Manifest (containing Employee SKU) 4. Attempt to delete the Org in UI
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.