Skip to content
Snippets Groups Projects
Commit 9ab48b0e authored by Eesaan Atluri's avatar Eesaan Atluri
Browse files

Update README.md with a note.

parent 60934b7a
No related branches found
No related tags found
No related merge requests found
...@@ -29,6 +29,8 @@ cluster with vagrant: ...@@ -29,6 +29,8 @@ cluster with vagrant:
vagrant up ohpc vagrant up ohpc
``` ```
Note: If you encounter an issue with OHPC node provisioning due to GPG key errors as mentioned in https://github.com/jprorama/CRI_XCBC/issues/77. Please run the following command: `vagrant box update`
The ansible config will bring the master node to the point where its The ansible config will bring the master node to the point where its
ready to ingest compute nodes via wwnodescan and prompt to you ready to ingest compute nodes via wwnodescan and prompt to you
start a compute node. You can create a compute node and start it with start a compute node. You can create a compute node and start it with
...@@ -111,14 +113,11 @@ The default user name and password for the web UI is 'vagrant'. ...@@ -111,14 +113,11 @@ The default user name and password for the web UI is 'vagrant'.
## Issues and Work arounds ## Issues and Work arounds
1. If you encounter an issue with OHPC node provisioning due to GPG key errors as mentioned in https://github.com/jprorama/CRI_XCBC/issues/77. Please run the below command as a work around from outside your VM:
`vagrant box update`
2. After you run the above command if you were to get a `"kernel mismatch error"`. To get past this error please run the below commands: 1. After you run the above command if you were to get a `"kernel mismatch error"`. To get past this error please run the below commands:
`vagrant ssh ohpc -c "uname -r"` `vagrant ssh ohpc -c "uname -r"`
Copy and paste this kernel version in the group_vars/all to update the kernel version in the `build_kernel_ver` variable. Copy and paste this kernel version in the group_vars/all to update the kernel version in the `build_kernel_ver` variable.
3. If you encounter an issue with nodes_vivify role in updating the slurm status on nodes, specifically the error `slurm_update error: Invalid node state specified`. Please increase the compute node memory. For example if you're using 4GB already increase the memory to 6GB in your Virtual Box. 2. If you encounter an issue with nodes_vivify role in updating the slurm status on nodes, specifically the error `slurm_update error: Invalid node state specified`. Please increase the compute node memory. For example if you're using 4GB already increase the memory to 6GB in your Virtual Box.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment