Details
Description
What's the issue?
Users are unable to take a backup of a 7.1.0 cluster which has eventing function definitions and immediately restore this backup. They'll see an error such as the one below:
Error restoring cluster: unexpected status code 400 for 'POST' request to '/api/v1/backup', [
|
{
|
"code": 33,
|
"info": "Function scope cannot be changed"
|
}
|
]
|
This in-of-itself isn't a particularly interesting use-case, however, it does raise the question of how of how the export/import workflow works without some form of conflict resolution.
Steps to reproduce
1) Spin up a 7.1.0 cluster
2) Create an eventing function (can be very basic)
3) Perform a backup
4) Perform a restore
Ideally we'd like to be able to backup+restore in this case (and similar cases) for example, you should be able to perform the restore as expected by using '--disable-eventing' (note that all other services accept the payload back).
Attachments
Issue Links
- is caused by
-
MB-29224 Allow Eventing functions to run as non-admin user
- Closed