After Getting the System Upgrade to Complete a Readiness Check and Complete the Full backup the Update process begins after 5 minutes some lines are displayed in the Console log.
[2016-01-22 10:44:07 UTC] Job "maintenance_mode {"enable":true}" has been started
[2016-01-22 10:44:07 UTC] Magento maintenance mode is enabled.
[2016-01-22 10:44:07 UTC] Job "maintenance_mode {"enable":true}" has successfully completed
[2016-01-22 10:44:07 UTC] Job "update {"components":[{"name":"magento/product-community-edition","version":"2.0.1"}]}" has been started
[2016-01-22 10:44:07 UTC] Starting composer update...
After sitting for an almost 2 hours with only this being displayed in the Console Log I'm clueless to know what happen because Google Inspect/Network displays that
Status
{,…}
complete: false
error: false
isUpdateInProgress: true
pending: false
After 11.4 hours of wating and the status being updating saying no errors the installation finally completed saying it has stopped due to error then says try to roll the system back. or click here to manually roll the system back.
This is my var/update_status.log
[2016-01-22 10:44:07 UTC] Job "maintenance_mode {"enable":true}" has been started
[2016-01-22 10:44:07 UTC] Magento maintenance mode is enabled.
[2016-01-22 10:44:07 UTC] Job "maintenance_mode {"enable":true}" has successfully completed
[2016-01-22 10:44:07 UTC] Job "update {"components": {"name":"magento/product-community-edition","version":"2.0.1"}]}" has been started
[2016-01-22 10:44:07 UTC] Starting composer update...
[2016-01-22 10:44:07 UTC] ./composer.json has been updated
Then I tried clicking the Rollback button which run no code just greyed the box out.
So then i proceeded to do the manual rollback using magento.docs
rolled back media and code successfully then must have error-ed out while doing DB rollback because then the file bin/magento Poof diapered.
Best Answer
Found a Solution although its not exactly How i wanted to be able to Update Magento 2.0.0 to 2.0.1 because so far for me Magento2 is full of bugs and problems. but so far on 2.0.1 its been just as stable as 2.0.0 has been.
Solution to my problem was to start over because I'm using Google.cloud I had a snapshot before trying to upgrade to 2.0.1 because i knew there was gonna be problems.
So those of you who run into this problem like me & are using a Fresh CE 2.0.0 Installation Do this to Upgrade to Magento CE 2.0.1 via Composer CLI.
Step 1 open a SSH terminal navigate to Magento install directory. mine was.
Step 2
Step 3
Step 4
Step 5
Step 6
Permissions might Very Depending on how your using your magento2 installation. Thanks to @Rob Mangiafico for his help on another Stackexchange question.