systemctl stop atomic-openshift-master-api does not do graceful shutdown leading to service outage

Solution In Progress - Updated -

Issue

  • When we stop (or restart) the master-api service, it takes up to 20 seconds until the master gets removed in the 'kubernetes endpoint'. Thus the dns queries from all containers were going to the "stopped" master api for 20 seconds, which resulted in a lot of errors on my check tool.

Environment

  • Red Hat OpenShift Container Platform 3.3 and 3.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.