changes to the capsule upgrade playbook test

[pondrejk]

Problem Statement

We are not really equipped to test the full capsule upgrade in the regular automation and I wouldn't say it's necessary. Meanwhile there came also an update playbook, that will be covered with #15863 (awaits packaging)

Solution

This pr changes the upgrade playbook tests to merely check that the playbook is around

Related Issues

[pondrejk]

trigger: test-robottelo
pytest: tests/foreman/api/test_remoteexecution.py -k upgrade

[Satellite-QE]

PRT Result

Build Number: 8579
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_remoteexecution.py -k upgrade --external-logging
Test Result : =========== 1 passed, 2 deselected, 11 warnings in 622.21s (0:10:22) ===========

[lhellebr]

Did it ever work in the original state? Why doesn't it anymore? Is this a regression testing-wise? Is there a plan to restore testing again? Why isn't it necessary to test it in your opinion? I know, a lot of questions :)

[pondrejk]

It did work in the sense that it triggered the playbook, but that didn't have a chance to actually complete the y-stream upgrade of capsule (for that we'd need an n-1 capsule + repos, etc). I suppose previously the playbook did "succeed" by doing nothing, likely the response from sat-maintain changed -- now when you try to upgrade to the same version you are on, you get failures

So I figure we could leave the y-stream scenario for upgrade pipeline, and in the regular run just check the playbook exists (this PR) + fully test z-stream capsule update, which is a newly added playbook (pr here #15863).