Skip to content
This repository has been archived by the owner on Apr 21, 2019. It is now read-only.

Federation Provider for Azuredns #219

Merged
merged 4 commits into from
Mar 18, 2018
Merged

Federation Provider for Azuredns #219

merged 4 commits into from
Mar 18, 2018

Conversation

xtophs
Copy link
Contributor

@xtophs xtophs commented Feb 2, 2018

What this PR does / why we need it:
Adds Azure DNS support to federation

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Fixes Issue #44874

Special notes for your reviewer:

Release note:


The federation provider for AzureDNS allows for using AzureDNS to manage DNS records for federated kubernetes clusters. The clusters do not have to run in Azure.

Running the provider requires

	• an active Azure subscription with a DNS zone configured. See Azure Docs on how to [configure a DNS Zone](https://docs.microsoft.com/en-us/azure/dns/dns-zones-records).
	• Service Principal credentials with permissions to manage the DNS Zone

To configure federation, you follow the steps at: https://kubernetes.io/docs/tasks/federation/set-up-cluster-federation-kubefed/

Note, that at this time, a cluster created with acs-engine may need kubernetes RBAC (not Azure RBAC) configured first. See detailed instructions link below.

The DNS provider needs a configuration file with the information to access the Azure Subscription. The format of the config file is:

[Global]
subscription-id = [Azure Subscription ID]
tenant-id = [Azure Tenant ID where the Service Principal is created]
client-id = [Service Principal Client ID]
secret = [Service Principal Secret]
resourceGroup = [Azure Resource Group where the DNS Zone is provisioned]

You can get Subscription ID and Tenant ID by running the following Azure CLI 2.0 command:

`az account show`


You can create a Service Principal with write access to the resource group:

`az ad sp create-for-rbac -n "http://MyApp" --role contributor --scopes /subscriptions/[subscription id]/resourceGroups/[resource group name]`

With the provider config file, you can initialize a federation:

`kubefed init myfederation --host-cluster-context=[cluster name] --dns-provider="azure-azuredns" --dns-zone-name="[dns Zone]" --dns-provider-config=[path to provider config file]`

Join a federation:

`kubefed join [your cluster name] --host-cluster-context=[your cluster name] --cluster-context=[your cluster name]`

And verify that the cluster was joined:

kubectl get clusters
NAME STATUS AGE
fed-west Ready 13s

For complete instructions setting up federated clusters in Azure see: https://github.com/xtophs/k8s-setup-federation-cluster

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 2, 2018
@xtophs xtophs force-pushed the azuredns branch 2 times, most recently from 8c37402 to 3682d9c Compare February 2, 2018 20:07
@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 2, 2018
@xtophs xtophs mentioned this pull request Feb 2, 2018
Closed
@irfanurrehman
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 3, 2018
@irfanurrehman
Copy link
Contributor

@xtophs please run hack/update-bazel.sh to update the relevant build files.
Post that run hack/verify-all.sh to find out remaining problems.
Please reach out to me if you still run into problems or find it difficult to correctly vendor the libs.

@xtophs
Copy link
Contributor Author

xtophs commented Feb 5, 2018

I had to manually update the azure libs. The versions of vendor/git.luolix.topAzure/... do not match what's required by vendor/k8s.io/pkg/cloudprovider/providers/azure. There's also a related issue that the azure libs were pulled in using glide: #220

Definitely would appreciate help @irfanurrehman

@xtophs xtophs mentioned this pull request Feb 6, 2018
Closed
@irfanurrehman
Copy link
Contributor

@xtophs do you use slack? What time zone are you in? I did send a personal message around the same time yesterday. If you prefer any other mechanism to talk; let me know.
Meanwhile, I checked and compared the code updated for the vendored Azure libs in this PR. It does not map to the Azure libs vendored in currently. We did vendor in k8s version mapping to 4aee60804874a7cd2533425ac81bc9ecbda5a38b and the libs, which include Azure libs mapped to (and still map to) this k8s hash.
This is the version of one of the libs mapped to k8s latest.
This is the version of k8s that we vendor in here. We intend to update this soon and some work is already done as part of #183.

It seems the Azure libs version you are adding here is not what is currently vendored in and also not the one that is there in k8s latest.
Which version are you actually using against your code? :-) . Does the code have tight dependency to the version of the libs?

#220 is probably a valid issue as of today and we will work out a mechanism to handle the same. IMHO the work in this PR however need not wait for that.

@maru did already point out the reasons of using glide earlier, which seemed genuine and applicable at that time.
We will update our vendoring mechanism also, but that will take some time.
cc @marun @quinton-hoole @shashidharatd

@irfanurrehman
Copy link
Contributor

@xtophs, where are you at with this? Were you able to figure your way around?
I remember posting steps for e2e on your earlier PR here.
I did organise your code a little bit, last week, expecting to talk to you on slack and to enable cleaner view and ensure that verify jobs pass, in my branch here. There still was a gofmt issue in your code which I did leave as is; you can fix it using hack/update-gofmt.sh
I am willing to help you correctly vendor any other additional dependencies that you might want (Not sure that is needed though as the code compiles successfully in this branch).
Please let me know if you run into more problems or would want me to help you with something more. I could not get response from you on slack ???

@xtophs
Copy link
Contributor Author

xtophs commented Feb 12, 2018

we missed each other on slack last week.

Same problem as before. Automated e2e tests only execute on gce. I still need someone with expertise to manually run the tests.

Help getting the right version of the azure SDK might be helpful as well. Looks at the Godeps shows it requires a very specific version https://github.com/kubernetes/kubernetes/blob/5927426100b0c5be51232d4147257fd5e09bce7d/Godeps/Godeps.json#L33 which doesn't seem to be compatible with vendor/k8s.io/kubernetes/cloudproviders/provider/azure

Would definitely like to see why it wasn't building in my fork. Then we can figure out how we handle dependencies. We do need to prune what's in vendor/azure-sdk-for-go. The dependencies were correct prior to the split. Now probably 90% of the code in there is not used.

I'll find you on slack and we can get this merged.

@grahamhayes grahamhayes mentioned this pull request Feb 19, 2018
Closed
@irfanurrehman
Copy link
Contributor

@xtophs We have progressed quite a lot in changing the vendoring mechanism and #237 (in flight) would soon merge.
Meanwhile, I would not want you to rebase and rework your code again, given that you already have done that once. Would it be possible for you to speed up the closure for this PR?
On the contrary, if there are any issues (do you forsee any) following this sequence:
1 - merge your PR.
2 - update the vendored code including the azure sdk.
Would u be available to help?

@shashidharatd do you have any alternative suggestion.

@xtophs
Copy link
Contributor Author

xtophs commented Feb 22, 2018 •
edited

Would love to wrap this up. Any one of you available to work through this tomorrow? (Friday)

xtophs and others added 4 commits March 2, 2018 18:25
@xtophs @irfanurrehman
Azure DNS Provider
58b43fb
@irfanurrehman
Update bazel files for Azure DNS provider
957307c
@irfanurrehman
Add vendor files for Azure dns provider
04dcc36 
Adds specific version (v12.1.0-beta) of github.com/Azure/azure-sdk-for-go
which maps to the vendored version of k8s (1.10.0-alpha.3).
@irfanurrehman
Issue fix: RecordSetsClient's ListByDNSZone() method adds param in ne…
f51018c 
…wer vendored version
@irfanurrehman
Copy link
Contributor

@xtophs why remove the earlier commits?, Whats the update ? Also Update to the e2e tests ideally needs to be done as a separate PR!

@xtophs
Copy link
Contributor Author

xtophs commented Mar 16, 2018

I haven't made any changes since January 10. No changes to e2e were necessary. We can remove fe869ff as it only enabled the Pending flag on the test to run.

@irfanurrehman
Copy link
Contributor

/test pull-federation-verify

@irfanurrehman
Copy link
Contributor

logs of e2e run on federated azure clusters federated using --dns-provider=azure-azuredns

e2e.test --kubeconfig=/root/work/azure/latest/kconf --provider=mine --federated-kube-context federation --ginkgo.focus="Federated\sServices\s\[Feature\:Federation" --test.v -v 5

root@irf-work:~/work/src/k8s.io/federation# e2e.test --kubeconfig=/root/work/azure/latest/kconf --provider=mine --federated-kube-context federation --ginkgo.focus="Federated\sServices\s\[Feature\:Federation" --test.v -v 5
=== RUN   TestE2E
I0318 23:36:14.993219   31995 e2e.go:322] Starting e2e run "0c5424b5-2ad7-11e8-8edd-fc3fdbfb485c" on Ginkgo node 1
Running Suite: Kubernetes e2e suite
===================================
Random Seed: 1521396374 - Will randomize all specs
Will run 9 of 47 specs

Mar 18 23:36:15.003: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
Mar 18 23:36:15.057: INFO: Waiting up to 4h0m0s for all (but 0) nodes to be schedulable
Mar 18 23:36:16.798: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Mar 18 23:36:18.154: INFO: 12 / 12 pods in namespace 'kube-system' are running and ready (1 seconds elapsed)
Mar 18 23:36:18.155: INFO: expected 5 pod replicas in namespace 'kube-system', 5 are Running and Ready.
Mar 18 23:36:18.377: INFO: Waiting for pods to enter Success, but no pods in "kube-system" match label map[name:e2e-image-puller]
Mar 18 23:36:18.378: INFO: Dumping network health container logs from all nodes...
Mar 18 23:36:18.623: INFO: Client version: v0.0.0-master+$Format:%h$
Mar 18 23:36:18.932: INFO: Server version: v1.9.2
SSSSSSSSSSSSSS
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters DNS 
  should be able to discover a federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:214
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:36:18.932: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Reading the federation configuration
Mar 18 23:36:18.938: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
Mar 18 23:36:18.945: INFO: >>> kubeContext: federation
STEP: Creating a release 1.5 federation Clientset
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-kzxzr
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:36:20.979: INFO: 2 clusters registered, waiting for 2
Mar 18 23:36:20.979: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:36:21.392: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:36:21.695: INFO: Cluster federation-sc is Ready
Mar 18 23:36:21.695: INFO: 2 clusters are Ready
Mar 18 23:36:21.695: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:36:21.701: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-kzxzr" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-kzxzr" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-kzxzr" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-kzxzr" exists in cluster "federation-sc"
[BeforeEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:178
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-east"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-east": {{ } {federated-service-test-pod  e2e-tests-federated-service-kzxzr /api/v1/namespaces/e2e-tests-federated-service-kzxzr/pods/federated-service-test-pod 11cbbba0-2ad7-11e8-a563-000d3a1b7460 370197 0 2018-03-18 23:36:23 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-bzbl9 {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-bzbl9,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-bzbl9 true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc420666410 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-sc"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-sc": {{ } {federated-service-test-pod  e2e-tests-federated-service-kzxzr /api/v1/namespaces/e2e-tests-federated-service-kzxzr/pods/federated-service-test-pod 1200d774-2ad7-11e8-98e8-000d3a72e8d5 369818 0 2018-03-18 23:36:24 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-s4lgd {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-s4lgd,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-s4lgd true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc42061a2b0 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-kzxzr"
STEP: try creating federated service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" with nodePort 31958
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:36:24.889: INFO: check if service "federated-service" have been created in 2 clusters
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-east" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-sc" found
STEP: Successfully created federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:36:25.522: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-kzxzr" in cluster is present
[It] should be able to discover a federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:214
STEP: Looking up "federated-service"
STEP: Creating pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:36:27.251: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-0)
STEP: Deleting pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr"
STEP: Creating pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:36:57.129: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-1)
STEP: Deleting pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:00.817: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-2)
STEP: Deleting pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.federation"
STEP: Creating pod "federated-service-e2e-discovery-pod-3" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-3" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:04.609: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-3)
STEP: Deleting pod "federated-service-e2e-discovery-pod-3" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-3" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.federation.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-4" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-4" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:08.503: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-4)
STEP: Deleting pod "federated-service-e2e-discovery-pod-4" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-4" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Verified that DNS rules are working as expected
STEP: Deleting the service to verify that DNS rules still work
STEP: Looking up "federated-service"
STEP: Creating pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:12.387: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-0)
STEP: Deleting pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr"
STEP: Creating pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:17.321: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-1)
STEP: Deleting pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:21.194: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-2)
STEP: Deleting pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.federation"
STEP: Creating pod "federated-service-e2e-discovery-pod-3" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-3" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:24.882: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-3)
STEP: Deleting pod "federated-service-e2e-discovery-pod-3" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-3" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Looking up "federated-service.e2e-tests-federated-service-kzxzr.federation.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-4" in namespace "e2e-tests-federated-service-kzxzr"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-4" in namespace "e2e-tests-federated-service-kzxzr"
Mar 18 23:37:28.492: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-4)
STEP: Deleting pod "federated-service-e2e-discovery-pod-4" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Deleted pod "federated-service-e2e-discovery-pod-4" from namespace "e2e-tests-federated-service-kzxzr"
STEP: Verified that deleting the service does not affect DNS records
[AfterEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:191
Mar 18 23:37:31.885: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-east" was deleted
Mar 18 23:37:32.268: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-kzxzr" in cluster "federation-sc" was deleted
STEP: No service to delete.  Service is nil
STEP: No service shards to delete. `serviceShard` is nil
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-kzxzr" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:37:48.231: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:89.911 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    DNS
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:170
      should be able to discover a federated service
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:214
------------------------------
SSSSSSSSS
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters Federated Service 
  should not be deleted from underlying clusters when OrphanDependents is nil
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:141
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:37:48.846: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-gwcmp
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:37:50.079: INFO: 2 clusters registered, waiting for 2
Mar 18 23:37:50.079: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:37:50.380: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:37:50.605: INFO: Cluster federation-sc is Ready
Mar 18 23:37:50.605: INFO: 2 clusters are Ready
Mar 18 23:37:50.606: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:37:50.612: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-gwcmp" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-gwcmp" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-gwcmp" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-gwcmp" exists in cluster "federation-sc"
[BeforeEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:94
[It] should not be deleted from underlying clusters when OrphanDependents is nil
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:141
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-gwcmp"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-gwcmp"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-gwcmp"
STEP: Waiting for service federated-service to be created in all underlying clusters
STEP: Deleting service federated-service
Mar 18 23:37:57.755: INFO: Deleting service "federated-service" in namespace e2e-tests-federated-service-gwcmp
STEP: Verifying services federated-service in underlying clusters
STEP: Verified that services were not deleted from underlying clusters
[AfterEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:99
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-gwcmp" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:38:20.181: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:31.644 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    Federated Service
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:88
      should not be deleted from underlying clusters when OrphanDependents is nil
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:141
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters Federated Service 
  should be deleted from underlying clusters when OrphanDependents is false
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:127
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:38:20.491: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-px26b
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:38:21.635: INFO: 2 clusters registered, waiting for 2
Mar 18 23:38:21.636: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:38:21.858: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:38:22.127: INFO: Cluster federation-sc is Ready
Mar 18 23:38:22.127: INFO: 2 clusters are Ready
Mar 18 23:38:22.127: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:38:22.133: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-px26b" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-px26b" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-px26b" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-px26b" exists in cluster "federation-sc"
[BeforeEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:94
[It] should be deleted from underlying clusters when OrphanDependents is false
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:127
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-px26b"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-px26b"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-px26b"
STEP: Waiting for service federated-service to be created in all underlying clusters
STEP: Deleting service federated-service
Mar 18 23:38:29.317: INFO: Deleting service "federated-service" in namespace e2e-tests-federated-service-px26b
STEP: Verifying services federated-service in underlying clusters
STEP: Verified that services were deleted from underlying clusters
[AfterEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:99
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-px26b" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:38:51.620: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:31.354 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    Federated Service
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:88
      should be deleted from underlying clusters when OrphanDependents is false
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:127
------------------------------
S
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters Federated Service 
  should create and update matching services in underlying clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:110
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:38:51.846: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-mjdbb
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:38:53.262: INFO: 2 clusters registered, waiting for 2
Mar 18 23:38:53.262: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:38:53.565: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:38:53.873: INFO: Cluster federation-sc is Ready
Mar 18 23:38:53.873: INFO: 2 clusters are Ready
Mar 18 23:38:53.873: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:38:53.879: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-mjdbb" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-mjdbb" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-mjdbb" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-mjdbb" exists in cluster "federation-sc"
[BeforeEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:94
[It] should create and update matching services in underlying clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:110
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
STEP: Wait for service shards to be created in all clusters for service "e2e-tests-federated-service-mjdbb/federated-service"
Mar 18 23:38:55.409: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster is present
Mar 18 23:38:56.024: INFO: Successfully created and synced service "e2e-tests-federated-service-mjdbb/federated-service" to all clusters
STEP: Update federated service "e2e-tests-federated-service-mjdbb/federated-service"
STEP: Successfully updated federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
Mar 18 23:38:56.637: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster is present
Mar 18 23:38:57.252: INFO: Successfully updated and synced service "e2e-tests-federated-service-mjdbb/federated-service" to clusters
STEP: Deleting service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
[AfterEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:99
STEP: Deleting service shards and their provider resources in underlying clusters for service "federated-service" in namespace "e2e-tests-federated-service-mjdbb"
Mar 18 23:38:57.778: INFO: Deleting service "federated-service" in 2 clusters
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster "federation-east" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster "federation-east" deleted
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster "federation-sc" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-mjdbb" in cluster "federation-sc" deleted
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-mjdbb" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:39:14.969: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:23.430 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    Federated Service
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:88
      should create and update matching services in underlying clusters
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:110
------------------------------
SSSSSS
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters DNS non-local federated service 
  should be able to discover a non-local federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:256
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:39:15.278: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-4qqj6
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:39:18.450: INFO: 2 clusters registered, waiting for 2
Mar 18 23:39:18.450: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:39:18.757: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:39:19.064: INFO: Cluster federation-sc is Ready
Mar 18 23:39:19.064: INFO: 2 clusters are Ready
Mar 18 23:39:19.064: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:39:19.070: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-4qqj6" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-4qqj6" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-4qqj6" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-4qqj6" exists in cluster "federation-sc"
[BeforeEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:178
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-east"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-east": {{ } {federated-service-test-pod  e2e-tests-federated-service-4qqj6 /api/v1/namespaces/e2e-tests-federated-service-4qqj6/pods/federated-service-test-pod 7acb07e9-2ad7-11e8-a563-000d3a1b7460 370726 0 2018-03-18 23:39:20 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-hw8kz {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-hw8kz,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-hw8kz true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc421026360 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-sc"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-sc": {{ } {federated-service-test-pod  e2e-tests-federated-service-4qqj6 /api/v1/namespaces/e2e-tests-federated-service-4qqj6/pods/federated-service-test-pod 7afb4124-2ad7-11e8-98e8-000d3a72e8d5 370159 0 2018-03-18 23:39:20 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-4lgnc {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-4lgnc,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-4lgnc true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc4208f4950 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-4qqj6"
STEP: try creating federated service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" with nodePort 31785
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-4qqj6"
Mar 18 23:39:20.908: INFO: check if service "federated-service" have been created in 2 clusters
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-east" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-sc" found
STEP: Successfully created federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-4qqj6"
Mar 18 23:39:21.526: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-4qqj6" in cluster is present
[BeforeEach] non-local federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:246
Mar 18 23:39:22.750: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-east" was deleted
[It] should be able to discover a non-local federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:256
STEP: Looking up "federated-service.e2e-tests-federated-service-4qqj6.federation"
STEP: Creating pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-4qqj6"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-4qqj6"
Mar 18 23:39:23.982: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-0)
STEP: Deleting pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-4qqj6"
STEP: Deleted pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-4qqj6"
STEP: Looking up "federated-service.e2e-tests-federated-service-4qqj6.federation.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-4qqj6"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-4qqj6"
Mar 18 23:44:58.564: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-1)
STEP: Deleting pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-4qqj6"
STEP: Deleted pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-4qqj6"
[AfterEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:191
Mar 18 23:45:22.703: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-east" does not exist. No need to delete it.
Mar 18 23:45:23.011: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-4qqj6" in cluster "federation-sc" was deleted
Mar 18 23:45:23.011: INFO: Deleting service "federated-service" in namespace e2e-tests-federated-service-4qqj6
STEP: No service shards to delete. `serviceShard` is nil
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-4qqj6" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:45:44.515: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:389.544 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    DNS
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:170
      non-local federated service
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:245
        should be able to discover a non-local federated service
        /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:256
------------------------------
S
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters Federated Service 
  should recreate service shard in underlying clusters when service shard is deleted
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:147
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:45:44.824: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-9ws29
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:45:45.823: INFO: 2 clusters registered, waiting for 2
Mar 18 23:45:45.823: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:45:46.062: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:45:46.363: INFO: Cluster federation-sc is Ready
Mar 18 23:45:46.363: INFO: 2 clusters are Ready
Mar 18 23:45:46.364: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:45:46.370: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-9ws29" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-9ws29" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-9ws29" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-9ws29" exists in cluster "federation-sc"
[BeforeEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:94
[It] should recreate service shard in underlying clusters when service shard is deleted
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:147
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-9ws29"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29"
STEP: Wait for service shards to be created in all clusters for service "e2e-tests-federated-service-9ws29/federated-service"
Mar 18 23:45:47.895: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-9ws29" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-9ws29" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster is present
Mar 18 23:45:48.613: INFO: Successfully created and synced service "e2e-tests-federated-service-9ws29/federated-service" to all clusters
STEP: Deleting a service shard in one underlying cluster
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster "federation-east" deleted
Mar 18 23:45:48.919: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-9ws29" from cluster
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster.  Found: false, waiting for Found: true, trying again in 2s (err=services "federated-service" not found)
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster.  Found: false, waiting for Found: true, trying again in 2s (err=services "federated-service" not found)
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster.  Found: false, waiting for Found: true, trying again in 2s (err=services "federated-service" not found)
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster.  Found: false, waiting for Found: true, trying again in 2s (err=services "federated-service" not found)
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster.  Found: false, waiting for Found: true, trying again in 2s (err=services "federated-service" not found)
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-9ws29" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster is present
Mar 18 23:45:59.876: INFO: Successfully recreated service shard "e2e-tests-federated-service-9ws29/federated-service" in "federation-east" cluster
STEP: Deleting service "federated-service" in namespace "e2e-tests-federated-service-9ws29"
[AfterEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:99
STEP: Deleting service shards and their provider resources in underlying clusters for service "federated-service" in namespace "e2e-tests-federated-service-9ws29"
Mar 18 23:46:00.388: INFO: Deleting service "federated-service" in 2 clusters
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster "federation-east" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster "federation-east" deleted
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster "federation-sc" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-9ws29" in cluster "federation-sc" deleted
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-9ws29" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:46:17.599: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:33.076 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    Federated Service
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:88
      should recreate service shard in underlying clusters when service shard is deleted
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:147
------------------------------
SS
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters DNS non-local federated service [Slow] missing local service 
  should never find DNS entries for a missing local service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:272
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:46:17.901: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-rl56l
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:46:19.065: INFO: 2 clusters registered, waiting for 2
Mar 18 23:46:19.065: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:46:19.333: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:46:19.641: INFO: Cluster federation-sc is Ready
Mar 18 23:46:19.641: INFO: 2 clusters are Ready
Mar 18 23:46:19.641: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:46:19.647: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-rl56l" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-rl56l" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-rl56l" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-rl56l" exists in cluster "federation-sc"
[BeforeEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:178
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-east"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-east": {{ } {federated-service-test-pod  e2e-tests-federated-service-rl56l /api/v1/namespaces/e2e-tests-federated-service-rl56l/pods/federated-service-test-pod 758611d4-2ad8-11e8-a563-000d3a1b7460 371401 0 2018-03-18 23:46:20 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-z65x4 {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-z65x4,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-z65x4 true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc4206bd000 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-sc"
STEP: Successfully created pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-sc": {{ } {federated-service-test-pod  e2e-tests-federated-service-rl56l /api/v1/namespaces/e2e-tests-federated-service-rl56l/pods/federated-service-test-pod 75b5d9cf-2ad8-11e8-98e8-000d3a72e8d5 370792 0 2018-03-18 23:46:21 +0530 IST <nil> <nil> map[foo:bar] map[] [] nil [] } {[{default-token-ntzff {nil nil nil nil nil &SecretVolumeSource{SecretName:default-token-ntzff,Items:[],DefaultMode:*420,Optional:nil,} nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil}}] [] [{federated-service-test-pod gcr.io/google_containers/echoserver:1.6 [] []  [] [] [] {map[] map[]} [{default-token-ntzff true /var/run/secrets/kubernetes.io/serviceaccount  <nil>}] [] nil nil nil /dev/termination-log File Always nil false false false}] Always 0xc4206bd430 <nil> ClusterFirst map[] default default <nil>  false false false &PodSecurityContext{SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,SupplementalGroups:[],FSGroup:nil,} []   nil default-scheduler [] []  <nil> nil} {Pending []     <nil> [] [] BestEffort}}
STEP: Creating federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-rl56l"
STEP: try creating federated service "federated-service" in namespace "e2e-tests-federated-service-rl56l" with nodePort 31979
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-rl56l"
Mar 18 23:46:21.585: INFO: check if service "federated-service" have been created in 2 clusters
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-east" found
STEP: Service "federated-service" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-sc" found
STEP: Successfully created federated service (type: load balancer) "federated-service" in namespace "e2e-tests-federated-service-rl56l"
Mar 18 23:46:22.098: INFO: Waiting for service "federated-service" in 2 clusters
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-rl56l" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-rl56l" in cluster is present
STEP: Fetching a federated service shard of service "federated-service" in namespace "e2e-tests-federated-service-rl56l" from cluster
STEP: Success: shard of federated service "federated-service" in namespace "e2e-tests-federated-service-rl56l" in cluster is present
[BeforeEach] non-local federated service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:246
Mar 18 23:46:23.257: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-east" was deleted
[It] should never find DNS entries for a missing local service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:272
STEP: Looking up "federated-service"
STEP: Creating pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-rl56l"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-0" in namespace "e2e-tests-federated-service-rl56l"
Mar 18 23:46:24.452: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-0)
STEP: Deleting pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-rl56l"
STEP: Deleted pod "federated-service-e2e-discovery-pod-0" from namespace "e2e-tests-federated-service-rl56l"
STEP: Looking up "federated-service.e2e-tests-federated-service-rl56l"
STEP: Creating pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-rl56l"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-1" in namespace "e2e-tests-federated-service-rl56l"
Mar 18 23:46:25.705: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-1)
STEP: Deleting pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-rl56l"
STEP: Deleted pod "federated-service-e2e-discovery-pod-1" from namespace "e2e-tests-federated-service-rl56l"
STEP: Looking up "federated-service.e2e-tests-federated-service-rl56l.svc.cluster.local."
STEP: Creating pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-rl56l"
STEP: Successfully created pod "federated-service-e2e-discovery-pod-2" in namespace "e2e-tests-federated-service-rl56l"
Mar 18 23:46:26.915: INFO: Cannot fetch pod logs: the server rejected our request for an unknown reason (get pods federated-service-e2e-discovery-pod-2)
STEP: Deleting pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-rl56l"
STEP: Deleted pod "federated-service-e2e-discovery-pod-2" from namespace "e2e-tests-federated-service-rl56l"
[AfterEach] DNS
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:191
Mar 18 23:46:27.831: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-east" does not exist. No need to delete it.
Mar 18 23:46:28.139: INFO: Deleting Pod "federated-service-test-pod" in namespace "e2e-tests-federated-service-rl56l" in cluster "federation-sc" was deleted
Mar 18 23:46:28.139: INFO: Deleting service "federated-service" in namespace e2e-tests-federated-service-rl56l
STEP: No service shards to delete. `serviceShard` is nil
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-rl56l" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:46:54.866: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:37.274 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    DNS
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:170
      non-local federated service
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:245
        [Slow] missing local service
        /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:271
          should never find DNS entries for a missing local service
          /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:272
------------------------------
[k8s.io] Federated Services [Feature:Federation] Without Clusters [NoCluster] 
  should succeed when a service is created
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:62
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:46:55.176: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-x7zzs
[BeforeEach] Without Clusters [NoCluster]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:53
[It] should succeed when a service is created
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:62
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-x7zzs"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-x7zzs"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-x7zzs"
STEP: Creation of service "federated-service" in namespace "e2e-tests-federated-service-x7zzs" succeeded.  Deleting service.
STEP: Deletion of service "federated-service" in namespace "e2e-tests-federated-service-x7zzs" succeeded.
[AfterEach] Without Clusters [NoCluster]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:58
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-x7zzs" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:47:13.086: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:18.227 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  Without Clusters [NoCluster]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:52
    should succeed when a service is created
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:62
------------------------------
SSSS
------------------------------
[k8s.io] Federated Services [Feature:Federation] with clusters Federated Service 
  should not be deleted from underlying clusters when OrphanDependents is true
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:134
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:106
STEP: Creating a kubernetes client
Mar 18 23:47:13.405: INFO: >>> kubeConfig: /root/work/azure/latest/kconf
[BeforeEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:70
STEP: Waiting for federation-apiserver to be ready
STEP: federation-apiserver is ready
STEP: Creating a federation namespace
STEP: Created federation namespace e2e-tests-federated-service-zqdpl
[BeforeEach] with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:77
STEP: Obtaining a list of all the clusters
Mar 18 23:47:14.630: INFO: 2 clusters registered, waiting for 2
Mar 18 23:47:14.630: INFO: Checking that 2 clusters are Ready
STEP: Checking readiness of cluster "federation-east"
Mar 18 23:47:14.938: INFO: Cluster federation-east is Ready
STEP: Checking readiness of cluster "federation-sc"
Mar 18 23:47:15.245: INFO: Cluster federation-sc is Ready
Mar 18 23:47:15.245: INFO: 2 clusters are Ready
Mar 18 23:47:15.245: INFO: Creating a clientset for the cluster federation-east
Mar 18 23:47:15.250: INFO: Creating a clientset for the cluster federation-sc
STEP: Waiting for namespace "e2e-tests-federated-service-zqdpl" to be created in cluster "federation-east"
STEP: Namespace "e2e-tests-federated-service-zqdpl" exists in cluster "federation-east"
STEP: Waiting for namespace "e2e-tests-federated-service-zqdpl" to be created in cluster "federation-sc"
STEP: Namespace "e2e-tests-federated-service-zqdpl" exists in cluster "federation-sc"
[BeforeEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:94
[It] should not be deleted from underlying clusters when OrphanDependents is true
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:134
STEP: Creating federated service "federated-service" in namespace "e2e-tests-federated-service-zqdpl"
STEP: Trying to create service "federated-service" in namespace "e2e-tests-federated-service-zqdpl"
STEP: Successfully created federated service "federated-service" in namespace "e2e-tests-federated-service-zqdpl"
STEP: Waiting for service federated-service to be created in all underlying clusters
STEP: Deleting service federated-service
Mar 18 23:47:22.413: INFO: Deleting service "federated-service" in namespace e2e-tests-federated-service-zqdpl
STEP: Verifying services federated-service in underlying clusters
STEP: Verified that services were not deleted from underlying clusters
[AfterEach] Federated Service
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:99
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/framework/framework.go:62
STEP: Destroying federation namespace "e2e-tests-federated-service-zqdpl" for this suite.
[AfterEach] [k8s.io] Federated Services [Feature:Federation]
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:107
Mar 18 23:47:44.806: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready

• [SLOW TEST:31.745 seconds]
[k8s.io] Federated Services [Feature:Federation]
/root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/k8s/e2e/framework/framework.go:413
  with clusters
  /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:76
    Federated Service
    /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:88
      should not be deleted from underlying clusters when OrphanDependents is true
      /root/work/src/k8s.io/federation/_output/local/go/src/k8s.io/federation/test/e2e/service.go:134
------------------------------
SMar 18 23:47:45.151: INFO: Running AfterSuite actions on all node
Mar 18 23:47:45.151: INFO: Running AfterSuite actions on node 1

Ran 9 of 47 Specs in 690.155 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 38 Skipped --- PASS: TestE2E (690.16s)

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irfanurrehman, xtophs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2018
@k8s-ci-robot k8s-ci-robot merged commit 3468d22 into kubernetes-retired:master Mar 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@xtophs @k8s-ci-robot @irfanurrehman