milvus

milvus copied to clipboard

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

<_MultiThreadedRendezvous:StatusCode.PERMISSION_DENIED,PrivilegeGetFlushState:permissiondeny to xxxx> <_MultiThreadedRendezvous: StatusCode.PERMISSION_DENIED, PrivilegeShowPartitions: permission deny to xxxx>

Expected Behavior

no permission error

Steps To Reproduce

1. upgrage milvus from 2.3.3 to 2.3.12

Milvus Log

No response

Anything else?

No response

@xige-16 can you show the privileges of the related roles?

/assign @SimFG /unassign

@xige-16 can you show the privileges of the related roles?

I have checked and found that after the upgrade, there is indeed no Privilege on the partition, as well as the Privilege on flushState. I added it manually. @SimFG

Before the upgrade, I did not have grant partition Privilege, but I could operate partition and flsuh.

@xige-16 yes, the related privileges are added in the new version. in the v2.3.x version, if the apis are not required the privileges, you can use it. When you upgrade the v2.4.x version, there are some new privileges, which caused the error.

@SimFG It is best to have compatibility processing, otherwise you will not be able to operate the partition after the upgrade, and it is recommended to provide prompts in the document https://milvus.io/docs/v2.3.x/users_and_roles.md

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

any updates for this ?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.