openQA Project (public) » openQA Infrastructure (public)

I suggest to also reference URLs for EngInfra tickets, easier to click around this way :) So the according ticket is
https://infra.nue.suse.com/SelfService/Display.html?id=185915

I never can see infra tickets anyway but good you put the link here :)
In the meantime while we wait for an answer I created https://gitlab.suse.de/nicksinger/github-autologin which could automate our gitlab login over the webui in the future to avoid blocked accounts.

It seems slindomansilla has replaced the git ssh URL with an https URL but I am not aware of any place where he might have documented that so noting it here. This is a kinda workaround by allowing to pull from the gitlab repo but not allowing to push so this would need to be reverted as soon as the account is ok again. Evzenie Sujskaja told me over private chat that they will add the employee flag to the openqa-pusher account. Nothing heard since this morning though.

Applying workaround:

changing remote from SSH url gitlab@gitlab.suse.de:openqa/os-autoinst-needles-sles.git to HTTPS url https://gitlab.suse.de/openqa/os-autoinst-needles-sles.git.

This allows to fetch data without user authentication, but doesn't allow by default any push (webui credentials would be needed)

geekotest@openqa:~/share/tests/sle/products/sle/needles> git remote -v
origin  https://gitlab.suse.de/openqa/os-autoinst-needles-sles.git (fetch)
origin  https://gitlab.suse.de/openqa/os-autoinst-needles-sles.git (push)
origin-ssh      gitlab@gitlab.suse.de:openqa/os-autoinst-needles-sles.git (fetch)
origin-ssh      gitlab@gitlab.suse.de:openqa/os-autoinst-needles-sles.git (push)

When the gitlab account is unblocked, the following commands need to be executed

geekotest@openqa:~/share/tests/sle/products/sle/needles> git remote rename origin origin-https
geekotest@openqa:~/share/tests/sle/products/sle/needles> git remote rename origin-ssh origin

The https remote doesn't harm to be there, but if necessary, it can be removed with

geekotest@openqa:~/share/tests/sle/products/sle/needles> git remote remove origin-https

At the moment there are two commits on osd needles clone that cannot be pushed.

Can anyone temporarily give push permissions to my gitlab user SLindoMansilla?

nicksinger wrote:

We have the account back. I renamed the remotes accordingly and pushed/pulled left-overs. Everything seems fine.

not sure, maybe I do something wrong.
I tried to create hpc needle now in osd and got:
"Fatal error when saving needle.
Task for saving needles failed: Checkout Minion dashboard for further details."

sebchlad wrote:

nicksinger wrote:

We have the account back. I renamed the remotes accordingly and pushed/pulled left-overs. Everything seems fine.

not sure, maybe I do something wrong.
I tried to create hpc needle now in osd and got:
"Fatal error when saving needle.
Task for saving needles failed: Checkout Minion dashboard for further details."

Thanks for reporting back. Seems like openqa-gru was stuck somehow and didn't even write any error onto the minion dashboard. I've restarted the service now and was able to save a needle. Please try again if it works for you :)
@okurz I'd not create a bug about this now as I can't really provide any logging data. The journal was empty, no failed minion logged anything. Feel free to create one anyway if you see the need for it

nicksinger wrote:

sebchlad wrote:

nicksinger wrote:

We have the account back. I renamed the remotes accordingly and pushed/pulled left-overs. Everything seems fine.

not sure, maybe I do something wrong.
I tried to create hpc needle now in osd and got:
"Fatal error when saving needle.
Task for saving needles failed: Checkout Minion dashboard for further details."

Thanks for reporting back. Seems like openqa-gru was stuck somehow and didn't even write any error onto the minion dashboard. I've restarted the service now and was able to save a needle. Please try again if it works for you :)

yes, all works now. Thx.