action #36739
closed[functional][y][smt] SMT server needs to be updated. Mirror for SLES15-Updates and SLES15-Pool is missing
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-gnome_install_smt@64bit fails in
scc_registration
because the mirror of SLES15-Updates and SLES15-Pool seems to be missing and/or outdated.
Reproducible¶
Fails since (at least) Build 652.1
Expected result¶
Last good: 652.1 (2018-05-27)
Acceptance criteria¶
- AC1: Documentation of how the SMT server is maintained and updated is referenced in this ticket (not just documented in this ticket)
- AC2: Test can access up-to-date resources for the corresponding builds
Suggestions¶
- Find out how test is supposed to work
- Find out who maintains the SMT server, e.g. ask in irc or mailing list, I assume QA SLE migration team
- Make sure the SMT server has the updated resources
- Make sure the test works again
- Optional: Improve post_fail_hook providing hints how to make sure the SMT server has the necessary resources
Further details¶
Always latest result in this scenario: latest
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-05 to 2018-06-19
Updated by riafarov almost 6 years ago
- Subject changed from [functional][smt][fast] SMT server needs to be updated. Mirror for SLES15-Updates and SLES15-Pool is missing to [functional][smt] SMT server needs to be updated. Mirror for SLES15-Updates and SLES15-Pool is missing
Updated by okurz almost 6 years ago
- Subject changed from [functional][smt] SMT server needs to be updated. Mirror for SLES15-Updates and SLES15-Pool is missing to [functional][y][smt] SMT server needs to be updated. Mirror for SLES15-Updates and SLES15-Pool is missing
- Due date set to 2018-07-03
- Priority changed from Normal to High
- Target version set to Milestone 17
happening in SLE15 GMC.
Updated by okurz almost 6 years ago
should be at least crosschecked in this sprint if the prio "high" is still valid.
Updated by okurz almost 6 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz almost 6 years ago
- Due date deleted (
2018-07-03) - Priority changed from High to Normal
- Target version changed from Milestone 17 to Milestone 21+
we have to delay that, no capacity for this
Updated by riafarov almost 6 years ago
- Related to action #36742: [sle][functional][y] test fails in scc_registration because repositories haven't been synced fully on smt added
Updated by riafarov almost 6 years ago
- Related to deleted (action #36742: [sle][functional][y] test fails in scc_registration because repositories haven't been synced fully on smt)
Updated by riafarov almost 6 years ago
- Has duplicate action #36742: [sle][functional][y] test fails in scc_registration because repositories haven't been synced fully on smt added
Updated by riafarov almost 6 years ago
- Description updated (diff)
Issue may get fixed by increase of disk space. We may also consider to create multi-machine test, one of which uses YaST wizard to configure smt and then we conduct installation using this instance. Then we won't have issues with maintenance of the smt instance and can adjust scope to verify feature. Same is applicable to RMT, which is not yet integrated into installer.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21+ to Milestone 21+
Updated by okurz over 5 years ago
- Target version changed from Milestone 21+ to future
Updated by riafarov over 3 years ago
- Status changed from Workable to Rejected
- Assignee set to riafarov
Seems to be very outdated. Rejecting as no action is planned for smt.