Re: Hawkular metrics returns Forbiden

Did you find any solution for this? On Fri, 15 Sep 2017 at 01:34 Mateus Caruccio wrote: > Yep, there it is: > > [OSEv3:children] > masters > etcd > nodes > > [OSEv3:vars] > deployment_type=origin > openshift_release=v3.6 > debug_level=1 > openshift_debug_level=1

Re: OpenShift Origin v3.6.0 is released

o be a point change. > > On Mon, Jul 31, 2017 at 11:02 PM, Andrew Lau <and...@andrewklau.com> > wrote: > >> I think the node images are still missing the sdn-ovs package. >> >> On Tue, 1 Aug 2017 at 07:45 Clayton Coleman <ccole...@redhat.com> wrote: >> >&

Re: OpenShift Origin v3.6.0 is released

te: > >> Hrm, so they do. Looking. >> >> On Mon, Jul 31, 2017 at 11:57 AM, Andrew Lau <and...@andrewklau.com> >> wrote: >> >>> The images still seem to be using rc0 packages. >>> >>> rpm -qa | grep origin >>> origin-clients-3.6.0

Re: OpenShift Origin v3.6.0 is released

The images still seem to be using rc0 packages. rpm -qa | grep origin origin-clients-3.6.0-0.rc.0.359.de23676.x86_64 origin-3.6.0-0.rc.0.359.de23676.x86_64 I also had a PR which just got merged for a missing package in the node image https://github.com/openshift/origin/pull/15542 On Tue, 1 Aug

Re: Origin v1.5.1 has been released

Cheers On Thu, 18 May 2017 at 15:00 Clayton Coleman <ccole...@redhat.com> wrote: > Check now > > On Thu, May 18, 2017 at 12:10 AM, Andrew Lau <and...@andrewklau.com> > wrote: > >> Will metrics get their tags bumped to v1.5.1? >> >> On Wed

Re: Origin v1.5.1 has been released

Will metrics get their tags bumped to v1.5.1? On Wed, 17 May 2017 at 07:48 Clayton Coleman wrote: > Two bugs were addressed in this release, please see the GitHub release > page for more info: > > https://github.com/openshift/origin/releases/tag/v1.5.1 >

Pods sometimes deployed without internal network connectivity

I have an issue open here https://github.com/openshift/origin/issues/14092 about pods sometimes getting deployed without internal network connectivity (using multinenant plugin). They still seem to have outbound network connectivity. I believe these may be the relevant logs, I was wondering if

Critical Routing Bug v1.5.0

I believe this is a significant bug that needs attention https://github.com/openshift/origin/issues/13862 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Re: Node report OK but every pod marked unready

Thanks! Hopefully we don't hit this too much until 1.5.0 is released On Fri, 21 Apr 2017 at 01:26 Patrick Tescher <patr...@outtherelabs.com> wrote: > We upgraded to 1.5.0 and that error went away. > > -- > Patrick Tescher > > On Apr 19, 2017, at 10:59 PM, Andrew Lau <a

Re: Node report OK but every pod marked unready

how_bug.cgi?id=1427212 > > > On Thu, 20 Apr 2017 at 15:41 Tero Ahonen <taho...@redhat.com> wrote: > >> Hi >> >> Did u try to ssh to that node and execute sudo docker run to some >> container? >> >> .t >> >> Sent from my iPhone >> >&

Re: Node report OK but every pod marked unready

ker run to some > container? > > .t > > Sent from my iPhone > > > On 20 Apr 2017, at 8.18, Andrew Lau <and...@andrewklau.com> wrote: > > > > I'm trying to debug a weird scenario where a node has had every pod > crash with the error: > >

Node report OK but every pod marked unready

I'm trying to debug a weird scenario where a node has had every pod crash with the error: "rpc error: code = 2 desc = shim error: context deadline exceeded" The pods stayed in the state Ready 0/1 The docker daemon was responding and the kublet and all it's services were running. The node was

Re: Backport requests?

e's running the AWS patches. > > -bc > > > > On Fri, Apr 14, 2017 at 11:37 AM, Clayton Coleman <ccole...@redhat.com> > wrote: > >> I am surprised that hasn't already been backported. Copying some folks >> who may know. >> >> On Apr 13,

Re: Erased pvc disk

Had a similar thing happen an EBS volume last year. Haven't been able to replicate it since. Happened when a node was overloaded and couldn't report back it's status, my best guess was it tried to mount onto another node and some sort of race condition wiped the contents. On Fri, 7 Apr 2017 at

Re: Important: hold on installing/upgrading to Origin 1.4.0

Worth noting, the cluster policy for egressnetworkpolicy became egressnetworkpolicies (had to update our policies) On Wed, 25 Jan 2017 at 10:12 Jordan Liggitt wrote: > Origin 1.4.1 is now available and fixes this issue. > >

Starting container fails with system error

Hi, Has anyone hit this issue where a pod is not able to start after it's been successfully built: Starting container fails with "System error: read parent: connection reset by peer" This issue (https://github.com/docker/docker/issues/14203) seems to say it's fixed in docker 1.10 but atomic

S3 docker registry performance

Hi, Does anyone have any comparisons of s3 registry performance? We've found it to be quite slow, at least 2-3 times longer then using something like an EBS volume. Here's the config being used: encrypt: true secure: true v4auth: true chunksize: 26214400 I stumbled

Excluding replacement pods from quota?

Hi, Is there a way to have the old pod moved into the terminating scope? Or is there an alternative solution for the following use case: User has the following quota: 1 pod in terminating scope 1 pod in non-terminating scope For new builds, the build will complete in the terminating scope but

Re: Project limits

Not sure how I missed that, thanks! On Thu, 14 Apr 2016 at 11:37 Clayton Coleman <ccole...@redhat.com> wrote: > The docs here: > https://docs.openshift.org/latest/admin_guide/managing_projects.html#limit-projects-per-user > > Cover that. > > > On Apr 13, 2

Project limits

Hi, There seems to be documentation on project quotas and disabling self provisioning, however is there a facility that lets us set a limit for the the number of projects a user can have? Thanks. ___ dev mailing list dev@lists.openshift.redhat.com

AWS Dynamic Provision EBS automated annotation?

Hi, When creating a PVC via console or template/quickstart, the volume isn't dynamically created in AWS and the PVC is stuck in an infinite pending state until the following annotation is added to the claim: annotations: volume.alpha.kubernetes.io/storage-class: foo Is there anyway that

Re: Origin updated to v1.1.5

On Fri, 1 Apr 2016 at 07:49 Jason DeTiberus <jdeti...@redhat.com> wrote: > On Thu, Mar 31, 2016 at 4:47 PM, Andrew Lau <and...@andrewklau.com> wrote: > >> The repos there are for just for the standard CentOS rpm installs? I was >> hoping to update my centos atomic

Re: Origin updated to v1.1.5

grab > them now. We are slowly but surely migrating the builds to the Cent OS PaaS > SIG repositories. > > On Wed, Mar 30, 2016 at 12:06 AM, Andrew Lau <and...@andrewklau.com> > wrote: > >> Is there any timeline on when the centos atomic packages will be updated &g

Re: Origin updated to v1.1.5

Is there any timeline on when the centos atomic packages will be updated to meet the new kubernetes+docker version requirements? On Wed, 30 Mar 2016 at 08:12 Clayton Coleman wrote: > Release notes are here > https://github.com/openshift/origin/releases/tag/v1.1.5 > > Note