Description of problem (please be detailed as possible and provide log
snippests):

CU noobaa PVC is growing. After extending +2GB is still growing.
TRUNCATE command is giving below error:

nbcore-# TRUNCATE activitylogs;
ERROR: syntax error at or near "nbcore"

related KCS: https://access.redhat.com/solutions/7055080

also activitylogs consumes very less size , as per schema out put

Schema | Name | Type | Owner | Persistence | Access method | Size | Description
---------------------------------------------------------------------------+------------
public | accounts | table | noobaa | permanent | heap | 56 kB |
public | activitylogs | table | noobaa | permanent | heap | 80 kB |
public | agent_configs | table | noobaa | permanent | heap | 48 kB |
public | alertslogs | table | noobaa | permanent | heap | 48 kB |
public | buckets | table | noobaa | permanent | heap | 2472 kB |
public | bucketstats | table | noobaa | permanent | heap | 72 kB |
public | chunk_configs | table | noobaa | permanent | heap | 48 kB |
public | clusters | table | noobaa | permanent | heap | 168 kB |
public | datablocks | table | noobaa | permanent | heap | 3960 MB |
public | datachunks | table | noobaa | permanent | heap | 9550 MB |
public | endpointgroupreports | table | noobaa | permanent | heap | 3744 kB |
public | funcs | table | noobaa | permanent | heap | 8192 bytes |
public | iostats | table | noobaa | permanent | heap | 112 kB |
public | master_keys | table | noobaa | permanent | heap | 64 kB |
public | mdsequencesnative | sequence | noobaa | permanent | | 8192 bytes |
public | namespace_resources | table | noobaa | permanent | heap | 8192 bytes |
public | nodes | table | noobaa | permanent | heap | 256 kB |
public | objectmds | table | noobaa | permanent | heap | 6207 MB |
public | objectmultiparts | table | noobaa | permanent | heap | 153 MB |
public | objectparts | table | noobaa | permanent | heap | 4045 MB |
public | objectstats | table | noobaa | permanent | heap | 48 kB |
public | pools | table | noobaa | permanent | heap | 544 kB |
public | replicationconfigs | table | noobaa | permanent | heap | 8192 bytes |
public | roles | table | noobaa | permanent | heap | 48 kB |
public | system_history | table | noobaa | permanent | heap | 1288 kB |
public | systems | table | noobaa | permanent | heap | 256 kB |
public | tieringpolicies | table | noobaa | permanent | heap | 56 kB |
public | tiers | table | noobaa | permanent | heap | 48 kB |
public | usagereports | table | noobaa | permanent | heap | 7424 kB |

Version of all relevant components (if applicable):

OCP version 4.16.8
ODF version 4.16.1
NooBaa operator
mcg-operator.v4.16.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

PVC gets filled with NooBaa DB

Is there any workaround available to the best of your knowledge?
Extending the PVC

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

N/A

Can this issue reproducible?
N/A

Can this issue reproduce from the UI?
N/A

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
N/A

Actual results:
NooBaa DB grows extensively
Truncate command gives an error

Expected results:
Truncate command should not fail.
Noobaa DB should not grow extensively

Additional info:

case 03941049