From cf at cloudssky.com Mon Jul 23 03:15:03 2018 From: cf at cloudssky.com (Christian Frank) Date: Mon, 23 Jul 2018 11:15:03 +0200 Subject: [caasp-beta] CAP installation failing in uaa.yaml Message-ID: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> Hi all, our partner manager pointed us to this mailing list, I hope we've come to the correct place. We're in the process of installing CAP 1.1 on upstream Kubernetes (as outlined in chapter 6 of the deployment guide) and are running into the following issue: [arash]$ helm install suse/uaa --name susecf-uaa --namespace uaa --values scf-config-values.yaml Error: render error in "uaa/templates/uaa.yaml": template: uaa/templates/uaa.yaml:45:67: executing "uaa/templates/uaa.yaml" at <.Values.env.DOMAIN>: can't evaluate field DOMAIN in type interface {} Any idea? We've set up DNS as described in the Cloud Foundry documentation (https://docs.cloudfoundry.org/deploying/common/dns_prereqs.html), but we're not sure if that's sufficient for CAP. Here's our values.yaml file: === begin scf-config-values.yaml env: # Enter the domain you created for your CAP cluster DOMAIN: cloudssky.net # UAA host and port UAA_HOST: uaa.cloudssky.net UAA_PORT: 2793 kube: # The IP address assigned to the kube node pointed to by the domain. external_ips: ["84.200.100.221"] # Run kubectl get storageclasses # to view your available storage classes storage_class: hostpath persistent: "persistent" shared: "shared" # The registry the images will be fetched from. # The values below should work for # a default installation from the SUSE registry. registry: hostname: "registry.suse.com" username: "" password: "" organization: "cap" # Required for CaaSP 2 auth: rbac secrets: # Create a password for your CAP cluster CLUSTER_ADMIN_PASSWORD: password # Create a password for your UAA client secret UAA_ADMIN_CLIENT_SECRET: password === end scf-config-values.yaml Any help, ideas or pointers would be greatly appreciated! Many thanks in advance and best regards: Chris ____________________________ Clouds Sky GmbH Im Mediapark 4c 50670 K?ln Tel.: +49 221 4853 5783 Mobile: +49 171 993 6814 www.cloudssky.com Sitz der Gesellschaft: K?ln Registergericht: Amtsgericht K?ln, HRB 70999 Gesch?ftsf?hrer: Stephan Hartmann, Arash Kaffamanesh F.v.G.u.v.S. From lcavajani at suse.com Mon Jul 23 03:23:19 2018 From: lcavajani at suse.com (Ludovic Cavajani) Date: Mon, 23 Jul 2018 11:23:19 +0200 Subject: [caasp-beta] CAP installation failing in uaa.yaml In-Reply-To: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> References: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> Message-ID: <463c3c79-54c5-e457-1dd6-370fc01d0719@suse.com> Hi Christian, There is an indentation problem in your yaml config file, the DOMAIN, UAA_HOST, UAA_PORT options must be indented under "env" : env: DOMAIN: cloudssky.net UAA_HOST: uaa.cloudssky.net UAA_PORT: 2793 On 07/23/2018 11:15 AM, Christian Frank wrote: > Hi all, > > our partner manager pointed us to this mailing list, I hope we've come to > the correct place. > > We're in the process of installing CAP 1.1 on upstream Kubernetes (as > outlined in chapter 6 of the deployment guide) and are running into the > following issue: > > [arash]$ helm install suse/uaa --name susecf-uaa --namespace uaa --values > scf-config-values.yaml > Error: render error in "uaa/templates/uaa.yaml": template: > uaa/templates/uaa.yaml:45:67: executing "uaa/templates/uaa.yaml" at > <.Values.env.DOMAIN>: can't evaluate field DOMAIN in type interface {} > > Any idea? We've set up DNS as described in the Cloud Foundry documentation > (https://docs.cloudfoundry.org/deploying/common/dns_prereqs.html), but we're > not sure if that's sufficient for CAP. > > Here's our values.yaml file: > > === begin scf-config-values.yaml > > env: > > # Enter the domain you created for your CAP cluster > DOMAIN: cloudssky.net > > # UAA host and port > UAA_HOST: uaa.cloudssky.net > UAA_PORT: 2793 > kube: > # The IP address assigned to the kube node pointed to by the domain. > external_ips: ["84.200.100.221"] > > # Run kubectl get storageclasses > # to view your available storage classes > storage_class: hostpath > persistent: "persistent" > shared: "shared" > > # The registry the images will be fetched from. > # The values below should work for > # a default installation from the SUSE registry. > registry: > hostname: "registry.suse.com" > username: "" > password: "" > organization: "cap" > # Required for CaaSP 2 > auth: rbac > secrets: > # Create a password for your CAP cluster > CLUSTER_ADMIN_PASSWORD: password > > # Create a password for your UAA client secret > UAA_ADMIN_CLIENT_SECRET: password > > === end scf-config-values.yaml > > Any help, ideas or pointers would be greatly appreciated! > > Many thanks in advance and best regards: > > Chris > > > ____________________________ > > Clouds Sky GmbH > Im Mediapark 4c > 50670 K?ln > Tel.: +49 221 4853 5783 > Mobile: +49 171 993 6814 > www.cloudssky.com > > Sitz der Gesellschaft: K?ln > Registergericht: Amtsgericht K?ln, HRB 70999 > Gesch?ftsf?hrer: Stephan Hartmann, Arash Kaffamanesh F.v.G.u.v.S. > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From lproven at suse.cz Mon Jul 23 03:28:15 2018 From: lproven at suse.cz (Liam Proven) Date: Mon, 23 Jul 2018 11:28:15 +0200 Subject: [caasp-beta] CAP installation failing in uaa.yaml In-Reply-To: <463c3c79-54c5-e457-1dd6-370fc01d0719@suse.com> References: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> <463c3c79-54c5-e457-1dd6-370fc01d0719@suse.com> Message-ID: <708a658d-d07b-c8e2-89c5-13f837d44b0c@suse.cz> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 23/07/18 11:23, Ludovic Cavajani wrote: > There is an indentation problem in your yaml config file, I am not sure -- do multiple whitespaces pass through email without modification? It may depend on the client and the server being used. - -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEeNZxWlZYyNg7I0pvkm4MJhv0VBYFAltVn68ACgkQkm4MJhv0 VBazVw//VWTyD1jEbqi+vq9Skfhe7MfAKxc2wmziq4k13Mbia4/sQhKh8trk6aSY Eu/D5PFPHZwb7ZagUrrYfZTVLAqsRCumFn6S81cGG/tXRLIwjdaAVt+8OSXs3Pov Y5xR0N9v1x/u+e6kJuFIRXUGqljDkVFS/jEuTgsOaLalB/ap0H40i9sFo1mSp2s+ GCNbdLKDiCv+umU6l6lnOwJRtmp1GYT9PTOL9M6PNhZPvFGqCdYFOTsskOYY+bnl JPMgPh5trAhlEHFNzx+xmskoVJUt+TpuxCUu2ogFBvJp7fTq2ZDlboD+NDcKBXRT yVvy0DsDdOr8eUVenHrxoT+VAuPIAB8h6Unfy0l/0rBA3U1t9x/vj9iAsYV/+VDE jnFp9WMcEWEE3iK3a4rwJK0OdyLNFm0hR54e2BtUXEMfhivYuw85691v/DHcrV/U Ry187hwQ3/k+w6g7GYo1Dg7BUkx858paZfNR8q9OSuqofEpX8z8hfctH5PReb+yO MeWYRAfNfpCBWfANsyHONV2+2ZiSJX7xQqhgicUHUWzdIdtPSN1bNCwH80h51CeB hJeo1sMxaFsB6DXhFaOLHUCAC7R+Zj3apuW6iUZe3JG0Trx01ZYYjnjrT6wp1p9w c6TitzkfBA1L5HmpiXz1xSa+1XrbZfne/a3+sMa6jVzQKBnEKFE= =9miF -----END PGP SIGNATURE----- From kukuk at suse.com Mon Jul 23 03:31:15 2018 From: kukuk at suse.com (Thorsten Kukuk) Date: Mon, 23 Jul 2018 11:31:15 +0200 Subject: [caasp-beta] CAP installation failing in uaa.yaml In-Reply-To: <708a658d-d07b-c8e2-89c5-13f837d44b0c@suse.cz> References: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> <463c3c79-54c5-e457-1dd6-370fc01d0719@suse.com> <708a658d-d07b-c8e2-89c5-13f837d44b0c@suse.cz> Message-ID: <20180723093115.ukfa6rrvo7hcz2qf@suse.com> On Mon, Jul 23, Liam Proven wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 23/07/18 11:23, Ludovic Cavajani wrote: > > There is an indentation problem in your yaml config file, > > I am not sure -- do multiple whitespaces pass through email without > modification? It may depend on the client and the server being used. They should, else gpg signtatures e.g. would become invalidated. 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 troy.topnik at suse.com Thu Jul 26 12:34:06 2018 From: troy.topnik at suse.com (Troy Topnik) Date: Thu, 26 Jul 2018 11:34:06 -0700 Subject: [caasp-beta] CAP installation failing in uaa.yaml In-Reply-To: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> References: <001a01d42265$a4487400$ecd95c00$@cloudssky.com> Message-ID: <20180726183405.GC22407@phoenix> Christan, This is not the correct place to get help with CAP. I'll respond separately to get you connected to the right people and get you some help with the problem. TT -- Troy Topnik Senior Product Manager, SUSE Cloud Application Platform troy.topnik at suse.com On Mon, Jul 23, 2018 at 11:15:03AM +0200, Christian Frank wrote: > Hi all, > > our partner manager pointed us to this mailing list, I hope we've come to > the correct place. > > We're in the process of installing CAP 1.1 on upstream Kubernetes (as > outlined in chapter 6 of the deployment guide) and are running into the > following issue: > > [arash]$ helm install suse/uaa --name susecf-uaa --namespace uaa --values > scf-config-values.yaml > Error: render error in "uaa/templates/uaa.yaml": template: > uaa/templates/uaa.yaml:45:67: executing "uaa/templates/uaa.yaml" at > <.Values.env.DOMAIN>: can't evaluate field DOMAIN in type interface {} > > Any idea? We've set up DNS as described in the Cloud Foundry documentation > (https://docs.cloudfoundry.org/deploying/common/dns_prereqs.html), but we're > not sure if that's sufficient for CAP. > > Here's our values.yaml file: > > === begin scf-config-values.yaml > > env: > > # Enter the domain you created for your CAP cluster > DOMAIN: cloudssky.net > > # UAA host and port > UAA_HOST: uaa.cloudssky.net > UAA_PORT: 2793 > kube: > # The IP address assigned to the kube node pointed to by the domain. > external_ips: ["84.200.100.221"] > > # Run kubectl get storageclasses > # to view your available storage classes > storage_class: hostpath > persistent: "persistent" > shared: "shared" > > # The registry the images will be fetched from. > # The values below should work for > # a default installation from the SUSE registry. > registry: > hostname: "registry.suse.com" > username: "" > password: "" > organization: "cap" > # Required for CaaSP 2 > auth: rbac > secrets: > # Create a password for your CAP cluster > CLUSTER_ADMIN_PASSWORD: password > > # Create a password for your UAA client secret > UAA_ADMIN_CLIENT_SECRET: password > > === end scf-config-values.yaml > > Any help, ideas or pointers would be greatly appreciated! > > Many thanks in advance and best regards: > > Chris > > > ____________________________ > > Clouds Sky GmbH > Im Mediapark 4c > 50670 K?ln > Tel.: +49 221 4853 5783 > Mobile: +49 171 993 6814 > www.cloudssky.com > > Sitz der Gesellschaft: K?ln > Registergericht: Amtsgericht K?ln, HRB 70999 > Gesch?ftsf?hrer: Stephan Hartmann, Arash Kaffamanesh F.v.G.u.v.S. > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta