Extended.idling and unidling idling with a single service and DeploymentConfig [Conformance] should idle the service and DeploymentConfig properly

[ncdc]

From https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_gce/1638/consoleFull

• Failure [53.339 seconds]
idling and unidling
/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin8YATB3/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/test/extended/idling/idling.go:468
  idling
  /openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin8YATB3/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/test/extended/idling/idling.go:276
    with a single service and DeploymentConfig [Conformance]
    /openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin8YATB3/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/test/extended/idling/idling.go:264
      should idle the service and DeploymentConfig properly [It]
      /openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin8YATB3/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/test/extended/idling/idling.go:263

      Expected error:
          <*util.ExitError | 0xc421cfa030>: {
              Cmd: "oc idle --config=/tmp/extended-test-cli-idling-lr7hx-15j1n-user.kubeconfig --namespace=extended-test-cli-idling-lr7hx-15j1n --resource-names-file /tmp/openshift-extended-tests/idling-services-820636018",
              StdErr: "error: unable to mark service \"extended-test-cli-idling-lr7hx-15j1n/idling-echo\" as idled: endpoints \"idling-echo\" is forbidden: endpoint address 172.16.4.79 is not allowedDeploymentConfig \"extended-test-cli-idling-lr7hx-15j1n/idling-echo\" has been idled",
              ExitError: {
                  ProcessState: {
                      pid: 28512,
                      status: 256,
                      rusage: {
                          Utime: {Sec: 0, Usec: 264425},
                          Stime: {Sec: 0, Usec: 28687},
                          Maxrss: 49084,
                          Ixrss: 0,
                          Idrss: 0,
                          Isrss: 0,
                          Minflt: 13901,
                          Majflt: 0,
                          Nswap: 0,
                          Inblock: 0,
                          Oublock: 0,
                          Msgsnd: 0,
                          Msgrcv: 0,
                          Nsignals: 0,
                          Nvcsw: 2885,
                          Nivcsw: 65,
                      },
                  },
                  Stderr: nil,
              },
          }
          exit status 1
      not to have occurred

      /openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin8YATB3/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/test/extended/idling/idling.go:165

cc @sttts @deads2k @liggitt

[sttts]

Disabled this test in #14024 for the time being.

What we know until now:

It's a strange 403 on the endpoint, claiming that the PATCH from the idle cli command changes the ip addresses, although in the PATCH request body only an annotation is set. Maybe, we have yet another PATCH conflict problem. that would explain the flakiness. But that's just a guess right now.

[liggitt]

error comes from our endpoint_admission plugin, which thinks subsets are changing (and that the IP is restricted, and that the user doing the idling is not a superuser)

[DirectXMan12]

While I'm willing to help out with this, based on @liggitt's and @sttts's response, I'm not entirely convinced I should be the assignee.

[smarterclayton]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/15915/test_pull_request_origin_extended_conformance_gce/7631/#-idling-and-unidling-idling-with-a-single-service-and-deploymentconfig-conformance-should-idle-the-service-and-deploymentconfig-properly-suiteopenshiftconformanceparallel

I'd like to reenable this.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close