Re: Failure when adding node - Approve node certificates when bootstrapping

Hi, I've recently run the scaleup procedeure on a 3.11 OKD cluster with the same result(failure) from the ansible run. However, when checking for node status and extra info I've found that the node was successfully added to the cluster and in "Ready" state. oc get nodes -o wide -> gives the

OKD 3.10 and Jenkins update

Hello all! OKD-3.10 ships with Jenkins 2.107.3(I guess LTS version). Looking at the Dashboard, there are multiple security vulnerabilities reported for both the main version and for the plugins that are shipped with it. I tried a simple upgrade on all listed plugins, but the result was that

Re: ServiceAccount token for a build Pod (Dynamic resource creation )

reference to? Thanks again for the info and help, Dan Pungă On 30.11.2018 02:49, Ben Parees wrote: On Thu, Nov 29, 2018 at 6:53 PM Dan Pungă <mailto:dan.pu...@gmail.com>> wrote: Thanks for the reply! My response is inline as well. On 30.11.2018 00:51, Ben Parees wrote:

Re: ServiceAccount token for a build Pod (Dynamic resource creation )

Thanks for the reply! My response is inline as well. On 30.11.2018 00:51, Ben Parees wrote: On Thu, Nov 29, 2018 at 5:34 PM Dan Pungă <mailto:dan.pu...@gmail.com>> wrote: Hello all, The short version/question would be: How can I use a custom ServiceAccount with a Bu

Re: OKD 3.9 to 3.10 upgrade failure on CentOS

Hi Dharmit, What you're experiencing looks a lot like a problem I had with the upgrade. I ended up doing a fresh install. I've tried fiddling around with the ansible config and as I was trying to get my head about what was happening I discovered an issue about node names. With this reply

ServiceAccount token for a build Pod (Dynamic resource creation )

Hello all, The short version/question would be: How can I use a custom ServiceAccount with a BuildConfig? It appears the build Pod doesn't have the serviceAcoount's token mounted at the location: cat: /var/run/secrets/kubernetes.io/serviceaccount/token: No such file or directory Thank

Re: Node names as IPs not hostnames

On 09.10.2018 20:45, Rich Megginson wrote: Are you hitting https://github.com/openshift/openshift-ansible/pull/9598 ? On 10/9/18 11:25 AM, Dan Pungă wrote: Thanks for the reply Scott! I've used the release branches for both 3.9 and 3.10 of the openshift-ansible project, yes. I've initially checked

Re: Node names as IPs not hostnames

, Scott Dodson wrote: Dan, are you using the latest from release-3.10 branch? I believe we've disabled the IaaS interrogation when you've not configured a cloud provider via openshift-ansible in the latest on that branch. On Mon, Oct 8, 2018, 7:38 PM Dan Pungă <mailto:dan.pu...@gmail.com>&

Re: Node names as IPs not hostnames

to integrate with a provider was if I'd specifically set the openshift_cloudprovider_kind variable in the inventory file along with the rest of the specific variables. Regards, Dan Pungă On 08.10.2018 18:44, Dan Pungă wrote: Hello all, I'm trying to upgrade a working cluster from Openshift

Node names as IPs not hostnames

Hello all, I'm trying to upgrade a working cluster from Openshift Origin 3.9 to OKD 3.10 and the control plane update fails at one point with host not found. I've looked abit over the problem and found this issue on github: https://github.com/openshift/openshift-ansible/issues/9935 where

Openshift Origin 3.9 - Web-Console masterURL configMap and authentication problems - part 2

Hello all! I'll have to resubmit this issue as it's still a problem for my installed cluster. My environment consists of 2 masters and one load-balancer that has the default HAProxy installed by the automated install procedure via the openshift-ansible project. So it's basically the

Re: hawkular-cassandra failed to startup on openshift origin 3.9

Hi, I've installed a similar configuration and it works. Origin 3.9 with metrics installed and ephemeral storage(emptyDir/default). What I have specified in my inventory file is openshift_metrics_image_prefix=docker.io/openshift/origin- openshift_metrics_image_version=v3.9 so I also have the

Origin 3.9 master-api error

Hello all! Yet another question/problem from yours truly ...:) I'm trying to access the cluster with oc login which returns Error from server (InternalError): Internal error occurred: unexpected response: 400 I've tried both the lb entrypoint and also to directly connect to a master. Don't

Re: Origin 3.9 Installation Issue

Hi, Not sure about the error, but I've noticed a task that I haven't seen during my installation attempts (also Origin 3.9 on a cluster). From what I see, "origin_control_plane" is an ansible role that's present on the master branch of the openshift-ansible repo, but not on the release-3.9

Minimum hardware requirements regarding storage

requirements? Thank you, Dan Pungă ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Image pull error when using the integrated registry

60-441f-98b3-704cf181692c http.request.method=GET http.request.remoteaddr="10.128.2.1:42448" http.request.uri="/v2/generic/ot-builder-npm-is/manifests/sha256:9efdf954ec62e662e67d3f1c71f9d46faf9c82c76f8513338c2a4b19b6f318b5" http.request.useragent="docker/1.13.1 go/go1.8.3 kernel

Image pull error when using the integrated registry

Hello all! I'm experiencing a problem when trying to pull an image from Openshift's container registry. I've recently installed OpenshiftOrigin 3.9 with docker-registry deployed. I'm using 2 projects, one where "generic" images are built and one for "applications". When running a build in

Re: Provisioning persistence for metrics with GlusterFS

ara trabalhar no Brasil pelo *Great Place to Work*. On Wed, May 16, 2018 at 10:35 PM, Dan Pungă <dan.pu...@gmail.com <mailto:dan.pu...@gmail.com>> wrote: Hello all! I have setup a cluster with 3 glusterFS nodes for disk persistence just as specified in the docs. I have

Re: Web-Console masterURL configMap and authentication problems

. On Wed, May 16, 2018 at 7:34 PM, Dan Pungă <dan.pu...@gmail.com <mailto:dan.pu...@gmail.com>> wrote: Thanks for the reply Sam! Unfortunately with this setup I get only the "invalid request" page that I've attached previously. But now the URL stays on loadbalan

Provisioning persistence for metrics with GlusterFS

ab2244ca721b7d15ea1e514 vg_bd61a1e6f317bb9decade964449c12e8 Vwi-aotz--  5,00g tp_8818ffee7ab2244ca721b7d15ea1e514 7,57   tp_7aa3a789badd1ae620a2bbefe51b8c73 vg_bd61a1e6f317bb9decade964449c12e8 twi-aotz-- 2,00g    0,71 0,33   tp_8818ffee7ab2244ca721b7d15ea1e514 vg_bd61a1e6f317bb9decade964449c12e8 twi-aotz-- 5,00g    7,57   0,29 Any ideas where to look for misconfigurations? Thank you, Dan Pungă ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Web-Console masterURL configMap and authentication problems

":["https://loadbalance.my.net:8443/"]}' Editing the OAuth client should fix the invalid request error on login. Sam On Wed, May 16, 2018 at 6:03 PM, Dan Pungă <dan.pu...@gmail.com <mailto:dan.pu...@gmail.com>> wrote: Hello all! I'm setting up a recently ins

Web-Console masterURL configMap and authentication problems

t:8443/console/ Do you have any ideas about these 2 issues? Especially the second one. Thank you for any help in advance, Dan Pungă ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OShift install - DNS resolution and NetworkManager issues

Ss got via DHCP + my 192.168.150.5 On 09.05.2018 19:30, Dan Pungă wrote: Hello all! Let me first start by specifying that my problem isn't specifically OpenShift related, but I'm trying this mailing list in hopes that someone faced my problem before and somehow managed to solve it. I'm running

OShift install - DNS resolution and NetworkManager issues

without restarting NetworkManager service. This way name resolution is functioning and I'm also able to start the origin-node service, but I'm afraid this is not suited for the automated installation process. Any help/hints are much appreciated! Dan Pungă

Re: Deployment Strategy: lifecycle hooks how to inject configuration

g out of a new deployment is quicker, with the old pods being quickly switched to the new ones. In a stateless environment, such as mine, this is nice. Thanks again, Dan Pungă PS: I'm kind of interfering in an ongoing discussion. Please, don't let my message stop you; this is first-hand

Re: Parametrizing a BuildConfiguration with Docker ARGs

time being no ARGs prior to FROM for me. :) Thanks again for the help, Ben! On 08.02.2018 23:01, Ben Parees wrote: On Thu, Feb 8, 2018 at 3:53 PM, Dan Pungă <dan.pu...@gmail.com <mailto:dan.pu...@gmail.com>> wrote: I guess it does have to do with your Docker version.

Re: Parametrizing a BuildConfiguration with Docker ARGs

/must have//|FROM|as its first instruction/" while for 17.12, it appears they have relaxed this requirement. On 08.02.2018 17:19, Ben Parees wrote: On Wed, Feb 7, 2018 at 10:30 AM, Dan Pungă <dan.pu...@gmail.com <mailto:dan.pu...@gmail.com>> wrote: Thank

Re: Parametrizing a BuildConfiguration with Docker ARGs

, Ben Parees wrote: btw, openshift will happily substitute your FROM statement w/ an image referenced by your BuildConfig, so if that's your goal, perhaps that is a way to accomplish it. https://docs.openshift.org/latest/dev_guide/builds/build_strategies.html#docker-strategy-from On Wed, Feb 7, 2018 at

Parametrizing a BuildConfiguration with Docker ARGs

Hello all! I've recently discovered and join this mailing list; hope I'm in the right place. I'm new to the OShift ecosystem, currently trying to develop a configuration to containerize some apps. I'm using minishift local cluster on a Ubuntu 16.04 machine (details below). I want to write a