Break-fix Scenario

Objectives:

  • Investigate the instance connectivity issue in Red Hat OpenStack Platform.

  • Solve the instance connectivity in the hands-on lab environment.

Scenario:

Your team manages a Red Hat OpenStack Platform (RHOSP) infrastructure used by an important development team for your company. There was a requirement from your internal networking team to have Open Virtual Network (OVN), an open-source software-defined networking (SDN) solution that seamlessly integrates with OpenStack. Recently networking team noticed that there is connectivity issue with instance running in OpenStack envrionment.

They noticed the following error:

[student@workstation ~]$ ssh -i /home/student/osp_training/.scenariobfx021/scenario-bfx021-key.pem cirros@192.168.51.191
Connection closed by 192.168.51.191 port 22

Recreate scenario

  1. Log in to your lab environment on the ROLE platform.

  2. As the student user, run the lab start script on the workstation VM to reproduce the issue.

     ----
cd /home/student/osp_training/scenarios_repo/
./lab start bfx021
----

    The lab customization script is already cloned in the /home/student/osp_training/scenarios_repo/ directory.

    Sample output
    [student@workstation ~]$ cd /home/student/osp_training/scenarios_repo/
[student@workstation scenarios_repo]$ ./lab start bfx021
Running start action against scenario bfx021
Run the following command:
ssh -i /home/student/osp_training/.scenariobfx021/scenario-bfx021-key.pem cirros@192.168.51.98

[student@workstation scenarios_repo]$

    In the preceding output, IP address can differ in your lab environment.

  3. This creates an instance with broken ssh connectivity.

  4. To ensure scenario is recreated, run the ssh command from the previous output:

    Sample output
    [student@workstation ~]$ ssh -i /home/student/osp_training/.scenariobfx021/scenario-bfx021-key.pem cirros@192.168.51.98
Connection closed by 192.168.51.98 port 22

IMPORTANT NOTE:

  • If the lab script fails, you will not see the ssh command for instance connectivity.

  • Wait a few minutes for the lab to initialize properly, then re-run the lab start script.

  • You can retrieve the instance connectivity message generated by the lab script at any time by running the following command.

    cat ~/osp_training/.scenariobfx021/message

  • Run the lab finish script if you wish to clean up the environment either to start fresh or to switch to another scenario.

    cd /home/student/osp_training/scenarios_repo/
./lab finish bfx019