action #108278
Updated by JERiveraMoya about 2 years ago
#### 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:
```xml
<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