MySQL データベースの Google Cloud SQL への移行: チャレンジラボ のレビュー

doesn't work (task 5) and cannot understand why (have tried everything)

Chitale Deeksha · 2ヶ月前にレビュー済み

Negniboue Nitcheu Loic · 2ヶ月前にレビュー済み

Díaz David · 2ヶ月前にレビュー済み

Liapin Vitalii · 2ヶ月前にレビュー済み

YADAV RAUSHAN · 2ヶ月前にレビュー済み

Yadav Mukesh Kumar · 2ヶ月前にレビュー済み

Law John · 2ヶ月前にレビュー済み

Mullings Shawn · 2ヶ月前にレビュー済み

Equite Manzo Jason · 2ヶ月前にレビュー済み

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.

Carmo Alexandre · 2ヶ月前にレビュー済み

Sahoo Brajesh · 2ヶ月前にレビュー済み

GOOGLEUSER Shaik Salima · 2ヶ月前にレビュー済み

S Sumesh · 2ヶ月前にレビュー済み

Kumar Ram · 2ヶ月前にレビュー済み

Pathak Lalit · 2ヶ月前にレビュー済み

Dangi Sachin · 2ヶ月前にレビュー済み

Saravanabavan Shivashankar · 2ヶ月前にレビュー済み

R YOGESH · 2ヶ月前にレビュー済み

Grazi Tomasz · 2ヶ月前にレビュー済み

Varahala Raju · 2ヶ月前にレビュー済み

at last thanks!

Ali Jamiil Toure · 2ヶ月前にレビュー済み

Varahala Raju · 2ヶ月前にレビュー済み

ee

verma sanjay · 2ヶ月前にレビュー済み

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.

Pesaru Ananth · 2ヶ月前にレビュー済み

Joshi Aditi · 2ヶ月前にレビュー済み