Open alexelshamouty opened 8 years ago
Bug was found in the cloudbroker failing to register subset of api. fixed in b4
I think the interruption/restore state will be improved when code will be migrated to ays/js8, not before.
COO Notified
@grimpy how can a critical bug end up in backlog
Environment could not be installed due to this error
Environment :
du-conv-2
Behaviour
1 Create ovc_git 2 ssh into ovc_git 3 execute master_spawn.py -q 4 execute the following command :
jspython scripts/master-configure.py --gateway 192.168.31.254 --start 192.168.28.10 --end 192.168.28.200 --netmask 255.255.252.0 --ssl wildcard --gid 777
Result
I have cleaned & started the installation for 5 times with the same parameters and the result is the same
notes :
1 . installation script does not support reinstallation or re-running the scripts much , there are no parameters to identify that this is a re installation and that old hrds should be ignored/overwritten , hence the result is always remove everything and start over
2 . the script 'master_spawn' does not really check if the machine has been created successfully , i have faced an error when it thinks that the machine has been created while in reality it has not and it was in an error stat , this is probably due to the lack of error checking on ms1 api side , but there should be a way to check if the machine was really started or not
3 . master_spawn.py is really slow , and this is due to the fact that the script runs sequentially , in my opinion i think it should utilises threading or any other means of parallelism to cut down the wait time , especially that the virtual machines are independent of each other
4 . if master_configure.py was interrupted it does not cleanly restart , it reads values from hrd and disregard the actual data thats on disk ( add check ? )