Re: [foreman-users] Re: How do I re-create a previously deleted host that was auto-created via puppet?

[Greg Sutcliffe]

Taking each question separately:

1) You can just run Puppet again on your hosts, and they will be recreated
in the UI just as before. There's no difference to Foreman whether a host
has been around for 5 minutes or 5 months - when it sees a report from an
unknown host, it'll create an entry for it.

2) That's a valid usecase - but such hosts are usually created via the
report-in method as above. If you need to create them ahead of time, you
can either:

(a) put in fake provisioning data, Save, then Edit the host and click
Unmanage at the top right, which will remove the provisioning fields. This
button isn't available on the New Host page, unfortunately.
(b) use the CLI tool to create a host with unamanged=true in the call.

It's generally easier to use the check-in method though, as this ensures
the certname is set correctly in Foreman.

Hope that helps
Greg

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: How do I re-create a previously deleted host that was auto-created via puppet?

[otheus uibk]

To be clear: The Foreman does not allow me to manually create a host. Why 
not? Because it wants to provision a host. This is kind of stupid, and I 
dont understand why the foreman needs to act as both ENC *and* provisioner. 
These are related, but separate roles. It would be nice if I could somehow 
create a host without any kind of provisioning at all (because it already 
exists, and I just need to tell TheForeman about it)

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Katello 3.0.2 (Saison) Released

[Eric D Helms]

Can you run:

systemctl start httpd
journalctl -xn
On Jul 8, 2016 7:05 AM, "Edgars M."  wrote:

> Hi
>
> Here it is:
>
> sudo /bin/systemctl start  httpd.service
> Job for httpd.service failed because the control process exited with
> error code. See "systemctl status httpd.service" and "journalctl -xe" for
> details.
>
> sudo /bin/systemctl status httpd.service
> ● httpd.service - The Apache HTTP Server
>Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled;
> vendor preset: disabled)
>Active: failed (Result: exit-code) since Fri 2016-07-08 10:57:44 CEST;
> 6s ago
>  Docs: man:httpd(8)
>man:apachectl(8)
>   Process: 13510 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status
> =1/FAILURE)
>   Process: 13508 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=
> exited, status=1/FAILURE)
>  Main PID: 13508 (code=exited, status=1/FAILURE)
>
>
> Jul 08 10:57:44 katello.tld systemd[1]: Starting The Apache HTTP Server...
> Jul 08 10:57:44 katello.tld systemd[1]: httpd.service: main process exited
> , code=exited, status=1/FAILURE
> Jul 08 10:57:44 katello.tld kill[13510]: kill: cannot find process ""
> Jul 08 10:57:44 katello.tld systemd[1]: httpd.service: control process
> exited, code=exited status=1
> Jul 08 10:57:44 katello.tld systemd[1]: Failed to start The Apache HTTP
> Server.
> Jul 08 10:57:44 katello.tld systemd[1]: Unit httpd.service entered failed
> state.
> Jul 08 10:57:44 katello.tld systemd[1]: httpd.service failed.
>
> sudo cat /var/log/httpd/error_log
> [Fri Jul 08 10:48:00.407263 2016] [core:notice] [pid 13049] SELinux
> policy enabled; httpd running as context system_u:system_r:httpd_t:s0
> [Fri Jul 08 10:48:00.407385 2016] [mime_magic:error] [pid 13049] (2)No
> such file or directory: AH01515: mod_mime_magic: can't read magic file
> /etc/httpd/NEVER_EVER_USE
> [Fri Jul 08 10:48:00.480310 2016] [ssl:emerg] [pid 13049] AH02311: Fatal
> error initialising mod_ssl, exiting. See /var/log/httpd/crane_error_ssl.log
> for more information
> [Fri Jul 08 10:57:44.170768 2016] [core:notice] [pid 13508] SELinux policy
> enabled; httpd running as context system_u:system_r:httpd_t:s0
> [Fri Jul 08 10:57:44.170854 2016] [mime_magic:error] [pid 13508] (2)No
> such file or directory: AH01515: mod_mime_magic: can't read magic file /
> etc/httpd/NEVER_EVER_USE
> [Fri Jul 08 10:57:44.197505 2016] [ssl:emerg] [pid 13508] AH02311: Fatal
> error initialising mod_ssl, exiting. See /var/log/httpd/crane_error_ssl.log
> for more information
>
> sudo cat /var/log/httpd/crane_error_ssl.log
> [Fri Jul 08 10:48:00.480289 2016] [ssl:emerg] [pid 13049] AH01903: Failed
> to configure CA certificate chain!
> [Fri Jul 08 10:57:44.197492 2016] [ssl:emerg] [pid 13508] AH01903: Failed
> to configure CA certificate chain!
>
> sudo cat /etc/httpd/conf.d/03-crane.conf
> # 
> # Vhost template in module puppetlabs-apache
> # Managed by Puppet
> # 
>
>
> 
>   ServerName katello.tld
>
>
>   ## Vhost docroot
>   DocumentRoot "/usr/share/crane/"
>
>
>   ## Directories, there should at least be a declaration for
> /usr/share/crane/
>
>
>   
> Options Indexes FollowSymLinks MultiViews
> AllowOverride None
> Require all granted
>   
>
>
>   ## Logging
>   ErrorLog "/var/log/httpd/crane_error_ssl.log"
>   ServerSignature Off
>   CustomLog "/var/log/httpd/crane_access_ssl.log" combined
>
>
>   ## SSL directives
>   SSLEngine on
>   SSLCertificateFile  "/etc/pki/katello/certs/katello-apache.crt"
>   SSLCertificateKeyFile   "/etc/pki/katello/private/katello-apache.key"
>   SSLCertificateChainFile "/etc/pki/katello/certs/katello-default-ca.crt"
>   SSLCACertificatePath"/etc/pki/tls/certs"
>   SSLCACertificateFile"/etc/pki/katello/certs/katello-default-ca.crt"
>   SSLVerifyClient optional
>   SSLVerifyDepth  3
>   SSLOptions +StdEnvVars +ExportCertData +FakeBasicAuth
>
>
>   # SSL Proxy directives
>   SSLProxyEngine On
>   WSGIScriptAlias / "/usr/share/crane/crane.wsgi"
> 
>
>
>
>
> piektdiena, 2016. gada 8. jūlijs 12:58:40 UTC+2, Eric Helms rakstīja:
>>
>> What is the journal -xn output after you try to start httpd manually?
>> On Jul 8, 2016 5:12 AM, "Edgars M."  wrote:
>>
>>> No, there is nothing special about our certificates. No wildcard, no
>>> even SAN. 2048 bits.
>>>
>>> Why is Crane needed? Can I disable it? Can I disable everything related
>>> to Puppet as we don't need that functionality?
>>>
>>> I just tested it and it failed again, here is my full install command:
>>>
>>> sudo foreman-installer --scenario katello \
>>> --certs-server-cert="/etc/pki/tls/certs/katello.tld.crt" \
>>> --certs-server-cert-req="/etc/pki/tls/csr/katello.tld.csr" \
>>> --certs-server-key="/etc/pki/tls/private/katello.tld.key" \
>>> --certs-server-ca-cert="/etc/pki/tls/certs/CompanyInternalCA.crt" \
>>> --foreman-admin-email="n...@company.tld" \
>>> 

Re: [foreman-users] Repository priorities

[Marcin Trendota]

W dniu 07.07.2016 o 20:25, Eric D Helms pisze:

> There is no support for configuring this today; however, given the votes of
> that feature request we can take it into consideration for the 3.2 release.
> If you have use cases outside of setting it through the activation key as
> that particular issue suggests, please open new issues or add info to the
> issue.

Great! TBH i don't know my use case yet (:) - i want to migrate to
foreman/katello from plain puppet and this is blocker for me. Is there
any workaround? In worst case i'll try to get rid of RepoForge (which is
source of trouble).

> Eric

-- 
Over And Out
MoonWolf

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Katello 3.0.2 (Saison) Released

[Edgars M.]

No, there is nothing special about our certificates. No wildcard, no even 
SAN. 2048 bits.

Why is Crane needed? Can I disable it? Can I disable everything related to 
Puppet as we don't need that functionality?

I just tested it and it failed again, here is my full install command:

sudo foreman-installer --scenario katello \
--certs-server-cert="/etc/pki/tls/certs/katello.tld.crt" \
--certs-server-cert-req="/etc/pki/tls/csr/katello.tld.csr" \
--certs-server-key="/etc/pki/tls/private/katello.tld.key" \
--certs-server-ca-cert="/etc/pki/tls/certs/CompanyInternalCA.crt" \
--foreman-admin-email="n...@company.tld" \
--foreman-admin-first-name="Name" \
--foreman-admin-last-name="LastName" \
--foreman-admin-password="SomeCustomPassword" \
--foreman-initial-organization="Company" \
--katello-num-pulp-workers="24" \
--katello-proxy-url="http://corporate.proxy.tld; \
--katello-proxy-port="8080" \
--verbose


Errors:
[ERROR 2016-07-08 10:48:00 verbose]  Could not start Service[httpd]: 
Execution of 
'/usr/share/katello-installer-base/modules/service_wait/bin/service-wait 
start httpd' returned 1: Redirecting to /bin/systemctl start  httpd.service
[ INFO 2016-07-08 10:48:00 verbose] Job for httpd.service failed because 
the control process exited with error code. See "systemctl status 
httpd.service" and "journalctl -xe" for details.
[ERROR 2016-07-08 10:48:00 verbose]  /Stage[main]/Apache::Service/Service[
httpd]/ensure: change from stopped to running failed: Could not start 
Service[httpd]: Execution of 
'/usr/share/katello-installer-base/modules/service_wait/bin/service-wait 
start httpd' returned 1: Redirecting to /bin/systemctl start  httpd.service
[ERROR 2016-07-08 10:48:18 verbose]  /Stage[main]/Foreman::Database/Foreman
::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/
sbin/foreman-rake db:seed returned 1 instead of one of [0]
[ERROR 2016-07-08 10:48:18 verbose]  /Stage[main]/Foreman::Database/Foreman
::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed 
returned 1 instead of one of [0]
[ERROR 2016-07-08 10:49:15 verbose]  /Stage[main]/Foreman_proxy::Register/
Foreman_smartproxy[katello.tld]: Failed to call refresh: Proxy katello.tld 
cannot be registered (Could not load data from https://katello.tld
[ INFO 2016-07-08 10:49:15 verbose]  - is your server down?
[ INFO 2016-07-08 10:49:15 verbose]  - was rake apipie:cache run when using 
apipie cache? (typical production settings)): N/A
[ERROR 2016-07-08 10:49:15 verbose]  /Stage[main]/Foreman_proxy::Register/
Foreman_smartproxy[katello.tld]: Proxy katello.tld cannot be registered (
Could not load data from https://katello.tld
[ INFO 2016-07-08 10:49:15 verbose]  - is your server down?
[ INFO 2016-07-08 10:49:15 verbose]  - was rake apipie:cache run when using 
apipie cache? (typical production settings)): N/A
[ INFO 2016-07-08 10:49:15 verbose] /usr/share/ruby/vendor_ruby/puppet/util/
errors.rb:106:in `fail'
[ INFO 2016-07-08 10:49:19 verbose] Executing hooks in group post
  Something went wrong! Check the log for ERROR-level output

sudo cat /var/log/httpd/crane_error_ssl.log
[Fri Jul 08 10:48:00.480289 2016] [ssl:emerg] [pid 13049] AH01903: Failed 
to configure CA certificate chain!
[Fri Jul 08 10:57:44.197492 2016] [ssl:emerg] [pid 13508] AH01903: Failed 
to configure CA certificate chain!

Edgars

ceturtdiena, 2016. gada 7. jūlijs 20:26:43 UTC+2, Eric Helms rakstīja:
>
> Edgars,
>
> I tested this scenario today and could not duplicate your results. Is 
> there anything special about your custom certificates? Wildcard? Attributes 
> special to them? This is my test scenario:
>
> https://github.com/Katello/forklift/pull/247/files
>
> On Thu, Jul 7, 2016 at 8:07 AM, Eric D Helms  > wrote:
>
>> Edgars,
>>
>> I will test this today and report back to you.
>>
>>
>> Eric
>>
>> On Thu, Jul 7, 2016 at 5:53 AM, Edgars M. > > wrote:
>>
>>> Hi
>>>
>>> I still cannot install new Katello because of this issue: 
>>> http://projects.theforeman.org/issues/15507
>>>
>>> It fails every time.. Does anyone know workaround?
>>>
>>> Edgars
>>>
>>>
>>> trešdiena, 2016. gada 6. jūlijs 22:51:48 UTC+2, Eric Helms rakstīja:

 Katello 3.0.2 has been released to supply bug fixes and major upgrade 
 issues found by some awesome users. Please see the changelog for more 
 information (
 https://github.com/Katello/katello/blob/KATELLO-3.0/CHANGELOG.md). 

 Installation 
  

 For installation, please see the instructions at: 

Server: http://www.katello.org/docs/3.0/installation/index.html 
  
Capsule: http://www.katello.org/docs/3.0/installation/capsule.html 
  

 Bug reporting 
 = 
 If you come across a bug in your testing, please file it and note the 
 version of Katello 

[foreman-users] Katello 3 Installation failed cause of dependencies

['Denis Müller' via Foreman users]

Hi,

i was trying to install "katello.noarch 0:3.0.0-9.el7" but no luck here. 
Installation can not resolve all dependencies, is it a bug? See install.log.
I would appreciate any help.

Best regards,

Denis

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Geladene Plugins: fastestmirror, package_upload, priorities, product-id, search-
: disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
 * epel: mirrors.n-ix.net
72 packages excluded due to repository priority protections
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket katello.noarch 0:3.0.0-9.el7 markiert, um installiert zu werden
--> Abhängigkeit katello-common = 3.0.0-9.el7 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit java-openjdk < 1:1.8.0.45 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit mongodb-server >= 2.4 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit mongodb >= 2.4 wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit java-openjdk >= 1:1.7.0 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit createrepo >= 0.9.9-18.el7 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit squid wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit qpid-dispatch-router wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit qpid-cpp-server-linearstore wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit qpid-cpp-client-devel wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit python-pulp-streamer wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit python-gofer-qpid wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit python-crane wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-server wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-selinux wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-rpm-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-puppet-tools wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-puppet-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-katello wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-docker-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql-server wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit mod_xsendfile wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit lsof wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit foreman-installer-katello wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit cyrus-sasl-plain wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit candlepin-selinux wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit candlepin wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Transaktionsprüfung wird ausgeführt
---> Paket candlepin.noarch 0:0.9.54.6-1.el7 markiert, um installiert zu werden
--> Abhängigkeit liquibase >= 2.0.5 wird für Paket 
candlepin-0.9.54.6-1.el7.noarch verarbeitet
--> Abhängigkeit tomcat wird für Paket candlepin-0.9.54.6-1.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql-jdbc wird für Paket candlepin-0.9.54.6-1.el7.noarch 
verarbeitet
---> Paket candlepin-selinux.noarch 0:0.9.54.6-1.el7 markiert, um installiert 
zu werden
---> Paket createrepo.noarch 0:0.9.9-25.el7_2 markiert, um installiert zu werden
--> Abhängigkeit python-deltarpm wird für Paket 
createrepo-0.9.9-25.el7_2.noarch verarbeitet
--> Abhängigkeit deltarpm wird für Paket createrepo-0.9.9-25.el7_2.noarch 
verarbeitet
---> Paket cyrus-sasl-plain.x86_64 0:2.1.26-20.el7_2 markiert, um installiert 
zu werden
---> Paket foreman-installer-katello.noarch 0:3.0.2-1.el7 markiert, um 
installiert zu werden
--> Abhängigkeit katello-installer-base = 3.0.2-1.el7 wird für Paket 
foreman-installer-katello-3.0.2-1.el7.noarch verarbeitet
--> Abhängigkeit katello-service >= 3.0.0 wird für Paket 
foreman-installer-katello-3.0.2-1.el7.noarch verarbeitet
---> Paket java-1.7.0-openjdk.x86_64 1:1.7.0.101-2.6.6.1.el7_2 markiert, um 
installiert zu werden
--> Abhängigkeit java-1.7.0-openjdk-headless = 1:1.7.0.101-2.6.6.1.el7_2 wird 
für Paket 1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64 verarbeitet
--> 

Re: [foreman-users] [Katello 3.0] foreman-installer --help fails ("no documentation found for manifest")

[Marvin Beckers]

I have created an issue, available at 
http://projects.theforeman.org/issues/15619 - Thank you very much for 
looking into this!


Am Donnerstag, 7. Juli 2016 20:28:57 UTC+2 schrieb Eric Helms:
>
> Please report as an issue with your traceback so that the right developers 
> can take a look.
>
> On Wed, Jul 6, 2016 at 2:37 AM, Marvin Beckers  > wrote:
>
>> Hello everybody,
>>
>> recently I've been trying to apply some changes to our Katello 3.0 setup 
>> through foreman-installer and noticed it fails to run. The last time it 
>> used to work was June 27th (according to 
>> /var/log/foreman-installer/foreman.log) when I updated Katello related 
>> packages and run `foreman-installer --scenario=katello --upgrade` 
>> afterwards to make sure everything was properly updated. This was the yum 
>> update on June 27th:
>>
>> Packages Altered:
>> Updated NetworkManager-1:1.0.6-29.el7_2.x86_64   @updates
>> Update 1:1.0.6-30.el7_2.x86_64   @updates
>> Updated NetworkManager-libnm-1:1.0.6-29.el7_2.x86_64 @updates
>> Update   1:1.0.6-30.el7_2.x86_64 @updates
>> Updated NetworkManager-team-1:1.0.6-29.el7_2.x86_64  @updates
>> Update  1:1.0.6-30.el7_2.x86_64  @updates
>> Updated NetworkManager-tui-1:1.0.6-29.el7_2.x86_64   @updates
>> Update 1:1.0.6-30.el7_2.x86_64   @updates
>> Updated device-mapper-7:1.02.107-5.el7_2.2.x86_64@updates
>> Update7:1.02.107-5.el7_2.4.x86_64@updates
>> Updated device-mapper-event-7:1.02.107-5.el7_2.2.x86_64  @updates
>> Update  7:1.02.107-5.el7_2.4.x86_64  @updates
>> Updated device-mapper-event-libs-7:1.02.107-5.el7_2.2.x86_64 @updates
>> Update   7:1.02.107-5.el7_2.4.x86_64 @updates
>> Updated device-mapper-libs-7:1.02.107-5.el7_2.2.x86_64   @updates
>> Update 7:1.02.107-5.el7_2.4.x86_64   @updates
>> Updated dracut-033-360.el7_2.x86_64  @updates
>> Update 033-360.el7_2.1.x86_64@updates
>> Updated dracut-config-rescue-033-360.el7_2.x86_64@updates
>> Update   033-360.el7_2.1.x86_64  @updates
>> Updated dracut-network-033-360.el7_2.x86_64  @updates
>> Update 033-360.el7_2.1.x86_64@updates
>> Updated epel-release-7-6.noarch  @
>> /epel-release-latest-7.noarch
>> Update   7-7.noarch  @epel
>> Updated foreman-1.11.2-1.el7.noarch  @foreman
>> Update  1.11.3-1.el7.noarch  @foreman
>> Updated foreman-compute-1.11.2-1.el7.noarch  @foreman
>> Update  1.11.3-1.el7.noarch  @foreman
>> Updated foreman-debug-1.11.2-1.el7.noarch@foreman
>> Update1.11.3-1.el7.noarch@foreman
>> Updated foreman-installer-1:1.11.2-1.el7.noarch  @foreman
>> Update1:1.11.3-1.el7.noarch  @foreman
>> Updated foreman-installer-katello-3.0.0-10.rc8.el7.noarch@katello
>> Update3.0.2-1.el7.noarch @katello
>> Updated foreman-postgresql-1.11.2-1.el7.noarch   @foreman
>> Update 1.11.3-1.el7.noarch   @foreman
>> Updated foreman-proxy-1.11.2-1.el7.noarch@foreman
>> Update1.11.3-1.el7.noarch@foreman
>> Updated foreman-release-1.11.2-1.el7.noarch  @/
>> foreman-release
>> Update  1.11.3-1.el7.noarch  @foreman
>> Updated foreman-selinux-1.11.2-1.el7.noarch  @foreman
>> Update  1.11.3-1.el7.noarch  @foreman
>> Updated foreman-vmware-1.11.2-1.el7.noarch   @foreman
>> Update 1.11.3-1.el7.noarch   @foreman
>> Updated iproute-3.10.0-54.el7.x86_64 
>> @anaconda
>> Update  3.10.0-54.el7_2.1.x86_64 @updates
>> Updated katello-3.0.0-8.rc8.el7.noarch   @katello
>> Update  3.0.0-9.el7.noarch   @katello
>> Updated katello-common-3.0.0-8.rc8.el7.noarch@katello
>> Update 3.0.0-9.el7.noarch@katello
>> Updated katello-debug-3.0.0-8.rc8.el7.noarch @katello
>> Update3.0.0-9.el7.noarch @katello
>> Updated katello-installer-base-3.0.0-10.rc8.el7.noarch   @katello
>>