Skip to content

error after 1.1.12 -> 1.2.0 "error: You're using the staticfiles app without having set the required STATIC_URL setting." #11342

@lifeisafractal

Description

@lifeisafractal

Please verify that this bug has NOT been raised before.

  • I checked and didn't find a similar issue

Describe the bug*

I'm trying to upgrade from 1.1.12 -> 1.2.0 and the invoke update command is failing with:

[... truncated ...]
INVE-W3: Could not detect git information.
Unknown command: 'collectplugins'
Type 'manage.py help' for usage.
ERROR: InvenTree command failed: 'python3 manage.py collectplugins'
- Refer to the error messages in the log above for more information

I entered the container and tried to run manage.py and got this:

root@e775518f48bc:/home/inventree# ./src/backend/InvenTree/manage.py --help
INVE-W3: Could not detect git information.

Type 'manage.py help <subcommand>' for help on a specific subcommand.

Available subcommands:

[django]
    check
    compilemessages
    createcachetable
    dbshell
    diffsettings
    dumpdata
    flush
    inspectdb
    loaddata
    makemessages
    makemigrations
    migrate
    optimizemigration
    runserver
    sendtestemail
    shell
    showmigrations
    sqlflush
    sqlmigrate
    sqlsequencereset
    squashmigrations
    startapp
    startproject
    test
    testserver
Note that only Django core commands are listed as settings are not properly configured (error: You're using the staticfiles app without having set the required STATIC_URL setting.).

I highly bet this is due to my local configuration somehow, but if it worked on 1.1.12 if feels like it should work on 1.2.0. I looked through breaking changes and didn't see anything that seemed like it'd be relevant. I'm digging more into this, but wanted to open a bug in case this is obvious to a maintainer.

This feels similar to the already closed #9592, but this might just be a similar error presentation (Django mis-configuration) with different underlying root cause.

Steps to Reproduce

  1. Using docker install setup
  2. Start at 1.10.0
  3. Upgrade to 1.2.0
  4. run docker compose run --rm inventree-server invoke update
  5. Observe error

Note: It's very likely this is due to my configuration, not inherit to all InvenTree installs.

Expected behaviour

I expect to be able to upgrade to 1.2.0 from 1.1.10 or get a clearer error message with guidance on fixing the issue.

Deployment Method

Docker

Version Information

All from official docker releases:
Upgrading from 1.12.0
Upgrading to 1.2.0

I couldn't get the full version info as the server can't run right now.

Try to reproduce on the demo site

I did not try to reproduce

Is the bug reproducible on the demo site?

Not reproducible

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIdentifies a bug which needs to be addresseddockerDocker / docker-composequestionThis is a questionsetupRelates to the InvenTree setup / installation process

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions