similar to: Locked version repos

On April 10, 2015 7:45:00 PM EDT, Steven Barre <steven at realestatewebmasters.com> wrote: >Hello Everyone > >I'm looking into the best way to have locked version repos for my >CentOS >systems. The systems are all set up with Chef and have a couple >different recopies/roles. I'd like to have locked version repos for >each >role with tested RPMs. Then

mrepo or reposync works fine with apache. Eero 11.4.2015 2.45 ap. "Steven Barre" <steven at realestatewebmasters.com> kirjoitti: > Hello Everyone > > I'm looking into the best way to have locked version repos for my CentOS > systems. The systems are all set up with Chef and have a couple different > recopies/roles. I'd like to have locked version repos for

On 2015-07-22 13:34, Thomas Eriksson wrote: > The upstream project is called Katello, http://www.katello.org/ > It has nothing to do with Spacewalk as far as I can tell. Katello is just one piece. Satellite 6 also integrates Candlepin, Puppet and more. What I'm wondering is if the entire set of software - Satellite 6 as one piece - is going to get a new upstream project. > I have

I have read a couple old threads here on updates for servers, and I am looking for some mechanics to getting the actual updates done. I don't want automatic updates; I want to control when and what gets updated. First I have to determine that a particular server needs updates. I suppose a daily script that would run "yum check-updates' and emails me the results could work, but

Hi Everyone, Since Satellite 6 is an amalgam of other F/OSS projects and is no longer solely based on Spacewalk, is a new upstream project for Satellite 6 going to be created? BEtter yet, is a new upstream project already available? Ranbir -- Kanwar R.S. Sandhu

I work on the Pulp Project (http://www.pulpproject.org/), and we are trying to fully implement the forge API so we can create new repositories that can be reached via a command like: $ sudo puppet module install --module_repository http://localhost/pulp/puppet/myforge/ someone/theirmodule The problem I''ve encountered is that the install command includes hard-coded absolute paths to

Hi, I am setting up a local forge for some weird political reasons. I came to know that puppetlabs is working on such a feature. But, in the meantime I wanted to try out setting up the repo and use --modules_repository flag in "puppet module install: command. For that, I need to mimic the puppet forge repo format (meaning the directory structure of the modules). Can somebody point me

Hello, I have been asked to come up with a strategy for centralized patch management of our linux servers. Today, this is only centos and rhel. What is everyone else doing in this arena? Thanks!

Using CentOS 7.5, I can't (and don't expect) to see rhn-ssl-tool. But I was expecting to find something similar. I can't see anything in the recent RH documentation about it - I presume it was remove/changed with the move from Spacewalk to Satellite - but I presume the functionality is still required? Has something replaced it? Cheers L. ------ '...postwork futures are

Hi, yesterday I was trying to create local mirror of CentOS7 using katello/pulp. I was receiving CRC checksum errors while attempting to sync the mirror. The particular error in question was: Feb 12 07:46:34 bazinga pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [e2cd9930] Generating metadata databases. Feb 12 07:47:06 bazinga pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [e2cd9930]

Hi, all I have a number of machines that are out of sync with one another by virtue of having done a yum update after a base 6.2 install at different times (all were previous CentOS 5.3) Consequently, systems are a mix of 2.6.32-220.7.1, 2.6.32-220.13.1 or 2.6.32-220.17.1. So 2 questions: - Is it possible to perform a yum update (or another other kind of update), specifying installation

On 07/22/2015 11:46 AM, Kanwar Ranbir Sandhu wrote: > On 2015-07-22 13:34, Thomas Eriksson wrote: >> The upstream project is called Katello, http://www.katello.org/ >> It has nothing to do with Spacewalk as far as I can tell. > > Katello is just one piece. Satellite 6 also integrates Candlepin, Puppet > and more. What I'm wondering is if the entire set of software -

I am a little new to managing large numbers of CentOS/RHEL servers and was wondering what you experienced sysadmins prefer, Spacewalk or Puppet? Thanks, Dan Burkland -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20091103/de975d32/attachment-0004.html>

Hello, When I try to sync CentOS 6 from different ftp mirrors using spacewalk command "spacewalk-repo-sync" I get this message " 'Unable to load package', 'Invalid information uploaded to the server' " for 38 packages. When I check, these 38 packages are not named correctly. For example, sync command is looking for

I actually move the default *.repo files and replace them with "". The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more. I would argue that I should not need to install any *-release-* rpms at all to get all the required software. On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:

For even more information about "Heartbleed". -Connie Sieh ---------- Forwarded message ---------- Date: Wed, 9 Apr 2014 12:27:54 -0500 From: The SANS Institute <NewsBites at sans.org> Subject: FLASH NewsBites - Heartbleed Open SSL Vulnerability FLASH NewsBites - Heartbleed Open SSL Vulnerability FLASH NewsBites are issued only when a security event demands global and immediate

This is not abit issue just a minor annoyance. I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo. I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d. -- Alvin

Dear Patrice, I have noticed that you are referencing to the Stahnma repository for Spacewalk Client Tools. These are quite old and I would suggest to use the tools from: http://spacewalk.redhat.com/yum instead. Mr. Suchy already pushed some of the packages to Fedora/EPEL so they might be available there, soon. Besides that the Spacewalk Team is thinking about a split between client/server on

The subscription-manager dnf plugin is disabled by default as part of our debranding in both CentOS Linux and CentOS Stream. c8: https://git.centos.org/rpms/subscription-manager/blob/580aca8629536c64577e6a443b9349ecb629cc17/f/SPECS/subscription-manager.spec#_850 c8s:

Do we know if dovecot is vulnerable to the heartbleed SSL problem? I'm running dovecot-2.0.9 and openssl-1.01, the latter being intrinsically vulnerable. An on-line tool says that my machine is not affected on port 993 but it would be nice to know for sure if we were vulnerable for a while. (Naturally I've blocked it anyway!). Thanks John