stag7824 commented on issue #13944: URL: https://github.com/apache/cloudstack/issues/13944#issuecomment-6111727838
Thanks Mau, and thanks again for the careful testing. The VPC row is a separate question, and the change in #14293 doesn't touch it, so you would still see it. I can't explain it from the code. The VPC "limit" and "available" values are computed from the same variable in `DomainJoinDaoImpl`, `ViewResponseHelper` treats VPC and network separately, and the `domain_view` SQL joins `vpc` and `network` to their own limits. In your `listResourceLimits` output the network limit is 67 and the VPC limit is 77, so the row looks like it shows the network number as its limit while "Available" shows the right VPC number. To tell whether the server or the page produces the 67, could you share the raw `listDomains` response for that domain with `details=resource`? What I'd compare is `vpclimit`, `vpcavailable`, `vpctotal` and `networklimit`. One caveat on testing: the PR build on the QA site only contains the UI and runs against a 4.21 server, so it can't show the server-side fix in #14293. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
