Bug 714052 - 'PGError: ERROR: null value in column "realm_or_provider_id" violates not-null constraint" when Add mapping to realm
Summary: 'PGError: ERROR: null value in column "realm_or_provider_id" violates not-nul...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-17 09:21 UTC by Aziza Karol
Modified: 2012-01-26 12:19 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
error while add mapping to realm (211.33 KB, image/png)
2011-06-17 09:21 UTC, Aziza Karol
no flags Details

Description Aziza Karol 2011-06-17 09:21:59 UTC
Created attachment 505217 [details]
error while add mapping to realm

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.create a new realms and save.
2.click on that realms and click on "Add mapping to realm" button.
3.Click on save button.

PGError: ERROR: null value in column "realm_or_provider_id" violates not-null constraint : INSERT INTO "realm_backend_targets" ("frontend_realm_id", "realm_or_provider_type", "realm_or_provider_id") VALUES(2, 'Realm', NULL) RETURNING "id"  is displayed on UI.

Screen shot attached.

  
Actual results:


Expected results:


Additional info:
[root@hp-z600-01 log]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.3.0-0.el6.20110616211223git96e2d09.noarch
aeolus-configure-2.0.1-0.el6.20110602110128git5cb9257.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110616211223git96e2d09.noarch
aeolus-conductor-0.3.0-0.el6.20110616211223git96e2d09.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110616211223git96e2d09.noarch
aeolus-all-0.3.0-0.el6.20110616211223git96e2d09.noarch

Comment 1 wes hayutin 2011-06-23 13:28:20 UTC
this is fixed right? need git hash

Comment 2 Jan Provaznik 2011-06-23 13:34:12 UTC
patch for this is waiting for review, it's not pushed yet

Comment 3 Jan Provaznik 2011-06-24 12:31:15 UTC
commit c9a1dd744c381bf0ab560053fb6447e783a0cb3e

Comment 4 wes hayutin 2011-08-01 19:54:40 UTC
release pending...

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

Comment 7 wes hayutin 2011-12-08 13:52:08 UTC
closing out old bugs

Comment 8 wes hayutin 2011-12-08 14:05:37 UTC
perm close


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