Friday, 2019-04-05

*** flwang has quit IRC00:12
*** ttsiouts has joined #openstack-containers01:32
*** ttsiouts has quit IRC02:05
*** itlinux has joined #openstack-containers02:52
*** hongbin has joined #openstack-containers03:02
*** anyrude10 has joined #openstack-containers03:39
anyrude10Hi Team, I am installing k8s cluster on Magnum Rocky with Fedora 25 atomic image, my stack remains Create in progress and eventually fails. On debugging I found in the master node file /var/log/cloud-init-output.log the following error : error: unable to decode "STDIN": no kind "ClusterRole" is registered for version "rbac.authorization.k8s.io/v1beta1". Can you please help me in resolving the issue03:41
*** udesale has joined #openstack-containers03:42
*** ramishra has joined #openstack-containers03:43
ykarelanyrude10, any reason to use Fedora25 atomic? u should use fedora 27 atomic which is used in magnum CI, that should be good to use03:46
ykarelhttps://github.com/openstack/magnum/blob/stable/rocky/magnum/tests/contrib/gate_hook.sh#L8803:46
ykarelhttps://download.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180212.2/CloudImages/x86_64/images/Fedora-Atomic-27-20180212.2.x86_64.qcow203:47
anyrude10yes, previously I was using Fedora 27 only, but it failed in curl http://127.0.0.1:8080/healthz, so i just thought to degrade the image. Any pointers that could help03:50
anyrude10ykarel, I have manual openstack rocky setup in which I am install Magnum service and creating k8s cluster, but the kube_master remains create in progress and after 1 hr, stack fails. Can you please help a little further so that I ca resolve the issue03:53
*** itlinux has quit IRC03:54
ykarelanyrude10, let me find a link, steps there will help u in narrow down the issue03:56
anyrude10ykarel, sure that would be a great help03:56
ykarelanyrude10, follow comments for the bug: https://bugs.launchpad.net/magnum/+bug/165500703:57
openstackLaunchpad bug 1655007 in Magnum "Magnum cluster takes forever to create with status 'kube_masters create in progress'" [Undecided,New]03:57
ykarelanyrude10, main reason is kube master is not able to notify to heat about it completion03:57
ykareland ^^ can happen due to multiple reason03:58
ykarelyou need to find that reason and comments in bug will help you03:58
anyrude10i'll go through it and get back to you03:58
ykarelok03:59
ykarelanyrude10, first of all check cloud-init-output log there u will get some hint04:01
ykareland use f27 image04:01
anyrude10in Fedora 25, the error in cloud-init-output.log is Failed to start heat-container-agent.service: Unit heat-container-agent.service not found. I'll try using Fedora 2704:02
*** ttsiouts has joined #openstack-containers04:03
anyrude10ykarel, need 1 input, how can I resolve my controller hostname in kube_master node while creating the cluster? What I do is I login into the node and manually update the /etc/hosts file04:06
ykarelanyrude10, so your endpoints contains hostname instead of ip?04:16
*** hongbin has quit IRC04:18
anyrude10ykarel, yes all the endpoints contains hostname04:18
ykarelanyrude10, okk i am not sure about best method, but for now you can update magnum scripts to do that automatically04:20
ykarelyou can do that in ca_script which runs first: https://github.com/openstack/magnum/blob/stable/rocky/magnum/drivers/k8s_fedora_atomic_v1/templates/kubemaster.yaml#L61804:21
ykarelmainly https://github.com/openstack/magnum/blob/stable/rocky/magnum/drivers/common/templates/fragments/atomic-install-openstack-ca.sh04:22
anyrude10ykarel, i'll give it a try04:26
ykarelokk04:28
*** ykarel is now known as ykarel|afk04:28
*** ykarel|afk has quit IRC04:32
*** spsurya has joined #openstack-containers04:32
*** ttsiouts has quit IRC04:36
*** ramishra has quit IRC04:43
*** ttsiouts has joined #openstack-containers04:46
*** ramishra has joined #openstack-containers04:47
*** ykarel|afk has joined #openstack-containers04:48
*** ykarel|afk is now known as ykarel04:49
anyrude10ykarel, I have used Fedora 27, and facing the error curl http://127.0.0.1:8080/healthz, curl: (7) Failed to connect to 127.0.0.1 port 8080: Connection refused05:08
*** pcaruana has joined #openstack-containers05:08
ykarelanyrude10, you checked cloud-init-output log as described in bug comments?05:14
anyrude10ykarel, yes I have checked. The issue is on controller, endpoints are created on Management IP 10.0.39.11 and external network ip is 10.0.61.5 , and my kube-master has a floating IP on external network 10.0.61.23 which reaches the controller. I hae also resolved the controller hostname in Kube master as 10.0.61.5 controller, which is reachable. But curl http://controller:9511/v1/  gets connection refused05:22
ykarelanyrude10, so http://controller:9511/v1/ will not work until and unless magnum is listening on external network and public endpoint is created with external interface05:25
*** sidx64 has joined #openstack-containers05:52
*** ttsiouts has quit IRC06:13
anyrude10ykarel, i have figured out that issue and now my cloud-init-output.log completed without any error, just healthz check failed' ']' ping ok occurred. Now as per the bug, when I run the kubectl get nodes command, it shows no resources found06:27
ykarelanyrude10, what is ' '] and ping ok?06:31
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: k8s_fedora: Update to kubernetes v1.14.0  https://review.openstack.org/64960906:50
*** henriqueof has joined #openstack-containers06:59
*** ttsiouts has joined #openstack-containers07:04
*** sidx64 has quit IRC07:12
*** sidx64_ has joined #openstack-containers07:12
*** sidx64 has joined #openstack-containers07:15
*** gsimondon has joined #openstack-containers07:16
*** sidx64_ has quit IRC07:17
*** gsimondo1 has joined #openstack-containers07:23
*** ramishra_ has joined #openstack-containers07:24
*** ramishra has quit IRC07:25
*** gsimondon has quit IRC07:26
*** sidx64 has quit IRC07:31
*** ramishra_ is now known as ramishra07:36
*** ykarel is now known as ykarel|lunch07:39
anyrude10ykarel, My kube_master has been deployed successfully, but in Minions i am facing issue in Flannel service. curl -sf --cacert /etc/flanneld/certs/ca.crt --cert /etc/flanneld/certs/proxy.crt --key /etc/flanneld/certs/proxy.key 'https://10.0.0.8:2379/v2/keys/atomic.io/network/config?quorum=false&recursive=false&sorted=false' + echo 'Waiting for flannel configuration in etcd...07:39
*** sidx64 has joined #openstack-containers07:42
*** rcernin has quit IRC07:48
*** ramishra_ has joined #openstack-containers08:29
*** ramishra has quit IRC08:32
*** sidx64 has quit IRC08:34
*** sidx64 has joined #openstack-containers08:43
*** anyrude10 has quit IRC08:58
*** anyrude10 has joined #openstack-containers09:01
*** ykarel|lunch is now known as ykarel09:08
anyrude10Hi, I am installing k8s cluster using magnum rocky and fedora 27. In minion, cloud-init-output.log is showing the following log: curl -sf --cacert /etc/flanneld/certs/ca.crt --cert /etc/flanneld/certs/proxy.crt --key /etc/flanneld/certs/proxy.key 'https://10.0.0.4:2379/v2/keys/atomic.io/network/config?quorum=false&recursive=false&sorted=false' + echo 'Waiting for flannel configuration in etcd...' Waiting for flannel co09:12
*** sidx64 has quit IRC09:22
*** flwang1 has joined #openstack-containers09:26
flwang1strigazi: around for a catch up?09:27
openstackgerritSpyros Trigazis proposed openstack/magnum master: Revert "Specify internal network to improve stability in a multi-NIC scenario."  https://review.openstack.org/65024909:29
flwang1strigazi: as for above patch, after reverted it, does the v1.14.0 work for you?09:31
*** sidx64 has joined #openstack-containers09:56
*** yolanda has joined #openstack-containers10:07
*** sidx64 has quit IRC10:11
*** sidx64_ has joined #openstack-containers10:11
*** mkuf has quit IRC10:14
*** mkuf has joined #openstack-containers10:19
brtknrflwang1: strigazi: hmm yes it doesn't play well with 1.1410:35
brtknrI reverted it it seems okay now10:35
flwang1brtknr: thanks for the feedback10:35
*** ttsiouts has quit IRC10:54
*** ttsiouts has joined #openstack-containers10:55
*** ttsiouts has quit IRC10:59
*** ttsiouts has joined #openstack-containers11:01
*** ttsiouts has quit IRC11:11
*** ttsiouts has joined #openstack-containers11:12
*** ttsiouts has quit IRC11:16
*** ttsiouts has joined #openstack-containers11:21
*** ykarel is now known as ykarel|afk11:23
*** ioni has joined #openstack-containers11:24
ionihello guys11:25
ionii'm trying for the first time magnum and i was able to spin a kubernets cluster11:25
ionii was wondering if there is a way to set up the domain for template to use in order to have a FQDN hostname for all the vms that are part from the cluster11:26
ionimaster and minions11:26
ionicurrently the name is:  k8s-cluster-somerandomtext-minion-011:26
ionibut i want something like  k8s-cluster-somerandomtext-minion-0.mydomain.net11:27
ionii'm trying to resolve this:11:27
ionihelm install stable/wordpress11:27
ioniError: forwarding ports: error upgrading connection: error dialing backend: dial tcp: lookup k8s-cluster-coreos-7pctbrnuykc6-minion-0 on 8.8.8.8:53: no such host11:27
*** anyrude10 has quit IRC11:27
*** ykarel|afk is now known as ykarel11:30
*** udesale has quit IRC11:32
*** udesale has joined #openstack-containers11:32
*** yolanda has quit IRC11:39
brtknrflwang1: Why do certs only get generated for ipv4 address and not ipv6?11:45
brtknrstrigazi: ^11:45
*** mariusleu has joined #openstack-containers12:09
mariusleuHello, I am running Magnum on a Rocky release. Using Fedora-Atomic-2712:10
mariusleuafter creating a Kubernetes cluster, the kube_masters fail to install etcd certificates,12:11
mariusleugetting this in journalctl -xn: open /etc/etcd/certs/server.crt: no such file or directory12:11
mariusleuetcd fails to start because of this, thus kube-apiserver fails to start as well12:11
mariusleuI am using the Magnum's internal x509 configuration for certificates, not using Barbican12:12
mariusleu@channel did anyone run into this issue?12:14
guimalufI'm running on queen with fedora atomic 27 and gettings this: Failed to update Node Allocatable Limits "": failed to set supported cgroup subsy12:15
guimalufstems for cgroup : Failed to set config for supported subsystems : failed to write 4135825408 to memory.limit_in_bytes: write /rootfs/var/lib/containers/atomic/kubelet.0/rootfs/sys/fs/cgroup/12:15
guimalufmemory/memory.limit_in_bytes: invalid argument12:15
*** ivve has quit IRC12:20
brtknrmariusleu: check your /var/log/cloud-init-output.log for errors12:23
brtknrguimaluf: can you create a pod?12:23
guimalufbrtknr, everything I try to create get 0/1 on READY12:24
brtknrguimaluf: how did you deploy magnum?12:24
guimalufbrtknr, using puppet-magnum12:25
guimalufactually, I had a Pike openstack and magnum was not creating any cluster. so I upgraded to queens and at least now I have a k8s cluster. but I can't creating nothing...12:26
guimalufI tought was lack of resourcers, since my instances were m1.small, but I've create another cluster with m1.medium and the result is the same12:27
brtknrguimaluf: how much RAM does m1.medium have?12:29
guimalufbrtknr, master 2GB, minions 4GB12:30
guimalufI'm trying to run hello-world-like pods/deployments12:30
brtknrshow me your cluster template12:31
brtknruse paste.openstack.org12:31
dioguerraflwangl: how did you test for NPD? shoudn't the minion status change to NotReady with https://github.com/kubernetes/node-problem-detector/blob/master/test/kernel_log_generator/problems/docker_hung12:31
guimalufbrtknr, http://paste.openstack.org/show/748940/12:33
brtknrguimaluf: have you tried with docker_storage_driver=overlay12:34
brtknrguimaluf: and docker_volume_size=012:34
brtknrguimaluf: can you also tell me which version of fedora-atomic you're using?12:35
guimalufbrtknr, IRC I'm using fedora atomic 2712:38
guimalufbrtknr, I will recreate my cluster and try with those options. should I create a new template, or can I pass those options to coe cluster create?12:39
*** mariusleu has quit IRC12:39
brtknrguimaluf: i suggest creating a new template in case it doesnt work12:40
guimalufI'll give a try ;) ty12:40
guimalufbrtknr, Unknown attribute for argument cluster_template: hidden, maybe I'm using magnum 2.13 in a queens openstack?12:50
guimalufbrtknr, downgrading magnumclient I can create the new template. but I couldn't set docker-volume-size 0, I let 1 :)12:57
*** mkuf_ has joined #openstack-containers13:07
*** mkuf has quit IRC13:11
*** mkuf_ has quit IRC13:11
openstackgerritSpyros Trigazis proposed openstack/magnum master: k8s_fedora: Update to kubernetes v1.14.0  https://review.openstack.org/64960913:42
openstackgerritSpyros Trigazis proposed openstack/magnum master: Revert "ci: Disable functional tests"  https://review.openstack.org/64287313:51
*** johanssone has joined #openstack-containers13:52
openstackgerritMerged openstack/magnum master: Revert "Specify internal network to improve stability in a multi-NIC scenario."  https://review.openstack.org/65024913:59
*** sidx64_ has quit IRC13:59
*** goldyfruit has joined #openstack-containers14:00
guimalufbrtknr, did as you said and I got the same error Failed to update Node Allocatable Limits "": failed to set supported cgroup subsystems for cgroup : Failed to set config for supported subsystems : failed to write 4135833600 to memory.limit_in_bytes: write /rootfs/var/lib/containers/atomic/kubelet.0/rootfs/sys/fs/cgroup/memory/memory.limit_in_bytes: invalid argument14:07
*** gsimondo1 has quit IRC14:16
*** ttsiouts has quit IRC14:22
*** ttsiouts has joined #openstack-containers14:23
*** ttsiouts has quit IRC14:24
*** ttsiouts has joined #openstack-containers14:24
brtknrguimaluf: where do you see that error?14:47
*** itlinux has joined #openstack-containers14:54
NobodyCamioni: I solved that issue but creating a systemd service that builds a /etc/hosts file on the master node at startup14:59
*** ttsiouts has quit IRC15:00
*** ttsiouts has joined #openstack-containers15:00
*** ttsiouts has quit IRC15:01
*** ttsiouts has joined #openstack-containers15:02
NobodyCamtrick is to create the hosts inside the kube-* services containers15:06
*** yolanda has joined #openstack-containers15:13
brtknrflwang1: how do I resolve this when using keystone auth: Error from server (Forbidden): nodes is forbidden: User "demo" cannot list resource "nodes" in API group "" at the cluster scope15:15
openstackgerritDiogo Guerra proposed openstack/magnum master: [k8s] Set traefik to stable version v1.7.9  https://review.openstack.org/65033115:15
openstackgerritDiogo Guerra proposed openstack/magnum master: [k8s] Set traefik to stable version v1.7.9  https://review.openstack.org/65034715:21
*** ttsiouts has quit IRC15:25
*** ttsiouts has joined #openstack-containers15:26
*** ttsiouts has quit IRC15:30
*** henriqueof has quit IRC15:40
*** ykarel is now known as ykarel|away15:41
*** yolanda has quit IRC15:52
*** udesale has quit IRC16:03
*** ykarel|away has quit IRC16:22
*** ivve has joined #openstack-containers16:34
ioniNobodyCam, i believe is mostly  problem with coreos, with fedora-atomic, works fine16:43
*** ramishra_ has quit IRC16:46
*** ivve has quit IRC16:48
*** ykarel|away has joined #openstack-containers17:22
*** itlinux has quit IRC17:25
guimalufbrtknr, I see that error when I run `kubectl get events` or `kubectl describe nodes`17:28
*** hongbin has joined #openstack-containers17:53
*** itlinux has joined #openstack-containers18:08
*** mkuf_ has joined #openstack-containers18:12
*** sidx64 has joined #openstack-containers18:22
*** sidx64_ has joined #openstack-containers18:26
*** sidx64 has quit IRC18:27
*** ivve has joined #openstack-containers18:32
*** goldyfruit has quit IRC18:36
*** itlinux has quit IRC18:42
flwang1dioguerra: ping18:50
flwang1brtknr: still around?18:50
*** mkuf_ has quit IRC18:54
*** itlinux has joined #openstack-containers19:13
flwang1brtknr: by default, user don't have permission to list nodes19:22
flwang1brtknr: here is the default policy https://github.com/openstack/magnum/blob/master/magnum/drivers/common/templates/kubernetes/fragments/enable-keystone-auth.sh#L7219:23
*** goldyfruit has joined #openstack-containers20:44
*** sidx64_ has quit IRC21:06
*** goldyfruit has left #openstack-containers21:42
*** mgariepy has quit IRC22:01
*** tbarron has quit IRC22:01
*** brtknr has quit IRC22:01
*** aspiers has quit IRC22:01
*** guimaluf has quit IRC22:01
*** nwonknu has quit IRC22:01
*** FracKen has quit IRC22:01
*** FracKen has joined #openstack-containers22:02
*** nwonknu has joined #openstack-containers22:07
*** aspiers has joined #openstack-containers22:23
*** openstackgerrit has quit IRC22:28
*** openstackgerrit has joined #openstack-containers22:39
openstackgerritRicardo Rocha proposed openstack/magnum master: [k8s] Add nginx based ingress controller  https://review.openstack.org/64865522:39
*** pcaruana has quit IRC22:57
*** ykarel|away has quit IRC23:01
*** hongbin has quit IRC23:09
*** sapd1_x has joined #openstack-containers23:40

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!