VMware Cloud Community
glenngahnstedt
Contributor
Contributor
Jump to solution

vSphere 5 - host profile issue

Hi,

After a clean upgrade from 4.1 -> 5,

When I attempt to create a NEW host profile I get the message "Cannot update the profile. Check the profile for errors."

There are no existing host profiles, this would have been a new, first profile.

When I start digging a little deeper and check the vpxd logs I find this,

  • vim.fault.ProfileUpdateFailed
  • Call "HostProfileManager.CreateProfile" for object "HostProfileManager" on vCenter Server "hostname.domain.com" failed.
  • message = "Parameter 'sourceNamespaces' cannot be left unset."

vpxd log show this:

[09584 info 'Default' opID=F24D1A3A-00000086] [VpxLRO] -- ERROR task-487 -- host-25 -- vim.profile.ProfileManager.createProfile: vim.fault.ProfileUpdateFailed:
--> Result:
--> (vim.fault.ProfileUpdateFailed) {
-->    dynamicType = <unset>,
-->    faultCause = (vmodl.MethodFault) null,
-->    failure = (vim.fault.ProfileUpdateFailed.UpdateFailure) [
-->       (vim.fault.ProfileUpdateFailed.UpdateFailure) {
-->          dynamicType = <unset>,
-->          profilePath = (vim.profile.ProfilePropertyPath) {
-->             dynamicType = <unset>,
-->             profilePath = "cimIndications_cimIndicationsProfile_CimIndications.cimIndications_cimxmlIndications_CimXmlIndicationsProfile["793fc206b95a762b9bfb8442c4ee77fec79f537f517eb75a278dc052237f96fa"]",
-->             policyId = "CimXmlIndicationsProfilePolicy",
-->          },
-->          errMsg = (vmodl.LocalizableMessage) {
-->             dynamicType = <unset>,
-->             key = "com.vmware.vim.profile.host.UpdateError.ParameterNotSet.label",
-->             arg = (vmodl.KeyAnyValue) [
-->                (vmodl.KeyAnyValue) {
-->                   dynamicType = <unset>,
-->                   key = "paramName",
-->                   value = "sourceNamespaces",
-->                }
-->             ],
-->             message = "Parameter 'sourceNamespaces' cannot be left unset.",
-->          },
-->       },
-->       (vim.fault.ProfileUpdateFailed.UpdateFailure) {
-->          dynamicType = <unset>,
-->          profilePath = (vim.profile.ProfilePropertyPath) {
-->             dynamicType = <unset>,
-->             profilePath = "cimIndications_cimIndicationsProfile_CimIndications.cimIndications_cimxmlIndications_CimXmlIndicationsProfile["d3980f93c324484e06b827e28598a0f21149008492ce732e254e685d7c1b31c8"]",
-->             policyId = "CimXmlIndicationsProfilePolicy",
-->          },
-->          errMsg = (vmodl.LocalizableMessage) {
-->             dynamicType = <unset>,
-->             key = "com.vmware.vim.profile.host.UpdateError.ParameterNotSet.label",
-->             arg = (vmodl.KeyAnyValue) [
-->                (vmodl.KeyAnyValue) {
-->                   dynamicType = <unset>,
-->                   key = "paramName",
-->                   value = "sourceNamespaces",
-->                }
-->             ],
-->             message = "Parameter 'sourceNamespaces' cannot be left unset.",
-->          },
-->       }
-->    ],
-->    msg = "Cannot update the profile. Check the profile for errors.",
--> }
--> Args:
-->
--> Arg createSpec:
--> (vim.profile.host.HostProfile.HostBasedConfigSpec) {
-->    dynamicType = <unset>,
-->    name = "hostprofile-glenn",
-->    annotation = "hostprofile-glenn",
-->    enabled = true,
-->    host = 'vim.HostSystem:host-25',
-->    useHostProfileEngine = true,
--> }

Anyone, any ideas?

Reply
0 Kudos
1 Solution

Accepted Solutions
kristianaasen
Contributor
Contributor
Jump to solution

VMware has confirmed the bug and will have a fix in Update 1. Looks like this might be out at the end next week.

K

View solution in original post

Reply
0 Kudos
14 Replies
RHITSupport
Contributor
Contributor
Jump to solution

Have a similar problem after upgrading from esxi4.1 to esxi5.0.

One server the profile has worked the other it has failed with the same reason.

The only thing I can think of is I profiled the first before the HP CIM was put on.

Reply
0 Kudos
kristianaasen
Contributor
Contributor
Jump to solution

Having the same issue.

I have installed the HP CUM Bundle (and the 2 esxi 5.0 updates)

Kristian

Reply
0 Kudos
RHITSupport
Contributor
Contributor
Jump to solution

Have run re-run the host profile on the good esxi server with both updates and HP CIM loaded. Still works.

kristianaasen
Contributor
Contributor
Jump to solution

I'm getting this when i create a NEW host profile.

Not sure why i'm getting "cannot UPDATE the profile". I deleted the one I had from my 4.1u1 environment.

Kristian

Reply
0 Kudos
glenngahnstedt
Contributor
Contributor
Jump to solution

Yes, its very strange.

What really bothers me is: Parameter 'sourceNamespaces' cannot be left unset. Do you get this too? (vpxd.log)


I belive this is a bug, Would be great if a developer could give us input to this issue.
I have no earlier 4.1 profiles and no esxi5 profiles either. This would as mentioned earlier, be a new, first profile.

Reason I wanted to create a good host profile is to play around with Autodeploy. But thats impossible at the moment...


My setup is this:

Site: A  - 2 HP BLADES + vCenter in linked mode + SRM

Site: B  - 2 HP BLADES + vCenter in linked mode + SRM

EVA 4400

All hosts have the same issue when it comes to creating host profiles

Tomorrow I will try to first reinstall one of the hosts with a clean setup (no upgrade) and see if that might solve issue.

Else I will reinstall 1 vCenter server + 1 hosts. Where is the issue? I belive its a property that's unset on host, ESXi5 kernel level.

Reply
0 Kudos
kristianaasen
Contributor
Contributor
Jump to solution

Yes. I'm getting the Parameter 'sourceNamespaces' cannot be left unset. to.

Logging a support case now.

K

glenngahnstedt
Contributor
Contributor
Jump to solution

Thanks K,

Let me know how it goes Smiley Happy

Reply
0 Kudos
glenngahnstedt
Contributor
Contributor
Jump to solution

Problem solved

Just wanted to let everyone know that this issue was solved by reinstalling the host using the option:

  • Re-Install ESXi5 / Preserve VMFS --- this only took 15 min and is totally worth it.

I had HP Bundled ESXi 4.1 installed before upgrade which apparantly might/will give you problems creating host profiles after update from ESXi4 --> ESXi5. I know that Hewlett-Packard will release a new ESXi5 ISO soon which will solve a few known issues. I can only hope that this issue will be one of them.

@kristianaasen: Thanks for youe help buddy. Im sure this will be the conclusion as you have a VMware SR open.

Reply
0 Kudos
chh_sys
Contributor
Contributor
Jump to solution

I have the same problem here.

But was using VMwares iso to Update to vSphere 5, not the HP iso.

Reply
0 Kudos
glenngahnstedt
Contributor
Contributor
Jump to solution

Cheers! good to know.

Reply
0 Kudos
kristianaasen
Contributor
Contributor
Jump to solution

VMware has confirmed the bug and will have a fix in Update 1. Looks like this might be out at the end next week.

K

Reply
0 Kudos
glenngahnstedt
Contributor
Contributor
Jump to solution

Thanks for confirming kristianaasen, much appriciated.

Reply
0 Kudos
kristianaasen
Contributor
Contributor
Jump to solution

Or maybe not... Last email from SR-team:

---

Engineering have brought forward the release of the patch to resolve this issue to be released with Patch 2 for ESXi 5, rather than with Update 1.

I'm still waiting for confirmation from them as to whether or not they are going to be providing a hot patch to customers with the issue - as I believe Patch 2 for ESXi 5 is not due for release till the end of this year.

If creating a host profile is something you urgently need to do - at the moment - the work around is to do a fresh installation.

---

K

Reply
0 Kudos
cabralta
Contributor
Contributor
Jump to solution

I am using HP Branded ESXi installs and ran into the same issues. When I installed the following ESX patch to resolve a different issue it also cleared up the host profiles problem described here. ESXi500-201112401-SG is the patch id. Hopefully this helps someone.

Reply
0 Kudos