Bug 1268356 - Managing Spacewalk with Puppet
Managing Spacewalk with Puppet
Status: NEW
Product: Spacewalk
Classification: Community
Component: Installation (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2015-10-02 12:04 EDT by s.zemlyanoy
Modified: 2015-10-02 12:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description s.zemlyanoy 2015-10-02 12:04:12 EDT
Description of problem:
I want to provide Spacewalk into our environment in order to keep all systems updated and have reporting systems cross the board. In meantime we are widely using puppet for configuration, setup etc.  
There are few issues I’m concerning about:
1.	Manage yum repos by puppet, disable rhnplugin to hide channels as YUM repos on clients and force SW to install updates from unmanaged repositories. How can I prevent SW to download packages locally to itself but just update list of packages?
2.	Manage client’s yum repos by SW channels but I still want to have control over local YUM repos by puppet. Is it feasible?

Which approach might be more optimal?

Thanks in advance!

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Note You need to log in before you can comment on or make changes to this bug.