Apply workaround for yast content not being loaded for MU sp4

[skliu]

Apply workaround for yast content not being loaded for MU sp4

• Related ticket: https://progress.opensuse.org/issues/112577
• Needles: -
• Verification run: http://d218.qam.suse.de/tests/156

[jknphy]

@skliu any clue about what is this failure about at the end of the VR?

[skliu]

@skliu any clue about what is this failure about at the end of the VR?

I think it's due to the time out.

[jknphy]

I see too much troubles with this workaround, now that we have libyui, we could switch to
yast2_gui/bootloader/bootcode_options
which covers only the first tab, but we can plan for covering a bit more.
For the instserver have you investigated the error? did you file a bug for it?

[jknphy]

@skliu @JRivrain @ge0r Do we have a solid solution already for bootloader?, if not, please @skliu apply yast2_gui/bootloader/bootcode_options instead of needle-based module. And then we can merge this PR.
If we don't have a clear idea for the second issue, file a ticket with current findings, looks less important that bootloader module, we can live without it for a while.

[JRivrain]

@skliu any clue about what is this failure about at the end of the VR?

I think it's due to the time out.

I had mentioned it in https://progress.opensuse.org/issues/112589: there are more issues with this module, just applying the workaround is not enough to fix it I'm afraid.

[jknphy]

@JRivrain we just need to fix the first error, correct, but we need a ticket with clear info to tackle the second error as part of the outcome of this task, that ticket that I rejected didn't have that info (including links to our observations could also help for next time)

@skliu are we missing something before merging? I remembered we talked offline about creating new module to be schedule before this to do zypper ref and autoimport the keys. Are you planning to add that?

[skliu]

@JRivrain we just need to fix the first error, correct, but we need a ticket with clear info to tackle the second error as part of the outcome of this task, that ticket that I rejected didn't have that info (including links to our observations could also help for next time)

@skliu are we missing something before merging? I remembered we talked offline about creating new module to be schedule before this to do zypper ref and autoimport the keys. Are you planning to add that?

only the coping CD problem. http://d218.qam.suse.de/tests/131#step/yast2_instserver/43

[skliu]

For the instserver have you investigated the error? did you file a bug for it?

Yes, I did. the first error is due to the time out of coping CD contents, and the rest errors are all due to the failure of sending "alt-f", so "yast2 instserver" window is not disappeared, all the errors happens randomly. BTW: where can I file a bug? on https://bugzilla.suse.com/ ?

[skliu]

@JRivrain we just need to fix the first error, correct, but we need a ticket with clear info to tackle the second error as part of the outcome of this task, that ticket that I rejected didn't have that info (including links to our observations could also help for next time)

@skliu are we missing something before merging? I remembered we talked offline about creating new module to be schedule before this to do zypper ref and autoimport the keys. Are you planning to add that?

the module is created.

[skliu]

I see too much troubles with this workaround, now that we have libyui, we could switch to yast2_gui/bootloader/bootcode_options which covers only the first tab, but we can plan for covering a bit more. For the instserver have you investigated the error? did you file a bug for it?

I created a progress ticket for it. https://progress.opensuse.org/issues/115748

[jknphy]

LGTM