Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kola: Improve debugging abilities through SSH login #57

Merged
merged 2 commits into from
Mar 6, 2020

Conversation

pothos
Copy link
Member

@pothos pothos commented Mar 2, 2020

  • kola: Improve debugging abilities through SSH login
    The tests in "kola run" used a temporary SSH key and
    directly deleted the machines after a failure.

    Add the same SSH key option as in "kola spawn"
    to include additional SSH keys (just "-k" is
    enough to include the agent/default SSH keys).
    Also use the option to skip machine removal as
    in "kola spawn --remove=false".

  • Use the private IP because the default firewall
    rules do not allow incoming traffic on 2379 for
    the public IP.
    Also, there are no FLATCAR__IP variables set up in
    /etc/environment for machines running in
    Google Compute Engine because (as with afterburn)
    the prefix is still COREOS_.

@pothos pothos requested review from t-lo and dongsupark March 2, 2020 16:14
@pothos pothos force-pushed the kai/fix-gce-variable branch 2 times, most recently from b821e1d to f4a169c Compare March 5, 2020 19:36
@pothos
Copy link
Member Author

pothos commented Mar 5, 2020

Tests are now starting additional machines with cloud-config but there the bash script errors. To debug this I need a way to tell kola to use an additional SSH key besides the random key that it generates.

@pothos pothos changed the title kola/tests/kubernetes: Use correct GCE variable kola: Improve debugging abilities through SSH login Mar 6, 2020
The tests in "kola run" used a temporary SSH key and
directly deleted the machines after a failure.

Add the same SSH key option as in "kola spawn"
to include additional SSH keys (just "-k" is
enough to include the agent/default SSH keys).
Also use the option to skip machine removal as
in "kola spawn --remove=false".
@pothos pothos force-pushed the kai/fix-gce-variable branch from 2698019 to b68e0fd Compare March 6, 2020 14:33
Use the private IP because the default firewall
rules do not allow incoming traffic on 2379 for
the public IP.
Also, there are no FLATCAR_*_IP* variables set up in
/etc/environment for machines running in
Google Compute Engine because (as with afterburn)
the prefix is still COREOS_.
@pothos pothos force-pushed the kai/fix-gce-variable branch from b68e0fd to 96f71af Compare March 6, 2020 14:42
@pothos
Copy link
Member Author

pothos commented Mar 6, 2020

The Kubernetes test passes, I'm quite surprised that it isn't outdated :)

Copy link
Member

@dongsupark dongsupark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

BTW there are probably many other places with a wrong FLATCAR_ prefix being used. From the first look, FLATCAR_ looks really correct, COREOS_ looks wrong to normal users. It is one of the corner cases that prevent us from maintaining repos in an automated way.

@pothos pothos merged commit 2e6bc1b into flatcar-master Mar 6, 2020
@pothos pothos deleted the kai/fix-gce-variable branch March 6, 2020 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants