following in mind:

* **JSON configuration files that contain fields with incorrect case will no longer be valid. You must correct these files before upgrading.** When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 and the API server will once again be enforcing...

        Exception cause2 = new RuntimeException("loop") {
            @Override
            public synchronized Throwable getCause() {
                return causeRef.get();
            }
        };
        causeRef.set(cause2);

        Plugin plugin = new Plugin();
        Exception cause = new PluginContainerException(plugin, null, null, cause2);
        cause2.initCause(cause);

     * The abort flag is set to false by default.
     *
     * @param url the URL where the crawling error occurred
     * @param message the error message
     * @param cause the underlying exception that caused this error
     */
    public DataStoreCrawlingException(final String url, final String message, final Throwable cause) {
        this(url, message, cause, false);
    }

  upgrading an existing pre-v1.6.4 cluster to Kubernetes v1.6.5 will cause an unintentional
  [overwrite of manual edits to GCP Health Checks](https://github.com/kubernetes/ingress/issues/842)
  managed by the GLBC Ingress Controller. This can cause the health checks to start failing,
  requiring you to reapply the manual edits.

   */
  protected final void notifyFailed(Throwable cause) {
    checkNotNull(cause);

    monitor.enter();
    try {
      State previous = state();
      switch (previous) {
        case NEW:
        case TERMINATED:
          throw new IllegalStateException("Failed while in state:" + previous, cause);
        case RUNNING:
        case STARTING:
        case STOPPING:

    }

    /**
     * Test constructor with cause only
     */
    public void test_constructor_withCause() {
        Exception cause = new IllegalArgumentException("Root cause");
        CrawlerSystemException exception = new CrawlerSystemException(cause);

        assertNotNull(exception);
        assertSame(cause, exception.getCause());
        // When constructed with cause only, message should be cause's toString()

                Throwable cause = exception.getCause();

                if (cause instanceof PluginContainerException) {
                    Throwable cause2 = cause.getCause();

                    if (cause2 instanceof NoClassDefFoundError) {
                        String message = cause2.getMessage();

     * @param message The detailed error message explaining the cause of the exception
     */
    public SsoProcessException(final String message) {
        super(message);
    }

    /**
     * Constructs a new SSO process exception with the specified detailed message and cause.
     *
     * @param message The detailed error message explaining the cause of the exception
     * @param cause The underlying exception that caused this SSO process exception

### Bug or Regression

- Fix deprecated version for pod_scheduling_duration_seconds that caused the metric to be hidden by default in 1.29. ([#123042](https://github.com/kubernetes/kubernetes/pull/123042), [@alculquicondor](https://github.com/alculquicondor)) [SIG Instrumentation and Scheduling]

        executor.shutdown();

        // Then - Verify no exceptions occurred
        if (!exceptions.isEmpty()) {
            fail("Concurrent operations caused exceptions: " + exceptions.get(0));
        }

        assertEquals(threadCount * opsPerThread, successCount.get(), "All operations should succeed");
    }

    /**