Bug 858661 - impossible to remove not promoted repo: "Repository cannot be deleted since it has already been promoted."
Summary: impossible to remove not promoted repo: "Repository cannot be deleted since i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Dmitri Dolguikh
QA Contact: Garik Khachikyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 11:24 UTC by Garik Khachikyan
Modified: 2019-09-25 21:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Unpromoted repositories could not be deleted. This is the incorrect behavior. This bug fix corrects this behavior and all unpromoted repositories can be deleted.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:55:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Garik Khachikyan 2012-09-19 11:24:53 UTC
Description of problem:
It is recently impossible to remove the repo just being created and not promoted to anywhere.

Version-Release number of selected component (if applicable):
provided puddle 1 for CFSE 1.1
---
candlepin-0.7.8-1.el6cf.noarch
katello-glue-pulp-1.1.12-7.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-4.el6cf.noarch
qpid-cpp-client-0.14-22.el6_3.x86_64
katello-common-1.1.12-7.el6cf.noarch
qpid-cpp-client-ssl-0.14-22.el6_3.x86_64
katello-selinux-1.1.1-1.el6cf.noarch
pulp-1.1.12-1.el6cf.noarch
candlepin-tomcat6-0.7.8-1.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-agent-1.1.2-1.el6cf.noarch
qpid-cpp-server-0.14-22.el6_3.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
python-isodate-0.4.4-4.pulp.el6.noarch
python-qpid-0.14-11.el6_3.noarch
pulp-selinux-server-1.1.12-1.el6cf.noarch
katello-glue-candlepin-1.1.12-7.el6cf.noarch
candlepin-cert-consumer-dell-per310-01.rhts.eng.bos.redhat.com-1.0-1.noarch
pulp-common-1.1.12-1.el6cf.noarch
katello-configure-1.1.9-3.el6cf.noarch
mod_wsgi-3.3-3.pulp.el6.x86_64
candlepin-selinux-0.7.8-1.el6cf.noarch
katello-1.1.12-7.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-1.1.8-4.el6cf.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
qpid-cpp-server-ssl-0.14-22.el6_3.x86_64
---
UI however is ok.

How reproducible:
always through cli.

Steps to Reproduce:
client remember --option org --value "ACME_Corporation"
provider create --name test
product create --name test --provider test
repo create --name test1 --product test --url http://inecas.fedorapeople.org/fakerepos/zoo3/
repo delete --name test1 --product test

 
Actual results:
Repository cannot be deleted since it has already been promoted. Using a changeset, please delete the repository from existing environments before deleting it.

Expected results:
possible to remove the repo not being promoted yet.

Additional info:

Comment 1 Garik Khachikyan 2012-09-19 11:28:26 UTC
please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=835875

Comment 2 Brad Buckingham 2012-09-20 19:20:28 UTC
I started working on this bugzilla and then saw that Dmitri has submitted a pull request with a fix, so reassigning to him.

Comment 3 Dmitri Dolguikh 2012-09-21 10:52:40 UTC
fixed in 4060945f7d2e23dededf498d28a266a7083fe5da

Comment 6 Garik Khachikyan 2012-10-04 10:27:32 UTC
# VERIFIED

fixed. the cli scenario in comment#0 is going fine now.
recreating the repo after its deletion also works. so all looks ok :) tyvm

checked on:
---
katello-1.1.12-12.el6cf.noarch
katello-cli-1.1.8-6.el6cf.noarch
pulp-1.1.12-1.el6cf.noarch

Comment 8 errata-xmlrpc 2012-12-04 19:55:52 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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html

Comment 9 Mike McCune 2013-08-16 18:05:48 UTC
getting rid of 6.0.0 version since that doesn't exist


Note You need to log in before you can comment on or make changes to this bug.