Ansible Networking Workshop error #2160
Assignees
Comments
|
I am trying to see what is going on, recreating now in mye nv |
|
OK I have been hammering on this most of Friday and today (Monday July 8th). I don't have a fix yet.... but these types of unreliable errors that are hard to reproduce are a giant pain.... it is really hard to figure out what is going on. In parallel I am ordering a bunch of workbenches from demo.redhat.com to see if I can get one to mess up. Unrelated... but also causing pains are the Cisco IOS-XE support for SSH keys... I am testing a fix right now to move us to ED25519 vs ssh-rsa. My first few tests are favorable and will get rid of a lot of errors people have with ssh legacy SSH keys. Anyways.... some findings for this specific issue with code-server and the workshop:
The task that fails on July 2nd-> It is weird that it is failing for 7 (seven) hosts but the others are fine, because they should all be identical. It also.... "sorta' matches that "some hosts" are broken..... There seems to be some sort of "order of operations" with using controller configuration collection to pre-provision groups. However... I am not sure why this would affect visual studio code (or code-server in this case). These roles are not connected in anyway... when I look at the code-server code everything ran correctly.... My thoughts:
I wish I was 100% certain what is going on... this workshop type is in the process of being migrated to agnosticd and the demo.redhat.com native software so I have not been maintaining it as frequently as I used to... so this is also probably slowing down mean time to resolution. Keep reporting any issue you are seeing and I will continue to hammer on this. |
|
OK it is related b/c its a handler.... the handler to restart code-server is never run I was able to recreate In this example, student1 and studen5 are missing from the code-server restart, b/c they failed on the identical task |
|
So the reason this fails is because when I use the controller_configuration content collection It is a dictionary... dictionaries are commonly not ordered.... so the problem happens SOMETIMES because it will try to configure the group I have gotten rid of those two groups from using controller configuration and forced them into manual adds at the end in the right order. Will send fixes tomorrow. |
IPvSean
added a commit
to IPvSean/workshops
that referenced
this issue
Jul 8, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Summary
Workshop Name: Ansible Automation Platform 2 Networking Automation Workshop
Workshop URL: http://m4j6m.example.opentlc.com/
Description:
The workshop provides 3 links -
In some workshop user instances, when trying to access the VS Code URL, you get the message "This site cannot provide a secure connection. student3.m4j6m.example.opentlc.com sent an invalid response. ERR_SSL_PROTOCOL_ERROR".
To circumvent this error you can change "https" to "http", and the login page will load. However, if you then input the password, it says the password is incorrect and you cannot access the VS Code browser link.
In the event that a workshop user can successfully access the https link, this issue does not happen.
Reproducing the issue is unreliable. Some instances work and some do not.
This is not an issue for the Automation Controller or the SSH access, only the VS Code link.
Issue Type
Bug
Extra vars file
N/A
Ansible Playbook Output
N/A
Ansible Version
[student@ansible-1 ~]$ ansible --version
ansible [core 2.15.5]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/student/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.9/site-packages/ansible
ansible collection location = /home/student/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.9.16 (main, Sep 12 2023, 00:00:00) [GCC 11.3.1 20221121 (Red Hat 11.3.1-4)] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
Ansible Configuration
[student@ansible-1 ~]$ ansible-config dump --only-changed
ACTION_WARNINGS(/etc/ansible/ansible.cfg) = False
COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH(/etc/ansible/ansible.cfg) = ignore
CONFIG_FILE() = /etc/ansible/ansible.cfg
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = ['/home/student/lab_inventory/hosts']
DEFAULT_STDOUT_CALLBACK(/etc/ansible/ansible.cfg) = yaml
DEFAULT_TIMEOUT(/etc/ansible/ansible.cfg) = 60
DEPRECATION_WARNINGS(/etc/ansible/ansible.cfg) = False
DEVEL_WARNING(/etc/ansible/ansible.cfg) = False
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
INTERPRETER_PYTHON(/etc/ansible/ansible.cfg) = auto_silent
PERSISTENT_COMMAND_TIMEOUT(/etc/ansible/ansible.cfg) = 200
PERSISTENT_CONNECT_TIMEOUT(/etc/ansible/ansible.cfg) = 200
RETRY_FILES_ENABLED(/etc/ansible/ansible.cfg) = False
SYSTEM_WARNINGS(/etc/ansible/ansible.cfg) = False
Ansible Execution Node
CLI Ansible (Ansible Core)
Operating System
Windows & MacOS
The text was updated successfully, but these errors were encountered: