cloud-init Landscape module needs to modify the "ssl_public_key" in WSL environments #5904
Labels
bug: external
This issue was filed against the cloud-init bug tracker but is an issue in an external project.
bug
Something isn't working correctly
enhancement
New feature or request
Bug report
This bug does not lay solely in the hands of the cloud-init team, there is an opportunity for a collaborative solution between the codebases of cloud-init and the Landscape Client.
cloud-init has awareness of the execution environment, and is best positioned to formulate the path of the "ssl_public_key" in a manner that is appropriate for Ubuntu, and not Windows. Modifying the path from a Windows to a Linux-friendly one isn't something we wish to tackle within Landscape Client, because it would be bad practice for us to begin writing conditional logic for various Ubuntu types within Landscape Client.
Today, cloud-init's Landscape module fails in WSL environments, and the Ubuntu Pro for Windows agent is detecting the failure and correcting the Windows file path of the "ssl_public_key" parameter. The cloud-init-output.log will add clarity.
Steps to reproduce the problem
Use cloud-init.yaml to provision a WSL instance via Landscape.
Environment details
cloud-init logs
The text was updated successfully, but these errors were encountered: