Re: oc -w timeout

Hi, You might want to take a look at this thread: https://lists.openshift.redhat.com/openshift-archives/users/2017-June/msg00135.html ​ Cheers ___ users mailing list users@lists.openshift.redhat.com

Re: timeout expired waiting for volumes to attach/mount for pod

Andrew, YOU MADE MY DAY! The issue is GONE (sorry, I'm very excited and relieved at the same time). We tried to nuke docker completely on the node (also removing /var/lib/docker), but we hadn't removed /var/lib/origin/. So, for an obscur reason, we had a lot of old volumes from May, June and

Re: timeout expired waiting for volumes to attach/mount for pod

On Tue, Jul 25, 2017 at 12:21 PM, Andrew Lau wrote: > I think your issue may come from https://github.com/ > kubernetes/kubernetes/issues/38498 > > Too many orphaned volumes causing the timeout. I guess the downgrade > doesn't help with the increased number of volumes(?) >

Re: timeout expired waiting for volumes to attach/mount for pod

I'm pretty sure it's not related, but I took a look at the git log from the day we started to have issues, and noticed it was the first time we were using env vars set from secrets (env[x].valueFrom.secretKeyRef). Maybe it will ring a bell for someone. ​

Re: timeout expired waiting for volumes to attach/mount for pod

We have tried to rollback the master to 1.4, and it worked for a few moments. And now, again, we can't deploy anything unless we restart origin-node for every deploy. I guess now the solution will be to restart origin-node every 5 minutes on all nodes to make sure deploy are not blocked :( ​

Re: timeout expired waiting for volumes to attach/mount for pod

And the problem occurs on all our nodes btw. ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: oc rsh or oc get pod -w disconnection after few minutes

We have achieved a lot of tests, and the connection is dropped somewhere in Openshift, not by the firewall. As we don't have any proxy, except haproxy. We've seen

Re: timeout expired waiting for volumes to attach/mount for pod

Could it be related to this? https://github.com/openshift/origin/issues/11016 ​ Sounds definitely like our issue, I just don't understand why would we hit this suddenly. ___ users mailing list users@lists.openshift.redhat.com

Re: timeout expired waiting for volumes to attach/mount for pod

On the master, we're seeing this on a regular basis: https://gist.github.com/gravis/cae52e763cd5cdac19a8456f9208aa34 I don't know if it can be related ___ users mailing list users@lists.openshift.redhat.com

Re: timeout expired waiting for volumes to attach/mount for pod

Our nodes are up-to-date already, but we're not using docker-latest (1.13). I don't think that's an issue, since everything was fine with 1.12 last week. ​ The only thing having changed lately are PVs, we are migrating some datastores. I wonder if one of them could be an issue, and openshift is

Re: timeout expired waiting for volumes to attach/mount for pod

Hi, We have this issue on Openshift 1.5 (with 1.4 nodes because of this crazy bug https://github.com/openshift/origin/issues/14092). It started a few days ago, and nothing really changed in our cluster. We just added a bunch of secrets, and noticed longer and longer deploys. We have nothing

Re: timeout expired waiting for volumes to attach/mount for pod

And... it's starting again. Pods are getting stuck because volumes (secrets) can't be mounted, then after a few minutes, everything starts. I really don't get it :( ​ ___ users mailing list users@lists.openshift.redhat.com

Re: timeout expired waiting for volumes to attach/mount for pod

After a lot of tests, we discovered the pending pods were always on the same node. There were some (usual) "thin: Deletion of thin device" messages. After draining the node, nuking /var/lib/docker, a hard reboot, everything went back to normal. I suspect devicemapper to be the source of all our

timeout expired waiting for volumes to attach/mount for pod

Hi, Since a few days, we have pods waiting for volumes to be mounted, and get stuck for several minutes. https://www.dropbox.com/s/9vuge2t9llr7u6h/Screenshot%202017-07-11%2011.29.19.png?dl=0 After 3-10 minutes, the pod eventually starts, with no obvious reason. Any idea what could cause this?

Re: oc whoami bug?

Just to be clear, my point is: if `oc whoami` returns "error: You must be logged in to the server (the server has asked for the client to provide credentials)", `oc whoami -t` should return the same if the session has timed out ;)​ ___ users mailing list

Re: oc whoami bug?

On Mon, Jun 19, 2017 at 4:56 PM, Louis Santillan wrote: > The default user for any request is `system:anonymous` a user is not > logged in or a valid token is not found. Depending on your cluster, this > usually has almost no access (less than `system:authenticated`).

oc whoami bug?

Hi, I think I have hit a bug (or a lack of warning message) with `oc whoami -t`: I tried to login on our registry, and only got "unauthorized: authentication required" responses. After a couple of tries, I launched `oc whoami` without -t: "error: You must be logged in to the server (the server

Re: Cronjob: Failed to pull image "...": unauthorized: authentication required

Answering to myself: https://github.com/openshift/origin/issues/13161 ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Cronjob: Failed to pull image "...": unauthorized: authentication required

ps: the image is an imageStream in the same namespace.​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Cronjob: Failed to pull image "...": unauthorized: authentication required

Hi, I created a cronJob ( https://docs.openshift.com/container-platform/3.5/dev_guide/cron_jobs.html) in a project on openshift 1.5, and the job fails to start with: Failed to pull image "...": unauthorized: authentication required Error syncing pod, skipping: failed to "StartContainer" for

Re: Possible bug with haproxy?

On Fri, May 26, 2017 at 4:24 PM, Clayton Coleman wrote: > HAProxy doesn't currently support HTTP/2 connections - so unless you've > done something custom, you shouldn't even be able to connect to HAProxy as > http/2 That's maybe the issue then. Since A.domain is a

Possible bug with haproxy?

Hi, could you take a look at this please: https://stackoverflow.com/questions/44162263/request-cached-when-using-http-2/44163462 I wonder if the problem could come from haproxy? We're using the images "openshift/origin-haproxy-router:v1.5.0" Thanks, Philippe

Re: Pods has connectivity to other pod and service only when I run an additional pod

Do you know if it's possible to run 1.4 nodes with 1.5 masters? We need to start rolling back, we have too many issues with our clients :( Thanks ​ ___ users mailing list users@lists.openshift.redhat.com

Re: Pods has connectivity to other pod and service only when I run an additional pod

@Clayton, it sounds like a critical bug here, other people are seeing this issue too. Thanks, Philippe ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Passthrough and insecure route

Hmm, tested with OS 1.4.1: Route "https" is invalid: spec.tls.insecureEdgeTerminationPolicy: Invalid value: "Redirect": InsecureEdgeTerminationPolicy is only allowed for edge-terminated routes but the doc ( https://docs.openshift.com/container-platform/3.4/architecture/core_concepts/routes.html)

Re: Passthrough and insecure route

On Wed, Apr 19, 2017 at 2:35 PM, Clayton Coleman wrote: > 1.4 added the ability to specify insecureEdgeTerminationPolicy for > passthrough Good, thanks :) ___ users mailing list users@lists.openshift.redhat.com

Passthrough and insecure route

Hi, It seem impossible to register a route with both "passthrough" tls termination and standard http. The "insecure" route is being rejected because the https route already exposes the same host. Is there a reason for that? I'm using passthrough because the underlying service has its own ssl

Re: Volumes with subpath

ps : we're using NFS in our test, but it should not matter.​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Volumes with subpath

Hi, We're testing the new k8s SubPath for volumes, and it's not working as what we had in mind. We'd like to have something like: volumeMounts: - name: app mountPath: /var/data subPath: /data - name: app mountPath: /opt/data2 subPath: /data2 But it seems like the PV

Re: Let's encrypt routers

Thanks for your efforts and investment Tomas, I'm sure it will benefit to a large number of users!​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Let's encrypt routers

://caddyserver.com/docs/proxy). Thanks, Philippe -- Philippe Lafoucrière - CEO http://www.tech-angels.com https://gemnasium.com France : +33 (0) 3 65 96 02 92 Canada: +1 (418) 478-1175 USA: +1 (954) 607-7443 ___ users mailing list users

Re: S2I and git-lfs

On Mon, Jan 16, 2017 at 12:40 PM, Jonathan Yu wrote: > What about git-annex? https://apps.fedoraproject.org/packages/git-annex > Unfortunately, we don't manage what our clients are using. LFS is now supported directly in Github, Gitlab, and Bitbucket (and probably others),

Re: S2I and git-lfs

@Clayton, does it sound reasonable to you to ask for LFS support in s2i? If yes, where should this ticket go? https://github.com/openshift/source-to-image ? Thanks ​ ___ users mailing list users@lists.openshift.redhat.com

Re: S2I and git-lfs

On Thu, Jan 12, 2017 at 3:50 PM, Ben Parees wrote: > ​it's part of the origin/sti-builder infrastructure image. if git-lfs > requires client side logic, it's not going to work with openshift s2i > builds i'm afraid. (at least not w/o some hackery like doing the git clone >

Re: S2I and git-lfs

On Thu, Jan 12, 2017 at 3:43 PM, Ben Parees wrote: > ​no known issues but no known uses either. s2i is basically just git > cloning your repo, it sounds like the lfs pointers didn't resolve properly > during the clone operation. I don't know the inner workings of how that

Re: ceph pv

On Mon, Jan 9, 2017 at 3:42 AM, James Eckersall wrote: > Our use case would be utilisation of openshift clusters with untrusted > clients in distinct projects, so we’re trying to ensure they can’t access > each/others storage. We are in the same situation, and we

Re: Link to other files in yaml configuration

On Mon, Jan 9, 2017 at 3:18 PM, Ben Parees wrote: > or references to secrets from within the DC? Sorry, I meant routes, I mixed up two messages. So no, I don't think I can use a secret in a route :) Going with a template is probably the only way to achieve this. Thanks!

Link to other files in yaml configuration

Hi, Does anyone know if I can use external files in a yaml file? I'd like to keep out the certificate files (crt, CA and key) from my DeploymentConfig yaml file. Thanks! Philippe ___ users mailing list users@lists.openshift.redhat.com

Re: Can't push images after 1.3.0 upgrade

Hmm, I got it working by removing the :443 in our repo url (while this port was needed before to be able to push...) ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Can't push images after 1.3.0 upgrade

: sha256:fa1f5a94b89552b2c9d370c7ff779d658e09547eae00d931a3b1f2502f1f7260 size: 3339 Cordialement, Philippe Lafoucrière -- Philippe Lafoucrière - CEO http://www.tech-angels.com https://gemnasium.com France : +33 (0) 3 65 96 02 92 Canada: +1 (418) 478-1175 USA: +1 (954) 607-7443 On Thu, Jan 5

Re: Can't push images after 1.3.0 upgrade

I'm digging this up. We just upgraded our production cluster to OS 1.3, and having this issue again. Builds are working as expected, but we can't push using our CI any more, with the same exact symptoms as above :( Any idea? I have tried to reconcile roles, with no success. Thanks

oc .env files

on cluster, not any of the test clusters) - Current namespace (to make sure apply won't fu.. up another project if we forget to specify it). Is there something we could see in the future? Thanks, Philippe -- Philippe Lafoucrière - CEO http://www.tech-angels.com https://gemnasium.com France : +33 (0) 3 6

Re: Upgrading to 1.3 / 3.3

On Mon, Nov 7, 2016 at 5:31 PM, Diego Castro wrote: > Hi Philippe i have upgraded without major issues using blue/green upgrade. > The only thing was the secured registry that i managed to solve turning off > the hosted registry at inventory file. > Thanks for

Re: Metrics - Could not connect to Cassandra cluster

The problem is we removed everything in the project, and tried to reinstall with ansible. Since we can't deploy the metrics (even with the v1.2.1 image, note that v1.2.2 doesn't exist: https://hub.docker.com/r/openshift/origin-metrics-deployer/tags/), we're screwed :( We'll try this on another

Re: Metrics - Could not connect to Cassandra cluster

We have the exact same problem, except hawkular-metrics never starts in our case. We tried a lot of things, ending with removing everything in openshift-infra, and now metrics aren't deploying anymore (with or without ansible). The deployer always fails: [...] Adding password for user hawkular

Re: How can I put logstash config files in ConfigMap ?

It seems to have been fixed in k8s 1.4.0, so with OS 1.3.1 as well. https://github.com/kubernetes/kubernetes/blob/v1.4.0/pkg/util/validation/validation.go#L273 ​ ___ users mailing list users@lists.openshift.redhat.com

Re: Why I don't have debug information in DockerRegistry logs?

See: https://github.com/openshift/openshift-ansible/issues/2648 The registry is not logging anything because the ssl handshake failed. ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: HELP - Image pull back off

For the record, I'm pretty sure that's the issue blocking us from upgrading to 1.3.X (the symptoms are exactly the same + this issue https://github.com/openshift/origin/issues/11164). We're using ansible to upgrade, and this change is part of it (yes, we should run ansible more often).

Re: HELP - Image pull back off

It's definitely ansible :( We have updated by hand all nodes, and after an ansible run, the wrong config is back ​We'll investigate from here ___ users mailing list users@lists.openshift.redhat.com

Re: Managing OpenShift Configuration with Puppet/Ansible… what are your best practices?

Thanks Clayton! Really looking forward to seeing this released :) ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Managing OpenShift Configuration with Puppet/Ansible… what are your best practices?

Just to clarify our need here: We want the projects config inside a configuration tool. There's currently nothing preventing from modifying the config of a project (let's say, a DC), and no one will be notified of the change. We're looking for something to keep track of changes, and make sure the

Re: Secrets not available anymore with 1.3.0

Any news on this? This is really a blocking issue to upgrade to 1.3.0 for us. ​ Thanks Philippe ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Can't push images after 1.3.0 upgrade

We're using :443/namespace/imagestream We had to rollback to previous snapshots, we never managed to get it working :( ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Secrets not available anymore with 1.3.0

It's definitely an issue related to 1.3.0. I have downgraded the cluster to 1.2.1, and it works again :(​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Can't push images after 1.3.0 upgrade

Note that I can pull the image with this account. I have tried to readd the role to the user: $ oadm policy add-cluster-role-to-user system:image-builder our_ci_user with no success. According to https://docs.openshift.com/container-platform/3.3/admin_guide/manage_authorization_policy.html, I

Re: Can't push images after 1.3.0 upgrade

On Tue, Sep 27, 2016 at 4:29 PM, Jordan Liggitt wrote: > > Do you have the registry logs available from the timeframe during the push? 10.1.0.1 - - [27/Sep/2016:20:59:57 +] time="2016-09-27T20:59:58.948672089Z" level=error msg="error authorizing context: authorization

Re: Secrets not available anymore with 1.3.0

Is this what you're looking for? secret.go:152] Setting up volume airbrake-secrets for pod 41cdd02f-84ea-11e6-be87-005056b17dcc at /var/lib/origin/openshift.local.volumes/pods/41cdd02f-84ea-11e6-be87-005056b17dcc/volumes/ kubernetes.io~secret/airbrake-secrets nsenter_mount.go:183] findmnt

Can't push images after 1.3.0 upgrade

Hi, Another issue we're facing after the upgrade to 1.3.0: our CI service account can't push images to the registry anymore. I have tried to push the image by hand: 202bc3fd6fe4: Pushing [==>] 7.114 MB be16db112b16: Pushing

Secrets not available anymore with 1.3.0

Hi, We're testing OS 1.3.0 on our test cluster, and have something weird happening. The secrets are mounted, but apparently not readable anymore in _some_ pods: This is on openshift 1.2.1: { "Source":

Re: Adding master to 3 node install

On Thu, Aug 11, 2016 at 8:42 PM, Jason DeTiberus wrote: > This sounds like your registry was using ephemeral storage rather than > being backed by a PV or object storage. It's should not. We're using: docker_register_volume_source='{"nfs": { "server": "10.x.x.x", "path":

Re: configuring periodic import of images

https://docs.openshift.com/enterprise/3.2/install_config/install/docker_registry.html " The manifest v2 schema 2 (*schema2*) is not yet supported." Sorry :) ​

Re: configuring periodic import of images

On Thu, Aug 11, 2016 at 5:15 PM, Tony Saxon wrote: > Damn, I just went through having to downgrade my registry because I was > pushing with 1.12 and openshift (running docker 1.10) wasn't able to pull > the image due the the sha256 hash that it was referencing not existing

Re: configuring periodic import of images

If you are using different versions of docker on openshift, and the server where the image was build, you will fall into this (known) problem. Check out https://trello.com/c/CJiUnVUm/136-3-docker-1-10- push-force-schema1-manifest-via-daemon-flag Hopefuly, this seems to be fixed in the upcoming

Re: unexpected fault address 0x0

Hmm, indeed, the container will be always Up: # cat /usr/local/bin/origin-node-run.sh #!/bin/sh set -eu conf=${CONFIG_FILE:-/etc/origin/node/node-config.yaml} opts=${OPTIONS:---loglevel=2} function quit { pkill -g 0 openshift exit 0 } trap quit SIGTERM if [ ! -f

Re: Adding master to 3 node install

Did you check out this? https://docs.openshift.com/enterprise/3.1/install_config/install/advanced_install.html#adding-nodes-advanced ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Recreate strategy optimization

Hi, I have noticed something that could be optimized in recreate strategy: During a deploy, Openshift will set the current running replicas to zero, and then pull the new image, and eventually starts it. The problem is, sometimes, the pull can very (very) long, and during that period, the pods

Re: Atomic Centos, can't upgrade

We're using postgres 9.5. It was working fine before the upgrade. Unfortunately, we upgraded atomic AND Openshift at the same time, so I can't tell if it's a problem with docker 1.10 or openshift 1.2.1. I'd tend to say Docker 1.10, but we need to isolate this first. Thanks, Philippe ​

Re: Atomic Centos, can't upgrade

https://docs.openshift.org/latest/dev_guide/shared_memory.html fixed the issue, but It seems something changed regarding /dev or shm docker mounts between 1.2.0 and 1.2.1. Can someone confirm? ​ ___ users mailing list users@lists.openshift.redhat.com

Re: Atomic Centos, can't upgrade

I confirm: it's fixed :)​ thanks! ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

On Tue, Jul 12, 2016 at 5:22 PM, Scott Dodson wrote: > I'll see if I can get openshift/node:v1.2.0 rebuilt with this fix but > you can also rebuild the node image placing the docker wrapper script > in /usr/local/bin > Any news on this? Thanks

Re: Atomic Centos, can't upgrade

Testing it right away. Thanks guys :) ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

Good catch Scott: [plafoucriere@atomic-test-node-1 origin]# docker info /usr/bin/docker-current: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory ​ ___ users mailing list

Re: Atomic Centos, can't upgrade

On Mon, Jul 11, 2016 at 9:56 AM, Scott Dodson wrote: > That commit is mostly related to the fact that we cannot > upgrade/downgrade docker on atomic host like can on RHEL so abort the > docker upgrade playbook early. > Ok, I get it now, thanks. Anyway, we couldn't fix our

Re: Atomic Centos, can't upgrade

Sounds like docker 1.10 is a bad idea, I found this commit: https://github.com/openshift/openshift-ansible/commit/b377f9d85df11c532281c213eda1869596642204 I was probably running openshift-ansible with a wrong tag :( ​ ___ users mailing list

Re: PVs, Endpoints, and GlusterFS

That's right, you'll have to create endpoints inside each project, and a service to make sure the endpoints are not cleaned-up. We have switched back to simple NFS after having a LOT of issues with glusterfs, especially data corruption. It's a lot easier to setup in openshift (no endpoints, no

Re: Atomic Centos, can't upgrade

We have updated our beta cluster to latest atomic centos: -bash-4.2# atomic host status TIMESTAMP (UTC) VERSIONID OSNAME REFSPEC * 2016-07-07 21:23:41 7.20160707 cd47a72eb5 centos-atomic-host centos-atomic-host:centos-atomic-host/7/x86_64/standard

Error pulling image (v1.2.0) from docker.io/openshift/origin-metrics-hawkular-metrics, HTTP code 400

Hi, We can't pull this image anymore on our nodes: Error pulling image (v1.2.0) from docker.io/openshift/origin-metrics-hawkular-metrics, HTTP code 400 We're still using docker 1.9, and it seems we can pull the image everywhere else (docker 1.9, 1.11, etc.), but not on the nodes where it was

Labels removed from private registry

Hi, We have labeled our images with a git commit sha, and apparently this label disappear when the image is pushed on our openshift private registry. Is this something on purpose? Thanks, Philippe ___ users mailing list users@lists.openshift.redhat.com

Re: logs aggregation

Great! I will take a look Thanks ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: All my image stream are bad docker registry IP, where is my mistake ?

On Thu, Jun 23, 2016 at 12:37 PM, Clayton Coleman wrote: > Did you delete and recreate your docker registry? > > yes, several times. And we can't find any clue from where this IP is coming from. We have grep all files, searched in etcd, and nothing. It's a mystery :)

Re: What is the consequence if I switch from ovs-subnet to ovs-multitenant on production cluster ?

Thanks! We would love some feedback from people having done this before. We have a test cluster, with snapshots, but sometimes it's all about the details, and something could fail after a while :) ​ ___ users mailing list

Re: What is the consequence if I switch from ovs-subnet to ovs-multitenant on production cluster ?

@Clayton, any idea on this?​ Thanks ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: prune tags

On Tue, Jun 21, 2016 at 2:33 PM, Clayton Coleman wrote: > I don't think we have anything to prune tags (since we don't know what > tag names to prune). We'd need some way of knowing the tag was "not > important" before it could be pruned. > I would say, if no stream nor

prune tags

Hi, As we're using openshift for continuous deployments, we often have a lot of tags per ImageStream (to test branches). We would love to see these unused tags pruned, like other objects. Is there something in the roadmap? Thanks, Philippe -- Philippe Lafoucrière - CEO http://www.tech

Re: MySQL: Readiness probe failed

Have you tried to raise initialDelaySeconds ? ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Build/Deploy notifications

Hi, We're using Openshift to do continuous deployment, and it's working great. Anyway, we should be notified (email, slack, etc.) when something went wrong, like a failing deployment. Is there anyway to achieve that? Thanks Philippe ___ users mailing

Re: Atomic Centos, can't upgrade

Thanks Tobias for the detailed help! I should have thought of running again ansible, I was focused on the error. ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Atomic Centos, can't upgrade

Hi, We have tried to update our atomic host centos 7, with the tree 3c3786d1dd (from the tree e39c28570a), but deployments are all failing after the updates on the nodes: Error syncing pod, skipping: failed to "SetupNetwork" for "some_deploy" with SetupNetworkError: "Failed to setup network for

Re: ImagePullBackOff - API error (500): manifest unknown

Thanks!​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: ImagePullBackOff - API error (500): manifest unknown

Is there a github issue we can follow to have updates on this? Thanks ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: 503 - Maintenance page

On Tue, Jun 7, 2016 at 6:45 PM, Ram Ranganathan wrote: > Is your server always returning 503 - example for a GET/HEAD on / ? That > could cause haproxy to mark it as down. > > You can also see the stats in haproxy to look at if the server has been > marked down: >

Re: 503 - Maintenance page

On Tue, Jun 7, 2016 at 3:46 PM, Luke Meyer wrote: > It sounds like what he wants is for the router to simply not interfere > with passing along something that's already returning a 503. It sounds like > haproxy is replacing the page content with its own in that use case.

Re: 503 - Maintenance page

@Clayton: Sorry for the confusion. I'm not updating the routeR, I'm updating the route directly. The route to our website is pointing to a "maintenance" service during maintenance. This service serves 503 pages for most URLs, except a few for testing purprose. The problem is: If I browse my

Re: Limiting scaling of a pod

On Sun, May 22, 2016 at 7:05 PM, Clayton Coleman wrote: > What are you trying to defend against? The more concrete examples you > can provide (where the app would be broken if there is >1 copy) the > more we can do to ensure the use case is solved. > We have a legacy

Re: Error updating deployment [deploy] status to Pending

Hi, Yes the node is ready. I have tried to unschedule it, and evacuate pods, it's not working either. I don't use any PV in the test I'm doing. The other node seems to have the same problem, so I guess it's somewhere else than the node. Maybe corrupted data in etcd? This cluster has been working

Re: Error updating deployment [deploy] status to Pending

If I make this node unschedulable, I get an event: "node 'openshift-node-1' is not in cache" Does this ring a bell? (and the pod is still pending) For the record, there's PV used in this pod, and all pods have the same behavior now on this cluster. Only a restart of origin-node can unlock them.

Re: Error updating deployment [deploy] status to Pending

I have this in the logs (with loglevel=4): https://gist.github.com/gravis/7454a743cb988f6d192bf5a5c9890a82 So, nothing fancy :( Thanks ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Error updating deployment [deploy] status to Pending

Hello, I can't deploy any on os 1.1.3: the deploy (and/or build) is stuck on pending, with the message: Error updating deployment [project]/[deploy] status to Pending in the events. Nothing specific in the logs. Using oc describe doesn't give any reason, and I see a different event: Events:

Re: RWO mounted on multiple hosts

ho, and btw, Openshift was mentioned MANY times ;)​ Thanks for the hard work guys. http://www.slideshare.net/plafoucriere/rails-monolithtomicroservicesdesign (With speaker notes:) https://speakerdeck.com/jipiboily/from-rails-to-microservices-with-go-our-experience-with-gemnasium-enterprise

Re: RWO mounted on multiple hosts

I'm at a conference this week, will try to send you something next week. Thanks Philippe ​ ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

  1   2   >