# Automatic\_requirements contradicting sched\_requirements **URL:** \ **Category:** Product Support\ **Created:** [August 30, 2019, 6:07am UTC](https://forum.opennebula.io/t/automatic-requirements-contradicting-sched-requirements/7609 "2019-08-30T06:07:38Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![sulaweyo](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/sulaweyo/32/4708_2.png) [@sulaweyo](https://forum.opennebula.io/u/sulaweyo)\ **Post date:** [August 30, 2019, 6:07am UTC](https://forum.opennebula.io/t/automatic-requirements-contradicting-sched-requirements/7609/1 "2019-08-30T06:07:38Z")
Hi, I sometimesi have the issue that instances ramped up via econe get automatic\_requirements set that contradict sched\_requirements and thus the instances stay pending. I have multiple instances that get started and it’s not like an image or template is affected as the same image via the same template works 99% of the time but sometimes my default cluster is not included int the automatic requirements. The interesting part of onevm show: SCHED\_REQUIREMENTS=“CLUSTER\_ID=0 & ! ID=34 & !ID=35” VIRTUAL MACHINE TEMPLATE AUTOMATIC\_DS\_REQUIREMENTS="“CLUSTERS/ID” @\> 102 | “CLUSTERS/ID” @\> 103 | “CLUSTERS/ID” @\> 106" AUTOMATIC\_REQUIREMENTS="(CLUSTER\_ID = 102 | CLUSTER\_ID = 103 | CLUSTER\_ID = 106) & !(PUBLIC\_CLOUD = YES)" You see that the instance is bound to cluster 0 but the automatic requirement does not include cluster 0 so the instance never gets scheduled. On the instances that work (same image, same template) cluster 0 is included and everything is fine. It looks a bit like it’s load related but can’t really put my finger on it yet, it just looks like that happens more often if a lot of instances get requested in a short period of time. I’m still on 5.14.15 as i did not yet find the time to upgrade (i will as soon as possible) and i’m running a 3 node ha setup. Any ideas would be highly appreciated.