cf-mgmt CLI failed with "Apps Unknown field(s): 'log_rate_limit_in_bytes_per_second'"
search cancel

cf-mgmt CLI failed with "Apps Unknown field(s): 'log_rate_limit_in_bytes_per_second'"

book

Article ID: 298310

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

When run cf-mgmt CLI to update space quotas for TAS foundation, it might fail with error as shown below.
$ ~/cf-mgmt update-space-quotas  --config-dir=config --user-id=cf-mgmt --client-secret='changeme' --system-domain=my.sys.example.com
2023/12/05 04:10:48 I1205 04:10:48.862504 16622 quota.go:270] Updating space quota myquota
error: cfclient error (CF-UnprocessableEntity|10008): Apps Unknown field(s): 'log_rate_limit_in_bytes_per_second'

# space quotas was not changed
$ cf space-quota myquota
Getting space quota myquota for org myorg as admin...

total memory:         1G
instance memory:      unlimited
routes:               0
service instances:    0
paid service plans:   disallowed
app instances:        10
route ports:          0

Property log_rate_limit_in_bytes_per_second is available in /v3/space_quotas API endpoint since version 3.125.0. And cf-mgmt CLI starts to support property log_rate_limit_in_bytes_per_second since version 1.0.68. For TAS this property is supported in 3.0 and later releases. 

In this case the cf-mgmt CLI version is 1.0.69 and TAS version is 2.11.47. Therefore cf-mgmt update-space-quotas command would submit a CAPI call to TAS including property log_rate_limit_in_bytes_per_second which can't be recongized by target TAS yet, which caused the error. 

Environment

Product Version: 2.11

Resolution

There are two ways to address the issue:
1. Use one cf-mgmt CLI version earlier than 1.0.68
2. Or upgrade TAS to 3.0+ if cf-mgmt CLI version is 1.0.68 and later