Bug 709417 - aeolus-cleanup fails to drop postgres db's
Summary: aeolus-cleanup fails to drop postgres db's
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configure
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
Assignee: Mike Orazi
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 16:56 UTC by wes hayutin
Modified: 2012-01-26 12:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 13:58:24 UTC


Attachments (Terms of Use)
full log (120.44 KB, text/plain)
2011-05-31 16:56 UTC, wes hayutin
no flags Details

Description wes hayutin 2011-05-31 16:56:04 UTC
Created attachment 502046 [details]
full log

ssh root.rhts.eng.bos.redhat.com aeolus-cleanup
Stdout: 
[0;36mnotice: /Stage[main]/Aeolus::Image-factory::Disabled/Exec[remove_aeolus_templates]/returns: executed successfully[0m
[0;36mnotice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: (in /usr/share/aeolus-conductor)[0m
[0;36mnotice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: Couldn't drop conductor : #<PGError: FATAL: password authentication failed for user "aeolus"[0m
[0;36mnotice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: >[0m
[0;36mnotice: /Stage[main]/Aeolus::Conductor::Disabled/Rails::Drop::Db[drop_aeolus_database]/Exec[drop_rails_database]/returns: executed successfully[0m
[0;36mnotice: Finished catalog run in 1.69 seconds[0m
Stderr:
ExitCode: 0


full log of install/configure/cleanup attached

Comment 1 Martyn Taylor 2011-06-02 13:14:49 UTC
This only happens when aeolus-cleanup is run before aeolus-configure.

In which case, cleanup will not be able to drop the "conductor" database from Postgres with user "aeolus" since neither the user nor the database exist.

Since puppet only shows a Notice and not an Error I reccomend we close this one off.  We might want to add another BZ to catch the Error message output by Postgres.

Thanks

Martyn

Comment 2 wes hayutin 2011-06-02 13:28:03 UTC
Martyn,
Please look at the log here..
http://hudson.rhq.lab.eng.bos.redhat.com:8080/hudson/view/DEV-CloudForms/job/cloudEngine-smoke-test/190/artifact/automatjon/cloudEngine/test-output/html/index.html

Search on aeolus-configre and aeolus-cleanup. You should see configure is run first, and cleanup unable to drop the postgres tables.

Thanks

Comment 3 wes hayutin 2011-06-02 13:28:39 UTC
click log output

Comment 4 Martyn Taylor 2011-06-02 13:58:24 UTC
Closing off.  Seems it was an issue with QE testing suite.

Comment 5 wes hayutin 2011-07-11 00:32:43 UTC
removing from tracker

Comment 6 wes hayutin 2011-12-08 13:55:50 UTC
perm close


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