From casp at lists.suse.com Mon Mar 20 11:06:56 2017 From: casp at lists.suse.com (SUSE CaaSP Team) Date: Mon, 20 Mar 2017 18:06:56 +0100 Subject: [caasp-beta] Welcome to caasp-beta Message-ID: <58d00c3032620_6cbd104f3202744e@par-rochr.mail> ==Welcome to caasp-beta As you might know, our SUSE Container as a Servirce Platform Beta Program will start at the end of March! We are pretty excited about it and we are still actively preparing the last bits for this new SUSE product. ==Available Informations =Webinars As of today, we already made 2 webinars about SUSE CaaSP, in case you have missed them, please check them out: SUSE Container as a Service Platform - An Introduction[1] SUSE Container as a Service Platform - Grow your Technical knowledge[2] =Schedule We are planning to release "SUSE CaaSP Beta 2" as our first public beta. Yes, you read it right, beta 1 didn't contain some of the major feature we are preparing so we decide to keep it internal only. Here is the planned schedule: Beta 1 ? 02-03-2017 (Internal Beta) Beta 2 ? 30-03-2017 (Public Beta) Beta 3 ? 27-04-2017 (Public Beta) Release Candidate ? 24-05-2017 (Public Beta) Gold Master ? 29-06-2017 (Internal) First Customer Shipment ? Mid July (Official Final Release) Important: Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change of plan. ==Stay tuned! We will officially start the SUSE CaaSP Beta in the upcoming days. ==Question? If you have any question regarding the Beta Program, please reach us via beta-programs at lists.suse.com Your SUSE CaaSP Team [1]https://www.brighttalk.com/webcast/11477/242539 [2]https://www.brighttalk.com/webcast/11477/242543 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Tue Mar 21 03:28:53 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 21 Mar 2017 10:28:53 +0100 Subject: [caasp-beta] Welcome to caasp-beta In-Reply-To: <58d00c3032620_6cbd104f3202744e@par-rochr.mail> References: <58d00c3032620_6cbd104f3202744e@par-rochr.mail> Message-ID: Hello, ERRATUM:? This is the correct link to the SUSE Container as a Service Platform - Grow your technical knowledge webinar :? https://www.brighttalk.com/webcast/11477/248425 Sorry for the inconvenience,? Have a nice day, Regards, --? Vincent Moutoussamy SUSE Beta Program and SDK Project Manager On 20 March 2017 at 18:06:56, SUSE CaaSP Team (casp at lists.suse.com) wrote: Having trouble viewing this email? Please check the plain text version of it with your mailer. ? ? Welcome to caasp-beta As you might know, our SUSE Container as a Servirce Platform Beta Program will start at the end of March! We are pretty excited about it and we are still actively preparing the last bits for this new SUSE product. Available Informations Webinars As of today, we already made 2 webinars about SUSE CaaSP, in case you have missed them, please check them out: SUSE Container as a Service Platform - An Introduction SUSE Container as a Service Platform - Grow your Technical knowledge Schedule We are planning to release "SUSE CaaSP Beta 2" as our first public beta. Yes, you read it right, beta 1 didn't contain some of the major feature we are preparing so we decide to keep it internal only. Here is the planned schedule: Beta 1 ? 02-03-2017 (Internal Beta) Beta 2 ? 30-03-2017 (Public Beta) Beta 3 ? 27-04-2017 (Public Beta) Release Candidate ? 24-05-2017 (Public Beta) Gold Master ? 29-06-2017 (Internal) First Customer Shipment ? Mid July 2017 (Official Final Release) Important: Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change of plan. Stay tuned! We will officially start the SUSE CaaSP Beta in the upcoming days. ? Your SUSE CaaSP Team ? If you have any question regarding SUSE Beta Program, please reach us at beta-programs at lists.suse.com. You received this email because you're signed up to get updates from us. Click here to unsubscribe. _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From carsten.duch at suse.com Mon Mar 27 02:07:50 2017 From: carsten.duch at suse.com (Carsten Duch) Date: Mon, 27 Mar 2017 10:07:50 +0200 Subject: [caasp-beta] Beta Access for Customers? Message-ID: <9e08121f-de0f-6ba7-7e8b-efd2b8a98548@suse.com> Hello, how does a customer apply for the CaaSP beta? Our website still says that there is no public beta available right now. https://www.suse.com/de-de/support/beta-program/beta/ Mit freundlichen Gr??en / Best regards Carsten Duch Sales Engineer SUSE N?rdlicher Zubringer 9-11 40470 D?sseldorf (P)+49 173 5876 707 (H)+49 521 9497 6388 carsten.duch at suse.com -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From aj at suse.com Mon Mar 27 02:10:25 2017 From: aj at suse.com (Andreas Jaeger) Date: Mon, 27 Mar 2017 10:10:25 +0200 Subject: [caasp-beta] Beta Access for Customers? In-Reply-To: <9e08121f-de0f-6ba7-7e8b-efd2b8a98548@suse.com> References: <9e08121f-de0f-6ba7-7e8b-efd2b8a98548@suse.com> Message-ID: On 2017-03-27 10:07, Carsten Duch wrote: > Hello, > how does a customer apply for the CaaSP beta? Carsten, this is a public mailing list, just tell your customer to subscribe here, Andreas > Our website still says that there is no public beta available right now. > > https://www.suse.com/de-de/support/beta-program/beta/ -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From carsten.duch at suse.com Mon Mar 27 02:15:05 2017 From: carsten.duch at suse.com (Carsten Duch) Date: Mon, 27 Mar 2017 10:15:05 +0200 Subject: [caasp-beta] Beta Access for Customers? In-Reply-To: References: <9e08121f-de0f-6ba7-7e8b-efd2b8a98548@suse.com> Message-ID: Thanks AJ! Then we should update our website with this information. We have a few customers looking for the CaaSP beta who are not able to find it. On 27.03.2017 10:10, Andreas Jaeger wrote: > On 2017-03-27 10:07, Carsten Duch wrote: >> Hello, >> how does a customer apply for the CaaSP beta? > > Carsten, this is a public mailing list, just tell your customer to > subscribe here, > > Andreas > >> Our website still says that there is no public beta available right now. >> >> https://www.suse.com/de-de/support/beta-program/beta/ > > -- Mit freundlichen Gr??en / Best regards Carsten Duch Sales Engineer SUSE N?rdlicher Zubringer 9-11 40470 D?sseldorf (P)+49 173 5876 707 (H)+49 521 9497 6388 carsten.duch at suse.com -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From vmoutoussamy at suse.com Mon Mar 27 09:14:18 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 27 Mar 2017 17:14:18 +0200 Subject: [caasp-beta] Beta Access for Customers? In-Reply-To: References: <9e08121f-de0f-6ba7-7e8b-efd2b8a98548@suse.com> Message-ID: Hi, Please note that the official SUSE Beta pages are now: https://www.suse.com/betaprogram https://www.suse.com/betaprogram/beta/? The older SUSE Beta pages should have been shut down? (https://www.suse.com/de-de/support/beta-program/beta/), sorry for the? inconvenience I will trigger the redirection from the old to the new SUSE Beta pages.? Have a nice day, Regards, --? Vincent Moutoussamy SUSE Beta Program and SDK Project Manager On 27 March 2017 at 10:15:20, Carsten Duch (carsten.duch at suse.com) wrote: Thanks AJ! Then we should update our website with this information. We have a few customers looking for the CaaSP beta who are not able to find it. On 27.03.2017 10:10, Andreas Jaeger wrote: > On 2017-03-27 10:07, Carsten Duch wrote: >> Hello, >> how does a customer apply for the CaaSP beta? > > Carsten, this is a public mailing list, just tell your customer to > subscribe here, > > Andreas > >> Our website still says that there is no public beta available right now. >> >> https://www.suse.com/de-de/support/beta-program/beta/ > > -- Mit freundlichen Gr??en / Best regards Carsten Duch Sales Engineer SUSE N?rdlicher Zubringer 9-11 40470 D?sseldorf (P)+49 173 5876 707 (H)+49 521 9497 6388 carsten.duch at suse.com -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From magnus-caasp at linuxtag.org Thu Mar 30 07:12:27 2017 From: magnus-caasp at linuxtag.org (Nils Magnus) Date: Thu, 30 Mar 2017 15:12:27 +0200 Subject: [caasp-beta] Help! I'm stuck in an endless loop Message-ID: <2b6354e6-f9ee-ca5f-128a-907ac1563ddc@linuxtag.org> Hi, I tried my very best to find out about the CaaSP-Beta program on the website and in the news, got redirected to the list server, looked up the mailing list, subscribed to it, received a welcome message stating to go to the suse website, create another account there, get redirected through some white blank pages to the list server again where I started. This is a frustrating user experience. Is there some information available about the Beta programm staring today, as announced, or not? Regards, Nils From vmoutoussamy at suse.com Thu Mar 30 07:47:17 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 30 Mar 2017 15:47:17 +0200 Subject: [caasp-beta] Help! I'm stuck in an endless loop In-Reply-To: <2b6354e6-f9ee-ca5f-128a-907ac1563ddc@linuxtag.org> References: <2b6354e6-f9ee-ca5f-128a-907ac1563ddc@linuxtag.org> Message-ID: Hi, Sorry to hear you frustrating experience, I will contact you in private to get more details.? It is true that for now the mailing list and the web page? https://www.suse.com/betaprogram/beta/ are the only caasp-beta resources.? We will uncover more when our public beta iso images will be ready to download,? please be patient, you are at the right place (caasp-beta at lists.suse.com) to get? the official and fastest news about caasp-beta.? For now we are waiting for our QA processes to complete before being sure that? we can share our iso images.? Please stay tuned! We will send more details soon.? Regards, --? Vincent Moutoussamy SUSE Beta Program and SDK Project Manage On 30 March 2017 at 15:12:42, Nils Magnus (magnus-caasp at linuxtag.org) wrote: Hi, I tried my very best to find out about the CaaSP-Beta program on the website and in the news, got redirected to the list server, looked up the mailing list, subscribed to it, received a welcome message stating to go to the suse website, create another account there, get redirected through some white blank pages to the list server again where I started. This is a frustrating user experience. Is there some information available about the Beta programm staring today, as announced, or not? Regards, Nils _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From caasp-beta at lists.suse.com Thu Mar 30 11:14:45 2017 From: caasp-beta at lists.suse.com (SUSE CaaSP Team) Date: Thu, 30 Mar 2017 19:14:45 +0200 Subject: [caasp-beta] [ANNOUNCE] SUSE Container as a Service Platform 1.0 Beta 2 is available! Message-ID: <58dd3d053b8be_22ba71532c2085@par-rochr.mail> == Beta 2 of the SUSE Container as a Service Platform[1] We are happy to announce our first public Beta of the SUSE Container as a Service Platform 1.0: Download[2] == More informations Things to consider for this Beta: DHCP Your DHCP server should provide resolveable hostnames. If this is not the case like with libvirt/KVM, you should consider providing one yourself by appending this kernel parameter "hostname=HOSTNAME" during installation. However, the kubeconfig file downloaded from the Dashboard could contain an incorrect "server" hostname that should be replaced with the IP address of your Master. For more information read: https://en.opensuse.org/SDB:Linuxrc#Network_Configuration Autoyast/VMX-Images If you install via autoyast or one of the provided VMX beta images (KVM,Xen,VMware,...) please set a password or SSH key via cloud-init to be able to login. We recommend downloading kubectl config before rebooting the cluster. Release schedule[3] Release Notes[4] Documentation[5] Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SUSE CaaSP Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/caasp-beta [2]https://www.suse.com/betaprogram/caasp-beta/#download [3]https://www.suse.com/betaprogram/caasp-beta/#releases [4]https://www.suse.com/betaprogram/caasp-beta/#releasenotes [5]https://www.suse.com/betaprogram/caasp-beta/#documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.com Fri Mar 31 07:24:21 2017 From: kukuk at suse.com (Thorsten Kukuk) Date: Fri, 31 Mar 2017 15:24:21 +0200 Subject: [caasp-beta] Docu for tftpboot installation of SUSE CaaSP Message-ID: <20170331132421.GA5139@suse.com> Hello, there is one feature in SUSE CaaSP, which is not yet mentioned in our documentation: one RPM providing the installer ready to use by tftp/PXE boot. If you are in the lucky situation, that you can see SUSE CaaSP already in SMT, deploying CaaSP is quite simple: mirror SUSE CaaSP with SMT, go into that repository and install the "tftpboot-installation-CAASP-1.0-x86_64" RPM in the noarch diretory. No need to download and copy the DVD any longer. If you don't have a local SMT server running, or if you don't see SUSE CaaSP in it, you need to setup a local install server with help of the DVD to provide the RPMs via nfs, http, ftp or tftp. Afterwards, go into the suse/noarch directory and install or unpack the "tftpboot-installation-CAASP-1.0-x86_64" RPM. If you have this RPM installed, read /srv/tftpboot/CAASP-1.0-x86_64/README how to add this to your tftpboot configuration. If you add the repository containing the "tftpboot-installation-CAASP-1.0-x86_64" RPM to your tftpboot server, a "zypper up" will in the future update the installer, if we release a new version. You can get an autoyast profile from the Administration Dashboard, only add the autoyast url as described on one of the first pages, if you login to the dashboard the first time. If you need to make changes to the autoyast profile, e.g. to set a root password, provide a registration key or a network source, you can login as root on the commandline of the Administration Node and create your own autoyast profile with the "create_autoyast_profile" command. Now you only need to PXE boot all of your cluster nodes, they will install and register at the administration dashboard themself. No user interaction needed. On the dashboard, you only need to assign, if it is a kubernetes master or worker. If you know how syslinux works: you can also copy the content of the /srv/tftpboot/CAASP-1.0-x86_64/ diretory onto an USB stick and make this with syslinux bootable. Since some people asked, how many cluster nodes are needed: a cluster is more than one machine, so you need, beside the Administration Node, two cluster nodes. Regards, Thorsten Kukuk -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From bo.jin at suse.com Fri Mar 31 07:30:34 2017 From: bo.jin at suse.com (Bo Jin) Date: Fri, 31 Mar 2017 15:30:34 +0200 Subject: [caasp-beta] transactional updates Message-ID: <4d837258-c092-4165-0a18-7502aa0169eb@suse.com> Hi, I still want to better understand "transaction updates". From the available docu so far I know the the transactional-update script is looking if any new updates are available, if yes then a read only snapshot of btrfs root fs will be created. Then the script will execute the updates. After updates the ro snapshot will be marked as active/default and machine needs to be rebooted. My question is where does the rpm goto during updates? Into the ro snapshot? Or is it going into a new ro snapshot of the snapshot and mount it as rw somewhere and patch....? I read ubuntu snapy but it didn't help me to understand. Thanks for explaination in advance. -- Bo Jin Sales Engineer SUSE Linux Mobile: +41792586688 bo.jin at suse.com www.suse.com From kukuk at suse.com Fri Mar 31 07:38:32 2017 From: kukuk at suse.com (Thorsten Kukuk) Date: Fri, 31 Mar 2017 15:38:32 +0200 Subject: [caasp-beta] transactional updates In-Reply-To: <4d837258-c092-4165-0a18-7502aa0169eb@suse.com> References: <4d837258-c092-4165-0a18-7502aa0169eb@suse.com> Message-ID: <20170331133832.GA6243@suse.com> On Fri, Mar 31, Bo Jin wrote: > Hi, > I still want to better understand "transaction updates". > > From the available docu so far I know the the transactional-update script is > looking if any new updates are available, if yes then a read only snapshot > of btrfs root fs will be created. Then the script will execute the updates. > After updates the ro snapshot will be marked as active/default and machine > needs to be rebooted. > > My question is where does the rpm goto during updates? Into the ro snapshot? Yes, except that it is not ro. After creating the snapshot, it will be switched to read-write, than zypper up is called inside of the snapshot, and afterwards it is switched back to read-only. There is a generic talk from me from FOSDEM this year: https://fosdem.org/2017/schedule/event/transactional_update_with_btrfs/ The for your interesting part starts at about 9:50. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From bo.jin at suse.com Fri Mar 31 10:53:29 2017 From: bo.jin at suse.com (Bo Jin) Date: Fri, 31 Mar 2017 18:53:29 +0200 Subject: [caasp-beta] transactional updates In-Reply-To: <20170331133832.GA6243@suse.com> References: <4d837258-c092-4165-0a18-7502aa0169eb@suse.com> <20170331133832.GA6243@suse.com> Message-ID: <6480db14-4136-5665-98e6-16fa7250d63c@suse.com> Could I get the slides? Great video. On 03/31/2017 03:38 PM, Thorsten Kukuk wrote: > On Fri, Mar 31, Bo Jin wrote: > >> Hi, >> I still want to better understand "transaction updates". >> >> From the available docu so far I know the the transactional-update script is >> looking if any new updates are available, if yes then a read only snapshot >> of btrfs root fs will be created. Then the script will execute the updates. >> After updates the ro snapshot will be marked as active/default and machine >> needs to be rebooted. >> >> My question is where does the rpm goto during updates? Into the ro snapshot? > > Yes, except that it is not ro. After creating the snapshot, it will be > switched to read-write, than zypper up is called inside of the snapshot, > and afterwards it is switched back to read-only. > > There is a generic talk from me from FOSDEM this year: > https://fosdem.org/2017/schedule/event/transactional_update_with_btrfs/ > > The for your interesting part starts at about 9:50. > > Thorsten > -- Bo Jin Sales Engineer SUSE Linux Mobile: +41792586688 bo.jin at suse.com www.suse.com From rushi.ns at sap.com Fri Mar 31 21:22:25 2017 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 1 Apr 2017 03:22:25 +0000 Subject: [caasp-beta] caasp-beta Message-ID: <7D321314-6741-4282-ADDF-BA95D49E25BB@sap.com> Here is my beta test results. I setup total 5 systems (1 controller, 1 master, 3 workers) 1) Setup controller works fast and very quick too. 2) Bootstrap nodes with autoyast worked and as well manual install by selecting nodes by specifying the controller IP worked. 3) Install cluster with selection ran several hours and I see the following Any other tools to see whats happening other than kubelet commands I used here. lvcaasadmin:/var/lib # kubelet list I0401 03:58:17.465609 8571 feature_gate.go:189] feature gates: map[] W0401 03:58:17.465761 8571 server.go:400] No API client: no api servers specified I0401 03:58:17.465852 8571 docker.go:356] Connecting to docker on unix:///var/run/docker.sock I0401 03:58:17.465893 8571 docker.go:376] Start docker client with request timeout=2m0s E0401 03:58:17.467067 8571 cni.go:163] error updating cni config: No networks found in /etc/cni/net.d I0401 03:58:17.475120 8571 manager.go:143] cAdvisor running in container: "/user.slice" W0401 03:58:17.481167 8571 manager.go:151] unable to connect to Rkt api service: rkt: cannot tcp Dial rkt api service: dial tcp [::1]:15441: getsockopt: connection refused I0401 03:58:17.487164 8571 fs.go:117] Filesystem partitions: map[/dev/sda2:{mountpoint:/var/lib/docker/btrfs major:0 minor:34 fsType:btrfs blockSize:0}] I0401 03:58:17.489428 8571 manager.go:198] Machine: {NumCores:4 CpuFrequency:2297339 MemoryCapacity:33553862656 MachineID:026dbed750d34678baa318a927beb43c SystemUUID:4212E894-D404-BC7E-12C1-104406FAC1AF BootID:4fca4f86-b8df-40aa-9a52-9f32d82a65c6 Filesystems:[{Device:/dev/sda2 Capacity:105219358720 Type:vfs Inodes:0 HasInodes:true}] DiskMap:map[2:0:{Name:fd0 Major:2 Minor:0 Size:4096 Scheduler:cfq} 8:0:{Name:sda Major:8 Minor:0 Size:107374182400 Scheduler:cfq}] NetworkDevices:[{Name:eth0 MacAddress:00:50:56:92:78:da Speed:10000 Mtu:1500}] Topology:[{Id:0 Memory:33553862656 Cores:[{Id:0 Threads:[0] Caches:[]} {Id:1 Threads:[1] Caches:[]}] Caches:[{Size:41943040 Type:Unified Level:3}]} {Id:1 Memory:0 Cores:[{Id:0 Threads:[2] Caches:[]} {Id:1 Threads:[3] Caches:[]}] Caches:[{Size:41943040 Type:Unified Level:3}]}] CloudProvider:Unknown InstanceType:Unknown InstanceID:None} I0401 03:58:17.490209 8571 manager.go:204] Version: {KernelVersion:4.4.52-1-default ContainerOsVersion:SUSE Container as a Service Platform 1.0 DockerVersion:1.12.6 CadvisorVersion: CadvisorRevision:} I0401 03:58:17.491582 8571 cadvisor_linux.go:152] Failed to register cAdvisor on port 4194, retrying. Error: listen tcp :4194: bind: address already in use W0401 03:58:17.494066 8571 container_manager_linux.go:205] Running with swap on is not supported, please disable swap! This will be a fatal error by default starting in K8s v1.6! In the meantime, you can opt-in to making this a fatal error by enabling --experimental-fail-swap-on. W0401 03:58:17.494326 8571 server.go:669] No api server defined - no events will be sent to API server. W0401 03:58:17.497638 8571 kubelet_network.go:69] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth" I0401 03:58:17.497694 8571 kubelet.go:477] Hairpin mode set to "hairpin-veth" I0401 03:58:17.504274 8571 docker_manager.go:256] Setting dockerRoot to /var/lib/docker I0401 03:58:17.504311 8571 docker_manager.go:259] Setting cgroupDriver to cgroupfs I0401 03:58:17.506297 8571 server.go:770] Started kubelet v1.5.3 W0401 03:58:17.506331 8571 kubelet.go:1224] No api server defined - no node status update will be sent. E0401 03:58:17.506400 8571 server.go:481] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use E0401 03:58:17.506382 8571 kubelet.go:1145] Image garbage collection failed: unable to find data for container / I0401 03:58:17.506527 8571 server.go:123] Starting to listen on 0.0.0.0:10250 I0401 03:58:17.506647 8571 kubelet_node_status.go:204] Setting node annotation to enable volume controller attach/detach F0401 03:58:17.509424 8571 server.go:148] listen tcp 0.0.0.0:10255: bind: address already in use [cid:image001.png at 01D2AA5C.820478D0] [cid:image002.png at 01D2AA5C.820478D0] from messages I see the following. event.go:208] Unable to write event: 'Post http://127.0.0.1:8080/api/v1/namespaces/default/events: dial tcp 127.0.0.1:8080: getsockopt: connection refused' (may retry after sleeping) 2017-04-01T04:01:57.375925+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:57.375830 2651 reflector.go:188] pkg/kubelet/kubelet.go:378: Failed to list *api.Service: Get http://127.0.0.1:8080/api/v1/services?resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:57.443964+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:57.443871 2651 reflector.go:188] pkg/kubelet/config/apiserver.go:44: Failed to list *api.Pod: Get http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%3D127.0.0.1&resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:57.444895+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:57.444801 2651 reflector.go:188] pkg/kubelet/kubelet.go:386: Failed to list *api.Node: Get http://127.0.0.1:8080/api/v1/nodes?fieldSelector=metadata.name%3D127.0.0.1&resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:58.376648+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:58.376550 2651 reflector.go:188] pkg/kubelet/kubelet.go:378: Failed to list *api.Service: Get http://127.0.0.1:8080/api/v1/services?resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:58.444697+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:58.444601 2651 reflector.go:188] pkg/kubelet/config/apiserver.go:44: Failed to list *api.Pod: Get http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%3D127.0.0.1&resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:58.446107+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:58.446008 2651 reflector.go:188] pkg/kubelet/kubelet.go:386: Failed to list *api.Node: Get http://127.0.0.1:8080/api/v1/nodes?fieldSelector=metadata.name%3D127.0.0.1&resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:59.377433+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:59.377325 2651 reflector.go:188] pkg/kubelet/kubelet.go:378: Failed to list *api.Service: Get http://127.0.0.1:8080/api/v1/services?resourceVersion=0: dial tcp 127.0.0.1:8080: getsockopt: connection refused 2017-04-01T04:01:59.445470+00:00 lvcaasadmin hyperkube[2651]: E0401 04:01:59.445336 2651 reflector.go:188] pkg/kubelet/config/apiserver.go:44: F Best Regards, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 71692 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 58153 bytes Desc: image002.png URL: