You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by GitBox <gi...@apache.org> on 2022/07/25 14:43:26 UTC

[GitHub] [inlong] fuweng11 opened a new issue, #5201: [Bug][Manager] The inlong group cannot be updated normally after the approval is successful

fuweng11 opened a new issue, #5201:
URL: https://github.com/apache/inlong/issues/5201

   ### What happened
   
   <img width="1419" alt="WeChatWorkScreenshot_28ced6ba-f7ea-4600-b912-9d371e66af2a" src="https://user-images.githubusercontent.com/76141879/180804089-388d69c9-5d93-4a06-82fd-b38b76027810.png">
   After the approval is successful, the cluster tag cannot be inserted into the inlong group normally.
   
   ### What you expected to happen
   
   After successful approval, the inlong group and inlong stream can be updated normally.
   
   ### How to reproduce
   
   1、New access
   2、Approved
   
   ### Environment
   
   _No response_
   
   ### InLong version
   
   master
   
   ### InLong Component
   
   InLong Manager
   
   ### Are you willing to submit PR?
   
   - [X] Yes, I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [inlong] healchow closed issue #5201: [Bug][Manager] The inlong group cannot be updated normally after the approval is successful

Posted by GitBox <gi...@apache.org>.
healchow closed issue #5201: [Bug][Manager] The inlong group cannot be updated normally after the approval is successful
URL: https://github.com/apache/inlong/issues/5201


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org