VMware Cloud Community
AllBlack
Expert
Expert

Unable to apply drs resourcse settings?

Hi,

I have an error on one of my nodes in the cluster. "Unable to apply DRS resource settings on host. The operation is not allowed in the current state"

Any ideas? I have googled but failed to find something. Where can I get a better idea of the "Current state"

Cheers

Please consider marking my answer as "helpful" or "correct"
Tags (1)
Reply
0 Kudos
16 Replies
weinstein5
Immortal
Immortal

what are you trying to do when you receive this error? Is thing in the events tab of the DRS cluster?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
AllBlack
Expert
Expert

That's the thing, I am not doing anything. I noticed the host was marked as "Red" and decided to look into it. The events show this error.

Please consider marking my answer as "helpful" or "correct"
Reply
0 Kudos
weinstein5
Immortal
Immortal

I am wondering if someone attempted to manage the host directly with the vi client - first I would try to restart the management agent - using the command service vmware-mgmt restart and see if that clears the alarm if that does not worrk see if you can place that node in maintenance mode - in preparation to remove it and readd it to the cluster - you will have vmotion or shut the running vms on theis node

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
AllBlack
Expert
Expert

Possible, every sysadmin has access too it.

This is really an ignorant question but I have never looked into the "service vmware-mgmt restart" command.

Does this interrupt the VMs itself? If so, I need to plan for it.

Cheers

Please consider marking my answer as "helpful" or "correct"
Reply
0 Kudos
weinstein5
Immortal
Immortal

It should not - but one of the earlier versions of 3.5 it did cause a reboot of all VMs - not sure which one but if you are Update 1 you will be fine -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Reply
0 Kudos
kjb007
Immortal
Immortal

I ran into this error during an upgrade of one of my hosts. It kept getting this error, and I managed to get rid of it, by putting the host in maintenance mode, then removing it from my cluster, removing from maintenance mode, and then adding it back in.

For some reason, the rules would not stick, until I remove and re-added, and in effect re-applied my resource settings.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos
alain_trinh
Contributor
Contributor

hi all,

you can try this command line : "service mgmt-vmware restart" that solved my pb

note: this error message appeared after an update towards virtual center 2.5 update 2

Regards

Reply
0 Kudos
jfk8680
Contributor
Contributor

Hi guys,

Had the same problem after patching one of my ESX hosts to version 120512. Restarting the service didn't solve the problem. Removing and re-adding the host did resolve this issue for me.

Thanks!

Jeffrey

Reply
0 Kudos
iwsmith
Contributor
Contributor

Restarting the mgmt-vmware service worked for me as well - very helpful as always!

Reply
0 Kudos
PeterEppich
Contributor
Contributor

ATTENTION:

I had the same problem as result of updating to build 130756.

I restarted mgmt-vmware service beliving(=unwise), that 3.5 SP2 will have no problems with this.

The Warning dissapeard after 1 Minute --> I was very happy (for a very short time...)

Suddenly after 3 minutes: ALL VIRTUAL MACHINES WERE RESTARTED.

That shoud not happen - right?

To all users: Please be more wise and ensure that all virtual machines are evacuated BEFORE restarting the mgmt-Service

Thanks,

Peter Eppich

Reply
0 Kudos
maggu
Contributor
Contributor

Go to the "Configuration" tab for the server, choose "Virtual Machine Startup/Shutdown" and then "Properties". Deselect "Allow virtual machines to start and stop automatically with the system", then "OK" and verify that it now says "Disabled" in the top line. Now you can restart mgmt-vmware without that happening.

Reply
0 Kudos
gurjitd
Contributor
Contributor

Hi

restarting mgmt-vmware service worked for me, thanks Smiley Happy

Regards

Gurjit Dhillon

Reply
0 Kudos
unexpected
Contributor
Contributor

I had the same problem after upgrading to built 226117. I tried disabling / enabling HA without success. The "service mgmt-vmware restart" cleared the error, but it came back after a few moments.

Restarting the host did not solve the problem and gave the same result as the restarting of the service.

I finally managed to solve the problem by removing the host from the cluster, connecting to the removed host with the VIC and deleting all resource pools on it. Afterwards I added the host back to the ESX cluster and the issue seemed to be solved.

Now let's see if it stays like this... fingers crossed.

Geek, tech-enthusiast & blogger @ | twittering @

Geek, tech-enthusiast, VCP3, VCP4 & blogger @ http://www.unexpected.be | twittering @ http://twitter.com/unexxx
Reply
0 Kudos
Cyberfed27
Hot Shot
Hot Shot

I had this same issue pop up.

Turns out one of the other admins DID try and manage a host directly with the VI client. Why would that cause this DRS issue to come up?

I was able to get rid the issue with the restart console command you guys listed.

Question I have is why does accessing a host directly via vi Client cause this issue?

Reply
0 Kudos
mediawide
Enthusiast
Enthusiast

VI Client is very easy to understad, we can restar magn serives to login console. is there any option to restart Management serives by using VI Client or Vcenter Client.

Thanks

Durgesh

Reply
0 Kudos
IvanSinyov
Contributor
Contributor

Hi,

I have the same problem with ESX 4.1 build 582267.

Restarting management services and readding host to cluster does not help.

Problem appears when I try to migrate VM from problem host or to it. At this moment CPU chart in VC shows 0% or more than 400%.

Reply
0 Kudos