Openshift 3 error: FailedScheduling Failed for reason Region and possibly others

Solution Unverified - Updated -

Issue

  • Error seen when trying to deploy pod.
Events:
  FirstSeen LastSeen    Count   From        SubobjectPath   Reason          Message
  ───────── ────────    ─────   ────        ─────────────   ──────          ───────
  35s       35s     1   {scheduler }            FailedScheduling    Failed for reason Region and possibly others
  42s       11s     5   {scheduler }            FailedScheduling    Failed for reason MatchNodeSelector and possibly others
  • Getting the following error when I try to force registry to sit on specific nodes.
  • Pods are stuck in pending state with event message showing FailedScheduling

Environment

  • Openshift Enterprise
    • 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content