CL210 LAB setup errors

[Roopa1]

Hi, CL210 Virtual Lab seems to be repeatedly failing to setup properly. Like, in the lab: Managing openstack networking, the script lab 'networking-review setup' should create any resources  required to perform the exercise. But most of the resources are not created and tagged as failed. Due to this the lab exercise could not be done. The same issue is seen is almost all the exercises. Has anyone else facing this issue ?

[ricardodacosta]

The problem is most likely because the IDM admin user's password has expired and the IDM certificate has expired.

Mind trying the following please?

[1] Address the IDM admin user's expired password:

ssh root@utility

kinit admin

enter RedHat123^

It will then prompt you to enter a new password as the old password has expired. You *MUST* use RedHat123^ has the new password.

[2] Dirty workaround for the expired certificate

ssh root@utility

ipactl start

When you see a reference to pki-tomcatd hit ctrl+c

use netstat -plnt | grep :88

You want to see krb5kdc bound to port of 88

If you see that, then your lab scripts will work. If they don't, check it here again.

[Roopa1]

Its still not working. 

Also, with root login in utility, 'kinit admin' cmd gives the below response.

kinit: Cannot contact any KDC for realm 'LAB.EXAMPLE.NET' while getting initial credentials

[santoshkkhade]

Hello,

After ipactl start , i was able to kinit admin, however when i run the command

ipa user-info , getting connectivity error to https://utility.lab.example.com/ipa/json

[ricardodacosta]

Check if httpd on utility is started:

systemctl status httpd 

If not, have a look at the workaround that I posted.

Mind you, this may become moot soon because we're close to publishing a fixed version of CL210v13. By close a mean it could happen this coming week.

Ping me here if you need further assistance.

[santoshkkhade]

Hi sir

Http is not running , I even tried recreating the lab in vain .

[ricardodacosta]

Recreating the lab won't work because the problem is in the "golden" image for the course. Everytime you create a new lab, you will get the problem because it needs to be fixed in the "golden" image. This will happen really soon and we tested it last week in our staging environment.

If you want to do some of the activities in the meantime, follow my solution:

Just remember to hit Control C when you see "Starting pki-tomcatd service".

Good luck and happy learning!

[ricardodacosta]

I should have had you execute step 2 first, then step 1 🤪

[Roopa1]

Hi Ricardo,

There seems to be something wrong in the httpd service in the lab utility server.

'ipactl start' was getting stuck with error 'failed to start httpd Service'. 

I used 'ipactl start --ignore-service-failure' , then it ignored the httpd failure and reached upto pki-tomcatd entry. I was able to give cntl C at this point and port 88 was visibile in netstat output. I was able also able to change the passwd of admin to the RedHat123^. 

But, since httpd service didnot start, ipa is not working. Manual start of httpd service is throwing error. 'Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.'

I have deleted and re-provisioned the lab multiple times. But its the same status. 

[ricardodacosta · Accepted solution]

We don't need httpd up and running. 

The problem is in the blueprint for the course so every time you delete and recreate it, you will get the same problem.

I've spun up a lab and replicated the workaround with a screenshot. 

However, the curriculum team has addressed this issue and a new blueprint for the course will be published very soon (as in this week).

Reach out to me if you still have issues.