incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-322) During upgrade displays error - a foreign key constraint fails (`cloud/#sql-f34_6e`...
Date Fri, 12 Oct 2012 01:01:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474695#comment-13474695
] 

Chip Childers commented on CLOUDSTACK-322:
------------------------------------------

Prachi - Can you please confirm if this is limited to CloudPlatform?  If that's the case,
then please close this bug as invalid for CloudStack.  (I assume that Citrix has an internal
tracker for you to use instead).

If this affects for CloudStack, can you please see if we can figure out the root cause?  If
there is a code fix, please commit to master.  I'll cherry pick into the 4.0 branch.
                
> During upgrade displays error - a foreign key constraint fails (`cloud/#sql-f34_6e`...
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-322
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-322
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Install and Setup
>    Affects Versions: pre-4.0.0
>         Environment: RHEL 5.X, CloudStack 3.0.X, Upgrade utility in management server,
error in database. 
>            Reporter: Matt Mullins
>            Assignee: Prachi Damle
>              Labels: Upgrade
>             Fix For: 4.1.0
>
>
> ERROR [utils.db.ScriptRunner] (main:null) Error executing: ALTER TABLE `cloud`.`vlan`
ADD CONSTRAINT `fk_vlan__physical_network_id` FOREIGN KEY (`physical_network_id`) REFERENCES
`physical_network`(`id`) 
> Initial Corrective Action:
> Run against Cloud DB - "insert into network_tags values (3, 200, 'GSS');"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message