Welcome to the Linux Foundation Forum!

Lab 3.2

bike2wrk
bike2wrk Posts: 14
edited April 2017 in LFS252 Class Forum - Discontinued

Hi,

I am unable to complete Lab 3.2 step #6, access the BUI.  I completed the workaround steps listed in the Lab 2 discussion however I am still unable to connect.  Are we still waiting for Labs 3 & 4 to be fixed by the infrastructure team?

Thanks,

Christopher

Comments

  • phiney
    phiney Posts: 18
    edited April 2017

    I completed this only two days ago and it was successful. Click quit and start the lab again ?

    I did not need to use and workarounds.

    Peter

  • bike2wrk
    bike2wrk Posts: 14
    edited May 2017

    I may be experiencing another user error however I am still unable to login.  After the script (stack.sh) finishes running I try to use the IP address of my host to access the BUI, 192.168.97.2 .  The error I receive in my browser is "This site can't be reached."  I am also unable to ping the IP address of my host from my workstation.  

    I found the following warnings in the stack.sh.log but not sure if they are preventing me from reaching the BUI

    2017-05-03 18:10:17.805 | /tmp/tmpYAEmlH/pip.zip/pip/_vendor/requests/packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS request has been made

    , but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certific

    ate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedoc

    s.io/en/latest/security.html#snimissingwarning.

    2017-05-03 18:10:17.805 | /tmp/tmpYAEmlH/pip.zip/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true SSLContext object

     is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer vers

    ion of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning.

    Do you have any recommendations?

    Thanks,

    Christopher

     

  • bike2wrk
    bike2wrk Posts: 14
    edited May 2017

    Thanks for responding.  Sadly I did not properly follow the directions. 

    On your local system open a browser and point it at the public IP Address of your devstack-cc node. 

    I was trying to use the public IP Address of the compute-node.  

    Thank you,

    Christopher

  • fouronthebeach
    fouronthebeach Posts: 2
    edited October 2017

    LFS252 Labs -> cannot access Horizon dashboard in Lab# 2 Task# 5:



    ubuntu@devstack-cc:~/devstack$ ip a s eth0

    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

        inet 166.78.156.39/24 brd 166.78.156.255 scope global eth0



    trying Horizon Dashboard:

    http://166.78.156.39/dashboard/auth/login/?next=/dashboard/ -> Not Found



    http://166.78.156.39 -> gives Apache page (so Apache appears to be running on the devstack node, just not Horizon.?..)

     

    - what am I missing?

Categories

Upcoming Training