Plugins » Katello

Eric Helms wrote:

Hi Johannes,

In order for a new package to make it's way into a lifecycle environment, you need to publish a new version of the content view the systems are subscribed to and then promote that content view to the target lifecycle environment.

If this resolves your issue please update the issue or comment back for us.

So every time, upstream (e.g. CentOS) does an update for a rpm, I need to do a new promote? This sounds very very wrong, and this wasn't the behavior in the past.

After publishing a new version of the content view and promoting it to the environments, I get the updated packages via yum on the subscribed machines. But I still don't see any updates for the content hosts in the web interface.

And it still sounds wrong to me, that I have to check my products all time for possible updates and than publishing/promoting a new version of the content view. Package updates should be available to the clients automatically after repo-sync.

Hi,

This behavior is intentional and expected. The purpose of a Content View is to provide a snapshot that you can harden, test, and push to your production environments. The intent is for content to NOT be available immediately. If you want updates available immediately to all systems, simply register them to the "Library" (Default Organization View). This is where content lands immediately upon sync. Alternatively use a continuous integration system such as jenkins to auto-publish and promote.

As for your second issue, "But I still don't see any updates for the content hosts in the web interface", can you explain a bit more about this? Which page are you looking at? Do you have 'katello-agent' or 'katello-host-tools' installed on the clients?

1. I can't reopen

2. I disagree about the behaviour. A content view should not be a snapshot of the installed system. It should be a snapshot of installed packages. As soon as updates for the package are available, I want them available to subscribed systems. I don't want to check every day, if there are security updates for installed packages for all my systems. Installed packages should get updates without an new version of the content view. I'm very sure this behaviour was different with previous katello versions.

3. Subscribing to the library doesn't work either. Tested with one system, and I still don't see the updates with 'yum upgrade'.