scality / backbeat Goto Github PK

User info has to be updated on the destination because it does not always match the source user.

I setup replication between local1 and AWS and local2 and Azure.
I get a status replication PENDING on the objects I copy to local1 and local2.
But they are not replicated to AWS and Azure.
I am receiving the following errors in the backbeat logs:

code: 404,
description: 'This object does not exist',
ObjNotFound: true }
could not load managment db { Error: ObjNotFound
at reconstructError (/usr/src/app/node_modules/arsenal/lib/network/rpc/utils.js:42:30)
at Socket.wrapCb (/usr/src/app/node_modules/arsenal/lib/network/rpc/rpc.js:84:16)
at Socket.onack (/usr/src/app/node_modules/socket.io-client/lib/socket.js:312:9)
at Socket.onpacket (/usr/src/app/node_modules/socket.io-client/lib/socket.js:236:12)
at Manager. (/usr/src/app/node_modules/component-bind/index.js:21:15)
at Manager.Emitter.emit (/usr/src/app/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
at Manager.ondecoded (/usr/src/app/node_modules/socket.io-client/lib/manager.js:332:8)
at Decoder. (/usr/src/app/node_modules/component-bind/index.js:21:15)
at Decoder.Emitter.emit (/usr/src/app/node_modules/component-emitter/index.js:134:20)
at Decoder.add (/usr/src/app/node_modules/socket.io-parser/index.js:246:12)
at Manager.ondata (/usr/src/app/node_modules/socket.io-client/lib/manager.js:322:16)
at Socket. (/usr/src/app/node_modules/component-bind/index.js:21:15)
at Socket.Emitter.emit (/usr/src/app/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
at Socket.onPacket (/usr/src/app/node_modules/engine.io-client/lib/socket.js:451:14)
at WS. (/usr/src/app/node_modules/engine.io-client/lib/socket.js:268:10)
at WS.Emitter.emit (/usr/src/app/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
code: 404,
description: 'This object does not exist',
ObjNotFound: true }

Zapier creates a Jira for every GitHub issue created.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.