openvstorage/alba

Can't create namespace

Opened this issue · 3 comments

2017-07-09 07:37:15 778134 -0400 - NY1SRV0001 - 8675/0000 - arakoon - 42456826 - 
    info - Albamgr: unknown exception : "Assert_failure src/albamgr_plugin.ml:1529:15"

Apparently, it's a proper preset propagation predicament.

hotfix was deployed openvstorage/alba_ee#69

domsj commented

the fix in #759 is apparently not good enough, as we saw this issue again.

[12:17:50 AM] Jan Doms: fyi I tried creating a namespace and saw that it failed with error we've seen before ... 
2017-08-13 18:13:07 879065 -0400 - NY1SRV0001 - 23009/0000 - alba/cli - 11 - warning - Albamgr exception(Albamgr_protocol.Protocol.Error.Unknown,(Failure "\"local_encrypt\" version'=0 <> preset_version=1"))

this is because of some bug which we (alba team) hoped was properly fixed, but apparently it isn't

the workaround is the following

nuvolat@NY1SRV0001:~$ cat empty.json 
{}
nuvolat@NY1SRV0001:~$ alba update-preset --input-url empty.json --config arakoon://config/ovs/arakoon/ny1-hddbackend03-abm/config?ini=%2Fmnt%2Fssd1%2Farakoon%2Fexternal_arakoon_cacc.ini local_encrypt
2017-08-13 18:17:07 277628 -0400 - NY1SRV0001 - 29176/0000 - alba/cli - 0 - info - Albamgr_client.make_client :ny1-hddbackend03-abm
2017-08-13 18:17:07 278735 -0400 - NY1SRV0001 - 29176/0000 - alba/cli - 1 - info - connect_with : 172.17.16.6 26432 None Net_fd.TCP (fd:3)
2017-08-13 18:17:07 284799 -0400 - NY1SRV0001 - 29176/0000 - alba/cli - 2 - info - closing (fd:3)

forgot to check the preset version at that time. now (2017-08-16 05:02:22 172943 -0400) got this result:

    {
      "in_use": true,
      "name": "local_encrypt",
      "policies": [ [ 16, 8, 22, 2 ], [ 8, 6, 12, 1 ] ],
      "is_default": true,
      "fragment_size": 16777216,
      "osds": [ "all" ],
      "compression": "none",
      "fragment_checksum": [ "crc-32c" ],
      "object_checksum": {
        "allowed": [ [ "none" ], [ "sha-1" ], [ "crc-32c" ] ],
        "default": [ "crc-32c" ],
        "verify_upload": true
      },
      "fragment_encryption": [
        "aes-ctr-256",
        "XXX"
      ],
      "version": 3
    },

@toolslive do we still see this type of issues? I haven't heard of issues on Nuvolat/GIG with it (but I might not have all info of course).