Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix uyuni proxy sync #9439

Merged
merged 4 commits into from
Nov 17, 2024
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -794,7 +794,7 @@ Feature: Synchronize products in the products page of the Setup Wizard
@uyuni
@proxy
Scenario: Add Uyuni Leap 15.5 Proxy, including Uyuni Client Tools
When I use spacewalk-common-channel to add all "leap15.5" channels with arch "x86_64"
When I use spacewalk-common-channel to add all "uyuni-proxy" channels with arch "x86_64"
maximenoel8 marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The channels synchronized seems correct, but.. I wonder at which point we include the correct repository for the mgr-tools (in particular mgrpxy) during the CI.
I guess... we only do it on sumaform, and we rely on it, right? If that's the case, maybe it gonna be good a comment somewhere in this feature to explain that we skip that step because we do directly on deployment.

zypper ar https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/images/repo/Uyuni-Proxy-POOL-x86_64-Media1/

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is done during combustion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But in combustion we might be passing Stable or Master as repos, but... not the one coming from the MIs, as far as I know we don't handle MI injections in combustion.

Copy link
Contributor Author

@maximenoel8 maximenoel8 Nov 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean the repositories from additional_repository variable ?
We do now add those repositories into combustion: https://github.com/uyuni-project/sumaform/blob/addeb4382c1c77c2e84f8e7644d66319fa28361e/backend_modules/libvirt/host/combustion#L97C1-L105C5

That what trigger me to open this issue: https://github.com/SUSE/spacewalk/issues/25609

And I wait until all synchronized channels for "uyuni-proxy" have finished

@susemanager
Expand Down
12 changes: 4 additions & 8 deletions testsuite/features/support/constants.rb
Original file line number Diff line number Diff line change
Expand Up @@ -1338,14 +1338,10 @@
],
'uyuni-proxy' => # CHECKED
%w[
opensuse_leap15_5-x86_64
opensuse_leap15_5-uyuni-client-x86_64
opensuse_leap15_5-x86_64-backports-updates
opensuse_leap15_5-x86_64-non-oss
opensuse_leap15_5-x86_64-non-oss-updates
opensuse_leap15_5-x86_64-sle-updates
opensuse_leap15_5-x86_64-updates
uyuni-proxy-devel-leap-x86_64
opensuse_micro5_5-x86_64
opensuse_micro5_5-x86_64-sle-updates
maximenoel8 marked this conversation as resolved.
Show resolved Hide resolved
opensuse_micro5_5-uyuni-client-x86_64
opensuse_micro5_5-uyuni-client-devel-x86_64
]
# There are no channels for Retail under Uyuni
}
Expand Down
Loading