Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

GuestConfiguration errors out if the generated MOF filename has periods in the filename before the '.mof'

Abierto
  • ¿Algo no está bien?
#296 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
powershell
Área
tooling

Línea de trabajo

Reproduce el problema pasando un nombre de paquete que contenga puntos a New-GuestConfigurationPackage y, después, usa Get-GuestConfigurationPackageComplianceStatus con el paquete resultante. Rastrea cómo los comandos derivan las rutas de MOF y metaconfig a partir del nombre de archivo del paquete; se considera terminado cuando los paquetes con puntos resuelven correctamente ambos archivos y el estado de cumplimiento se ejecuta sin errores por documentos faltantes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Details of the scenario you tried and the problem that is occurring

The GuestConfiguration module errors out if the guest configuration package filename specified to New-GuestConfigurationPackage (by the Name parameter) includes periods in the package name. When the Guest Configuration package contains periods in the package name then the MOF file inside of the ZIP also includes periods in the filename, and when attempting to use the package with the Get-GuestConfigurationPackageComplianceStatus command , Guest Configuration mishandles this and tries to find the MOF using the wrong path.

This is particularly problematic because the guidance found here specifically suggests a package naming convention that will lead to users encountering this error condition: https://learn.microsoft.com/en-us/azure/governance/machine-configuration/how-to/create-policy-definition?source=recommendations#policy-lifecycle

Verbose logs showing the problem
Error: DSC document '/home/myaccount/.local/share/powershell/Modules/GuestConfiguration/4.5.0/gcworker/packages/UbuntuServer-20-04-LTS-CISv201-Section1-AuditAndSet-0.1.4/UbuntuServer-20-04-LTS-CISv201-Section1-AuditAndSet-0.1.mof' doesn't exist in assignment package.
Error: Metaconfig document '/home/myaccount/.local/share/powershell/Modules/GuestConfiguration/4.5.0/gcworker/packages/UbuntuServer-20-04-LTS-CISv201-Section1-AuditAndSet-0.1.4/UbuntuServer-20-04-LTS-CISv201-Section1-AuditAndSet-0.1.metaconfig.json' doesn't exist in assignment package.
Error: Failed to Run Consistency for 'UbuntuServer-20-04-LTS-CISv201-Section1-AuditAndSet-0.1.4' Error : Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first.

Write-Error: Job 29cd2220-d307-48a9-9123-267071dd52e6 : MIResult: 6 Error Message: Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration
first. Message ID: OMI:MI_Result:6 Error Category: 0 Error Code: 1 Error Type:
Suggested solution to the issue

It looks like the GuestConfiguration code is making a bad assumption regarding periods being in the filename, and parsing based on that bad assumption. I assume the related code for parsing the path of the MOF needs revising.

The DSC configuration that is used to reproduce the issue (if applicable)

n/a - this issue is not configuration-dependent

The operating system the target node is running

Ubuntu Server 18.04 LTS

Version and build of PowerShell the target node is running

7.3.10 (7.4+ doesn't seem to work with GuestConfiguration, so we have intentionally avoided upgrading)

Version of the module that was used

4.5.0

Lenguaje dominante
PowerShell
Estrellas
8
Forks
13
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/GuestConfiguration

Todos los issues de Azure/GuestConfiguration

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.