Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Issue Description
When the user clicks “Deploy”, Console displays continuous “Pending” status for following fields to the right of the display:
“Site address”
“Instance”
“Instance zone”
“WordPress administrator username”
“Wordpress admin password”
“MySQL password”
“phpMyAdmin installed”
Root cause
Launching the Wordpress service creates two VMs- one temporary “coord” VM that handles the Wordpress build and deployment, and a main WordPress VM that hosts Wordpress. The issue appears to arise as the “coord” VM is not able to retrieve a startup script needed to complete the build, specifically:
As a result of this, the coord VM continually and unsuccessfully attempts to retrieve “startup-script.sh”, and the WordPress installation remains stalled.
The cause of this appears to be that the “coord” VM doesn’t receive an external address upon it’s creation, preventing it from retrieving “startup-script.sh”.
Workaround
In order to resolve this issue you can assign the coord VM an external IP address, which allows it to retrieve “startup-script.sh”, which in turn allows it to complete the WordPress setup/deployment process.
Instructions:
In the Compute Engine “VM instances” page, click on the “coord” VM (the machine name should contain the string “coord”)
Click Edit
Click on the network interface for the machine
In the External IP drop-down select “Ephemeral”
Click on “Done”
Click on “Save” at the bottom of the page
This will provide it with an external IP address and allow it to access the resources it needs to complete the setup.
This issue has been reported to the corresponding team.