Skip to content

[Bug][config-ui] After upgrade the config UI is stuck #8623

Closed
Closed
[Bug][config-ui] After upgrade the config UI is stuck#8623
Labels
Stalecomponent/config-uiThis issue or PR relates to config-uipriority/highThis issue is very importantseverity/p0This bug blocks key user journey and functiontype/bugThis issue is a bug

Description

@michelengelen
michelengelen
opened on Oct 23, 2025

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

I have just recently updated the devlake version from 1.0.2 to 1.0.3-beta7 to include the nginx upgrade due to a security vulnerability in nginx 1.27 and now the config ui is stuck (see screenshot)

Image

What do you expect to happen

The config ui should be working

How to reproduce

Anything else

No response

Version

v1.0.3-beta7

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. michelengelen
    added
    type/bugThis issue is a bug
    on Oct 23, 2025

  2. dosubot commented on Oct 23, 2025

    @dosubot
    dosubotBot
    on Oct 23, 2025 – with DosuBot

    The 502 Bad Gateway error after upgrading to v1.0.3-beta7 and nginx 1.29 likely means the backend service is unreachable or misconfigured. There are no documented upgrade or migration steps for nginx or DevLake that specifically address this issue, but recent changes may impact backend availability.

    A recent pull request upgraded nginx in the config-ui Dockerfile to 1.29 for security reasons, but did not change nginx configuration itself PR #8481. Another change disabled CORS middleware in the backend API server, which could affect how nginx proxies requests to the backend and may cause errors if the frontend expects CORS headers PR #8549.

    There is also a known backend crash after upgrading to v1.0.3-beta7 due to a database migration issue (NULL to int conversion in the 'priority' column), which can prevent the backend from starting and result in 502 errors PR #8622.

    Troubleshooting steps:

    • Check that the backend service is running and healthy (not crashing due to migration errors).
    • Review backend logs for database migration errors or startup failures.
    • Make sure nginx is correctly proxying requests to the backend service and the backend port is reachable.
    • If you see migration errors, you may need to manually resolve database issues or confirm migrations are complete.
    • If you rely on CORS for frontend-backend communication, consider re-enabling CORS middleware or adjusting nginx proxy headers.

    If you need more targeted help, sharing backend logs or nginx config could help pinpoint the issue.

    To reply, just mention @dosu.

    Docs are dead. Just use Dosu.

    Leave Feedback Ask Dosu about incubator-devlake Share Dosu with your team

  3. dosubot
    added
    component/config-uiThis issue or PR relates to config-ui
    priority/highThis issue is very important
    severity/p0This bug blocks key user journey and function
    on Oct 23, 2025

  4. petkostas commented on Oct 23, 2025

    @petkostas
    petkostas
    on Oct 23, 2025
    Contributor

    Can you provide the logs from the devlake instance?
    This is most likely related to #8621

  5. michelengelen commented on Oct 24, 2025

    @michelengelen
    michelengelen
    on Oct 24, 2025
    Author

    All right ... seems like the instance keeps trying to restart due to a faulty SELECT:

    [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
 - using env:   export GIN_MODE=release
 - using code:  gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET    /ping                     --> github.com/apache/incubator-devlake/server/api/ping.Get (3 handlers)
[GIN-debug] GET    /ready                    --> github.com/apache/incubator-devlake/server/api/ping.Ready (3 handlers)
[GIN-debug] GET    /health                   --> github.com/apache/incubator-devlake/server/api/ping.Health (3 handlers)
[GIN-debug] GET    /version                  --> github.com/apache/incubator-devlake/server/api/version.Get (3 handlers)
time="2025-10-24 08:22:09" level=info msg=" [pipeline service] get lock and wait next pipeline"
time="2025-10-24 08:22:09" level=info msg="\x1b[31;1m/app/impls/dalgorm/dalgorm.go:227 \x1b[35;1msql: Scan error on column index 0, name \"priority\": converting NULL to int is unsupported\n\x1b[0m\x1b[33m[0.973ms] \x1b[34;1m[rows:1]\x1b[0m SELECT `priority` FROM `_devlake_pipelines` WHERE status IN ('TASK_CREATED','TASK_RERUN','TASK_RESUME') ORDER BY priority DESC LIMIT 1"
panic: attached stack trace
  -- stack trace:
  | github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).convertGormError
  |     /app/impls/dalgorm/dalgorm.go:547
  | github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).Pluck
  |     /app/impls/dalgorm/dalgorm.go:227
  | github.com/apache/incubator-devlake/server/services.dequeuePipeline
  |     /app/server/services/pipeline.go:268
  | github.com/apache/incubator-devlake/server/services.RunPipelineInQueue
  |     /app/server/services/pipeline.go:335
  | runtime.goexit
  |     /usr/local/go/src/runtime/asm_amd64.s:1598
Wraps: (2) sql: Scan error on column index 0, name "priority": converting NULL to int is unsupported (500)
Wraps: (3) sql: Scan error on column index 0, name "priority"
Wraps: (4) converting NULL to int is unsupported
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *fmt.wrapError (4) *errors.errorString

    Scan error on column index 0, name \"priority\": converting NULL to int is unsupported seems to be the problem here.

    cc @klesh @petkostas

  6. michelengelen commented on Oct 24, 2025

    @michelengelen
    michelengelen
    on Oct 24, 2025
    Author

    Seems the problem already got fixed here #8622 .. when will this be released?

  7. klesh commented on Oct 27, 2025

    @klesh
    klesh
    on Oct 27, 2025
    Contributor

    @d4x1 Let's release a new beta on Friday

  8. petkostas commented on Nov 3, 2025

    @petkostas
    petkostas
    on Nov 3, 2025
    Contributor

    @d4x1 is the a chance we get a release this week? as currently we had to disable Apache Devlake due to the specific issue.

  9. randidwinandra commented on Nov 6, 2025

    @randidwinandra
    randidwinandra
    on Nov 6, 2025

    Hey @d4x1 , we’re seeing the same issue too. Any update on when it might be released? Thanks a lot!

  10. d4x1 commented on Nov 7, 2025

    @d4x1
    d4x1
    on Nov 7, 2025
    Contributor

    https://github.com/apache/incubator-devlake/releases/tag/v1.0.3-beta8

    @randidwinandra @petkostas

  11. github-actions commented on Jan 7, 2026

    @github-actions
    github-actionsBot
    on Jan 7, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

  12. github-actions
    added
    Stale
    on Jan 7, 2026

  13. github-actions commented on Jan 14, 2026

    @github-actions
    github-actionsBot
    on Jan 14, 2026 – with GitHub Actions
    Contributor

    This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

  14. github-actions
    closed this as completedon Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stalecomponent/config-uiThis issue or PR relates to config-uipriority/highThis issue is very importantseverity/p0This bug blocks key user journey and functiontype/bugThis issue is a bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions