We are standing up Open OnDemand for our users that are currently using our HPC, after getting it stood up there is a red banner at the top of the page and will flip between two error messagegs
“The cluster config for viking-cluster has a problem: (): did not find expected key while parsing a block mapping at line 2 column 3”
“The cluster config for viking-cluster has a problem: (): did not find expected key while parsing a block mapping at line 7 column 5”
I have tried looking at the viking-cluster.yml file and made sure that there are spaces and not tabs, reloaded the webpage as well as the webserver and am still encountering the error, I have also tried this with other users who have never been to the site as well as tried it in a “incognito” browser. Line 2 column 3 is where you state metadata and line 7 column. 5 is where i have to declare what we are using (in this case slurm)
Haha, a second pair of eyes always helps! I can see a missing quote at the end of the host on line 5. Let’s start there and see if that fixes anything.
Hello travis,
Yeah i just went on my cluster and that was just from me trying to sanitize and forgot to include the end " . do you see any other problems?
Since some of this is sanitized for me to see, are you able to take the actual config you have and put it through a YAML validator? That might be the best bet as maybe something in that raw file is just slightly off?
I ran in through my linter in VSCodium and im not getting any errors in there. i even checked to make sure i was using spaces vs tabs. is there a log somewhere i can look at that would output these errors?
Ok, thanks for doing all that and giving me the updates.
I think the next best step is to try and strip this down as far as you can, even using a whole new file just to be sure, and start very simple with what is in the yaml and build up from there to see if the error finally pops up at a specific step.
WIth the correct values for your cluster and the configs. Leave out the bin_overrides for trhe moment.
That’s the simplest route i can think of at the moment. It’s very odd this file is not being read, so a fresh file with a minimal build will help find the root cause hopefully.
ok so the minimal build is working without showing the errors at the top of the page. im going to start adding options one by one and see if i can get the error to reproduce and put my findings here.