Project

General

Profile

Actions

action #108278

closed

Add to How-To section how to verify with new rpm an AutoYaST bug in second stage

Added by JERiveraMoya about 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2022-03-14
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Share the knowledge from
https://bugzilla.suse.com/show_bug.cgi?id=1196614#c24

Basically DUD= bootloader parameter only affects the installer, so when we need to verify a bug in AutoYaST and the fixes are applied to AutoYaST second stage, we need another strategy:

<add-on t="map">
    <add_on_products t="list">
    </add_on_products>
    <add_on_others t="list">
      <listentry>
        <media_url>http://<ip>/path/to/repo/</media_url>
        <product>custom_autoyast_service</product>
        <product_dir>/</product_dir>
        <name>Customized AutoYaST services</name>
        <priority config:type="integer">40</priority>
        <signature-handling>
          <accept_unsigned_file config:type="boolean">true</accept_unsigned_file>
          <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum>
          <accept_non_trusted_gpg_key>
            <all config:type="boolean">true</all>
          </accept_non_trusted_gpg_key>
          <accept_unknown_gpg_key>
            <all config:type="boolean">true</all>
          </accept_unknown_gpg_key>
          <accept_verification_failed config:type="boolean">true</accept_verification_failed>
        </signature-handling>
      </listentry>
    </add_on_others>
  </add-on>

Acceptance criteria

AC1: Document this way how to test a change for future second-stage bugs in AutoYaST.

To create repo we have in gitlab: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Development_Guide.md#create-rpm-repo-for-self_update-test
We should mention that in some way.

Suggestions

Probably we need a new section in Confluence for it, like in gitlab to not mix Manual validation with Development guide.
This is something that is documented in AutoYaST but we should documented as something useful when verifying a bug before it reaches the product.
For having a technical view about these stages, consult: https://confluence.suse.com/display/YAST/YaST+Systemd+Services

Actions #1

Updated by JERiveraMoya about 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Description updated (diff)
  • Status changed from New to Workable
Actions #2

Updated by rainerkoenig almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to rainerkoenig
Actions #3

Updated by JERiveraMoya almost 2 years ago

  • Status changed from In Progress to Workable
Actions #4

Updated by JERiveraMoya almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee changed from rainerkoenig to JRivrain
Actions #5

Updated by JRivrain almost 2 years ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by JERiveraMoya almost 2 years ago

could we also please create a section for https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Development_Guide.md#create-rpm-repo-for-self_update-test to specify how to create a repo, which will not obvious for new comers, and put in this article you created a link to it. It could be a copy/paste, the idea is to migrate from gitlab to confluence, so that should do.

Actions #7

Updated by JRivrain almost 2 years ago

JERiveraMoya wrote:

could we also please create a section for https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/blob/master/Development_Guide.md#create-rpm-repo-for-self_update-test to specify how to create a repo, which will not obvious for new comers, and put in this article you created a link to it. It could be a copy/paste, the idea is to migrate from gitlab to confluence, so that should do.

Done

Actions #8

Updated by JERiveraMoya almost 2 years ago

  • Status changed from Feedback to Closed

Thanks! we almost have all there I think :)

Actions

Also available in: Atom PDF