Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

staged recipes broken on travis 403 errors #10438

Closed
beckermr opened this issue Dec 13, 2019 · 10 comments
Closed

staged recipes broken on travis 403 errors #10438

beckermr opened this issue Dec 13, 2019 · 10 comments

Comments

@beckermr
Copy link
Member

Alright @conda-forge/core @conda-forge/staged-recipes, it appears that staged-recipes will be broken until someone can diagnose the 403 error we are getting on travis-ci.com.

It appears that when we ask travis-ci.com to make sure repos build only with yaml here in conda-smithy, we are getting a 403 HTTP code, meaning we don't have permission.

@ocefpaf tried to reset update the permissions/keys/whatever, but it is still not working.

Can someone on @conda-forge/core look into this? I think you all are the only ones with keys.

@chrisburr
Copy link
Member

This looks identical to #5846 with the error response:

{
  "@type": "error",
  "error_type": "insufficient_access",
  "error_message": "operation requires create_request access to repository",
  "resource_type": "repository",
  "permission": "create_request",
  "repository": {
    "@type": "repository",
    "@href": "/repo/6246397",
    "@representation": "minimal",
    "id": 6246397,
    "name": "staged-recipes",
    "slug": "conda-forge/staged-recipes"
  }
}

@ocefpaf
Copy link
Member

ocefpaf commented Dec 14, 2019

@ocefpaf tried to reset update the permissions/keys/whatever, but it is still not working.

Yep. Not sure it is related to that. @isuruf and @mariusvniekerk, do you have an idea on how to debug this?

@beckermr
Copy link
Member Author

Bump here @conda-forge/core. I know we are all very busy, but any help you can provide would be appreciated!

@beckermr
Copy link
Member Author

Looks like @chrisburr moved us back to .org and this fixed things. I guess this means this is an upstream issue with Travis?

@hmaarrfk
Copy link
Contributor

the keys encrypted for .org and .com are not compatible.

@beckermr
Copy link
Member Author

@ocefpaf is writing Travis to see if this is a bug on their end.

@isuruf
Copy link
Member

isuruf commented Dec 16, 2019

It's not a travis-ci issue anymore.

@beckermr
Copy link
Member Author

I’m not following but glad you all are on it. Thanks!

@beckermr
Copy link
Member Author

Now we are getting drone errors. I guess we need to go through and reencrypt all of the keys or something?

Traceback (most recent call last):
  File ".travis_scripts/create_feedstocks.py", line 161, in <module>
    drone_sync()
  File "/home/travis/miniconda/lib/python3.7/site-packages/conda_smithy/ci_register.py", line 163, in drone_sync
    response.raise_for_status()
  File "/home/travis/miniconda/lib/python3.7/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://cloud.drone.io/api/user/repos?async=true
+++python .travis_scripts/trigger_travis_build.py conda-forge/staged-recipes
b'access denied'

@beckermr
Copy link
Member Author

This appears resolved. Thanks @ocefpaf! Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants