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

Add a reference to the toolbox 5.5 vs 6.0 issue on the release notes #528

Closed
e-minguez opened this issue Jan 13, 2025 · 0 comments · Fixed by #546
Closed

Add a reference to the toolbox 5.5 vs 6.0 issue on the release notes #528

e-minguez opened this issue Jan 13, 2025 · 0 comments · Fixed by #546
Assignees

Comments

@e-minguez
Copy link
Collaborator

SUSE/release-notes#6

Basically SL Micro 6.0 toolbox need to use 5.5 toolbox instead. We probably would like to add a note on the known issues of the release notes.

@e-minguez e-minguez changed the title Add a reference to the toolbox issue on the release notes Add a reference to the toolbox 5.5 vs 6.0 issue on the release notes Jan 13, 2025
hardys added a commit to hardys/suse-edge.github.io that referenced this issue Jan 20, 2025
Make a note that the suse/sle-micro/5.5/toolbox image may be required

In future we can add more comprehensive troubleshooting docs, but this
at least points in the right direction for any users who encounter issues
trying to use the 6.0 toolbox image

Fixes: suse-edge#528
@hardys hardys self-assigned this Jan 20, 2025
hardys added a commit to hardys/suse-edge.github.io that referenced this issue Jan 20, 2025
Make a note that the suse/sle-micro/5.5/toolbox image may be required

In future we can add more comprehensive troubleshooting docs, but this
at least points in the right direction for any users who encounter issues
trying to use the 6.0 toolbox image

Fixes: suse-edge#528
@hardys hardys closed this as completed in a880a9f Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants