erikbocks commented on PR #12502: URL: https://github.com/apache/cloudstack/pull/12502#issuecomment-4274915625
@DaanHoogland @weizhouapache, after testing locally, I identified the reason for the CI failures. As @weizhouapache pointed out (https://github.com/apache/cloudstack/pull/12502#issuecomment-4266914755), the error occurs because an invalid UUID is being passed as a parameter, which causes the `UUID.fromString` method to throw an Exception. This invalid UUID is being used in the test_regions_accounts.py integration test. The current parameters used in the test are: ```json { "domain": { "name": "testuuid", "domainUUID": "domain1" }, "account": { "email": "[email protected]", "firstname": "Testuuid", "lastname": "Useruuid", "username": "test", "password": "password", "accountUUID": "account1", "userUUID": "user1" }, "user": { "email": "[email protected]", "firstname": "Testuuid", "lastname": "Useruuid", "username": "test", "password": "password", "userUUID": "user2" } } ``` The `accountUUID` and `userUUID` parameters are currently defined as plain strings, rather than valid UUIDs. While the `createAccount`, `createUser` and `createDomain` APIs allow users to provide a UUID for new resources, these fields are typed as strings instead of UUIDs. As a result, resources (accounts, users, domains) can be created with arbitrary values as their UUIDs. On the other hand, the `id` parameter of the listing APIs (`listAccounts`, `listDomains`, and `listUsers`) is typed as `UUID`, meaning the provided value is validated. With the changes introduced in PR #12502, Java’s UUID parsing now enforces that the value must be a valid UUID. To restore the functionality of the `test_regions_accounts` test, it should be updated to use valid UUID values instead of arbitrary strings. Would you like me to update the test? -- 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]
