Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error parsing bastion yaml #862

Closed
alok87 opened this issue Nov 10, 2016 · 3 comments
Closed

Error parsing bastion yaml #862

alok87 opened this issue Nov 10, 2016 · 3 comments
Assignees

Comments

@alok87
Copy link
Contributor

alok87 commented Nov 10, 2016

This PR #694 introduced private networking. After this PR, on doing below tasks to setup a new cluster with private networking i get the parsing error shown below.

  • kops create cluster --networking cni --topology private --zones=us-west-1a uswest1.clusters.mydomainexample.com
  • kops edit cluster uswest1.clusters.mydomainexample.com
  • added bypassBastion: true under topology and :wq
  • kops update cluster uswest1.clusters.mydomainexample.com --yes

The last update command fails with the below error

I1110 07:08:11.497292    5223 populate_cluster_spec.go:237] Defaulting DNS zone to: Z2NAIFNPNLZ1OZ
I1110 07:08:11.767655    5223 loader.go:307] error parsing yaml.  yaml follows:
  0: # ---------------------------------------------------------------
  1: #
  2: # Private Network Topology in AWS
  3: #
  4: # Inspired by https://github.com/kubernetes/kops/issues/428
  5: #
  6: # ---------------------------------------------------------------
  7:
  8:
  9:

error building tasks: error handling file "cloudup/_aws/topologies/_topology_private/bastion.yaml": error parsing yaml "_aws/topologies/_topology_private/bastion.yaml": error converting YAML to JSON: Expected document start at line 9, column 0

Parsing is failing for {{ if WithBastion }} in _aws/topologies/_topology_private/bastion.yaml

@krisnova krisnova self-assigned this Nov 10, 2016
@alok87
Copy link
Contributor Author

alok87 commented Nov 10, 2016

@kris-nova: The error gets resolved on removing the comments from bastion.yaml. Can u verify?

@alok87
Copy link
Contributor Author

alok87 commented Nov 10, 2016

Closed with #865

1 similar comment
@alok87
Copy link
Contributor Author

alok87 commented Nov 10, 2016

Closed with #865

@alok87 alok87 closed this as completed Nov 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants