-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.2.0
-
None
-
None
-
Quay Enterprise
Description of problem:
Failed to validate bitbucket build trigger in config tool
Version-Release number of selected component (if applicable):
quay.io/quay/quay:v3.2.0-4
How reproducible:
Always
Steps to Reproduce:
1.Refer to https://coreos.com/quay-enterprise/docs/latest/bitbucket-app.html , add oauth consumer in bitbucket
2.Setup config tool
3.Input secret and key, validate bitbucket build trigger
Actual results:
failed
Expected results:
succeed
Additional info:
logs:
2019-12-06 09:30:11,737 [53] [DEBUG] [urllib3.connectionpool] https://bitbucket.org:443 "POST /!api/1.0/oauth/request_token/ HTTP/1.1" 401 0 gunicorn-config stdout | 2019-12-06 09:30:11,737 [53] [DEBUG] [urllib3.connectionpool] https://bitbucket.org:443 "POST /!api/1.0/oauth/request_token/ HTTP/1.1" 401 0 2019-12-06 09:30:11,740 [53] [ERROR] [util.config.validator] Validation exception Traceback (most recent call last): File "/quay-registry/util/config/validator.py", line 79, in validate_service_for_config VALIDATORS[service](validator_context) File "/quay-registry/util/config/validators/validate_bitbucket_trigger.py", line 33, in validate raise ConfigValidationException("Invalid consumer key or secret") ConfigValidationException: Invalid consumer key or secret gunicorn-config stdout | 2019-12-06 09:30:11,740 [53] [ERROR] [util.config.validator] Validation exception Traceback (most recent call last): File "/quay-registry/util/config/validator.py", line 79, in validate_service_for_config VALIDATORS[service](validator_context) File "/quay-registry/util/config/validators/validate_bitbucket_trigger.py", line 33, in validate raise ConfigValidationException("Invalid consumer key or secret") ConfigValidationException: Invalid consumer key or secret 10.131.0.6 () - quayconfig [06/Dec/2019:09:30:11 +0000] "POST /api/v1/superuser/config/validate/bitbucket-trigger HTTP/2.0" 200 62 "https://quay-test-32-quay-config-quay-enterprise.apps.preserve-dyan1204.qe.gcp.devcluster.openshift.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" (0.255 3881 0.255) 2019-12-06 09:30:11,742 [53] [INFO] [gunicorn.access] - quayconfig [06/Dec/2019:09:30:11 +0000] "POST /api/v1/superuser/config/validate/bitbucket-trigger HTTP/1.0" 200 62 "https://quay-test-32-quay-config-quay-enterprise.apps.preserve-dyan1204.qe.gcp.devcluster.openshift.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" nginx stdout | 10.131.0.6 () - quayconfig [06/Dec/2019:09:30:11 +0000] "POST /api/v1/superuser/config/validate/bitbucket-trigger HTTP/2.0" 200 62 "https://quay-test-32-quay-config-quay-enterprise.apps.preserve-dyan1204.qe.gcp.devcluster.openshift.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" (0.255 3881 0.255) gunicorn-config stdout | 2019-12-06 09:30:11,742 [53] [INFO] [gunicorn.access] - quayconfig [06/Dec/2019:09:30:11 +0000] "POST /api/v1/superuser/config/validate/bitbucket-trigger HTTP/1.0" 200 62 "https://quay-test-32-quay-config-quay-enterprise.apps.preserve-dyan1204.qe.gcp.devcluster.openshift.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
- relates to
-
PROJQUAY-481 Git push triggers not compatible with BitBucket Server
- Closed