Skip to content

Dump is being placed in wrong dir #505

@Jonathan-Maciel

Description

@Jonathan-Maciel

Bug Report

What did you do?

I enabled dump on an application with WSLD on a P cluster.

What did you expect to see?

I expected to see the dump in /serviceability/<namespace>/<pod_name> just as with the trace files.

What did you see instead?

The files were put into the /serviceability dir.

sh-4.4$ ls serviceability
ebuy-wlo  heapdump.20230418.162243.1.0002.phd  javacore.20230418.162242.1.0001.txt
sh-4.4$ ls serviceability/ebuy-wlo
ebuy-dbos-86878c96d7-5zpnv  ebuy-dbos-86878c96d7-9r5tn
sh-4.4$ ls serviceability/ebuy-wlo/ebuy-dbos-86878c96d7-5zpnv
sh-4.4$ 

Environment

Large OpenShift P cluster

Additional context

I see that the operator does have the correct information, but is maybe just unzipping in the wrong place.
The WSLD has: dumpFile: '/serviceability/ebuy-wlo/ebuy-dbos-86878c96d7-5zpnv/2023-04-18_16:22:38.zip'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions