Bug 718354 - aeolus-image rails.log exception, RoutingError No route matching "/builds/update_status"
Summary: aeolus-image rails.log exception, RoutingError No route matching "/builds/upd...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: rubygem-aeolus-image
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Richard Su
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-01 21:51 UTC by Dave Johnson
Modified: 2012-01-26 12:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Dave Johnson 2011-07-01 21:51:37 UTC
Description of problem
Tailing rails.log, I noticed when I ran aeolus-image build, the following exception is printed out.

# command
================
aeolus-image build --target rhev-m --template my.tmpl


# building
================
Processing ApplicationController#index (for 127.0.0.1 at 2011-07-01 17:44:36) [POST]
  Parameters: {"uuid"=>"e2d2c414-c35c-4897-bd13-283cd5d5109b", "status"=>"building"}

ActionController::RoutingError (No route matches "/builds/update_status" with {:method=>:post}):
  haml (3.0.18) rails/./lib/sass/plugin/rack.rb:41:in `call'
  haml (3.0.18) rails/./lib/sass/plugin/rack.rb:41:in `call'
  thin (1.2.5) lib/thin/connection.rb:76:in `pre_process'
  thin (1.2.5) lib/thin/connection.rb:74:in `catch'
  thin (1.2.5) lib/thin/connection.rb:74:in `pre_process'
  thin (1.2.5) lib/thin/connection.rb:57:in `process'
  thin (1.2.5) lib/thin/connection.rb:42:in `receive_data'
  eventmachine (0.12.10) lib/eventmachine.rb:256:in `run_machine'
  eventmachine (0.12.10) lib/eventmachine.rb:256:in `run'
  thin (1.2.5) lib/thin/backends/base.rb:57:in `start'
  thin (1.2.5) lib/thin/server.rb:156:in `start'
  thin (1.2.5) lib/thin/controllers/controller.rb:80:in `start'
  thin (1.2.5) lib/thin/runner.rb:177:in `send'
  thin (1.2.5) lib/thin/runner.rb:177:in `run_command'
  thin (1.2.5) lib/thin/runner.rb:143:in `run!'
  thin (1.2.5) bin/thin:6
  /usr/bin/thin:19:in `load'
  /usr/bin/thin:19



# failed
======================================
Processing ApplicationController#index (for 127.0.0.1 at 2011-07-01 17:36:08) [POST]
  Parameters: {"uuid"=>"7f1722a4-3319-4112-9996-ab332ef15dc3", "status"=>"failed"}

ActionController::RoutingError (No route matches "/builds/update_status" with {:method=>:post}):
  haml (3.0.18) rails/./lib/sass/plugin/rack.rb:41:in `call'
  haml (3.0.18) rails/./lib/sass/plugin/rack.rb:41:in `call'
  thin (1.2.5) lib/thin/connection.rb:76:in `pre_process'
  thin (1.2.5) lib/thin/connection.rb:74:in `catch'
  thin (1.2.5) lib/thin/connection.rb:74:in `pre_process'
  thin (1.2.5) lib/thin/connection.rb:57:in `process'
  thin (1.2.5) lib/thin/connection.rb:42:in `receive_data'
  eventmachine (0.12.10) lib/eventmachine.rb:256:in `run_machine'
  eventmachine (0.12.10) lib/eventmachine.rb:256:in `run'
  thin (1.2.5) lib/thin/backends/base.rb:57:in `start'
  thin (1.2.5) lib/thin/server.rb:156:in `start'
  thin (1.2.5) lib/thin/controllers/controller.rb:80:in `start'
  thin (1.2.5) lib/thin/runner.rb:177:in `send'
  thin (1.2.5) lib/thin/runner.rb:177:in `run_command'
  thin (1.2.5) lib/thin/runner.rb:143:in `run!'
  thin (1.2.5) bin/thin:6
  /usr/bin/thin:19:in `load'
  /usr/bin/thin:19





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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jason Guiditta 2011-07-05 15:32:44 UTC
I suspect we didn't get around to disabling the proper things to remove the connector service, can you tell me if that is still running?  aeolus-image does not call conductor with this information, but the old connector _would_ spin up a console, which would receive events from factory and attempt to update conductor at the url you specified.  I am 99% this is the issue, in which case all we need to do is disable the connector service (and probably remove it as a dep from conductor or aeolus-all).

Comment 2 Dave Johnson 2011-07-06 18:15:38 UTC
aeolus-connector is installed and is running

Comment 3 Richard Su 2011-07-13 01:02:11 UTC
Image factory connector was removed with this build:
aeolus-all-0.3.0-0.fc14.20110712223242git096643e.noarch.rpm   
aeolus-conductor-0.3.0-0.fc14.20110712223242git096643e.noarch.rpm   
aeolus-conductor-daemons-0.3.0-0.fc14.20110712223242git096643e.noarch.rpm 
aeolus-conductor-devel-0.3.0-0.fc14.20110712223242git096643e.noarch.rpm   
aeolus-conductor-doc-0.3.0-0.fc14.20110712223242git096643e.noarch.rpm     
aeolus-configure-2.0.1-0.fc14.20110712153243gite2c11da.noarch.rpm

Comment 4 Dave Johnson 2011-07-14 19:38:30 UTC
good to go with the following rpms:

[root@hp-xw8400-01 ~]# rpm -qa | grep aeolus
rubygem-aeolus-cli-0.0.1-1.el6.20110712223242git096643e.noarch
aeolus-conductor-0.3.0-0.el6.20110712223242git096643e.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110712223242git096643e.noarch
aeolus-configure-2.0.1-0.el6.20110712153243gite2c11da.noarch
aeolus-all-0.3.0-0.el6.20110712223242git096643e.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110712223242git096643e.noarch

Comment 5 wes hayutin 2011-08-01 19:56:56 UTC
release pending...

Comment 6 wes hayutin 2011-08-01 19:58:17 UTC
release pending...

Comment 8 wes hayutin 2011-12-08 13:55:44 UTC
closing out old bugs

Comment 9 wes hayutin 2011-12-08 14:09:12 UTC
perm close


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