关于“将 MySQL 数据库迁移到 Google Cloud SQL：实验室挑战赛”的评价

Loic N. · 已于 2 months前审核

David D. · 已于 2 months前审核

Vitalii L. · 已于 2 months前审核

RAUSHAN Y. · 已于 2 months前审核

Mukesh Kumar Y. · 已于 2 months前审核

John L. · 已于 2 months前审核

Shawn M. · 已于 2 months前审核

Jason E. · 已于 2 months前审核

This lab has a validation bug in Task 3. The Cloud SQL instance automatically authorizes RFC 1918 IP ranges (including 10.142.0.3 from the blog VM), but the lab's scoring system fails to detect this implicit authorization and requires manual addition of the IP, which the Google Cloud API explicitly blocks. All manual steps were completed successfully and the WordPress blog is fully functional with the Cloud SQL database. Please fix the validation logic to recognize automatically authorized IP ranges.

Alexandre C. · 已于 2 months前审核

Brajesh S. · 已于 2 months前审核

Shaik Salima G. · 已于 2 months前审核

Sumesh S. · 已于 2 months前审核

Ram K. · 已于 2 months前审核

Lalit P. · 已于 2 months前审核

Sachin D. · 已于 2 months前审核

Shivashankar S. · 已于 2 months前审核

YOGESH R. · 已于 2 months前审核

Tomasz G. · 已于 2 months前审核

Raju V. · 已于 2 months前审核

at last thanks!

Jamiil Toure A. · 已于 2 months前审核

Raju V. · 已于 2 months前审核

ee

sanjay v. · 已于 2 months前审核

The lab environment is fundamentally broken on provisioning. The blog VM instance deployed with a corrupted local MySQL init state and a completely missing /var/www/html/wordpress application directory. Because of this, the baseline data dump (wp_backup.sql) could not be restored at startup. Task 5 fails while the lab infrastructure builds resources exclusively in us-east1. Even after manually downloading the WordPress source, configuring the database manually, and injecting the expected tables/metadata, the validation check remains unreachable due to this network routing misalignment.

Ananth P. · 已于 2 months前审核

Aditi J. · 已于 2 months前审核

Szymon J. · 已于 2 months前审核