fix zypper refresh timeout in zypper_lifecycle

[rfan1]

Enhance the current logic not to remove the zypper cache.

• Related ticket: https://progress.opensuse.org/issues/115292
• Needles: n/a
• Verification run:
  x86_64:
  https://openqa.suse.de/tests/9354276
  https://openqa.suse.de/tests/9357992
  aarch64:
  https://openqa.suse.de/tests/9357971
  s390x:
  https://openqa.suse.de/tests/9357991

[okurz]

s/timout/timeout/

And you created a pull request which has the template text included

[asdil12]

The patch itself looks fine

[rfan1]

s/timout/timeout/

And you created a pull request which has the template text included

Thanks @okurz, deleted that line.

[rfan1]

The issue can be seen on s390x and aarch64 platforms in the latest build, let me try to test them as well.

[okurz]

two more typos lifesycle and preparse. Please be more careful with the spelling. The git history is an important reference for future research and it's very hard to find corresponding changes by search term if not correctly written.

[rfan1]

two more typos lifesycle and preparse. Please be more careful with the spelling. The git history is an important reference for future research and it's very hard to find corresponding changes by search term if not correctly written.

Thanks, let me fix the typo in the code as well

[rfan1]

Hold on this PR, I need to investigate why we delete the zypper cache, and to see if we can enhance current logic
` select_console 'root-console';

 # First we'd make sure that we have a clean zypper cache env and all dirs have
 # 0755 and all files have 0644 pemmission.
 # For some reason the system will change the permission on /var/cache/zypp/{solv,raw}
 # files. this cause the zypper lifecycle failed when building cache for non-root user.
 script_run('rm -fr /var/cache/zypp/solv /var/cache/zypp/solv');
 script_run('rm -fr /var/cache/zypp/raw /var/cache/zypp/raw');`

[a-kpappas]

Why is it script_run "zypper refresh" and not assert_script_run?

[rfan1]

Why is it script_run "zypper refresh" and not assert_script_run?

Good question, as discussed with @hjluo, we don't have to make sure zypper fresh command get return code 0 for later tests.
just try to sync the repositories and then zypper lifecycle throws away everything

[asdil12]

Why is it script_run "zypper refresh" and not assert_script_run?

If at all, it should be:

zypper_call "refresh";