calico.yaml error
I am in lab 3.1 and I ran kubectl apply -f calico.yaml and I get this error:
error: error parsing calico.yaml: error converting YAML to JSON: yaml: line 182: did not find expected '-' indicator
I did some troubleshooting:
a. line 182 looks like the lines above and below it: type: object
b. I ran the calico.yaml that i downloaded on the master node through http://www.yamllint.com/ and that reports valid
c. I did some googling on the error and only found a similar bug with a different line: https://github.com/projectcalico/calico/issues/707
d. I tried to find a calico validation tool on the calico website and there is a command line tool for calico but it does not have a validator or syntax checking service.
any ideas on how to proceed?
Comments
-
Hi, i found the problem to be the indentation in the yaml of the -name and value, they were not indented properly:
# The default IPv4 pool to create on startup if none exists. Pod IPs will be
# chosen from this range. Changing this value after installation will have
# no effect. This should fall within--cluster-cidr
.
- name: CALICO_IPV4POOL_CIDR
value: "192.168.0.0/16"4 -
Hello,
Thank you for the feedback. As you should be downloading the calico file from the source, please let the projectcalico.org folks know of the issue. Typically they remedy the error quickly.
Regards,
0 -
Hi @catorarn,
The newer calico file when downloaded, has both
-name
andvalue
lines commented out. You can leave them commented out, they will work as expected.Regards,
-Chris1 -
Hi Chris, I faced the same error and fixed by indenting. Later I read you response for not to uncomment these lines. Any issue If I uncomment these lines and fixed the indention
0 -
Ignore this. Had the same issue then realised it was the indentation issue that was mentioned in the first response. Thanks for that!
0 -
@serewicz said:
Hello,Thank you for the feedback. As you should be downloading the calico file from the source, please let the projectcalico.org folks know of the issue. Typically they remedy the error quickly.
Regards,
Hi, I just stumbled upon this conversation after seeing the same error. The file as delivered works just fine. It's actually the next part of the instructions for exercise 3.1 which induces the error, if you botch the indents. Perhaps a clarification here, to be careful with the indents? Or remove this step, if it's really not necessary? The instructions technically don't say to edit the file, but they do say to avoid conflicts with existing networks. And the example shown has been uncommented. Item 6 in the screenshot below:
0 -
Hello,
You will note the command used is "less", a paginator which does not edit the file. If one had happened to choose 192.168 for their VM IP range they would have issues, which is why the step exists. There is no direction to edit. Download the file and look at it. Then use it.
Regards,
0 -
@serewicz said:
Hello,You will note the command used is "less", a paginator which does not edit the file. If one had happened to choose 192.168 for their VM IP range they would have issues, which is why the step exists. There is no direction to edit. Download the file and look at it. Then use it.
Regards,
That may be, but your example shows the lines not commented out. I'm sure everyone went down the same rabbit hole like I just did and tried to make our files look like your example.
0 -
hi! Thanks for posting this. I've the same issue uncommenting the CALICO_IPV4POOL_CIDR section. The value is still bad indented. now is working with my chosen network
1 -
Sorry for commenting on old thread but encountering same issue here while trying to run a command kubectl apply -f calico.yaml
getting an error:
error: error parsing calico.yaml: error converting YAML to JSON: yaml: line 182: did not find expected key
If I look at my calico.yaml contents then it has like below:
# no effect. This should fall within
--cluster-cidr
.
- name: CALICO_IPV4POOL_CIDR
value: "192.168.0.0/16"Could someone help me and share how it should look after edit?
Thanks!
Gaurav0 -
never mind ended up specifying the url instead of file we had downloaded in the process.
0 -
This is still an issue. I do have 192.168.x.x as my local network, thus I need to set a value here. The text could have been made clearer. One really needs to think to get grasp of the message in the text.
Now I just have to figure out what is the correct indent.
Edit: For me vim was removing a space in my indent. That is, if i did "sudo -i" and looked at the file everything was ok. But when I exited out from that shell in to the regular shell there was a space extra on the two uncommented lines.
This is on Debian 11 Bullseye
0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 734 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 166 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 6K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 222 LFD103 Class Forum
- 17 LFD110 Class Forum
- 34 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 110 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 112 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 18 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 118 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 50 LFS241 Class Forum
- 44 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 146 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 156 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 8 LFW111 Class Forum
- 257 LFW211 Class Forum
- 180 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- SKF201 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.2K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 312 Installation
- 79 All In Program
- 79 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)