ISSUES - Trivia May 2023

[snow_cloud]

Hi there!

I had a couple of issues in two of the labs included in the May 2023 Trivia.

The first lab is "Prisma Cloud: Protect your Cloud Instance with Host Defender", In task 2, after executing the command:

kubectl create -f twistlock_console.yaml

I had an error message related to the 8080 port being closed (I tried the lab 2 days ago, so I don't remember the complete message). I couldn't progress through the lab due to this issue.

The second lab, "Getting Started with NetApp BlueXP & Cloud Volumes ONTAP for Google Cloud", in Task 2, it is supposed you will find a "cloudmanager" VM deployed, but in my case, there wasn't any, therefore, I could not progress in this lab either.

Has anyone faced the same issues? If so, what would you suggest to do to solve them?

Thank you for your time and attention.

[Ajay]

Hi,

Lab : Prisma Cloud: Protect your Cloud Instance with Host Defender

Yes , I'm also facing the same issue. I have informed the qwiklabs support about this, hope they resolve it soon.

[snow_cloud]

I tried the Lab again today, but this time I had issued on task 3. When checking the workloads on Kubernetes Engine, it seems the pods didn't work. The error was related to "does not have minimum availability", Pod errors: "InvalidImageName". I was unable to go beyond task 3.

[Ajay]

Hi,

I'm facing the same situvation.

I've already reported this to qwiklabs Qwiklab support team. I hope they will fix it soon.

Lab Prisma Cloud

[snow_cloud]

Yes, exactly the same issue @Ajay . It seems that Palo Alto Networks needs to give it maintenance.  

[alxxthegeek]

Yes I'm having issues today.  Can't ssh to all the vm's (jenkins and juice-shop) and on the ones I can the ping command returns nothing and can't connect to the prisma console - connection refused.

Couldn't complete task 3

Looks like it needs some maintenance 

[alxxthegeek]

And support wasn't very helpful  - told a transient issue and try again in a few hours

[snow_cloud]

That happened to me as well @alxxthegeek.

When pinging the VMs, nothing comes, and I think it is because the twistlock 's pods are not properly deployed. I had the same issues that @Ajay is showing in the picture.

[Ajay]

Hi ,

Trivia March 2023  | Lab :[ Creating Dynamic Secrets for Google Cloud with Vault ] also fails in the midway. Kindly don't waste credits trying them. I've reported it to the qwiklabs support.

Please find the screenshots:

[alxxthegeek]

Also having issues with this one got up to the last step , all commands successful and then get on check my progress

Configure static accounts

Please configure a static account that generates OAuth2 access tokens.

very frustrating!!

[snow_cloud]

Hi @Ajay. I did not have issues with this one.

[Ajay]

Hi,

Lab :[ Creating Dynamic Secrets for Google Cloud with Vault ]

I don't know what's wrong ,I got authentication error,  so I reported this to qwiklabs team. They might have fixed it, I'll try again

[snow_cloud]

Unfortunately for me, I missed trivia in May Week 1.

I am not sure if Google will open it to those who missed it. Does anybody know?

Still, I had fun with all the labs done for May 2023, even though a few of them had issues.

[hoaidang97]

Me too, I had a question with Google support. So we can do it again at end month.

[snow_cloud]

Did they confirm that is going to be open at the end of the month? That is awesome @hoaidang97 !

[Ajay]

Hi,

Today I received an update on this issue , the qwiklabs team is still working on this. 

[Ajay]

Hi, @Lauren_vdv 

We are facing some issues with [ May Trivia 2023 ] labs. Can you help us out ?

LAB : Prisma Cloud: Protect your Cloud Instance with Host Defender

LAB : Creating Dynamic Secrets for Google Cloud with Vault

[Ajay]

ISSUE RESOLVED : ALL LABS WORKING FINE 

All labs working fine

[snow_cloud]

Hi there!

I just want to let you know that I tried again the LAB: Prisma Cloud: Protect your Cloud Instance with Host Defender, and it worked for me.

Be careful during Task 2 when you enter the token to Linux Twistcli. If the token is not the correct one, the pods' deployment will fail. Make sure to include the proper token, so the pods will deploy and the lab will work (I realized I put the wrong token and I had a failure to deploy the image, after correcting the token and repeating the steps, the pod deployed correctly and I was able to progress through the lab-picture is attached for your reference).

I hope this solution helps you. Good luck!