Oneview resetting ilo hostname

[UserName1]

Hi,

Anyone else having a problem since upgrading to 6.30.00-0447630 that when you update from template it is resetting the ilo hostname to the server serial number and you have to manually enter it again?

The profile is set so the ilo name is the the same as the template that is used but seems to be totally ignoring that setting.

[DanCernese · Accepted solution]

Maybe this issue?  "HPE OneView - Changing a Server Firmware Baseline Resets the iLO Hostname to a Default Value"

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00118510en_us

[UserName1]

That looks to be the issue, now just the waiting game for the fix.

Thanks

[ChrisLynch]

This is a new advisory that I haven't seen before for OneView.  I am looking into this, as the documented impacted releases are 6.10 and 6.20.  We have shipped 6.30 and 6.40 since then.

[UserName1]

OK thanks, we are running 6.3 currently.  If you find anything out that would be great.

[ChrisLynch]

I was able to find out more on this.  It currently is a known issue, including the current release (which of this post is 6.40).  We currently have no resolution as it is a core issue to how the product works.  We are exploring ways to address this, but I don't have any path to any other fix than to re-apply the profile settings as noted in the customer advisory.

[UserName1]

Just wanted to check I hadn't missed something, 6.50 has been released and no sign of this being fixed in the realse notes?

Document - HPE OneView 6.5 Release Notes | HPE Support

[ChrisLynch]

When we fixed it, it was not a customer found incidents.  We do not document all fixes (those that are found internally only) within the release notes, but I can confirm that this is fixed in 6.50.

[UserName1]

Excellent - thanks for confirming that Chris, appreciate the reply.

[UserName1]

@ChrisLynch Just to let you know this issue is not fixed in 6.50, just applied a new profile and it killed the name again.

[ChrisLynch]

Please work this through a support case.  I will notify our dev team of this.

[UserName1]

Ok will do.  I don't think I've ever managed to raise a support ticket for oneview succesffuly without then wanting 'AHS' logs thinking it is a server fault but I will give it a go and feed back.

[ChrisLynch]

There is a specific support group for OneView.  If you are trying to open a support case for the server hardware, that is not the right path.  OneView support would ask for an appliance support dump, not AHS log files, unless there is a specific reason.  They might in this case, but should really focus on the OneView support dump.

[UserName1]

Ok ticket has been raised, if you want the number I can send it over to you.  I just use the normal support.hpe.com website, if there is a special OV one would be good to know. 

[ChrisLynch]

Private message me the case ID.

[UserName1]

For anyone else having this problem here is the final conclusion from support, I'm not sure I agree with what they are saying thay it is 'working as designed':

The initial analysis indicates that this is working as currently designed, with no indication of a fix. The second is what appears to be an enhancement, to modify the behavior so this does not occur. There is currently no "planned to be resolved in version X" for this request. Based on this information, we currently do not have a resolution for this issue, it is being looked at by R&D and they will implement a solution as soon as possible. for now, the resolution in the CA is what we have: RESOLUTION : This issue will be addressed in a future version of HPE OneView.

Workaround : The profile can be re-applied to correct the hostname if it is reset when a baseline is changed.

The fix is still on the radar, but to fix properly requires a big architectural change which is why it is taking so long.

So, there is no fix but a workaround.

Am I happy about this responce, no but there isn't anything else I can do, seems we just have to put up with it.  The work around really isnt that viable as it breaks the whole single image VCLM process, hey ho!