text:
cache strategy with staleWhileRevalidate and broadcastUpdate

I'm using staleWhileRevalidate()
my code
workbox.routing.registerRoute (
      new RegExp ('https://api-production.vimbo.com/v1/*'),
     workbox.strategies.staleWhileRevalidate ({
          plugins: [
             new workbox.broadcastUpdate.Plugin ('api-updates', {
                 headersToCheck: ['last-modified'],
             })
          ]
      })
  );
On my client, I'm getting the change notification

my question, is this cache update made automated after being notified?
Do I need to do something to force caching?

@jeffposnick or @philipwalton can you help me ?

The cache updates (the "revalidate" step in stale-while-revalidate") happen automatically. The broadcast of the change notification will only happen after a revalidate takes place, and only if the response fetch()ed during the revalidation differed from the previously cached response.

perfect @jeffposnick  , but in my case this is not happening well.
I'm working with the value in header last-modified
step by step
1 - I got to the list of records, where it cached the values, including the last-modified header value.
2 - clicked edit and saved
3 - I was redirected to listing, where he made a new http request
Note: When it came back in the list, in step 3, it performed http again, actually it noticed that it changed the last-modified field, however I am already in the list and without the updated data, hence I have to force an update on the page by pressing F5.

probably similar to this
https://github.com/GoogleChrome/workbox/issues/1498

Good point—can you check to see if the Last-Modified header isn't being exposed when accessing the CORS response due to the scenario outlined in #1498?

I did recently chat with someone who was able to successfully use StaleWhileRevalidate and the BroadcastUpdatePlugin, so I think it's working in general.
If you need more control over determining what triggers a broadcast, I'd recommend adding in your own custom Workbox plugin that implemented the cacheDidUpdate callback, and you can examine whatever properties of the old and newly cached responses you need inside of that.

authors: GlauberF MohammadSabbagh jeffposnick

repo: GoogleChrome/workbox


text:
Default values at the docs

Issue or Feature Request Description:
request: list the default values in the docs of GenerateSW

Thanks for raising this–we do have the default values in the JSDocs, from which our documentation is derived, but the JSDoc to HTML publishing flow that we're currently using ends up dropping them.
We have some updates to this flow planned, and I think we can get it addressed.

Thanks for raising this–we do have the default values in the JSDocs, from which our documentation is derived, but the JSDoc to HTML publishing flow that we're currently using ends up dropping them.
We have some updates to this flow planned, and I think we can get it addressed.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team

source: gharchive/issue

authors: jeffposnick rrd108 tomayac

license: mit

license_type: permissive

license_source: bigquery


text:
[WPT_ChromeDriver] Unstable test test_multiple_top_level_contexts[window\]

The test test_multiple_top_level_contexts[window\] is unstable in the ChromeDriver. Should be investigated.

Successful run.
Failed run.

authors: sadym-chromium thiagowfx

repo: GoogleChromeLabs/chromium-bidi


text:
File location confusion

The repository has a src/ directory with .js files
The distributed package has a dist/ directory with .js and .mjs files
The README suggests using /node_modules/kv-storage/index.mjs which exists in neither case.
What's the plan?

Ah - need to modify the readme.

Readme modified for now, but it'd be nice to get rid of dist.

authors: developit domenic

repo: GoogleChromeLabs/kv-storage-polyfill


text:
Update retrofill to support non-Chrome browsers

The retrofill algorithm should support UA creation for non-Chrome browsers like Opera / Edge. But when we resolved #25, we limited retrofill for Chrome. As we get clarity around the UA reduction plans for other Chrome browsers, we should update retrofill accordingly.
Particularly when support for Full-Version-List lands (https://crbug.com/1249246), we can create a UA that better reflects current UA for non-Chrome browsers. So, the algorithm will need an update.

Current status of Chromium-based browsers when it comes to the navigator.userAgentData API (which we rely on here, not Accept-CH header) - testing with https://user-agent-client-hints.glitch.me/
Brave 1.46 (?): has support, and sends Brave in the brand list (no support for HTTP CH)
Opera 94: has support, and sends Opera in the brand list (does have support for HTTP CH)
Edge 108: has support, and sends Microsoft Edge in the brand list (does have support for HTTP CH)
Naver 3.18: has support, and sends Whale in the brand list (does have support for HTTP CH)
Vivaldi 5.6: has support, but only sends Chromium in the brand list (in addition to GREASE) (does have support for HTTP CH)

authors: bvattikonda miketaylr

repo: GoogleChromeLabs/uach-retrofill


text:
[dask] Add dask-ml and dask-bigquery packages by default

add dask ml and dask big query

/gcbrun

2.0 image test fails with:
gcloud compute ssh test-dask-standard-2-0-20220203-165321-bept-m --zone=us-central1-b --command="/opt/conda/default/bin/python verify_dask_standalone.py"
STDOUT:

STDERR:
Traceback (most recent call last):
  File "verify_dask_standalone.py", line 4, in <module>
    import dask_bigquery
  File "/opt/conda/default/lib/python3.8/site-packages/dask_bigquery/__init__.py", line 1, in <module>
    from .core import read_gbq
  File "/opt/conda/default/lib/python3.8/site-packages/dask_bigquery/core.py", line 11, in <module>
    from dask.layers import DataFrameIOLayer
ModuleNotFoundError: No module named 'dask.layers'

Please, fix.

@medb I created a few clusters with Dask init action they all work fine, I think the test case is wrong and provided a fix, could you please run it again?

Failed with the same error:
FAILED (failures=1)
================================================================================
==================== Test output for //dask:test_dask (shard 3 of 3):
/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/dask/test_dask.py:57: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if runtime is "standalone":
Running tests under Python 3.8.10: /usr/bin/python3
[ RUN      ] DaskTestCase.test_dask('STANDARD', ['m', 'w-0'], 'standalone')
[  FAILED  ] DaskTestCase.test_dask('STANDARD', ['m', 'w-0'], 'standalone')
======================================================================
FAIL: test_dask('STANDARD', ['m', 'w-0'], 'standalone') (__main__.DaskTestCase)
test_dask('STANDARD', ['m', 'w-0'], 'standalone') (__main__.DaskTestCase)
test_dask('STANDARD', ['m', 'w-0'], 'standalone')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/io_abseil_py/absl/testing/parameterized.py", line 265, in bound_param_test
    test_method(self, *testcase_params)
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/dask/test_dask.py", line 58, in test_dask
    self.verify_dask_standalone(name)
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/dask/test_dask.py", line 21, in verify_dask_standalone
    self._run_dask_test_script(name, self.DASK_STANDALONE_TEST_SCRIPT)
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/dask/test_dask.py", line 29, in _run_dask_test_script
    self.assert_instance_command(name, verify_cmd)
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/integration_tests/dataproc_test_case.py", line 253, in assert_instance_command
    ret_code, stdout, stderr = self.assert_command(
  File "/home/ia-tests/.cache/bazel/_bazel_ia-tests/83b1ae36bb04ea5432b9efccee83c25f/execroot/__main__/bazel-out/k8-fastbuild/bin/dask/test_dask.runfiles/__main__/integration_tests/dataproc_test_case.py", line 305, in assert_command
    self.assertEqual(
AssertionError: 1 != 0 : Failed to execute command:
gcloud compute ssh test-dask-standard-2-0-20220204-010842-h1y9-m --zone=us-central1-b --command="/opt/conda/default/bin/python verify_dask_standalone.py"
STDOUT:

STDERR:
Traceback (most recent call last):
  File "verify_dask_standalone.py", line 4, in <module>
    import dask_bigquery
  File "/opt/conda/default/lib/python3.8/site-packages/dask_bigquery/__init__.py", line 1, in <module>
    from .core import read_gbq
  File "/opt/conda/default/lib/python3.8/site-packages/dask_bigquery/core.py", line 11, in <module>
    from dask.layers import DataFrameIOLayer
ModuleNotFoundError: No module named 'dask.layers'

----------------------------------------------------------------------
Ran 1 test in 308.140s

@medb I just realize that conda had issue to resolve the right dask version, I have to fix the version, it should fix the error now.

source: gharchive/pull-request

authors: medb mengdong


text:
Clarify this repo vs. google-cloud-java/google-cloud-trace

https://github.com/GoogleCloudPlatform/google-cloud-java/tree/master/google-cloud-trace
What's the purpose of this repo vs. that one?

I suspect that one may be for v2 of the cloud trace API.

authors: danielcompton wsh

repo: GoogleCloudPlatform/cloud-trace-java


text:
Accounts daemon updates the OS Login NSS cache.

This includes testing for updates to the OS Login NSS cache.

Blocked by #561.


text:
Add Server 2025 to VSS allowlist

Add Server 2025 to VSS allowlist

/lgtm

authors: bkatyl zmarano

repo: GoogleCloudPlatform/compute-image-tools


text:
feat: GCS Based Templates Should Support All SparkSQL CSV Options

This request changes all Python templates that read from or write to Cloud Storage to support all CSV options supported by Spark. Listed here: https://spark.apache.org/docs/latest/sql-data-sources-csv.html#data-source-option
Because I didn't want to add the same code in multiple places I've refactored all templates to use central functions for adding CSV options to dataframes.
Example change for reading from Cloud Storage
Previous code:
        input_data: DataFrame

        if input_file_format == constants.FORMAT_PRQT:
            input_data = spark.read \
                .parquet(input_file_location)
        elif input_file_format == constants.FORMAT_AVRO:
            input_data = spark.read \
                .format(constants.FORMAT_AVRO_EXTD) \
                .load(input_file_location)
        elif input_file_format == constants.FORMAT_CSV:
            input_data = spark.read \
                .format(constants.FORMAT_CSV) \
                .option(constants.HEADER, True) \
                .option(constants.INFER_SCHEMA, True) \
                .load(input_file_location)
        elif input_file_format == constants.FORMAT_JSON:
            input_data = spark.read \
                .json(input_file_location)

New code:
        spark_read_options = spark_options_from_template_args(args, constants.GCS_BT_INPUT_SPARK_OPTIONS)
        input_data = ingest_dataframe_from_cloud_storage(
            spark, input_file_format, input_file_location, spark_read_options
        )

And same technique for writing to Cloud Storage.
Previous code:

        if gcs_output_format == constants.FORMAT_PRQT:
            writer \
                .parquet(gcs_output_location)
        elif gcs_output_format == constants.FORMAT_AVRO:
            writer \
                .format(constants.FORMAT_AVRO) \
                .save(gcs_output_location)
        elif gcs_output_format == constants.FORMAT_CSV:
            writer \
                .option(constants.HEADER, True) \
                .csv(gcs_output_location)
        elif gcs_output_format == constants.FORMAT_JSON:
            writer \
                .json(gcs_output_location)

New code:
        spark_write_options = spark_options_from_template_args(args, constants.GCS_TO_GCS_OUTPUT_SPARK_OPTIONS)
        persist_dataframe_to_cloud_storage(writer, gcs_output_format, gcs_output_location, spark_write_options)

This removes a lot of duplication.
The Spark options themselves are driven by constants, see SPARK_OPTIONS.
The tmeplate options are also driven by constants mapping them back to Spark options, e.g: GCS_BQ_INPUT_SPARK_OPTIONS
After merging this I need to raise an equivalent issue for the Java templates.

please review optional parameters in readmes

@shashank-google , I've modified several READMEs to highlight new attributes as optional as requested.
Unit and integration tests have run cleanly.

@NiloFreitas I have created a new PR based on your suggested modifications on branch issue-532-csv-options-refactor.
When we are done with the other PR I'll delete this one.

repo: GoogleCloudPlatform/dataproc-templates


text:
build[Spanner]: Update Google.Cloud.Spanner.Data dependencies

And fix a sample that was not using the intended transaction. Caught because of transaction inlining.

@jskeet I created a separate PR for updating Spanner dependencies because an existing sample needed fixing.

Closing, I'll do dependency updates and samples all in #2550 in separete commits. It's just easier to manage.

repo: GoogleCloudPlatform/dotnet-docs-samples


text:
Fix kotlin-springboot-appengine-standard deploy error in periodic tests.

Periodic tests are failing for getting-started-java because the kotlin-springboot-appengine-standard project fails to deploy. This is because the kotlin reflect library is needed as a dependency - when deploying locally, I was getting ClassNotFoundExceptions on kotlin's KClasses
Also kotlin-stdlib-jre8 is deprecated and should be replaced with kotlin-stdlib-jdk8.

@dpebot Merge when green


text:
Vision and Speech snippets?

So there are a couple ways that snippets are run right now.
The old way with {service}-snippets.py or the way @dhermes has done with doctest for datastore.
Are we for sure going to use doctest and head down that route?

I am :+1: for the approach set forth in datastore (as @daspecster already linked). Obviously, as the author, this is my preference.
I'm open to @tseaver and @lukesneeringer opinions.

Glancing at this code very briefly and early in the morning, it looks like it:

Compiles docs using Sphinx based on the code.
Runs in :: code.. snippets it finds and complains if any of them error.

Seems reasonable in principle. I would be interested in a way to make that not datastore-specific (but in the meantime...)

@lukesneeringer Putting it in system_tests/datastore.py was intentional: we want to make sure the snippets aren't "right with mock, wrong with actual code". So the only datastore specific pieces in that class are fairly easy to factor out (just used for listing all modules in the datastore package and for creating a temporary directory with a simple Sphinx conf containing only datastore modules)

Okay. Seems fine to me.

OK SGTM. Onward and forward!

@tseaver I just realized you hadn't weighed in. Feel free to reopen if you have some feedback!

authors: daspecster dhermes lukesneeringer

repo: GoogleCloudPlatform/google-cloud-python

license_source: github-api


text:
Add samples for speech diarization ga (auto-punctuation samples alrea…

…dy on v1)

@kurtisvg, mind merging when you get a chance?
Thanks

repo: GoogleCloudPlatform/java-docs-samples


text:
Add Mesh with multiple tcproutes e2e test

Setup

Create Mesh
Create multiple tcproutes and link them to the mesh
Create 2 backend services with healthcheck per tcproute and add them to tcproutes

Changes

Delete  backend service
Delete 1 of tcproutes (a one that backend service was removed from)

Expectations

Ensure that changes affect only tcproutes they modify

b/332473866

/cc @kl52752

/hold

/retest

/hold-remove

/retest

What is the next step here?

/retest

What is the next step here?

I am writing one pager with description of a small bug I found and proposed solution (however the fix breaks our unit tests, so it also need to be updated).

/retest

/retest

/cc @mag-kol

/cc @bowei

/approve
/remove-lgtm

Can you rebase to get rid of the merge commit?

Please rebase and put your commits on top to get rid of merge commits https://screenshot.googleplex.com/3vXpW8QE4PsybEQ

/retest

Please rebase and put your commits on top to get rid of merge commits https://screenshot.googleplex.com/3vXpW8QE4PsybEQ

Done

/lgtm
/approve

authors: akwi-github bowei kl52752


text:
kubectl create -f with filename is broken

➜  kubernetes git:(master) ✗ cat t
{
  "apiVersion": "v1beta3",
  "kind": "Pod",
  "metadata": {
    "name": "kube-scheduler"
  },
  "spec": {
    "hostNetwork": true,
    "containers": [
      {
        "name": "kube-scheduler",
        "image": "$SCHEDULER_IMAGE",
        "command": [
          "/bin/sh",
          "-c",
          "/usr/local/bin/kube-scheduler --master=127.0.0.1:8080"
        ],
        "livenessProbe": {
          "httpGet": {
            "path": "/healthz",
            "port": 10251
          },
          "initialDelaySeconds": 15,
          "timeoutSeconds": 15
        }
      }
    ]
  }
}

➜  kubernetes git:(master) ✗ k --v=10 create -f t
F0707 11:52:58.810549  109429 helpers.go:72] error: you must provide one or more resources by argument or filename

➜  kubernetes git:(master) ✗ curl -k -v -XPOST  -H "User-Agent: kubectl/v0.18.0 (linux/amd64) kubernetes/530bff3" http://127.0.0.1:8080/api/v1beta3/namespaces/default/pods -d @t
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> POST /api/v1beta3/namespaces/default/pods HTTP/1.1
> Host: 127.0.0.1:8080
> Accept: */*
> User-Agent: kubectl/v0.18.0 (linux/amd64) kubernetes/530bff3
> Content-Length: 557
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 557 out of 557 bytes
< HTTP/1.1 201 Created
< Content-Type: application/json
< Date: Tue, 07 Jul 2015 18:50:50 GMT
< Content-Length: 1009
<
* Connection #0 to host 127.0.0.1 left intact
{"kind":"Pod","apiVersion":"v1beta3","metadata":{"name":"kube-scheduler","namespace":"default","selfLink":"/api/v1beta3/namespaces/default/pods/kube-scheduler","uid":"16224f98-24d9-11e5-9823-8cdcd43413f0","resourceVersion":"161","creationTimestamp":"2015-07-07T18:50:50Z"},"spec":{"volumes":[{"name":"default-token-hi5ia","secret":{"secretName":"default-token-hi5ia"}}],"containers":[{"name":"kube-scheduler","image":"$SCHEDULER_IMAGE","command":["/bin/sh","-c","/usr/local/bin/kube-scheduler --master=127.0.0.1:8080"],"resources":{},"volumeMounts":[{"name":"default-token-hi5ia","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"livenessProbe":{"httpGet":{"path":"/healthz","port":10251,"scheme":"HTTP"},"initialDelaySeconds":15,"timeoutSeconds":15},"terminationMessagePath":"/dev/termination-log","imagePullPolicy":"IfNotPresent","capabilities":{}}],"restartPolicy":"Always","dnsPolicy":"ClusterFirst","serviceAccount":"default","hostNetwork":true},"status":{"phase":"Pending"}}

It works when I pipe but not with filename. @jlowdermilk @bgrant0607
➜  kubernetes git:(master) ✗ cat t | k create -f -
pods/kube-scheduler
➜  kubernetes git:(master) ✗ k create -f t
error: you must provide one or more resources by argument or filename

broke int this commit https://github.com/GoogleCloudPlatform/kubernetes/commit/697e07f864a09a4346475ef00d602b522aea564a cc @andronat

Did you try to add an extension .json to the file? We filter for file extension

ahhh ok. so working as intended. it used to autodetect :( ... thanks @andronat

That was unintended.
The file extensions should only be used for deciding which files in a directory to process. For a single file, any extension should be allowed.
We don't actually infer the content type from the extensions. For stdin and http sources, for instance, there are no extensions.
cc @jlowdermilk

Fix is pretty straightforward (ignore file extensions when dealing with single file); I have it working with manual test, just adding unit test. Will send shortly.

Thanks, but this is v1.0-post, so no rush

authors: andronat bgrant0607 jlowdermilk mikedanese

repo: GoogleCloudPlatform/kubernetes


text:
Flake: mirror pod not found

Seen here: https://app.shippable.com/builds/551b33890f3ae40d00e932a6
PATH=$HOME/gopath/bin:./third_party/etcd:$PATH KUBE_TEST_API_VERSIONS=$KUBE_TEST_API_VERSIONS ./hack/test-integration.sh
+++ [0331 23:56:57] Building go targets for linux/amd64:
    cmd/integration
+++ [0331 23:57:01] Placing binaries

etcd -data-dir /tmp/test-etcd.NOhobw --bind-addr 127.0.0.1:4001 >/dev/null 2>/dev/null

Waiting for etcd to come up.
+++ [0331 23:57:02] etcd:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100    87  100    87    0     0     68      0  0:00:01  0:00:01 --:--:--    68
{"action":"set","node":{"key":"/_test","value":"","modifiedIndex":3,"createdIndex":3}}
+++ [0331 23:57:03] Running integration test cases
Running tests for APIVersion: v1beta1
+++ [0331 23:57:03] Running unit tests without code coverage
ok  	github.com/GoogleCloudPlatform/kubernetes/test/integration	11.737s
+++ [0331 23:57:25] Running integration test scenario
I0331 23:57:25.236929   26985 integration.go:906] Running tests for APIVersion: v1beta1
I0331 23:57:25.239710   26985 integration.go:131] Creating etcd client pointing to []
W0331 23:57:25.254589   26985 master.go:192] Portal net unspecified. Defaulting to 10.0.0.0/24.
I0331 23:57:25.342851   26985 factory.go:78] creating scheduler from algorithm provider 'DefaultProvider'
I0331 23:57:25.343027   26985 factory.go:128] creating scheduler with fit predicates 'map[NoDiskConflict:{} MatchNodeSelector:{} HostName:{} PodFitsPorts:{} PodFitsResources:{}]' and priority functions 'map[LeastRequestedPriority:{} ServiceSpreadingPriority:{}]
I0331 23:57:25.345450   26985 nodecontroller.go:99] Sending events to api server.
I0331 23:57:25.419754   26985 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{127.0.0.1 <nil>}] [{ 43229 TCP}]}]}
I0331 23:57:25.424505   26985 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{127.0.0.1 <nil>}] [{ 43229 TCP}]}]}
I0331 23:57:25.427867   26985 nodecontroller.go:196] Registered node in registry: localhost
I0331 23:57:25.435639   26985 nodecontroller.go:196] Registered node in registry: 127.0.0.1
I0331 23:57:25.435705   26985 nodecontroller.go:201] Successfully registered all nodes
I0331 23:57:25.439843   26985 integration.go:233] Using /tmp/kubelet_integ_1.254803615 as root dir for kubelet #1
I0331 23:57:25.442184   26985 server.go:348] Sending events to api server.
I0331 23:57:25.444210   26985 server.go:391] Adding manifest file: /tmp/kubelet_integ_1.254803615/config189216626
I0331 23:57:25.444330   26985 file.go:47] Watching path "/tmp/kubelet_integ_1.254803615/config189216626"
I0331 23:57:25.444378   26985 server.go:397] Adding manifest url: http://127.0.0.1:33079/manifest
I0331 23:57:25.444431   26985 http.go:48] Watching URL http://127.0.0.1:33079/manifest
I0331 23:57:25.444450   26985 server.go:401] Watching apiserver
I0331 23:57:25.446220   26985 plugins.go:136] Loaded volume plugin "kubernetes.io/empty-dir"
I0331 23:57:25.446252   26985 plugins.go:136] Loaded volume plugin "empty"
E0331 23:57:25.446510   26985 kubelet.go:541] Image garbage collection failed: invalid capacity 0 on device "" at mount point ""
I0331 23:57:25.446652   26985 integration.go:240] Using /tmp/kubelet_integ_2.111047209 as root dir for kubelet #2
I0331 23:57:25.446790   26985 server.go:348] Sending events to api server.
I0331 23:57:25.446712   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"localhost", UID:"localhost", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'starting' Starting kubelet.
I0331 23:57:25.446863   26985 server.go:397] Adding manifest url: http://127.0.0.1:40206/manifest
I0331 23:57:25.446858   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"localhost", UID:"localhost", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'invalidDiskCapacity' invalid capacity 0 on device "" at mount point ""
I0331 23:57:25.450374   26985 plugins.go:56] Registering credential provider: .dockercfg
I0331 23:57:25.450391   26985 server.go:62] Starting to listen on 127.0.0.1:10250
I0331 23:57:25.450709   26985 http.go:48] Watching URL http://127.0.0.1:40206/manifest
I0331 23:57:25.450773   26985 server.go:401] Watching apiserver
I0331 23:57:25.459132   26985 plugins.go:136] Loaded volume plugin "kubernetes.io/empty-dir"
I0331 23:57:25.459169   26985 plugins.go:136] Loaded volume plugin "empty"
I0331 23:57:25.459237   26985 integration.go:913] API Server started on http://127.0.0.1:43229
I0331 23:57:25.459234   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"127.0.0.1", UID:"127.0.0.1", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'starting' Starting kubelet.
E0331 23:57:25.459306   26985 kubelet.go:541] Image garbage collection failed: invalid capacity 0 on device "" at mount point ""
I0331 23:57:25.459406   26985 server.go:62] Starting to listen on 127.0.0.1:10251
I0331 23:57:25.459530   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"127.0.0.1", UID:"127.0.0.1", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'invalidDiskCapacity' invalid capacity 0 on device "" at mount point ""
I0331 23:57:25.501884   26985 plugins.go:56] Registering credential provider: .dockercfg
I0331 23:57:25.513672   26985 kubelet.go:1125] No Infra Container for "container-vm-guestbook-pod-spec-localhost_default" found. All containers will be restarted.
I0331 23:57:25.514082   26985 kubelet.go:1295] Creating pod infra container for "container-vm-guestbook-pod-spec-localhost_default"
I0331 23:57:25.514603   26985 kubelet.go:1125] No Infra Container for "container-vm-guestbook-manifest-127_default" found. All containers will be restarted.
I0331 23:57:25.515096   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:25.515284   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.95c401b9_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_15780d1b
I0331 23:57:25.515357   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.95c401b9_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_15780d1b
I0331 23:57:25.515699   26985 kubelet.go:1295] Creating pod infra container for "container-vm-guestbook-manifest-127_default"
I0331 23:57:25.517672   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:25.517780   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.95c401b9_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_13616d68
I0331 23:57:25.517819   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.95c401b9_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_13616d68
I0331 23:57:25.519239   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{redis}"}): reason: 'created' Created with docker id /k8s_redis.7dae02bc_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_d3694090
I0331 23:57:25.519359   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{redis}"}): reason: 'started' Started with docker id /k8s_redis.7dae02bc_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_d3694090
I0331 23:57:25.520715   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{redis}"}): reason: 'created' Created with docker id /k8s_redis.7dae02bc_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_bd4b9ae5
I0331 23:57:25.523358   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{guestbook}"}): reason: 'created' Created with docker id /k8s_guestbook.305e1366_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_7550ffc7
I0331 23:57:25.523554   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-pod-spec-localhost", UID:"6d01d7f5b1a20f71132ffa774f58b68f", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{guestbook}"}): reason: 'started' Started with docker id /k8s_guestbook.305e1366_container-vm-guestbook-pod-spec-localhost_default_6d01d7f5b1a20f71132ffa774f58b68f_7550ffc7
I0331 23:57:25.523603   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{redis}"}): reason: 'started' Started with docker id /k8s_redis.7dae02bc_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_bd4b9ae5
I0331 23:57:25.523671   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{guestbook}"}): reason: 'created' Created with docker id /k8s_guestbook.305e1366_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_acfe6813
I0331 23:57:25.523713   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"container-vm-guestbook-manifest-127", UID:"8b0c177115717f5d80a61795ead28644", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{guestbook}"}): reason: 'started' Started with docker id /k8s_guestbook.305e1366_container-vm-guestbook-manifest-127_default_8b0c177115717f5d80a61795ead28644_acfe6813
I0331 23:57:25.609421   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"127.0.0.1", UID:"127.0.0.1", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'online' Node 127.0.0.1 is now online
I0331 23:57:25.610281   26985 event.go:185] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"localhost", UID:"localhost", APIVersion:"", ResourceVersion:"", FieldPath:""}): reason: 'online' Node localhost is now online
I0331 23:57:35.461416   26985 integration.go:450] Version test passed
I0331 23:57:35.469094   26985 integration.go:547] Created atomicService
I0331 23:57:35.469156   26985 integration.go:560] Starting to update (c, x)
I0331 23:57:35.469281   26985 integration.go:560] Starting to update (d, w)
I0331 23:57:35.469351   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.469362   26985 integration.go:560] Starting to update (b, y)
I0331 23:57:35.469422   26985 integration.go:560] Starting to update (e, v)
I0331 23:57:35.469472   26985 integration.go:560] Starting to update (foo, bar)
I0331 23:57:35.473971   26985 integration.go:571] Posting update (foo, bar)
I0331 23:57:35.475083   26985 integration.go:571] Posting update (c, x)
I0331 23:57:35.477252   26985 integration.go:571] Posting update (d, w)
I0331 23:57:35.477918   26985 factory.go:199] About to try and schedule pod foo
I0331 23:57:35.478255   26985 factory.go:335] Attempting to bind foo to localhost
I0331 23:57:35.478490   26985 integration.go:571] Posting update (e, v)
I0331 23:57:35.478576   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.480220   26985 integration.go:571] Posting update (b, y)
I0331 23:57:35.507406   26985 integration.go:417] Creating replication controllers
I0331 23:57:35.524459   26985 integration.go:584] Done update (d, w)
I0331 23:57:35.533473   26985 integration.go:514] Self link test passed in namespace default
I0331 23:57:35.546346   26985 integration.go:575] Conflict: (c, x)
I0331 23:57:35.546385   26985 integration.go:560] Starting to update (c, x)
I0331 23:57:35.547190   26985 integration.go:575] Conflict: (e, v)
I0331 23:57:35.547349   26985 integration.go:560] Starting to update (e, v)
I0331 23:57:35.547199   26985 integration.go:575] Conflict: (foo, bar)
I0331 23:57:35.547651   26985 integration.go:560] Starting to update (foo, bar)
I0331 23:57:35.547542   26985 integration.go:575] Conflict: (b, y)
I0331 23:57:35.548087   26985 integration.go:560] Starting to update (b, y)
I0331 23:57:35.548960   26985 integration.go:422] Done creating replication controllers
I0331 23:57:35.549581   26985 integration.go:575] Conflict: (a, z)
I0331 23:57:35.549610   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.550117   26985 integration.go:571] Posting update (e, v)
I0331 23:57:35.550496   26985 integration.go:571] Posting update (c, x)
I0331 23:57:35.550550   26985 integration.go:571] Posting update (foo, bar)
I0331 23:57:35.550922   26985 integration.go:571] Posting update (b, y)
I0331 23:57:35.568696   26985 replication_controller.go:206] Too few "nginx-controller" replicas, creating 2
I0331 23:57:35.572199   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.583963   26985 kubelet.go:1125] No Infra Container for "foo_default" found. All containers will be restarted.
I0331 23:57:35.584159   26985 kubelet.go:1295] Creating pod infra container for "foo_default"
I0331 23:57:35.586052   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1187", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:35.586116   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1187", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.8d16007e_foo_default_b4035805-d801-11e4-80be-0242ac111e9b_619e8070
I0331 23:57:35.586140   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1187", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.8d16007e_foo_default_b4035805-d801-11e4-80be-0242ac111e9b_619e8070
I0331 23:57:35.586163   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1187", FieldPath:"spec.containers{c1}"}): reason: 'created' Created with docker id /k8s_c1.190e049e_foo_default_b4035805-d801-11e4-80be-0242ac111e9b_c005e84c
I0331 23:57:35.586185   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1187", FieldPath:"spec.containers{c1}"}): reason: 'started' Started with docker id /k8s_c1.190e049e_foo_default_b4035805-d801-11e4-80be-0242ac111e9b_c005e84c
I0331 23:57:35.598572   26985 integration.go:514] Self link test passed in namespace other
I0331 23:57:35.613403   26985 integration.go:575] Conflict: (b, y)
I0331 23:57:35.613439   26985 integration.go:560] Starting to update (b, y)
I0331 23:57:35.613605   26985 factory.go:199] About to try and schedule pod nginx-controller-9r790
I0331 23:57:35.613651   26985 integration.go:575] Conflict: (foo, bar)
I0331 23:57:35.613683   26985 integration.go:560] Starting to update (foo, bar)
I0331 23:57:35.613706   26985 integration.go:575] Conflict: (e, v)
I0331 23:57:35.613726   26985 integration.go:560] Starting to update (e, v)
I0331 23:57:35.613824   26985 factory.go:335] Attempting to bind nginx-controller-9r790 to localhost
I0331 23:57:35.614110   26985 integration.go:575] Conflict: (a, z)
I0331 23:57:35.614132   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.614841   26985 integration.go:584] Done update (c, x)
I0331 23:57:35.699493   26985 integration.go:571] Posting update (b, y)
I0331 23:57:35.700178   26985 integration.go:571] Posting update (foo, bar)
I0331 23:57:35.704104   26985 integration.go:571] Posting update (e, v)
I0331 23:57:35.706450   26985 integration.go:668] PATCHs work.
I0331 23:57:35.708536   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.716755   26985 factory.go:199] About to try and schedule pod nginx-controller-ob0bt
I0331 23:57:35.716831   26985 modeler.go:166] listing pods: ['test/nginx-controller-9r790 (b413ba39-d801-11e4-80be-0242ac111e9b)'] assumed to exist in addition to 3 known pods.
I0331 23:57:35.716934   26985 modeler.go:166] listing pods: ['test/nginx-controller-9r790 (b413ba39-d801-11e4-80be-0242ac111e9b)'] assumed to exist in addition to 3 known pods.
I0331 23:57:35.717010   26985 factory.go:335] Attempting to bind nginx-controller-ob0bt to localhost
I0331 23:57:35.733674   26985 integration.go:584] Done update (foo, bar)
I0331 23:57:35.741204   26985 kubelet.go:1125] No Infra Container for "nginx-controller-9r790_test" found. All containers will be restarted.
I0331 23:57:35.744476   26985 integration.go:575] Conflict: (e, v)
I0331 23:57:35.744528   26985 integration.go:560] Starting to update (e, v)
I0331 23:57:35.764833   26985 integration.go:571] Posting update (e, v)
I0331 23:57:35.775088   26985 kubelet.go:1295] Creating pod infra container for "nginx-controller-9r790_test"
I0331 23:57:35.775114   26985 integration.go:575] Conflict: (b, y)
I0331 23:57:35.775163   26985 integration.go:560] Starting to update (b, y)
I0331 23:57:35.775983   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-9r790", UID:"b413ba39-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1198", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:35.776139   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-9r790", UID:"b413ba39-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1198", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.34cd001c_nginx-controller-9r790_test_b413ba39-d801-11e4-80be-0242ac111e9b_04ee28b1
I0331 23:57:35.776178   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-9r790", UID:"b413ba39-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1198", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.34cd001c_nginx-controller-9r790_test_b413ba39-d801-11e4-80be-0242ac111e9b_04ee28b1
I0331 23:57:35.776985   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-9r790", UID:"b413ba39-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1198", FieldPath:"spec.containers{nginx}"}): reason: 'created' Created with docker id /k8s_nginx.bbc10af3_nginx-controller-9r790_test_b413ba39-d801-11e4-80be-0242ac111e9b_a3cc2950
I0331 23:57:35.777146   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-9r790", UID:"b413ba39-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1198", FieldPath:"spec.containers{nginx}"}): reason: 'started' Started with docker id /k8s_nginx.bbc10af3_nginx-controller-9r790_test_b413ba39-d801-11e4-80be-0242ac111e9b_a3cc2950
I0331 23:57:35.777403   26985 integration.go:575] Conflict: (a, z)
I0331 23:57:35.777422   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.781209   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.783862   26985 integration.go:571] Posting update (b, y)
I0331 23:57:35.817962   26985 integration.go:575] Conflict: (b, y)
I0331 23:57:35.817982   26985 kubelet.go:1125] No Infra Container for "nginx-controller-ob0bt_test" found. All containers will be restarted.
I0331 23:57:35.818169   26985 kubelet.go:1295] Creating pod infra container for "nginx-controller-ob0bt_test"
I0331 23:57:35.818847   26985 integration.go:584] Done update (e, v)
I0331 23:57:35.817995   26985 integration.go:560] Starting to update (b, y)
I0331 23:57:35.819149   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-ob0bt", UID:"b4165aad-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1202", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:35.820459   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-ob0bt", UID:"b4165aad-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1202", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.34cd001c_nginx-controller-ob0bt_test_b4165aad-d801-11e4-80be-0242ac111e9b_b9820e16
I0331 23:57:35.820493   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-ob0bt", UID:"b4165aad-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1202", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.34cd001c_nginx-controller-ob0bt_test_b4165aad-d801-11e4-80be-0242ac111e9b_b9820e16
I0331 23:57:35.820962   26985 integration.go:571] Posting update (b, y)
I0331 23:57:35.830645   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-ob0bt", UID:"b4165aad-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1202", FieldPath:"spec.containers{nginx}"}): reason: 'created' Created with docker id /k8s_nginx.bbc10af3_nginx-controller-ob0bt_test_b4165aad-d801-11e4-80be-0242ac111e9b_d24f4858
I0331 23:57:35.834127   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"test", Name:"nginx-controller-ob0bt", UID:"b4165aad-d801-11e4-80be-0242ac111e9b", APIVersion:"v1beta1", ResourceVersion:"1202", FieldPath:"spec.containers{nginx}"}): reason: 'started' Started with docker id /k8s_nginx.bbc10af3_nginx-controller-ob0bt_test_b4165aad-d801-11e4-80be-0242ac111e9b_d24f4858
I0331 23:57:35.835808   26985 integration.go:575] Conflict: (a, z)
I0331 23:57:35.835827   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.841522   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.948021   26985 integration.go:575] Conflict: (a, z)
I0331 23:57:35.948092   26985 integration.go:560] Starting to update (a, z)
I0331 23:57:35.948192   26985 integration.go:584] Done update (b, y)
I0331 23:57:35.954393   26985 integration.go:571] Posting update (a, z)
I0331 23:57:35.974436   26985 integration.go:584] Done update (a, z)
I0331 23:57:35.976754   26985 integration.go:596] Atomic PUTs work.
I0331 23:57:36.469345   26985 kubelet.go:1125] No Infra Container for "static-pod-from-manifest-localhost_default" found. All containers will be restarted.
I0331 23:57:36.469582   26985 kubelet.go:1295] Creating pod infra container for "static-pod-from-manifest-localhost_default"
I0331 23:57:36.471438   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"ff1f2781eb1f90be534f72758b782fae", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "kubernetes/pause:latest"
I0331 23:57:36.471519   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"ff1f2781eb1f90be534f72758b782fae", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.d279df51_static-pod-from-manifest-localhost_default_ff1f2781eb1f90be534f72758b782fae_6cffe8ad
I0331 23:57:36.471558   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"ff1f2781eb1f90be534f72758b782fae", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.d279df51_static-pod-from-manifest-localhost_default_ff1f2781eb1f90be534f72758b782fae_6cffe8ad
I0331 23:57:36.472466   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"ff1f2781eb1f90be534f72758b782fae", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{static-container}"}): reason: 'created' Created with docker id /k8s_static-container.55bee96_static-pod-from-manifest-localhost_default_ff1f2781eb1f90be534f72758b782fae_d99073ae
I0331 23:57:36.472667   26985 event.go:185] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"ff1f2781eb1f90be534f72758b782fae", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{static-container}"}): reason: 'started' Started with docker id /k8s_static-container.55bee96_static-pod-from-manifest-localhost_default_ff1f2781eb1f90be534f72758b782fae_d99073ae
I0331 23:57:37.531083   26985 integration.go:292] default/service1 endpoint: 1.2.3.4:8080 &api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"", ResourceVersion:"1207", FieldPath:""}
I0331 23:57:37.564457   26985 integration.go:266] Check whether pod nginx-controller-9r790.test exists on node "localhost"
I0331 23:57:37.565478   26985 server.go:654] GET /api/v1beta1/podInfo?podID=nginx-controller-9r790&podNamespace=test: (439.286µs) 0 [[Go 1.1 package http] 127.0.0.1:40284]
I0331 23:57:37.567812   26985 integration.go:266] Check whether pod nginx-controller-ob0bt.test exists on node "localhost"
I0331 23:57:37.568242   26985 server.go:654] GET /api/v1beta1/podInfo?podID=nginx-controller-ob0bt&podNamespace=test: (197.531µs) 0 [[Go 1.1 package http] 127.0.0.1:40284]
I0331 23:57:37.568540   26985 integration.go:438] Pods created
I0331 23:57:38.539687   26985 integration.go:284] Error on creating endpoints: endpoints "service2" not found
I0331 23:57:39.541079   26985 integration.go:284] Error on creating endpoints: endpoints "service2" not found
I0331 23:57:40.540171   26985 integration.go:284] Error on creating endpoints: endpoints "service2" not found
I0331 23:57:41.540260   26985 integration.go:284] Error on creating endpoints: endpoints "service2" not found
I0331 23:57:42.542242   26985 integration.go:292] default/service2 endpoint: 1.2.3.4:8080 &api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"b4035805-d801-11e4-80be-0242ac111e9b", APIVersion:"", ResourceVersion:"1207", FieldPath:""}
I0331 23:57:42.554657   26985 integration.go:827] Service test passed.
I0331 23:57:47.467562   26985 integration.go:713] Master service test passed.
F0331 23:58:07.477200   26985 integration.go:394] static-pod-from-manifest FAILED: mirror pod has not been re-created or is not running: timed out waiting for the condition
!!! Error in ./hack/test-integration.sh:47

I saw that on one shippable run today as well.

The test has been added for a while now and AFAIK it started flaking only yesterday and only on shippable. There has been no recent change to this part of the code, so my guess is that the apiserver/watch was slow due to unknown reasons and the build hit the timeout.
This is a general test performance problem (on shippable), and there are other examples where the timeout was hit when waiting for pod to be running on a different test (runSchedulerNoPhantomPodsTest):
https://app.shippable.com/builds/551bb0cd0f3ae40d00e938af
F0401 08:53:17.665163   27111 integration.go:855] FAILED: pod never started running timed out waiting for the condition
I will increase the timeout to reduce the flake for now.

Should we close this issue?

Yes, let's close this since I am not aware of any new occurrence.

Another example: https://app.shippable.com/builds/5526d6995cb2750c00d8ad47
I0409 19:54:15.469401    1437 kubelet.go:1505] Killing unwanted container &{ID:/k8s_static-container.55bee96_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_aca74518 Name:static-container Image: Hash:89910934 Created:0}
I0409 19:54:15.470237    1437 kubelet.go:841] Killing container with id "/k8s_static-container.55bee96_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_aca74518"
I0409 19:54:15.470605    1437 kubelet.go:1505] Killing unwanted container &{ID:/k8s_POD.1a1fe303_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_a1189515 Name:POD Image: Hash:438297347 Created:0}
I0409 19:54:15.470866    1437 kubelet.go:841] Killing container with id "/k8s_POD.1a1fe303_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_a1189515"
I0409 19:54:15.470670    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"a85986a4ddd3712417df3ad71f8df509", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{static-container}"}): reason: 'killing' Killing /k8s_static-container.55bee96_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_aca74518
I0409 19:54:15.471333    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-manifest-localhost", UID:"a85986a4ddd3712417df3ad71f8df509", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'killing' Killing /k8s_POD.1a1fe303_static-pod-from-manifest-localhost_default_a85986a4ddd3712417df3ad71f8df509_a1189515
I0409 19:54:16.422048    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:17.421341    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:17.479770    1437 kubelet.go:1117] No Infra Container for "static-pod-from-spec-localhost_default" found. All containers will be restarted.
I0409 19:54:17.480111    1437 kubelet.go:1965] Query docker container info for pod "static-pod-from-spec-localhost_default" failed with error (no containers exist for this pod)
I0409 19:54:17.480448    1437 kubelet.go:1299] Creating pod infra container for "static-pod-from-spec-localhost_default"
I0409 19:54:17.483764    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-spec-localhost", UID:"7fc40faf8939a9956e10aa9c9da4ffe8", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'pulled' Successfully pulled image "gcr.io/google_containers/pause:0.8.0"
I0409 19:54:17.484138    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-spec-localhost", UID:"7fc40faf8939a9956e10aa9c9da4ffe8", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'created' Created with docker id /k8s_POD.1a1fe303_static-pod-from-spec-localhost_default_7fc40faf8939a9956e10aa9c9da4ffe8_515b9a33
I0409 19:54:17.484463    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-spec-localhost", UID:"7fc40faf8939a9956e10aa9c9da4ffe8", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.1a1fe303_static-pod-from-spec-localhost_default_7fc40faf8939a9956e10aa9c9da4ffe8_515b9a33
I0409 19:54:17.484774    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-spec-localhost", UID:"7fc40faf8939a9956e10aa9c9da4ffe8", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{static-container}"}): reason: 'created' Created with docker id /k8s_static-container.55bee96_static-pod-from-spec-localhost_default_7fc40faf8939a9956e10aa9c9da4ffe8_7b74c6a1
I0409 19:54:17.485052    1437 event.go:200] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"static-pod-from-spec-localhost", UID:"7fc40faf8939a9956e10aa9c9da4ffe8", APIVersion:"v1beta2", ResourceVersion:"", FieldPath:"spec.containers{static-container}"}): reason: 'started' Started with docker id /k8s_static-container.55bee96_static-pod-from-spec-localhost_default_7fc40faf8939a9956e10aa9c9da4ffe8_7b74c6a1
I0409 19:54:18.436566    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:19.420685    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:20.422398    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:21.421442    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:22.420511    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:23.421648    1437 integration.go:290] Error on creating endpoints: endpoints "service1" not found
I0409 19:54:24.421405    1437 integration.go:298] default/service1 endpoint: 1.2.3.4:8080 &api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"25b6070d-def2-11e4-bc1f-0242ac110b3a", APIVersion:"", ResourceVersion:"212", FieldPath:""}
I0409 19:54:25.447608    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:26.448363    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:27.447191    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:28.447710    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:29.446758    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:30.450489    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:31.446830    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:32.447628    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:33.447128    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:34.446818    1437 integration.go:290] Error on creating endpoints: endpoints "service2" not found
I0409 19:54:35.447619    1437 integration.go:298] default/service2 endpoint: 1.2.3.4:8080 &api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"foo", UID:"25b6070d-def2-11e4-bc1f-0242ac110b3a", APIVersion:"", ResourceVersion:"212", FieldPath:""}
I0409 19:54:36.462878    1437 integration.go:888] Service test passed.
F0409 19:55:24.047485    1437 integration.go:400] static-pod-from-spec FAILED: mirror pod has not been re-created or is not running: timed out waiting for the condition

Closing this since there is another issue open (#6651).

authors: dchen1107 lavalamp roberthbailey yujuhong


text:
make boilerplate more flexible

right now, boilerplate forces all sh scripts to be bash, from the hooks/boilerplate.sh.txt file,
  1 #!/bin/bash
  2
  3 # Copyright 2014 The Kubernetes Authors All rights reserved.

So the grep statement needs to be loosened up a little, i guess, to allow the top line to vary... maybe while we're at it we can consolidate all boilerplate files into a single string or regex
cc @eparis

I think this might be intentional (or at least a good side-effect)? That is, given the quantity of scripts we have in Kubernetes (Too Much™), we want them to be a consistent language so we don't have to support shell variants? I could be wrong here.

I fixed this in #7878  ... some docker files use sh scripts, after all ?

https://github.com/GoogleCloudPlatform/kubernetes/commit/c192cfb3deda6633cb19104b2a20b25add67198b here's my proposed fix .  just a two liner.  and im happy to also implement logic which forces all files to be bin/bash if thats something we want to enforce?

Those who worked on the boilerplate should probably decide this (@eparis and @lavalamp)

I think that's I'm ok with the change, but I generally dislike any script that starts with /bin/sh.  Even if /bin/sh == /bin/bash on 99.9% of systems, there's got to be some nutter out there who changes the symlink. Which is what makes me like the "force /bin/bash" idea....

I guess we sometimes use /bin/sh in busybox images... Not too keen on allowing it generally, though. Shell is hard enough without variants.

@jayunit100 Why do you want to make this change?

@lavalamp simply because its the right thing to do.

There are easy workarounds, BUT
verify-boilerplate.sh shouldnt determine what shells we allow.

HOWEVER i totally agree with eric, that we should enforce scripting types - but just not in verify-boilerplate.sh.

shall we create hack/verify-misc.sh or something of the sort which verified miscellaneous things like using bash wherever possible?

makes sense now?

I guess I don't really see the point in splitting one verification script into two absent an immediate use case.

I know the jayunit 'stole' a script for prometheus that was #!/bin/sh and then couldn't use it in kube because of this requirement.  That's over in #7878
we also enforce #!/usr/bin/env python in the python boilerplate
I'm not sure I see the value in having a separate new 'verify interpreter' script.  If we agree always #!/bin/bash and always #!/usr/bin/env python then we should leave them in the boilerplate.  If we need something more flexible, i'm ok with a separate tool...

Copied stuff should go in third_party somewhere, and then the boilerplate script shouldn't check it.
I think I'll close this, since @eparis seems to agree with me. Please reopen if there's a use case that requires this.

Briefly to clarify : that script was written by one of kube contributors... so it definetly goes in the main src.  I can layer some commits on top to change to bash to retest.
But in any case if we're going to use verify boilerplate to do more than boiler plate... we should at least output the correct error message... right?

authors: eparis jayunit100 lavalamp mbforbes


text:
Add a better networking doc

This makes a new docs/cluster dir - we should move all detailed cluster-setup related docs here.
Hopefully this explains a bit better what is going on.

Not sure about the new directory.  What else would go in there?  How about just putting this at the bottom of the current docs/networking.md.

I found this a really useful document.  I understood K8s networking much better after reading it.

Taking a look now.

Regarding new dir - I briefly discussed with Brian.  I could see all of the getting started guides moving here, all of the networking-related docs, etc.  Anything that the cluster admins would want to read but app developers might not care about.  I could be talked out of it if you care...

Many comments addressed

No need for an LGTM from me, I trust you addressed whichever of my comments you thought were reasonable. :)

If you are planning to do the work to move other things into the docs/cluster dir in the next PR, then fine.  Otherwise, let's not have a dir with one thing in it.

OK, I gave up on the extra dir - we can deal with that later

authors: davidopp erictune thockin


text:
E2E: Refactor Elasticsearch test to use [Skipped] Tags properly.

WARNING: THIS PR IS UNTESTED !!!!!
We don't want to inflate the e2e test results.... so this makes the E2E elasticsearch tests so that they use the It syntax, so that they are Skipped rather than returning passed.
Hope the elasticsearch folks can give it a look, or just add a commit on top of this to fix if I've made any mistakes.  I think this should work just fine, though.
I dont run tests on GCE so I cant confirm it works perfectly.

@satnam6502 Looks like you worked on this test, so maybe you will be best to review this.

Why skip this test? There is nothing cloud specific about it and it should run on all cloud providers.

There is a boolean flag in there which makes it skip unless GCE.  I have no idea what its there for.  I just made the skipping so that its done properly.

OK. Let me take a look.
On Mon, May 11, 2015 at 8:53 AM, jay vyas notifications@github.com wrote:

There is a boolean flag in there which makes it skip unless GCE. I have no
idea what its there for. I just made the skipping so that its done properly.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8055#issuecomment-100954945
.

I will test this PR on a GCE instance configured with Cloud Logging to ensure it is skipped.

Problem. This seems to skip the test when it should run. Output from a cluster created with Fluentd to Elasticsearch logging. Please investigate.
$ go run hack/e2e.go --v --test --test_args="--ginkgo.focus=.*Cluster.*"
2015/05/11 11:18:27 Running: get status
Project: kubernetes-satnam
Zone: us-central1-b
Client Version: version.Info{Major:"0", Minor:"16+", GitVersion:"v0.16.2-710-g2709bb3987698a-dirty", GitCommit:"2709bb3987698ab63af5d8cc60120fe7cb0eda52", GitTreeState:"dirty"}
Server Version: version.Info{Major:"0", Minor:"16+", GitVersion:"v0.16.2-710-g2709bb3987698a-dirty", GitCommit:"2709bb3987698ab63af5d8cc60120fe7cb0eda52", GitTreeState:"dirty"}
Waiting at most 1200 seconds for all pods to be 'Running'
Found 14 pods with statuses: Running Running Running Running Running Running Running Running Running Running Running Running Running Running
All pods are 'Running'
Project: kubernetes-satnam
Zone: us-central1-b
2015/05/11 11:18:31 Running: Ginkgo tests
Setting up for KUBERNETES_PROVIDER="gce".
Project: kubernetes-satnam
Zone: us-central1-b
Running Suite: Kubernetes e2e Suite run 1 of 1
==============================================
Random Seed: 1431368313 - Will randomize all specs
Will run 0 of 45 specs

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
Ran 0 of 45 Specs in 0.000 seconds
SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 45 Skipped I0511 11:18:33.507621   16475 driver.go:96] All tests pass
satnam@satnam-linux:~/gocode/src/github.com/GoogleCloudPlatform/kubernetes$ kubectl get pods
POD                                            IP           CONTAINER(S)              IMAGE(S)                                                                            HOST                                    LABELS                                                          STATUS    CREATED          MESSAGE
elasticsearch-logging-ky96p                    10.244.0.2                                                                                kubernetes-minion-89r2/104.197.69.110   kubernetes.io/cluster-service=true,name=elasticsearch-logging   Running   2 days
                                                            elasticsearch-logging     gcr.io/google_containers/elasticsearch:1.0                                                                                Running   2 days
etcd-server-kubernetes-master                                                                                kubernetes-master/                      <none>                                                          Running   2 days
                                                            etcd-container            gcr.io/google_containers/etcd:2.0.9                                                                                Running   17 hours         last termination: exit code 0
fluentd-elasticsearch-kubernetes-minion-89r2   10.244.0.4                                                                                kubernetes-minion-89r2/104.197.69.110   <none>                                                          Running   2 days
                                                            fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                Running   2 days
fluentd-elasticsearch-kubernetes-minion-kxcb   10.244.1.4                                                                                kubernetes-minion-kxcb/104.197.16.133   <none>                                                          Running   2 days
                                                            fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                Running   2 days
fluentd-elasticsearch-kubernetes-minion-t8m7   10.244.2.2                                                                                kubernetes-minion-t8m7/104.197.77.206   <none>                                                          Running   2 days
                                                            fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                Running   2 days
fluentd-elasticsearch-kubernetes-minion-xf0z   10.244.3.2                                                                                kubernetes-minion-xf0z/104.197.12.87    <none>                                                          Running   2 days
                                                            fluentd-elasticsearch     gcr.io/google_containers/fluentd-elasticsearch:1.5                                                                                Running   2 days
kibana-logging-7kcv4                           10.244.3.3                                                                                kubernetes-minion-xf0z/104.197.12.87    kubernetes.io/cluster-service=true,name=kibana-logging          Running   2 days
                                                            kibana-logging            gcr.io/google_containers/kibana:1.3                                                                                Running   2 days
kube-apiserver-kubernetes-master                                                                                kubernetes-master/                      <none>                                                          Running   About a minute
                                                            kube-apiserver            gcr.io/google_containers/kube-apiserver:277fe30e546796064bed598ac243aafa                                                                                Running   About a minute   last termination: exit code 255
kube-controller-manager-kubernetes-master                                                                                kubernetes-master/                      <none>                                                          Running   About a minute
                                                            kube-controller-manager   gcr.io/google_containers/kube-controller-manager:b06e6ce789137d0f05e578494badd8f3                                                                                Running   About a minute   last termination: exit code 255
kube-dns-i7hay                                 10.244.1.3                                                                                kubernetes-minion-kxcb/104.197.16.133   k8s-app=kube-dns,kubernetes.io/cluster-service=true             Running   2 days
                                                            skydns                    gcr.io/google_containers/skydns:2015-03-11-001                                                                                Running   2 days
                                                            kube2sky                  gcr.io/google_containers/kube2sky:1.4                                                                                Running   2 days
                                                            etcd                      gcr.io/google_containers/etcd:2.0.9                                                                                Running   2 days
kube-scheduler-kubernetes-master                                                                                kubernetes-master/                      <none>                                                          Running   About a minute
                                                            kube-scheduler            gcr.io/google_containers/kube-scheduler:847699939480eff0ba7913e04874eb25                                                                                Running   About a minute   last termination: exit code 255
monitoring-heapster-controller-b710j           10.244.1.2                                                                                kubernetes-minion-kxcb/104.197.16.133   kubernetes.io/cluster-service=true,name=heapster                Running   2 days
                                                            heapster                  gcr.io/google_containers/heapster:v0.11.0                                                                                Running   11 seconds       last termination: exit code 1
synthetic-logger-0.25lps-pod                   10.244.3.4                                                                                kubernetes-minion-xf0z/104.197.12.87    name=synth-logging-source                                       Running   2 days
                                                            synth-lgr                 ubuntu:14.04                                                                                Running   2 days
synthetic-logger-10lps-pod                     10.244.3.5                                                                                kubernetes-minion-xf0z/104.197.12.87    name=synth-logging-source                                       Running   2 days
                                                            synth-lgr                 ubuntu:14.04                                                                                Running   2 days

thanks satnam. i ll try to see why . unfortunately i dont have this sort of cluster so cant really test, but ill look if something pops out.
indeed i tested it skips, but wasnt able to test that it doesnt skip .

To prove my point, this is what happens when I run the test against a recent build from HEAD:
$ go run hack/e2e.go --v --test --test_args="--ginkgo.focus=.*Cluster.*"
2015/05/11 11:24:30 Running: get status
Project: kubernetes-satnam
Zone: us-central1-b
Client Version: version.Info{Major:"0", Minor:"16+", GitVersion:"v0.16.2-710-g2709bb3987698a-dirty", GitCommit:"2709bb3987698ab63af5d8cc60120fe7cb0eda52", GitTreeState:"dirty"}
Server Version: version.Info{Major:"0", Minor:"16+", GitVersion:"v0.16.2-710-g2709bb3987698a-dirty", GitCommit:"2709bb3987698ab63af5d8cc60120fe7cb0eda52", GitTreeState:"dirty"}
Waiting at most 1200 seconds for all pods to be 'Running'
Found 14 pods with statuses: Running Running Running Running Running Running Running Running Running Running Running Running Running Running
All pods are 'Running'
Project: kubernetes-satnam
Zone: us-central1-b
2015/05/11 11:24:35 Running: Ginkgo tests
Setting up for KUBERNETES_PROVIDER="gce".
Project: kubernetes-satnam
Zone: us-central1-b
Running Suite: Kubernetes e2e Suite run 1 of 1
==============================================
Random Seed: 1431368678 - Will randomize all specs
Will run 1 of 46 specs

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Cluster level logging using Elasticsearch
  should check that logs from pods on all nodes are ingested into Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46
[BeforeEach] Cluster level logging using Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:42
>>> testContext.KubeConfig: /usr/local/google/home/satnam/.kube/config
[It] should check that logs from pods on all nodes are ingested into Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46
STEP: Checking the Elasticsearch service exists.
STEP: Checking to make sure the Elasticsearch pods are running
STEP: waiting up to 5m0s for pod elasticsearch-logging-ky96p status to be running
STEP: Checking to make sure we are talking to an Elasticsearch service.
STEP: Checking health of Elasticsearch service.
STEP: Waiting for the pods to succeed.
STEP: waiting up to 5m0s for pod synthlogger-0 status to be success or failure
INFO: No Status.Info for container synth-logger in pod synthlogger-0 yet
INFO: Waiting for pod synthlogger-0 in namespace es-logging-3500 status to be "success or failure" (found "Pending") (39.994035ms)
INFO: No Status.Info for container synth-logger in pod synthlogger-0 yet
INFO: Waiting for pod synthlogger-0 in namespace es-logging-3500 status to be "success or failure" (found "Pending") (5.081380263s)
INFO: No Status.Info for container synth-logger in pod synthlogger-0 yet
INFO: Waiting for pod synthlogger-0 in namespace es-logging-3500 status to be "success or failure" (found "Pending") (10.122069274s)
STEP: Saw pod success
STEP: waiting up to 5m0s for pod synthlogger-1 status to be success or failure
STEP: Saw pod success
STEP: waiting up to 5m0s for pod synthlogger-2 status to be success or failure
STEP: Saw pod success
STEP: waiting up to 5m0s for pod synthlogger-3 status to be success or failure
INFO: No Status.Info for container synth-logger in pod synthlogger-3 yet
INFO: Waiting for pod synthlogger-3 in namespace es-logging-3500 status to be "success or failure" (found "Pending") (39.707774ms)
STEP: Saw pod success
STEP: Checking all the log lines were ingested into Elasticsearch
INFO: After 528.742009ms expecting to find 400 log lines but saw only 200
INFO: After 10.728495598s found all 400 log lines

• [SLOW TEST:62.117 seconds]
Cluster level logging using Elasticsearch
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:47
  should check that logs from pods on all nodes are ingested into Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46
------------------------------
SSSSSSSSS
Ran 1 of 46 Specs in 62.118 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 45 Skipped I0511 11:25:40.572155   18547 driver.go:96] All tests pass

Would you like me to debug it? I think that might be quicker since I have the clusters at hand? I don't want to steal your thunder!

sure go for it @satnam6502 :) ! ill try to learn more how these tests work meanwhile

OK, but I am drowning in other stuff right now so I may not get to this until later this week.

no prob. well maybe ill steal the thunder rightback , then :)

I think i see what went wrong.  something along these lines...
When refactoring, i guess i made it so that the testContext is referenced outside of code that is run via ginkgo, which results in a silent failure that causes all the tests not to run.

After looking deeper, i dont think we can use the [Skipped] mechanism in tests at test declarations unless we know apriori that a test shouldnt run (like in density).  If we are skipping for gce/gke, then we have to prematurely return from the test - which is unfortunate, because....  im pretty sure  this will make the number of passing tests inflated in cases that some tests are skipped.
So, ill close this guy :).


text:
Add note on firewall rules for private clusters

Fixes #29
Thanks to https://github.com/open-telemetry/opentelemetry-operator/issues/100#issuecomment-846125541 for documenting this solution. I was able to reproduce the issue in a private GKE autopilot cluster and applying this fix resolved the issue and I was able to deploy a collector.

There were some YAML linter checks in unrelated files, which are out of scope for this PR. But do those need to be addressed ?

nope, they are just warnings but it would be nice to clean them up to get rid of the noise.


text:
NL classifyText samples and client library version update

Ready for review. High priority to merge soon because of a launch.

This is all ready to go! Let's coordinate with the docs change (so the docs don't link to the moved files) and then we can merge these suckers!

authors: bshaffer ryanmats

repo: GoogleCloudPlatform/php-docs-samples


text:
Remove obsolete dockerfiles

These old docker images were recently disabled by replacing them with obsolete/Dockerfile (https://github.com/GoogleCloudPlatform/ruby-docker/pull/42). This PR cleans up the old unused dockerfiles, and updates the toplevel README.

This will close issue #30

@hxiong388 Can you approve this?

repo: GoogleCloudPlatform/ruby-docker


text:
feat: Remove references to specific credential types.

Closes #84
Closes #85

In #107 @rogerthatdev introduced using shortcodes to include code examples from dedicated files. I propose we move the code touched by this guideline to separate files, and change unmodified languages to something of a TODO. We could then file issues for each one, and merge the proposal based on the guideline readiness rather than blocking on 6 additional contributions.

@grayside @piaxc this is ready for review.
We'd need to gather the documentation links for the other languages but that can be done independently.

authors: amanda-tarafa grayside

repo: GoogleCloudPlatform/samples-style-guide


text:
Check official CODEOWNERS for references to non-existent Github handles

notebooks/community/CODEOWNERS is referencing internal usernames instead of Github handles.
CODEOWNERS errors
Unknown owner on line 6: make sure @aferlitsch exists and has write access to the repository
/sdk/sdk_* @aferlitsch
Unknown owner on line 7: make sure @aferlitsch exists and has write access to the repository
/gapic @aferlitsch
Unknown owner on line 8: make sure @aferlitsch exists and has write access to the repository
/ml_ops @aferlitsch
Unknown owner on line 9: make sure @mco exists and has write access to the repository
/model_monitoring/* @mco
Unknown owner on line 12: make sure @notebooks-team exists and has write access to the repository
/managed_notebooks/ @notebooks-team
Unknown owner on line 15: make sure @thehardikv exists and has write access to the repository
…_Model_Training_Example.ipynb @thehardikv
Unknown owner on line 16: make sure @thehardikv exists and has write access to the repository
…ting_evaluating_a_model.ipynb @thehardikv
Unknown owner on line 19: make sure @benofben exists and has write access to the repository
/neo4j @benofben @htappen
Unknown owner on line 19: make sure @htappen exists and has write access to the repository
/neo4j @benofben @htappen
Unknown owner on line 21: make sure @wattli exists and has write access to the repository
/tensorboard @yfang1 @wattli
Unknown owner on line 22: make sure @inardini exists and has write access to the repository
…store @nayaknishant @morgandu @inardini

Should check official as well.

The community CODEOWNERS was fixed thanks to an update from @galz10. So, I've narrowed this issue to official.

Once #361 is closed, we can close this issue. I believe we might need to rework the rules for community codeowners since users who contribute to community shouldn't have write access.

authors: galz10 ivanmkc kweinmeister

repo: GoogleCloudPlatform/vertex-ai-samples


text:
ci: copy nomos binary into path

This change adds a copy-cli target which copies the nomos binary from the os/arch subdirectory into the top level bin directory. This enables it to be in the PATH for subsequent commands. Call copy-cli after pulling postsubmit artifacts so that the binary can be used. This enables the periodic CI jobs to use the binary that is pulled from the postsubmit artifacts.

/assign @karlkfi

repo: GoogleContainerTools/kpt-config-sync


text:
kpt apply-setters fails when a value is not set in both Kptfiles

Expected behavior
I have a network package which includes a subnet subpackage that uses a "prefix" setter.
The "prefix" setter is only used in the subnet subpackage. I expect to only have to provide it to the apply-setters config in the subpackage (or only in the parent package).
Actual behavior
If I don't provide a value for the setter in both the parent and subpackage, this error is raised:
  Results:
    [ERROR] failed to apply setters: values for setters [${prefix}] must be provided
  Stderr:
    "values for setters [${prefix}] must be providedvalues for setters [${prefix}] must be provided"
    ""
  Exit code: 1

Information
kpt package: https://github.com/GoogleCloudPlatform/blueprints/tree/main/catalog/networking/network
Downstream issue: https://github.com/GoogleCloudPlatform/blueprints/issues/28

@morgante You will have to provide the value in the both places because, there is no delimiter between prefix and network-name setters. apply-setters function tries to do pattern matching in order to derive the values of setters for which the values are not provided(like prefix). Since there is no delimiter, it will need the user to provide the default value in both the places. You solved it the correct way by adding the default value in both places. So now, the package consumer can update the value in either of the places and it works fine. If the consumer updates the value in both parent and subpackage, parent package value wins.
There are no action items for apply-setters function in this case. Let me know if you are satisfied with the answer so that I can close the issue.

On a different note, you can use ensure-name-substring function in order to achieve the task instead of using setters.

@phanimarupaka I'm not sure that really answers it—in the cases where apply-setters doesn't have the information it needs (in the nested subpackage, or in the parent) I think it should ignore or drop the value.
Specifying the value in both places introduces confusion because the parent package always wins.

@morgante That is possible if we can match value with the pattern. for e.g. foonetwork-name-router-nat # kpt-set: ${prefix}${network-name}-router-nat if you just specify value for network-name setter and not prefix setter, apply-setters doesn't know what is the existing value of network-name setter. So it expects users to provide the value in such ambiguous cases.

I now see that if I exclude network-name and prefix from the subpackage setters.yaml, everything works properly. Given that I'm satisfied with the current behavior (though do suggest we should document this more somewhere).

Reopening because this has come up again. Currently, kpt v1 requires setting all the setters for a field at the same level which makes composition harder.

@morgante As explained earlier, it is only true for ambiguous strings. Can you elaborate steps to reproduce.

@morgante Are there any action items on this issue ? Can we close this and wait for a new issue from WIPE ?

authors: morgante phanimarupaka

repo: GoogleContainerTools/kpt


text:
Add "Examples" and "Long Description" to kpt apply command.

This currently only has a short description.

Update the guide as well

https://googlecontainertools.github.io/kpt/guides/consumer/apply/


text:
Improve $$err typing (and fix doc)

If the transformation is not possible, $$text expands to "null", not undefined. Corrected doc accordingly.

You should be able to write this:

function $$textSafe(exp: unknown): string {
  const $res = $$text!(exp)

  if ($res === 'null') {
    return $$err!('$$text: exp in not transformable.')
  }

  return $res
}

But I get an error:

Updating, $$err return type to never fixes the problem.

Thanks for the PR! Will be merged soon

authors: GoogleFeud Gurimarukin

repo: GoogleFeud/ts-macros

license: MIT


text:
Background color does not accept all valid CSS strings

Tried with background: linear-gradient(#e66465, #9198e5);, radial-gradient(#e66465, #9198e5) & transparent
Suggested resolution

For transparent load the underlying Three context with {alpha: true} add a console.warn() noting that setting the alpha of the underlying will potentially impact performance
Either provide the same note as above & set the .container's background-color to the CSS string, or could possibly do some static mapping version of #66 since we're already in a 3D context?

You totally called our bluff on 'all valid CSS strings', Andres :grimacing: we should update that in the docs to specify that it accepts the subset of <color> strings supported by THREE.Color#setStyle. Although it doesn't seem too outrageous to parse out gradients, I wonder if there's some combo of specifying a set of colors and generating something like #66 (for that blurry effect commonly used, e.g. #181)

Are there any blockers to making a new transparent attribute on the custom element, that uses Three's {alpha: true}? I can try to make a PR if that sounds good.

@forresto a PR to test the idea out would be nice indeed 👌

To test I set this.skysphere.visible = false; ... would there need to be more logic around that? There are a few place that expect the skysphere to exist.
With this.renderer.autoClear = false; other models on the page and trails:

With this.renderer.autoClear = true; gets rid of the other models, but still leaves these trails... any hints?

authors: AndresCuervo forresto jsantell mrdoob

repo: GoogleWebComponents/model-viewer


text:
Optional option for _bot and bot in jishaku py

The Problem

I want to be able to use _bot and bot varaibles in jsk py, I looked at docs, there doesn't appear to be a way I know of.
The Ideal Solution

The Current Solution

Summary

I Just want to make it possible to run
_bot.user

or
bot.user```

okay quick question, is it possible that I could get a flag to allow both _bot and bot, so I don't have to keep jishaku subclassed for this feature?

It does mildly confuse me why you'd want this. It's not exactly hard to implement, I just am unsure on why you wouldn't commit to one or the other for consistency.

Personally it doesn't mind me much, but People tend to try to your jsk code sometimes and I just want this so I have a lib default for it, it's cause people sometimes are curious what you are doing but they don't have the same repl as you
having both allows you to use either one, so it's easier to just test it out?
it was just because it was easier for others and me to learn stuff from jsk.

#176 is pretty much a duplicate of this, except it requests a more configurable system.

authors: Gorialis JDJGInc pythonmcpi

repo: Gorialis/jishaku


text:
What is the suggested workflow for creating a multiplayer game with godotsteam?

I've started prototyping some multiplayer interactions in a project using godotsteam, and after following the lobby tutorials, I'm wondering what what the network workflow for multiplayer games should be.
Godot's multiplayer support makes it seem almost like an idiomatic implementation of steam multiplayer in godot would be done by implementing by a custom PacketPeer, over the Steam P2P networking interface.
Being mostly inexperienced with Steamworks, I'm not even sure how that would fit in with Godot's authoritative client-server model and if steamworks has alternatives to p2p networking.
Is godotsteam designed to require p2p messaing and maual replication? Or is godotsteam designed to facilitate a handshake that leads to a regular godot high-level networking connection (although this would fail if a nat-punch can't be achieved, only a PacketPeer subclass could idiomatically use the p2p relay)? Maybe godotsteam is just not designed for godot's multiplayer, and instead just for achievements and etc?

Hey there.  Multiplayer can be handled a few ways; and I will say I am definitely not an expert or even really knowledgeable about networking.
I have tried a combination of Godot's high-level networking and Steam's P2P functions, which didn't work so great.  I kind of think it should probably be one or the other, as it makes the whole process a lot easier.  That being said, there are still two Networking classes I have yet to implement in GodotSteam, as well as Matchmaking Server.  From glancing at them, it appears they will definitely make things a bit easier and could probably allow better integration between Steamworks and Godot's high-level networking.  Mostly because the biggest issue I found mixing the two was that Godot's HLN used IP addresses for initial connection and Steamworks used server ID's, which made things difficult.  It definitely really made Steam's invite system break.
As far as I know, there is no real way to differentiate between a server or client in Steamworks; you basically have to set that up somehow in your code.  I usually have a variable for server or client, which gets set when a player creates a lobby and subsequently set for each player that joins.  All their data is sent at lobby join and added to a client list on the server then updated through functions I write and passed with P2P packets.  A lot of it is modeled on Godot's setup.
I don't know Steamworks was specifically designed to mix with a different networking framework (like Godot's) but it doesn't appear to really hamper it if you have access to all the Steamworks classes.  I think GodotSteam / Steamworks has better lobby functionality, for sure; as well as messaging, since there are specific functions for it.
Once those last three classes are added in, I will probably put together a tutorial based on my understanding at the time as well as a new sample project.  I will definitely be using it in my own game to upgrade the current multiplayer I have; which is now just pure Steamworks.
I don't know if that answers all your questions or not but I'm happy to continue figuring it out with you!
You can also check out @JDare's (GodotSteam High-Level Networking repo)[https://github.com/JDare/GodotSteamHL].  It might be useful or point you in the right direction.

From my understanding, GodotSteam is exposing the underlying steamworks SDK which has very little direction in terms of how you architect the networking for your game. As Gramps mentioned they provide both p2p as well as dedicated server support (although I believe that's in Beta right now).
You're correct in assuming you can do either p2p networking yourself or use their relay. The lobby system Steam provides is completely separate from any concept of networking. They include an example of where you group up users in a lobby and then use your own custom P2P networking to actually connect them (which would require punchthrough or a relay etc.).
If you're looking to just connect a handful of players together its probably easiest to use their P2P relay and implement it however you see fit. In a perfect world you could certainly do a deeper integration with Godot's core networking and look at creating a native high level abstraction along the lines of their ENet or WebRTC classes. I briefly investigated that option before rapidly deciding that creating a high level solution in GDScript would probably be good enough and a lot quicker to implement.
If you do want to dive deeper into Steams networking APIs, I strongly recommend their docs at https://partner.steamgames.com/doc/features/multiplayer/networking and https://partner.steamgames.com/doc/api/ISteamNetworking
And finally a shameless plug for GodotSteamHL if you want to see a proof of concept or one way you can architect networking for your game using GodotSteam.

No shame in that.
Thank you there's a lot of useful information here! I think I may eventually consider writing a custom PacketPeer subclass over the steam P2P interface because I like the idea, but I'll definitely table that for now and it indeed sounds non-trivial.
For my particular case which is more prototyping, I think I will try to bootstrap a godot ENet connection via steam lobbies, which is very much not long term. I'll definitely look into GodotSteamHL but I'm using C# so I'm afraid it'll be hard to use since there won't be any type info from the gdscript.

@JDare Haha, no plug is ever shameful.  And awesome reply!

Can this issue be closed after adding some comment to the documentation answering this question?

Sure.  I had planned on linking in GodotSteamHL as a resource for people to check out.  I can try to sum up the discussion here too.

Updated the lobby/P2P tutorial with the repo from @JDare linked in as well as a brief message and link to Valve's networking section from the SDK documentation.  Please let me know if there is anything specific I should add.
This week I'm going to get those last three classes added in and start building a new example project with the newer functions.  Afterward it might be a good time to get back to my GodotSteam server branch.

authors: Gramps JDare MichaelBelousov

repo: Gramps/GodotSteam


text:
Closing the game before Steps are saved to disc

Will this cause the steps taken after the save but before closing the game to disappear or are they cached somewhere/saved upon closing?
If they are deleted then i would like to set the value lower, i am only worried about wether this will cause any kind of lag.

I tried to convert the heatmap file into .png and it would not load. Not sure if thats still a bug.

@Geldahar Do you mean by pressing one of the "Write Heatmap Image" buttons? There are some users for whomst the image writing wasn't working, but I recently made an update which seems to have fixed it for them. The update still needs to be reviewed by the RuneLite devs before it'll be live, which will probs be another week or two.

Ok thank you, i will try it again but if not i will be looking forward to update. This is a really cool looking plugin!

authors: Geldahar GrandTheftWalrus

repo: GrandTheftWalrus/RuneLite-World-Heatmap