Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QB Repository Returns HTTP 500 #4251

jmuirhead ·

I have a QB 9.0.10 instance that needs to act as a QB repository to other QB instances. When trying to use the QB repository the server returns a 500 error. The build log shows:

12:36:19,690 INFO - Checking out revision 'configuration:ubit/Secure Deployment Framework (SDF)/Products/NVMe/5.1, build id:29055' of repository 'nvme_installer'...
12:36:19,690 INFO - Waiting for finish of dependency build (server: http://build.intel.com:8810, configuration: ubit/Secure Deployment Framework (SDF)/Products/5.1, build id: 29055)
12:36:19,776 INFO - Getting changes of 'nvme_installer' since build '539'...
12:36:19,836 INFO - Executing post-execute action...
12:36:19,836 ERROR - Step 'master>checkout installer' is failed.
java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 500 for URL: http://build.intel.com:8810/batch_download?build_id=29055&src_path=artifacts&file_patterns=**&compress=false

The QB server log on the machine acting as a QB repository shows:

2020-06-11 11:00:54,802 [qtp207870852-56] WARN org.eclipse.jetty.server.HttpChannel - /batch_download
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.pmease.quickbuild.model.User.memberships, could not initialize proxy - no Session

The user account has BATCH_DOWNLOAD_ARTIFACTS, ACCESS_ARTIFACTS, and ACCESS_RECOMMENDED_ARTIFACTS permissions only. Does the user perhaps need more permissions?

  • replies 5
  • views 173
  • stars 0
robinshen ADMIN ·

Tested with 9.0.10 and it works fine here. Can you please reproduce this with a sample database and send to [robin AT pmease DOT com]?

jmuirhead ·

Thanks Robin. I think I figured out the problem. The Active Directory user account we're using has some special characters in the password that don't work correctly over HTTP. I could not even use 'curl' to fetch the build artifacts with that user account. After creating a new Quickbuild user without special characters in the password everything worked fine.

robinshen ADMIN ·

Thanks for letting me know.

jmuirhead ·

After some further research it appears the password is _not _the problem. The problen is with any Active Directory user. If a local Quickbuild user is used, no matter what the password, everything works fine: Quickbuild repository with remote server, curl, wget, etc. All fine. I don't yet know if this is an Active Directory configuation problem or a Quickbuild problem. Still trying to research.

robinshen ADMIN ·

Thanks for the LDAP info. I got it reproduced with 9.0.12. This is actually a bug and has been fixed since QB 9.0.15.