HewlettPackard / HewlettPackard/PowerShell-ProLiant-SDK

Start-HPEiLOCertificateSigningRequest not working with iLO4 2.78 with Get-Culture other than en-US

Open
#69 5 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
PowerShell
Stars
97
Forks
44
PR merge metrics
No merged PRs in 30d

Description

Start-HPEiLOCertificateSigningRequest doesn't seem to work with HPEiLOCmdlets 3.1.0.1 and iLO4 2.78

Tested with:
BL460c Gen8, iLO4 2.78
BL460c Gen9, iLO4 2.78

```
> $(Get-Culture).Name
et-EE
```
```
> $VerbosePreference ="Continue"
```
```
> $credential = New-Object -TypeName "System.Management.Automation.PSCredential" `
-ArgumentList "username",$(ConvertTo-SecureString -String "password" -AsPlainText -Force)
```
```
> $connection = Connect-HPEiLO -Credential $credential -IP "ilo.host.tld" -DisableCertificateAuthentication
VERBOSE: Executing the cmdlets with 1 task serially.
VERBOSE: [Connect-HPEiLO][ilo.host.tld]: XML Reply on: Reading iLO xml data
VERBOSE: [Connect-HPEiLO][ilo.host.tld]: iLO FirmwareVersion: iLO4 v2,78
VERBOSE: [Connect-HPEiLO][ilo.host.tld]: Product Name: ProLiant BL460c Gen8
VERBOSE: [Connect-HPEiLO][ilo.host.tld]: Creating connection for connection type(s): RIBCL
VERBOSE: [Connect-HPEiLO][ilo.host.tld][RIBCL]: Establishing connection.
VERBOSE: [Connect-HPEiLO][ilo.host.tld][RIBCL]: Received response for create connection request.
VERBOSE: [Connect-HPEiLO][ilo.host.tld][RIBCL]: Connection established.
VERBOSE: [Connect-HPEiLO][ilo.host.tld]: Connection established for connection type(s): RIBCL
```
```
> Start-HPEiLOCertificateSigningRequest -Connection $connection -CommonName "ilo.host.tld" -City "City" `
-Country "TLD" -Organization "Org" -State "State" -OrganizationalUnit "OU" -IncludeiLOIP
VERBOSE: Executing the cmdlets with 1 task serially.
VERBOSE: [Start-HPEiLOCertificateSigningRequest][REST]: REST model is HPE.iLO.Communication.REST.Model.SetModel.
VERBOSE: [Start-HPEiLOCertificateSigningRequest][ilo.host.tld][REST]: Validating Cmdlet supportability.
VERBOSE: [Start-HPEiLOCertificateSigningRequest][ilo.host.tld][REST]: Checking for iLOGeneration, Model and Firmware for Cmdlet Supportability.
VERBOSE: [Start-HPEiLOCertificateSigningRequest][ilo.host.tld][REST]: Forming the error object.

IP Hostname Status StatusInfo
-- -------- ------ ----------
192.168.0.10 ilo.host.tld ERROR HPE.Framework.Core.StatusInfo
```
```
> Get-HPEiLOCertificateSigningRequest -connection $connection

IP Hostname Status StatusInfo
-- -------- ------ ----------
192.168.0.10 ilo.host.tld ERROR HPE.Framework.Core.StatusInfo
```

Works fine with Gen10 iLO5 v2.44 hosts though.

Workaround for iLO4:
Doing ```Set-Culture -CultureInfo en-US``` and running a new PowerShell session fixes the behaviour. Probably the iLO4 version parser expects dot instead of comma in "v2,78"

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.