Saw a few posts based on this and tried requesting for a new session as well which is not yet done by the way. I tried running the jobs after a few days but its still the same issue. I only have 2 more days on the course and I’m not really keen on spending another month’s fees just to finish this project. Can I please get some help on this?
Hello @AakashBolisetty
Have you filled out the lab refresh form? You need to wait for 2 business days after completing the form so that the team refresh your lab manually.
Sorry! I was busy with another exam and didnt respond! I actually received an email saying it was resolved but the problem still persists and now I have been charged for an extra month for no reason!
@AakashBolisetty I’m sorry for the inconvenience. Can you please share some details about in which step you are facing an issue? What’s the error you are getting?
In in the initial part where we would be going through the terraform set-up process, whenever I run terraform apply, it either just freezes and tried to reconnect or the terminal just fails.
@AakashBolisetty you can use the command terraform apply -no-color 2> errors.txt. This way the output to terraform commands gets written to a text file, and you will be able to see what’s causing the terminal crash and try to fix it.
I tried running that command and this is what I get. This is kind of annoying now. Can I get a complete reset of this lab? And let me know what option I need to choose on the form since this problem is not amongs the ones described on the form.
If you just fill out the form, it doesn’t really matter what reason you select. The course staff will figure out what you need.
I did that but nothing changed the last time.
Hopefully a mentor for that course will be able to assist you.
@AakashBolisetty You need to wait up to 3 business days after filling out the form. It is a manual process and it takes time. Please, try again afterwards.
Same happens to me – calling terraform apply for the data quality step, completely crashes the VS Code and it gets stuck in “attempting to reconnect”.
Tried a few times (reload/restart/reconnect) and it’s consistent.
Submitted ticket to refresh the lab environment.
@Amir_Zare I waited for almost another 3 days after getting the email saying it was reset but it has everything as it was when I had the issue previously. And now AWS_console also doesnt open up!
@AakashBolisetty @romik13 Just to clarify for everyone, when you fill out the form, what we do is one of two things: 1) assign to you a new AWS account Or 2) adjust the budget of the lab.
Filling out the form does not reset the files in the lab. If the terraform files are not correctly configured, filling out the form does not solve the issue. The form only helps when the AWS account assigned to you has some issues.
Now since the terminal is crashing, there should be something missing either in the terraform steps or the terraform files.
Amir suggested terraform apply -no-color 2> errors.txt, this will print the error in the errors.txt file. So you should see in your environment on the left side (from your screenshot), the files errors.txt. You can open it and check the errors. So,
- can you explain to me at what step you got the error?
- can you share with me the error in the errors.txt?
The “attempting to reconnect …” message: this is from coursera environment, and it happened to me many times. What I usually do when I get this, is that I close the window (I don’t do any refresh) and then from coursera again, I click on the lab item “Open Lab” (please don’t do any reboot if the session is still within the 3 hours assigned to the lab).
CC: @Mubsi
@AakashBolisetty I’ll double check your account info regarding the AWS console issue.
Thank you for breaking it down really well and explaining it. I opened my errors.txt but it turns out to be empty.
When I do the terraform apply step, thats when I face the issue of attempting to reconnect. I did try closing the window and opening again, trying it after a few days but nothing seemed to work.
AWS console seems to be a more wider issue since I did see a couple more people complaining on that, so not sure if there is anything I can do for now?
Also, is there any way I can get a complete lab reset just to start it from scratch?
Thank you @AakashBolisetty ! I’m checking the last two labs now, to see if there’s some issues in the stack of resources of the labs. I’ll get back to you in a bit.
When does your subscription end?
@AakashBolisetty @romik13 I just checked the capstone labs. It looks like the stack of AWS resources are note correctly loading. This happens when AWS updates the resources, so this is something in the lab settings that we need to fix from our side. I will check with the team on this and get back to you regarding the estimated time (when we can fix this). We’ll fix as soon as possible.
Please let me know when your subscriptions end.
I was able to pass the assignments and the course after:
- AWS account for both labs was reset (after I filled the form)
- Appending
|| echo "$?"to all terminal commands, which prevents them from passing the exception into VSCode and crashing it and getting the “attempting to reconnect”.
Without those:
Sometimes terraform apply was crashing because something in the configuration was wrong – this is the only state “expected” by the instructions in the course. In this case just note that doing || echo "$?" to show the error inline worked better than 2> errors.txt and also always prevented the full environment crash.
Sometimes terraform apply was crashing because it previously was left in an inconsistent state, and then it couldn’t override/recognize AWS resources that it created in a previous run. In this case I had to go to AWS console and find them and remove them manually.
And sometimes even terraform plan would crash, then the environment got totally messed up, and only worked after the AWS account reset + lab restart + waiting for 3 hours.
1 Like
First an update regarding the issue with empty resources in the last two capstone labs:
@AakashBolisetty @Mubsi
Explanation of the issue: Yesterday, AWS deprecated the usage of the computing node: dc2.large that we used for the redshift cluster in the last two capstone labs. This why the stack of AWS resources were failing to start and this is why you were not seeing any resources.
We fixed the issue, we used another type computing node (ra3: this is what AWS recommended). I tried both capstone labs and they are now working. Please let me know if you encounter any other issues. Thank you for your patience everyone!