-
Notifications
You must be signed in to change notification settings - Fork 34
Diagnostic invoking csm_allocation_create/delete #112
Comments
I have a fix pending in pull request #114, we need some test cases in the regression for this. |
Works now. Closing this issue. Issue the create allocation
Database:
|
We still see this problem on Austin system, with 1.1.2
We did delete the previous database create it again:
|
This code is not correct, The code in mainline is as follows:
If this is not present in csm_create_triggers.sql, then it's likely that the RPM is an old version of the RPM before the last fix was submitted. |
Chasing the source of the rpm 1.1.2-176. I assumed that all 1.1.2-xxx has the change, but that might not be true. |
Looking around a bit, it seems that the fix was merged in to master on Jun 18th. Looking at regression logs, seems like they would need at least version 1.1.2-432 (Built with latest git commit being 559ee9b) |
It is fixed on 1.2.0. Closing this issue. |
Diagnostic issues the command csm_allocation_create passing the status "running",
then at the end of the run it issue csm_allocation_delete. The csm_allocation_delete is failing with rc=25.
Then I Invoked the command manually, it says:
This message comes from the db function fn_csm_allocation_delete_start, when checking for valid transition.
The database says:
Why the csm_allocation_create is not setting the state to "running"?
The text was updated successfully, but these errors were encountered: