View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009526 | Taler | deployment and operations | public | 2025-02-09 13:00 | 2025-05-10 02:11 |
| Reporter | dvn | Assigned To | dvn | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009526: Unable to schedule CI jobs manually | ||||
| Description | Scheduling CI jobs manually through the web interface does not work anymore. In the web interface you get the error "invalid origin" From the buildbot-master http log: `/api/v2/forceschedulers/force-scheduler HTTP/1.0" 400 44 "https://buildbot.gnunet.org/"` | ||||
| Tags | No tags attached. | ||||
| The web interface module in buildbot has a whitelist of "allowed_origins". Since we switched to buildbot.gnunet.org, from buildbot.taler.org, the whitelist needed to be updated. Fixed in this commit: https://git.taler.net/taler-deployment.git/commit/?id=8cf623e54015cb17f9bcf97ec2412a43a2773b44 | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-09 13:00 | dvn | New Issue | |
| 2025-02-09 13:00 | dvn | Status | new => assigned |
| 2025-02-09 13:00 | dvn | Assigned To | => dvn |
| 2025-02-09 14:13 | dvn | Status | assigned => informing |
| 2025-02-09 14:13 | dvn | Resolution | open => fixed |
| 2025-02-09 14:13 | dvn | Note Added: 0024059 | |
| 2025-02-14 21:42 | Christian Grothoff | Target Version | => 1.0 |
| 2025-02-14 21:42 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-05-10 02:11 | Christian Grothoff | Status | informing => closed |