Bug 867845 - unable to install katello - pulp 403 errors
Summary: unable to install katello - pulp 403 errors
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Katello
Classification: Retired
Component: Installer
Version: 1.1
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 12:12 UTC by Ohad Levy
Modified: 2012-10-29 15:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-29 15:27:10 UTC
Embargoed:


Attachments (Terms of Use)
katello debug (61.32 KB, application/x-gzip)
2012-10-18 12:12 UTC, Ohad Levy
no flags Details

Description Ohad Levy 2012-10-18 12:12:24 UTC
Created attachment 629331 [details]
katello debug

Description of problem:

unable to install katello

Version-Release number of selected component (if applicable):
1.1

How reproducible:
100%

Steps to Reproduce:
1. yum install katello-all
2. katello-configure
3.
  
Actual results:

katello-configure --reset-data=YES --reset-cache=YES (tried with and without reset)
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20121018-082834/main.log]
Creating Katello database
############################################################ ... OK
Populating Katello database schema
############################################################ ... OK
Initializing Katello data
###########################################################
  Failed, please check [/var/log/katello/katello-configure/db_seed.log]
  Report errors using # katello-debug tool.
Initializing Katello data
###########################################################
  Failed, please check [/var/log/katello/katello-configure/db_seed.log]
  Report errors using # katello-debug tool.

Expected results:


Additional info:

Comment 1 Lukas Zapletal 2012-10-29 15:27:10 UTC
https://github.com/Katello/katello/pull/919


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