Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-14659

failed to connect to GitLab server: 401: invalid_token

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • None
    • DO417 - RHAAP2.4-en-2-20240821
    • DO417
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • en-US (English)

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/do417-2.4/pages/ch03s02
      Reporter RHNID: nehsingh@redhat.com
      Section Title:          Guided Exercise: Writing Playbooks                                                              

      Issue description

      failed to connect to GitLab server: 401: invalid_token
      This issue is reproduceable, just create a completely new lab environment, login to desktop, ssh to workstation.lab.example.com and start command "lab start playbook-write"
      It took me an half an hour to fix it, creating a new personal token on git.lab.example.com for user student and exchanged the token in file
      /home/student/.venv/labs/libs/python3.9/site-packages/do417/ansible/inventory/host_vars/git/vars.yml
      The fix helped not for the command "lab finish playbook-write". Other "lab start ..." commands did work after that fix.

      Steps to reproduce:

       

      Workaround: Run the following command every time you restart the lab environment

      `lab install -u --env test --version 2.4.4.dev0+pr.768 do417` and then run the lab scripts

      Expected result:

              glsbugs-automation@redhat.com PTL - Ansible Team
              nehsingh@redhat.com Neha Singh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: