date:20180321

Re: OpenShift All in One Cluster

2018-03-21 Thread Charles Moulliard

Hi

Your problem comes from this error

F0321 22:28:11.760953  128344 node.go:264] failed to run Kubelet: failed to
create kubelet: misconfiguration: kubelet cgroup driver: "systemd" is
different from docker cgroup driver: "cgroupfs"

that you could resolve if you the cgroupdriver of your docker daemon

https://www.kevinhooke.com/2017/09/25/error-starting-openshift-origin-on-centos-7-systemd-cgroup-driver-vs-cgroupfs-driver/

Regards


CHARLES MOULLIARD

SOFTWARE ENGINEER MANAGER SPRING(BOOT)

Red Hat 

cmoulli...@redhat.comM: +32-473-604014

@cmoulliard 

On Wed, Mar 21, 2018 at 11:40 PM, Tien Hung Nguyen  wrote:

> Hello everyone,
>
> I'm trying to install OpenShift Origin (3.7.2)  All in One Cluster using
> the method 2 of this link https://docs.openshift.
> org/latest/install_config/install/prerequisites.html#
> install-config-install-prerequisites in order to install it on my Ubuntu
> Server, which has been set up as a virtual machine on the Cloud using
> Microsoft Azure.
>
> However, I get the following error when I try to start the server with the
> command sudo ./openshift start :
>
> root@DevOpsToolchain:/usr/openshift-cli/oc-3-7-2# cd
> openshift-origin-server-v3.7.2-282e43f-linux-64bit
>
> root@DevOpsToolchain:/usr/openshift-cli/oc-3-7-2/
> openshift-origin-server-v3.7.2-282e43f-linux-64bit# ./openshift start
>
> W0321 22:28:04.362232  128344 start_master.go:290] Warning:
> assetConfig.loggingPublicURL: Invalid value: "": required to view
> aggregated container logs in the console, master start will continue.
>
> W0321 22:28:04.362298  128344 start_master.go:290] Warning:
> assetConfig.metricsPublicURL: Invalid value: "": required to view cluster
> metrics in the console, master start will continue.
>
> E0321 22:28:04.372259  128344 controllers.go:118] Server isn't healthy
> yet. Waiting a little while.
>
> 2018-03-21 22:28:04.884523 I | etcdserver/api/v3rpc: grpc:
> addrConn.resetTransport failed to create client transport: connection
> error: desc = "transport: dial tcp 10.1.2.4:4001: getsockopt: connection
> refused"; Reconnecting to {10.1.2.4:4001 }
>
> I0321 22:28:04.884902  128344 start_master.go:530] Starting master on
> 0.0.0.0:8443 (v3.7.2+282e43f)
>
> I0321 22:28:04.884920  128344 start_master.go:531] Public master address
> is https://10.1.2.4:8443
>
> I0321 22:28:04.884932  128344 start_master.go:538] Using images from
> "openshift/origin-:v3.7.2"
>
> 2018-03-21 22:28:04.885070 I | embed: peerTLS: cert =
> openshift.local.config/master/etcd.server.crt, key =
> openshift.local.config/master/etcd.server.key, ca =
> openshift.local.config/master/ca.crt, trusted-ca = , client-cert-auth =
> true
>
> 2018-03-21 22:28:04.885180 I | etcdserver/api/v3rpc: grpc:
> addrConn.resetTransport failed to create client transport: connection
> error: desc = "transport: dial tcp 10.1.2.4:4001: getsockopt: connection
> refused"; Reconnecting to {10.1.2.4:4001 }
>
> 2018-03-21 22:28:04.885686 I | embed: listening for peers on
> https://0.0.0.0:7001
>
> 2018-03-21 22:28:04.885737 I | embed: listening for client requests on
> 0.0.0.0:4001
>
> 2018-03-21 22:28:04.887541 I | etcdserver: name = openshift.local
>
> 2018-03-21 22:28:04.887561 I | etcdserver: data dir = openshift.local.etcd
>
> 2018-03-21 22:28:04.887569 I | etcdserver: member dir =
> openshift.local.etcd/member
>
> 2018-03-21 22:28:04.887581 I | etcdserver: heartbeat = 100ms
>
> 2018-03-21 22:28:04.887587 I | etcdserver: election = 1000ms
>
> 2018-03-21 22:28:04.887599 I | etcdserver: snapshot count = 10
>
> 2018-03-21 22:28:04.887643 I | etcdserver: advertise client URLs =
> https://10.1.2.4:4001
>
> 2018-03-21 22:28:04.888367 I | etcdserver: restarting member
> f054135f4cb3d247 in cluster edcb3d6165d0ae27 at commit index 120
>
> 2018-03-21 22:28:04.888529 I | raft: f054135f4cb3d247 became follower at
> term 3
>
> 2018-03-21 22:28:04.888577 I | raft: newRaft f054135f4cb3d247 [peers: [],
> term: 3, commit: 120, applied: 0, lastindex: 120, lastterm: 3]
>
> 2018-03-21 22:28:05.046282 W | auth: simple token is not cryptographically
> signed
>
> 2018-03-21 22:28:05.093216 I | etcdserver: starting server... [version:
> 3.2.8, cluster version: to_be_decided]
>
> 2018-03-21 22:28:05.093375 I | embed: ClientTLS: cert =
> openshift.local.config/master/etcd.server.crt, key =
> openshift.local.config/master/etcd.server.key, ca =
> openshift.local.config/master/ca.crt, trusted-ca = , client-cert-auth =
> true
>
> 2018-03-21 22:28:05.095359 I | etcdserver/membership: added member
> f054135f4cb3d247 [https://10.1.2.4:7001] to cluster edcb3d6165d0ae27
>
> 2018-03-21 22:28:05.095533 N | etcdserver/membership: set the initial
> cluster version to 3.2
>
> 2018-03-21 22:28:05.095645 I | etcdserver/api: enabled capabilities for
> version 3.2
>
> 2018-03-21 22:28:05.289056 I | raft: f054135f4cb3d247 is starting a new
> election at term 3
>
> 2018-03-21 22:28:05.289293 I | raft: f054

OpenShift All in One Cluster

2018-03-21 Thread Tien Hung Nguyen

Hello everyone,

I'm trying to install OpenShift Origin (3.7.2)  All in One Cluster using
the method 2 of this link
https://docs.openshift.org/latest/install_config/install/prerequisites.html#install-config-install-prerequisites
in order to install it on my Ubuntu Server, which has been set up as a
virtual machine on the Cloud using Microsoft Azure.

However, I get the following error when I try to start the server with the
command sudo ./openshift start :

root@DevOpsToolchain:/usr/openshift-cli/oc-3-7-2# cd
openshift-origin-server-v3.7.2-282e43f-linux-64bit

root@DevOpsToolchain:/usr/openshift-cli/oc-3-7-2/openshift-origin-server-v3.7.2-282e43f-linux-64bit#
./openshift start

W0321 22:28:04.362232  128344 start_master.go:290] Warning:
assetConfig.loggingPublicURL: Invalid value: "": required to view
aggregated container logs in the console, master start will continue.

W0321 22:28:04.362298  128344 start_master.go:290] Warning:
assetConfig.metricsPublicURL: Invalid value: "": required to view cluster
metrics in the console, master start will continue.

E0321 22:28:04.372259  128344 controllers.go:118] Server isn't healthy yet.
Waiting a little while.

2018-03-21 22:28:04.884523 I | etcdserver/api/v3rpc: grpc:
addrConn.resetTransport failed to create client transport: connection
error: desc = "transport: dial tcp 10.1.2.4:4001: getsockopt: connection
refused"; Reconnecting to {10.1.2.4:4001 }

I0321 22:28:04.884902  128344 start_master.go:530] Starting master on
0.0.0.0:8443 (v3.7.2+282e43f)

I0321 22:28:04.884920  128344 start_master.go:531] Public master address is
https://10.1.2.4:8443

I0321 22:28:04.884932  128344 start_master.go:538] Using images from
"openshift/origin-:v3.7.2"

2018-03-21 22:28:04.885070 I | embed: peerTLS: cert =
openshift.local.config/master/etcd.server.crt, key =
openshift.local.config/master/etcd.server.key, ca =
openshift.local.config/master/ca.crt, trusted-ca = , client-cert-auth = true

2018-03-21 22:28:04.885180 I | etcdserver/api/v3rpc: grpc:
addrConn.resetTransport failed to create client transport: connection
error: desc = "transport: dial tcp 10.1.2.4:4001: getsockopt: connection
refused"; Reconnecting to {10.1.2.4:4001 }

2018-03-21 22:28:04.885686 I | embed: listening for peers on
https://0.0.0.0:7001

2018-03-21 22:28:04.885737 I | embed: listening for client requests on
0.0.0.0:4001

2018-03-21 22:28:04.887541 I | etcdserver: name = openshift.local

2018-03-21 22:28:04.887561 I | etcdserver: data dir = openshift.local.etcd

2018-03-21 22:28:04.887569 I | etcdserver: member dir =
openshift.local.etcd/member

2018-03-21 22:28:04.887581 I | etcdserver: heartbeat = 100ms

2018-03-21 22:28:04.887587 I | etcdserver: election = 1000ms

2018-03-21 22:28:04.887599 I | etcdserver: snapshot count = 10

2018-03-21 22:28:04.887643 I | etcdserver: advertise client URLs =
https://10.1.2.4:4001

2018-03-21 22:28:04.888367 I | etcdserver: restarting member
f054135f4cb3d247 in cluster edcb3d6165d0ae27 at commit index 120

2018-03-21 22:28:04.888529 I | raft: f054135f4cb3d247 became follower at
term 3

2018-03-21 22:28:04.888577 I | raft: newRaft f054135f4cb3d247 [peers: [],
term: 3, commit: 120, applied: 0, lastindex: 120, lastterm: 3]

2018-03-21 22:28:05.046282 W | auth: simple token is not cryptographically
signed

2018-03-21 22:28:05.093216 I | etcdserver: starting server... [version:
3.2.8, cluster version: to_be_decided]

2018-03-21 22:28:05.093375 I | embed: ClientTLS: cert =
openshift.local.config/master/etcd.server.crt, key =
openshift.local.config/master/etcd.server.key, ca =
openshift.local.config/master/ca.crt, trusted-ca = , client-cert-auth = true

2018-03-21 22:28:05.095359 I | etcdserver/membership: added member
f054135f4cb3d247 [https://10.1.2.4:7001] to cluster edcb3d6165d0ae27

2018-03-21 22:28:05.095533 N | etcdserver/membership: set the initial
cluster version to 3.2

2018-03-21 22:28:05.095645 I | etcdserver/api: enabled capabilities for
version 3.2

2018-03-21 22:28:05.289056 I | raft: f054135f4cb3d247 is starting a new
election at term 3

2018-03-21 22:28:05.289293 I | raft: f054135f4cb3d247 became candidate at
term 4

2018-03-21 22:28:05.289397 I | raft: f054135f4cb3d247 received MsgVoteResp
from f054135f4cb3d247 at term 4

2018-03-21 22:28:05.289504 I | raft: f054135f4cb3d247 became leader at term
4

2018-03-21 22:28:05.289587 I | raft: raft.node: f054135f4cb3d247 elected
leader f054135f4cb3d247 at term 4

2018-03-21 22:28:05.289934 I | etcdserver: published {Name:openshift.local
ClientURLs:[https://10.1.2.4:4001]} to cluster edcb3d6165d0ae27

I0321 22:28:05.290061  128344 run.go:81] Started etcd at 10.1.2.4:4001

2018-03-21 22:28:05.290159 I | embed: ready to serve client requests

2018-03-21 22:28:05.290538 I | embed: serving client requests on [::]:4001

2018-03-21 22:28:05.300657 I | etcdserver/api/v3rpc: Failed to dial
0.0.0.0:4001: connection error: desc = "transport: remote error: tls: bad
certificate"; please retry.

W0321 22:28:05.301982  128344

Re: Adding host storage during advanced installation

2018-03-21 Thread Judd Maltin

WRT docker, it's part of the startup check/setup process, ensuring that you
have storage for your containers locallly.
/etc/sysconfig/docker-storage-setup has several settings that makes it easy
to manage the (optional creation) and use of LVM by docker.

On Wed, Mar 21, 2018 at 2:33 PM, Patrick Hemmer 
wrote:

> Thanks for the info.
>
> I didn't notice that these *-storage-setup scripts were installed as part
> of the prerequisites playbook in the ansible repo. So yes, they are
> available before starting the deployment process.
>
> In the interim I had just deployed LVM manually and mounted a big volume
> onto /var/lib/containers. Is there anything that details exactly what these
> scripts are doing and why? Such as if using overlay2, why would one want to
> use these scripts instead of a self-managed LVM mounted on
> /var/lib/containers? LVM is easy, and I would think doing it manually
> provides more flexibility than a script trying to guess what you want to
> do, and is also easier to understand. Is this just meant to automate the
> LVM tasks for people who are unfamiliar with it?
>
> -Patrick
>
>
>
> On 2018/3/21 02:03, Frederic Giloux wrote:
>
> Hi Patrick
>
> on RHEL 7.4 (and probably CENTOS 7.4) look at "man
> container-storage-setup". Similar to docker-storage-setup it is a helper
> script to configure the storage used by CRI-O.
> In regard of the procedure I will second what Louis said:
> - first prepare your nodes, including storage
> - install and run your cluster
> If you need later on to extend your storage capacity you can re-run the
> script to add block devices.
>
> Regards,
>
> Frédéric
>
> On Wed, Mar 21, 2018 at 5:14 AM, Louis Santillan 
> wrote:
>
>> Patrick,
>>
>> First, I think you're misunderstanding the order of operations here just
>> a bit.  `docker-storage-setup` is part of the host preparation steps and
>> happens on all nodes in the cluster before running the Advanced Installer.
>> The Container and PaaS Practice's Consulting Playbooks [0] might help your
>> understanding.
>>
>> I'm not fully intimate with CRI-O's internals but It looks like there are
>> some options to set [1].  I don't see any further details on GH so I
>> suspect those details are forthcoming.
>>
>> [0] http://v1.uncontained.io/playbooks/installation/
>> [1] https://github.com/kubernetes-incubator/cri-o/blob/
>> master/docs/crio.conf.5.md
>>
>> ___
>>
>> LOUIS P. SANTILLAN
>>
>> Architect, OPENSHIFT, MIDDLEWARE & DEVOPS
>>
>> Red Hat Consulting,  Container and PaaS Practice
>>
>> lsant...@redhat.com   M: 3236334854
>> 
>> TRIED. TESTED. TRUSTED. 
>>
>>
>>
>> On Tue, Mar 20, 2018 at 7:53 AM, Patrick Hemmer <
>> opensh...@stormcloud9.net> wrote:
>>
>>> How are you supposed to add additional storage to the host when using
>>> the advanced installation procedure (the openshift-ansible repo)?
>>>
>>> The documentation (https://docs.openshift.com/co
>>> ntainer-platform/3.9/install_config/install/host_preparation
>>> .html#configuring-docker-storage) says that you have to use this
>>> "docker-storage-setup" script, which gets installed during the ansible run.
>>> So it seems like ansible would need to pause after installing the script so
>>> the user can go run it. But this is just wrong as that's not how ansible
>>> should be used.
>>>
>>> Additionally the naming of that script sounds like it's docker specific.
>>> How should one handle CRI-O storage? Or does that not need anything special
>>> on top of just having a big /var ?
>>>
>>> -Patrick
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
> --
> *Frédéric Giloux*
> Principal App Dev Consultant
> Red Hat Germany
>
> fgil...@redhat.com M: +49-174-172-4661
>
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> 
> Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
> Handelsregister: Amtsgericht München, HRB 153243
> Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham, Michael
> O'Neill
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Judd Maltin
T: 917-882-1270
Money rewards people who have shut down (or are born without) that part of
themselves which empathizes and is made uncomfortable by exploiting and
harming others. In a system where money rewards sociopathy and money equals
power, that means we necessarily wind up in a system that is ruled by
sociopaths.
__

Re: Adding host storage during advanced installation

2018-03-21 Thread Patrick Hemmer

Thanks for the info.

I didn't notice that these *-storage-setup scripts were installed as
part of the prerequisites playbook in the ansible repo. So yes, they are
available before starting the deployment process.

In the interim I had just deployed LVM manually and mounted a big volume
onto /var/lib/containers. Is there anything that details exactly what
these scripts are doing and why? Such as if using overlay2, why would
one want to use these scripts instead of a self-managed LVM mounted on
/var/lib/containers? LVM is easy, and I would think doing it manually
provides more flexibility than a script trying to guess what you want to
do, and is also easier to understand. Is this just meant to automate the
LVM tasks for people who are unfamiliar with it?

-Patrick


On 2018/3/21 02:03, Frederic Giloux wrote:
> Hi Patrick
>
> on RHEL 7.4 (and probably CENTOS 7.4) look at "man
> container-storage-setup". Similar to docker-storage-setup it is a
> helper script to configure the storage used by CRI-O.
> In regard of the procedure I will second what Louis said:
> - first prepare your nodes, including storage
> - install and run your cluster
> If you need later on to extend your storage capacity you can re-run
> the script to add block devices.
>
> Regards,
>
> Frédéric
>
> On Wed, Mar 21, 2018 at 5:14 AM, Louis Santillan  > wrote:
>
> Patrick,
>
> First, I think you're misunderstanding the order of operations
> here just a bit.  `docker-storage-setup` is part of the host
> preparation steps and happens on all nodes in the cluster before
> running the Advanced Installer.  The Container and PaaS Practice's
> Consulting Playbooks [0] might help your understanding.
>
> I'm not fully intimate with CRI-O's internals but It looks like
> there are some options to set [1].  I don't see any further
> details on GH so I suspect those details are forthcoming.
>
> [0] http://v1.uncontained.io/playbooks/installation/
> 
> [1] 
> https://github.com/kubernetes-incubator/cri-o/blob/master/docs/crio.conf.5.md
> 
> 
>
> ___
>
> LOUIS P. SANTILLAN
>
> Architect, OPENSHIFT, MIDDLEWARE & DEVOPS
>
> Red Hat Consulting,  Container and PaaS
> Practice
>
> lsant...@redhat.com    M: 3236334854
> 
>
>   
> TRIED. TESTED. TRUSTED. 
>
>
>
>
> On Tue, Mar 20, 2018 at 7:53 AM, Patrick Hemmer
> mailto:opensh...@stormcloud9.net>> wrote:
>
> How are you supposed to add additional storage to the host
> when using the advanced installation procedure (the
> openshift-ansible repo)?
>
> The documentation
> 
> (https://docs.openshift.com/container-platform/3.9/install_config/install/host_preparation.html#configuring-docker-storage
> 
> )
> says that you have to use this "docker-storage-setup" script,
> which gets installed during the ansible run. So it seems like
> ansible would need to pause after installing the script so the
> user can go run it. But this is just wrong as that's not how
> ansible should be used.
>
> Additionally the naming of that script sounds like it's docker
> specific. How should one handle CRI-O storage? Or does that
> not need anything special on top of just having a big /var ?
>
> -Patrick
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 
>
>
>
>
> -- 
> *Frédéric Giloux*
> Principal App Dev Consultant
> Red Hat Germany
>
> fgil...@redhat.com  M: +49-174-172-4661
> 
>
> redhat.com  | TRIED. TESTED. TRUSTED. |
> redhat.com/trusted 
> 
> Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
> Handelsregister: Amtsgericht München, HRB 153243
> Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham,
> Michael O'Neill

___

CentOS PaaS SIG meeting (2018-03-21)

2018-03-21 Thread Troy Dawson

Hello,
It's time for our weekly PaaS SIG sync-up meeting

Time: 1700 UTC - Wedensdays (date -d "1700 UTC")
Date: Today Wedensday, 21 March 2018
Where: IRC- Freenode - #centos-devel

Agenda:
- OpenShift Current Status
-- rpms
-- Automated rpm building and Automated testing
-- Documentation
- Upcomming Committee Member Changes
- Open Floor

Minutes from last meeting:
https://www.centos.org/minutes/2018/March/centos-devel.2018-03-14-17.01.log.html

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

Re: OpenShift All in One Cluster

OpenShift All in One Cluster

Re: Adding host storage during advanced installation

Re: Adding host storage during advanced installation

CentOS PaaS SIG meeting (2018-03-21)

5 matches

Site Navigation

Mail list logo

Footer information