I’m moving my VMWare infrastructure from old hardware to new hardware. One of the last guest VMs I’ve waited to move is my GitHub Enterprise (GHE) host. My plan to migrate the system was simple: <\/p>\n
The installation instructions<\/a> provided by GitHub are pretty good. To deploy a new GitHub Enterprise image I followed Installing GitHub Enterprise on VMWare<\/a>.<\/p>\n Of course, no process is perfect. Here are a couple minor points that may save you some time:<\/p>\n <\/p>\n When I started the new GitHub Enterprise VM and connected to the console. Once I configured networking, the console provided the next step:<\/p>\n However, that didn’t work. It directed me to a blank page at http:\/\/192.168.0.123\/ssl_warning.html.<\/p>\n The answer? Specify https<\/strong> instead, e.g.:<\/p>\n I added the appropriate SSH key from a system where I had the GHE backup and restore tools installed, and then selected the Migration<\/em> option. It prompted me to run At first I thought I could just add the key to my known_hosts file:<\/p>\n But Eventually I decided to disable (Just remember to remove that entry when done! I should also note that the Running migrations<\/em> step took forever. I often wondered if it was still working. The first three steps were almost instant, but Running migrations<\/em> goes on for hours:<\/p>\n I tried visiting the regular (i.e. non-admin interface) and it gave me the following message:<\/p>\n How long is a long time? What is a hookshot database migration? Who knows, be patient.<\/p>\n The console shows these messages over and over and over:<\/p>\nVisit http:\/\/192.168.0.123\/setup to configure GitHub Enterprise.<\/code><\/pre>\nVisit https:\/\/192.168.0.123\/setup to configure GitHub Enterprise.<\/code><\/pre>\nghe-restore<\/code>:<\/p>\n$ .\/ghe-restore 192.168.0.123\r\nChecking for leaked keys in the backup snapshot that is being restored ...\r\n* No leaked keys found\r\nNo ECDSA host key is known for [192.168.0.123]:122 and you have requested strict checking.\r\nHost key verification failed.\r\nError: ssh connection with '192.168.0.123:122' failed\r\nNote that your SSH key needs to be setup on 192.168.0.123:122 as described in:\r\n* https:\/\/enterprise.github.com\/help\/articles\/adding-an-ssh-key-for-shell-access<\/code><\/pre>\n$ ssh-keyscan -t ecdsa 192.168.0.123<\/code><\/pre>\nssh-keyscan<\/code> exited with an error code and returned no output.<\/p>\nStrictHostKeyChecking<\/code> in my .ssh\/config<\/code> file for the target IP address:<\/p>\nHost 192.168.0.123\r\n\tStrictHostKeyChecking no<\/code><\/pre>\nStrictHostKeyChecking<\/code> is an important security control.)<\/p>\n\n
Migrating...\r\nPlease be patient, this may take a long time. Please do not reboot or shutdown the appliance until this has completed. \r\nPerforming hookshot database migrations.<\/code><\/pre>\n19:59:04 elasticsearch: Starting Elasticsearch...\r\n19:59:04 elasticsearch: Started Elasticsearch.\r\n19:59:12 elasticsearch: elasticsearch.service: main process exited, code=exited, status=1\/FAILURE\r\n19:59:12 elasticsearch: Unit elasticsearch.service entered failed state\r\n19:59:12 elasticsearch.service holdoff time over4, scheduling restart.\r\n19:59:12 cloud-config: Cannot add dependency job for unit could-config.service, ignoring: Unit cloud\r\n19:59:12 elasticsearch: Stopping Elasticsearch...<\/code><\/pre>\n