QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Restarted the failed job to see what is going on, but the retry passed the agama test, but then failed later in validate_product.

rainerkoenig wrote in #note-2:

Restarted the failed job to see what is going on, but the retry passed the agama test, but then failed later in validate_product.

Cannot reconnect, because the Agama profile we import doesn't have the post script to allow loging root, https://openqa.suse.de/tests/16380889/settings/yam/agama/auto/sap_default_no_scc.json
that is why is pointing to Lemon's ticket, but feel free to add it. Although for your issue I think you can reproduce it somehow because the repos are not reachable from ibs frequently.

As a high priority ticket, please let's try to report feedback more frequently.

I can see this WIP PR after one week of work which is a copy/paste of the example I provided in the ticket description.
Could you please share if you find some difficulties with this ticket that we could discuss aside (retro or 1:1) ? Happy to help if I know how...

I did a light research, maybe there is a way to manage that journalctl -u agama -f will show step by step the packages installed (In real time), maybe we can check this output in some manner.

jfernandez wrote in #note-7:

I did a light research, maybe there is a way to manage that journalctl -u agama -f will show step by step the packages installed (In real time), maybe we can check this output in some manner.

all the 40 mins stuck situation I saw in failure were related with installation not starting, so we are not even try to look for weird things like disconnections, it is more like check that the screen that does the installation and install the package is there and if not exit early.

all the 40 mins stuck situation I saw in failure were related with installation not starting, so we are not even try to look for weird things like disconnections, it is more like check that the screen that does the installation and install the package is there and if not exit early.

In PPC64LE there is no screen to check, puppeteer is headless and there is no installation/displaymanager screen to check Agama status.

You could do a pre-check previous to start install but it will fail in repository error or package installation error.

jfernandez wrote in #note-9:

all the 40 mins stuck situation I saw in failure were related with installation not starting, so we are not even try to look for weird things like disconnections, it is more like check that the screen that does the installation and install the package is there and if not exit early.

In PPC64LE there is no screen to check, puppeteer is headless and there is no installation/displaymanager screen to check Agama status.

You could do a pre-check previous to start install but it will fail in repository error or package installation error.

the page is still there in headless mode even if you don't see it, but of course the code should be done in puppeteer not with needles and openqa api.

the page is still there in headless mode even if you don't see it, but of course the code should be done in puppeteer not with needles and openqa api.

As I said in this approach you don't cover installation issues, only a pre installation check, this check can be included in all architectures and scenarios as a good practice but won't solve the issue in part of the cases.

Mitigation: https://github.com/jknphy/agama-integration-test-webpack/pull/76 to 15 minutes, but still can exit early if we find a way with this ticket.