-
Notifications
You must be signed in to change notification settings - Fork 11
DocGeneration fails on Ubuntu-2204 image with libmi error #131
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
Comments
Maybe it would be worthwhile to build and pack MOF-based modules on Windows. Installing |
I'm in talks with the PS & Config team on this. |
Right, I forgot about PSWSMan. I can confirm that the DocGenerator build task works on Ubuntu 22.04 WSL (and likely also 20) after using |
@gaelcolas the pipelines are still failing. Did your talks result in any new information, or should we try using PSWSMan? |
I have now noticed that this issue has also started occurring with Ubuntu-20.04 (in StorageDsc) at least. |
When I encounter this I move the pipeline to |
That is what I have done. Does solve it. |
The tests in this repo are now skipped on Linux. There are to much work keeping DSC up to date on Linux and going forward stuff for Linux should be tested on DSCv3. |
Details of the scenario you tried and the problem that is occurring
Running the Doc Generation task on an
ubuntu-2204
(usually justubuntu-latest
) fails with:Steps to reproduce the problem
Run the pipeline for any DSC resource using automated doc generation and using an
ubuntu-latest
image. See https://dev.azure.com/dsccommunity/StorageDsc/_build/results?buildId=7403&view=logs&jobId=bce26a94-9049-50eb-6c1c-385ccbec51f9&j=bce26a94-9049-50eb-6c1c-385ccbec51f9&t=512e4b73-7a3e-57af-0534-ae809c1351daExpected behavior
Should perform the build.
Current behavior
Throws exception:
Exception: Failed to import classes from file
/home/vsts/work/1/s/source/DSCResources/DSC_Disk/DSC_Disk.schema.mof. Error
Exception calling "ImportClasses" with "3" argument(s): "Unable to load shared
library 'libmi' or one of its dependencies. In order to help diagnose loading
problems, consider setting the LD_DEBUG environment variable: liblibmi: cannot
open shared object file: No such file or directory"
Suggested solution to the issue
Temporary solution is to pin build image to
ubuntu-20.04
. Long term solution needs investigation.The operating system the target node is running
ubuntu-20.04
Version and build of PowerShell the target node is running
Version of the module that was used
Latest
The text was updated successfully, but these errors were encountered: