Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] With the --bulk option, an error occurs; without --bulk, there is no error #413

Open
1 task done
torsten-liermann opened this issue Dec 28, 2024 · 2 comments
Open
1 task done
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@torsten-liermann
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

kantra v0.5.3

Priority

Major

Current Behavior

With the --bulk option, an error occurs; without --bulk, there is no error. This is what the error looks like when I run Kantra v0.5.3 with the --bulk option. It seems that the file dependencies.yaml needs to be named dependency-<A>.yaml.


2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory
ERRO[0354] container run error                           error="exit status 1"
ERRO[0354] failed to generate static report              error="2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory\n"
Error: 2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory

These files are present in the folder /home/me/projects/mta-output/all despite the error:

-rw-r--r--    1 root     0           112218 Dec 28 23:18 analysis.log.A
-rw-r--r--    1 root     0         39581096 Dec 28 23:18 output.yaml.A
-rw-r--r--    1 root     0          2863576 Dec 28 23:18 provider.log

`

Expected Behavior

The expectation is that the report will be fully available at the end of the analysis.

How Reproducible

Always (Default)

Steps To Reproduce

Environment Windows 11, Rancher Desktop 1.16.0, started kantra cli within an Alpine 3.20 environment.

With the --bulk option, an error occurs; without --bulk, there is no error. This is what the error looks like when I run Kantra v0.5.3 with the --bulk option. It seems that the file dependencies.yaml needs to be named dependency-<A>.yaml.


2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory
ERRO[0354] container run error                           error="exit status 1"
ERRO[0354] failed to generate static report              error="2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory\n"
Error: 2024/12/28 21:46:49 failed to load provider settings open /opt/output/dependencies.yaml: no such file or directory

### Environment

```markdown
- OS:Windows 11
- Rancher Desktop 1.16.0
- Alpine Linux 3.20

Anything else?

The issue occurs exactly the same on a Debian 12 bare metal system.

@torsten-liermann torsten-liermann added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 28, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Dec 28, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Dec 28, 2024
@zhoufenqin
Copy link

Is there any update? it seems the issue has opened for more than 2 months

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants