Skip to content

On compression failure, the path for logs is a container-internal path rather than a package-relative path. #602

@kirkrodrigues

Description

@kirkrodrigues

Bug

As reported by a user on Zulip:

This is a fairly minor bug but I've noticed when compression hits an error the path it says the log file will be at is incorrect.
It says:

2024-11-13 19:52:01,028 [ERROR] [/opt/clp/lib/python3/site-packages/clp_package_utils/scripts/native/compress.py] Compression failed. task 9: See logs /opt/clp/var/log/compression_worker/compression-job-9-task-9-stderr.log

But the real path is:

[clp_installation_dir/lib/python3/site-packages/clp_package_utils/scripts/native/compress.py] Compression failed. task 9: See logs clp_installation_dir/var/log/hostname/compression_worker/compression-job-9-task-9-stderr.log

CLP version

clp-json v0.2.0

Environment

Unknown

Reproduction steps

Compress a non-json file:

sbin/compress.sh etc/clp-config.yml

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions