Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M manjaro-arm-tools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • manjaro-armmanjaro-arm
  • applications
  • manjaro-arm-tools
  • Issues
  • #56
Closed
Open
Issue created Sep 18, 2022 by Ghost User@ghostContributor

[generic-efi] Some images don't get $ROOT_UUID defined

For some reason, currently unknown to me, some generic-efi images do not get a proper $ROOT_UUID set for Grub, while others, in the same CI run does. This results in the affected images to "Not able to find root" error after selecting the entry in Grub.

I have only seen this issue happen on the Github CI and I currently have no idea why.

Example:

In the last Dev image run today Minimal and Sway editions got the UUID, while the rest did not. There is nothing in the tools, as far as I can tell, that would prohibit the other editions from getting it.

I have verified that creating a kde-plasma (one of the failed ones) image on my local desktop, gets UUID just fine.

Assignee
Assign to
Time tracking