Description of problem: When user attempts to delete repos, a stack trace is returned. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Create a repo 2. Navigate to Administration > Content > Repositories 3. Click the checkbox next to your repo and attempt to delete ("Delete Selected"). Actual results: Failed to delete repositories. Cause: javax.ejb.EJBTransactionRolledbackException:org.hibernate.exception.SQLGrammarException: Could not execute JDBC batch update -> javax.persistence.PersistenceException:org.hibernate.exception.SQLGrammarException: Could not execute JDBC batch update -> org.hibernate.exception.SQLGrammarException:Could not execute JDBC batch update -> java.sql.BatchUpdateException:Batch entry 0 delete from RHQ_REPO_RHQ_TAG where RHQ_REPO_ID='10061' was aborted. Call getNextException to see the cause.[SQLException=Batch entry 0 delete from RHQ_REPO_RHQ_TAG where RHQ_REPO_ID='10061' was aborted. Call getNextException to see the cause. -> ERROR: relation "rhq_repo_rhq_tag" does not exist(error-code=0,sql-state=42P01)] Expected results: Can be deleted! Additional info: Found by automation.
This also breaks Content Providers - similar message occurs when trying to delete them.
Fixed. Dev sanity checking is done. I am able to delete repos and content providers without any errors or tracebacks. ~SayliK
QA Verified.
Mass-closure of verified bugs against JON.