Adding node 83701 of revision 83701 to deployment plan push_to_live_server failed. Only one entity per revision is allowed.

Not quite sure of this error.

Comments

aspilicious’s picture

aspilicious commented
Status: Active » Postponed (maintainer needs more info)

Can you reproduce this with latest code?
Description above the error message is: "// The query failed, most probably because of duplicate primary keys."

I'm closing this issue in a few weeks if you can't reproduce.

aspilicious’s picture

aspilicious commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Two weeks open without response

ciss’s picture

ciss commented
Title: Only one entity per revision is allowed. » deploy_manager_add_to_plan() not checking for existing revision
Component: node_deploy.module » deploy.module
Category: Support request » Bug report
Issue summary: View changes
Status: Closed (cannot reproduce) » Active

Encountered the same error when adding a Revisioning-controlled node to the deployment plan. Revisioning allows to modify the current revision instead of creating a new one.
deploy_manager_add_to_plan() in turn seems to assume that the entry hasn't been added previously, resulting in an attempted INSERT with a duplicate primary key.

... I'm not exactly sure what the intention here is, since the checkbox never seems to be checked, allowing to add multiple revisions of the same entity to a plan. Is this a bug or a feature? (Disclaimer: I'm just getting started with Deploy)

Deploy revision: 7dbe4a6 (2014-06-15, version 2.0-alpha2 +34 commits)

_grizly’s picture

_grizly commented

I'm getting this too, I believe its because of revisions, and the fact that my entities are.. complex.

I have seen logs on the destination server indicating a "successful login", however no new node data has propagated.. not even once. Not sure why, enabling debugging seems to only show the error at the top of the page.

What can I do to help?

This is the only indication that something is really wrong on the destination:
mod_fcgid: stderr: PHP Fatal error: Call to undefined function menu_execute_active_handler() in /var/www/vhosts/domain/httpdocs/index.php on line 21

On source server, dblog has:
Deployment eec3cd2e-68c8-441f-ba21-217be076b549 was deployed.
Followed by:

[url] => http://domain/services/rest/user/logout
    [status] => Done.
    [code] => 500
    [chunk_size] => 32768
    [data] => 
...
    [error] => Internal Server Error

I really need to get this working.. Can someone point me in the right direction?

_grizly’s picture

_grizly commented

Tried turning off revisions, but no dice, tried making a single basic page with no entities at all, and it gets to the server and b0rks the same.
Turned off all context modules on services endpoint (not deployment endpoint), and tried again.. new different batch of errors. (YES!)

Finally found this: https://www.drupal.org/node/1504184#comment-5852910

Upgraded entity dependency iterator to latest dev, and it worked!

Have to use memory processor for now, but I'm sure with a bit of head-desking I can figure out the rest. At least we haven't lost a week's work due to the servers not talking. yay!

dragon658’s picture

dragon658 commented

I also have this problem. Tried to update entity dependicy to lastest dev. It does not help. Dependency module does not work for me.