Bug 1218280 - [Build :30718:rubygem-actionpack-5_1] openQA test fails in hawk_gui
Summary: [Build :30718:rubygem-actionpack-5_1] openQA test fails in hawk_gui
Status: RESOLVED DUPLICATE of bug 1215707
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP5
Classification: openSUSE
Component: Other (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: package coldpool
QA Contact:
URL: https://openqa.suse.de/tests/13079303...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-20 16:19 UTC by Michele Pagot
Modified: 2024-01-04 10:26 UTC (History)
3 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments
journal (368.02 KB, text/x-log)
2023-12-20 16:19 UTC, Michele Pagot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michele Pagot 2023-12-20 16:19:17 UTC
Created attachment 871495 [details]
journal

## Observation

openQA test in scenario sle-15-SP5-Server-DVD-HA-Incidents-x86_64-qam_ha_hawk_client@64bit fails in
[hawk_gui](https://openqa.suse.de/tests/13079303/modules/hawk_gui/steps/406)

Web interface is stuck in Add Cluster page

## Test suite description
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.


## Reproducible

Fails since (at least) Build [:30718:rubygem-actionpack-5_1](https://openqa.suse.de/tests/13079303) (current job)


## Expected result

Last good: [:31906:yast2-network](https://openqa.suse.de/tests/13078474) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-HA-Incidents&machine=64bit&test=qam_ha_hawk_client&version=15-SP5)
Comment 1 Petr Gajdos 2024-01-04 10:16:30 UTC
Isn't that duplicate of bug 1215707?
Comment 2 Petr Gajdos 2024-01-04 10:26:20 UTC
Yeah, it seems so. If not, please reopen.

*** This bug has been marked as a duplicate of bug 1215707 ***