Bug 863379 - Not working dc:setup
Summary: Not working dc:setup
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta5
Assignee: Steve Linabery
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-05 09:57 UTC by Jaromir Coufal
Modified: 2012-10-16 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-12 19:55:11 UTC
Embargoed:


Attachments (Terms of Use)
Console output of rake dc:steup (34.30 KB, text/plain)
2012-10-05 09:57 UTC, Jaromir Coufal
no flags Details

Description Jaromir Coufal 2012-10-05 09:57:48 UTC
Created attachment 622072 [details]
Console output of rake dc:steup

Description of problem:
dc:setup doesn't work properly - throws error

Version-Release number of selected component (if applicable):
cloudforms/1.1, upstream/master

How reproducible:
* run rake dc:setup
* error: undefined method `find_by_username' for #<Class:0x00000004f5f1a0>
  
Actual results:
==  RenameUsersLoginToUsername: migrated (0.0019s) ============================

rake aborted!
undefined method `find_by_username' for #<Class:0x00000004f5f1a0>

Expected results:
passed dc:setup

Comment 2 Steve Linabery 2012-10-12 19:55:11 UTC
I cannot reproduce this.

'rake dc:setup' succeeds for me on both master (e551085) and 1.1 (51746ee).

I did:
1) install rpms from aeolus-nightly repo
2) run aeolus-configure
3) clone conductor
4) git checkout master
5) copy database.pg to database.yml
6) mv Gemfile Gemfile.in
7) rake db:create
8) rake dc:setup
9) git checkout 1.1
10) mv Gemfile Gemfile.in
11) rake dc:setup

no errors.

Please provide more detail on how to reproduce if I'm doing something vastly different from you.

Comment 3 Jaromir Coufal 2012-10-15 07:44:54 UTC
I am using bundler:

For 1.1
1) git fetch -all
2) git merge --ff-only cloudforms/1.1
3) git submodule update
-- here I should have the latest version of 1.1
4) for 1.1 I need to use this reference for aeolus-image in Gemfile: https://github.com/aeolusproject/conductor/blob/master/src/Gemfile#L20
(otherwise conductor with bundler doesn't run)
5) bundle exec rake db:drop
6) bundle exec rake db:create
7) bundle exec rake dc:setup
8) ->
rake aborted!
undefined method `find_by_username' for #<Class:0x00000004769590>

For upstream/master
1) git fetch -all
2) git merge --ff-only upstream/master
3) git submodule update
-- here I should have the latest version of upstream/master
(don't need to add reference to aeolus-image, it is already in Gemfile)
4) bundle exec rake db:drop
5) bundle exec rake db:create
6) bundle exec rake dc:setup
7) ->
rake aborted!
undefined method `find_by_username' for #<Class:0x000000059b3ac0>

Hope it helps.

Comment 4 Steve Linabery 2012-10-15 15:59:03 UTC
(In reply to comment #3)
> I am using bundler:
> 
> For 1.1
> 1) git fetch -all
> 2) git merge --ff-only cloudforms/1.1
> 3) git submodule update
> -- here I should have the latest version of 1.1
> 4) for 1.1 I need to use this reference for aeolus-image in Gemfile:
> https://github.com/aeolusproject/conductor/blob/master/src/Gemfile#L20
> (otherwise conductor with bundler doesn't run)
> 5) bundle exec rake db:drop
> 6) bundle exec rake db:create
> 7) bundle exec rake dc:setup
> 8) ->
> rake aborted!
> undefined method `find_by_username' for #<Class:0x00000004769590>
> 
> For upstream/master
> 1) git fetch -all
> 2) git merge --ff-only upstream/master
> 3) git submodule update
> -- here I should have the latest version of upstream/master
> (don't need to add reference to aeolus-image, it is already in Gemfile)
> 4) bundle exec rake db:drop
> 5) bundle exec rake db:create
> 6) bundle exec rake dc:setup
> 7) ->
> rake aborted!
> undefined method `find_by_username' for #<Class:0x000000059b3ac0>
> 
> Hope it helps.

We don't support bundler use in downstream, so this should not be a blocker for downstream. I suggest re-filing this against upstream since it does appear to be broken there.

Comment 5 Jaromir Coufal 2012-10-16 07:28:44 UTC
OK, I will fill it one more time against upstream.


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