Woodpecker 2.7.1 reporting "an unknown error occured" in repo settings #4240
Comments
Open browser console, look for errors in console and network tabs. |
|
I get this when opening the settings of a repo: This here when I change something, for example, adding and deleting a secret: However, the secret gets created and is usable in pipelines. Also deleting the secret works. As far as I can say, all settings (so far) work correctly and can be updated. Network tab shows lots of 403 Forbidden, for example: |
It's a repo's secret. There also might be organization and global secrets. On settings page all of them try to load, but you don't have access to org secrets, therefore the error: There was similar error for global secrets (#3013).
What is ID of your user? Are you member of some organization? Does your org have ID=3? What is your role/permissions in the org (like org admin, developer, read-only) in Bitbucket? Probably this is Bitbucket forge issue, cause I don't have it with Gitea. |
|
@zc-devs it looks to me that #3013 was closed in 2.5.0? So the fix is not effective (for some forges or at least Bitbucket Datacenter)?
I just stumbled upon Woodpecker yesterday, thus I cannot tell if this behavior is new or exclusive to Bitbucket. Anyways, enjoying Woodpecker a lot and definitely open to help improve on Bitbucket integration, especially testing stuff. Woodpecker is definitely the cleanest CI solution I have ever seen. Very straightforward yaml files, very organized UI. We had Jenkins and GitLab CI before & also tried Atlassian's Bamboo, Woodpecker will definitely stay around for long.
How would I find out the ID of my user? Yes, we use Bitbucket Datacenter together with Crowd Datacenter (Atlassian's user directory & SSO service), so Bitbucket synchronizes it's user database via our Crowd server, where we configured different groups. I am admin in both. Thank you very much for assisting :) |
Yes, it was just an example of similar "unknown error" in secrets. Symptoms were the same, but it was because of global secrets. Your issue is with organization's secrets.
Do you have access to database? Then something like Or can open User settings and look at requests in browser's Network tab:
Then in Repository settings I see 3 requests there I wanted to compare user org ID with org ID. Database approach is probably better, cause it have more potential useful info.
Maybe I think there are two problems here:
|
Component
web-ui
Describe the bug
Whenever I navigate to the settings of a repo (same behavior for all repos) woodpecker reports "an unknown error occured". However, as far as I can tell, repo settings are interpreted correctly and I can also still update settings. Pipelines also execute normally. Even the server logs do not show any errors.
Since I did not experience major issues yet and do not see any errors reported in the server logs (server is running with debug mode on currently), I am not sure how to debug further and thus wanted to report the issue. Probably a low priority issue with (hopefully) no major implications?
Steps to reproduce
Expected behavior
No response
System Info
Woodpecker v2.7.1 Bitbucket Datacenter v9.1.1 Woodpecker is running via docker compose: ... woodpecker-server: image: woodpeckerci/woodpecker-server:v2.7.1 depends_on: - traefik container_name: woodpecker-server restart: always environment: - WOODPECKER_OPEN=true - WOODPECKER_SERVER_ADDR=:8000 - WOODPECKER_HOST=<our-woodpecker-url> # OAuth setup for Bitbucket Datacenter - WOODPECKER_BITBUCKET_DC=true - WOODPECKER_BITBUCKET_DC_GIT_USERNAME=<dedicated-woodpecker-account> - WOODPECKER_BITBUCKET_DC_GIT_PASSWORD=<password> - WOODPECKER_BITBUCKET_DC_CLIENT_ID=<client-id> - WOODPECKER_BITBUCKET_DC_CLIENT_SECRET=<client-secret> - WOODPECKER_BITBUCKET_DC_URL=<bitbucket-dc-url> - WOODPECKER_BITBUCKET_DC_SKIP_VERIFY=true # Agent - WOODPECKER_AGENT_SECRET=<agent-secret> # Optional: Additional configurations - WOODPECKER_LOG_LEVEL=debug volumes: - woodpecker_server_data:/var/lib/woodpecker # Persist data across restarts networks: - harbor labels: - "traefik.enable=true" - "traefik.http.routers.woodpecker.rule=Host(`<woodpecker-url>`)" - "traefik.http.routers.woodpecker.entrypoints=websecure" - "traefik.http.routers.woodpecker.tls.certresolver=le" - "traefik.http.services.woodpecker.loadbalancer.server.port=8000" - "traefik.docker.network=harbor"Additional context
No response
Validations
nextversion already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: