fix satellite subscription handling#349
Conversation
ab3845a to
86b8dc1
Compare
|
[citest] |
86b8dc1 to
fdbaeb3
Compare
|
Changed the |
|
[citest] |
181c8ab to
60820ba
Compare
60820ba to
121d482
Compare
|
[citest] |
121d482 to
07568b8
Compare
|
[citest] |
Jira: RHEL-134401
07568b8 to
20063ea
Compare
|
[citest] |
|
I tried upgrading 8to9 with multiple different activation keys (pre_leapp, post_leapp and regular leapp AK) with different repositories exposed. It worked fine and reregistered every time resulting in a system subscribed with post_leapp key. |
|
Ready to merge? |
|
[citest] |
|
I've made the pre and post activation keys mirror the upgrade key if not specified. This makes them optional. Tested on 8to9 satellite upgrade with multiple keys and single key. Both worked fine. |
Variables for pre-upgrade and post-upgrade Satellite activation keys now default to the upgrade activation key, making them optional but recommended.
b64cf75 to
c94d304
Compare
|
Fixed duplicated readme section and added changelog note about the activation key variables change. |
|
[citest] |
As a followup on PR #348, fix the satellite subscription problem which originates from use of handlers and
include_roleincompatibility. Since usinginclude_roleis not supported in handlers (ansible/ansible#20493), it is not a good idea to wrap it ininclude_tasksand use it anyways. Thus, this patch removes the handlers entirely and converts them into regular tasks. This solution is inline with the original idea (#348 (comment)) and basically similar to the key handling in the upgrade role.Not tested yet, although I'm already able to setup satellite host and upgrade it. I'll try it soon.