Re: [foreman-users] katello 3.3/foreman 1.14

2017-05-30 Thread Eric D Helms 
The service you are looking for is when you installed katello-agent. This
package includes utilities that upload the hosts package profile and
enabled repositories to Katello which allow errata to be calculated.

Eric

On Tue, May 30, 2017 at 6:46 PM, Edward Clay 
wrote:

> Can anyone tell me what software/agent/code is used to to inform
> katello/foreman that a system is either up to date or needs patches (aka
> erratas that apply to host) and what executes it?  From what I've come up
> with thus far, I perform the following task on a host and then everything
> is good.  But this is because puppet agent does a puppet run every 35'is
> minutes.  At least that's what my understanding is.
>
> 1. So first I create a host in foreman with the specifics/details needed
> to define a specific host.
>
> 2. On a existing system I run these task.  Rough draft of the steps I
> follow to set up an existing host.
>
> -- install subscription manager
> wget https://copr.fedoraproject.org/coprs/dgoodwin/
> subscription-manager/repo/epel-6/dgoodwin-subscription-manager-epel-6.repo
> -O /etc/yum.repos.d/dgoodwin-subscription-manager-epel-6.repo
> -- install katello client
> yum install -y http://fedorapeople.org/groups/katello/releases/yum/3.
> 2/client/el6/x86_64/katello-client-repos-latest.rpm
> yum -y install katello-agent
> wget --no-check-certificate https://foreman.domain.com/
> pub/katello-ca-consumer-latest.noarch.rpm
> rpm -ihv ./katello-ca-consumer-latest.noarch.rpm
> subscription-manager register --org="myOrg" --activationkey="COS6"
>
> -- Install puppet
> rpm -ihv https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
> yum -y install puppet
> add the following two lines just under [main]
> server = foreman.domain.com
> environment = production
> --   puppet agent -t
> --   service puppet start
> --   chkconfig puppet on
>
> So after doing these steps i'm able to login to foreman and see weather or
> not a system has outstanding erratas that need to be applied and I can
> apply them.
>
> --
> 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.
>



-- 
Eric D. Helms
Red Hat Engineering

-- 
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] Katello 3.4 (Oud Bruin) Released!

2017-05-30 Thread Evgeni Golov 
On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote:
> On 30 May 2017 at 11:40, Lachlan Musicman  wrote:
> 
> > Great, thanks.
> >
> > I am seeing another issue:
> >
> >  - yum clean all, all good
> >  - yum upgrade doesn't recognise new repos. If I look into
> > /etc/yum.repos.d/redhat.repo and the new products aren't listed in that
> > file.
> >
> > In order to get it to work, traditionally I've then performed:
> >
> > subscription-manager identity
> > subscription-manager unsubscribe
> > subscription-manager register --org="ACMI" --activationkey="Utility
> > Server"
> 
> I have discovered that my traditional method was finally deprecated and it
> didn't work.
> 
> But I also found that the slightly easier work around works:
> 
> subscription-manager repos
> 
> For whatever reason, that refreshes the redhat.repo.

So would "subscription-manager refresh".
When you change repos, your subscription changes, but it is not pulled
in on every yum invocation.

You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
every aspect is properly updated [1].

Also, I would suggest against using sub-man unregister && sub-man
register as a cluebat workaround. The subscription certificate is also
used for katello-agent, and if you don't restart it after doing the
sub-man dance, you end up without the ability to apply errata via
katello-agent.

Cheers
Evgeni

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1439645

-- 
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander

-- 
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] foreman-installer fails with postgresql-9.4

2017-05-30 Thread Evgeni Golov 
Hi,

On Tue, May 30, 2017 at 05:10:27AM -0700, mc14...@bristol.ac.uk wrote:
> I'm trying to setup puppet/foreman. 
> 
> postgresql94-server

Do I guess right this is from yum.postgresql.org?

> May 30 12:59:33  systemd[1]: postgresql.service lacks both ExecStart= and 
> ExecStop= setting. Refusing.
> May 30 12:59:33  systemd[1]: postgresql.service lacks both ExecStart= and 
> ExecStop= setting. Refusing.

If your packages are from yum.postgresql.org, then the service you need
is called postgresql-9.4, not postgresql. Not sure where
postgresql.service is comming from in your case then.

That said, I have no idea if we can tell the installer to use an
alternative PostgreSQL service name.

Regards
Evgeni

-- 
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander

-- 
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.4 (Oud Bruin) Released!

2017-05-30 Thread Evgeni Golov 
On Tue, May 30, 2017 at 08:30:49AM -0400, Eric D Helms wrote:
> Duncan,
> 
> Can you point me to which website page/link you are meaning?

I think this should cover it:
 https://github.com/theforeman/theforeman.org/pull/884

-- 
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric 
Shander

-- 
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.4 (Oud Bruin) Released!

2017-05-30 Thread Eric D Helms 
Nah, someone put in a quick PR fix thanks to your report!

On May 30, 2017 10:05 AM, "Duncan Innes"  wrote:

> They've changed now.  Might I have been hitting a cache?
>
> On Tuesday, 30 May 2017 13:30:53 UTC+1, Eric Helms wrote:
>>
>> Duncan,
>>
>> Can you point me to which website page/link you are meaning?
>>
>> On Tue, May 30, 2017 at 8:20 AM, Duncan Innes  wrote:
>>
>>> The install docs are still referencing 3.3 as the latest stable versions
>>> and referring to 3.4 as 3.4-RC.
>>>
>>>
>>> On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:

 All,

 We are happy to announce the GA of Katello 3.4. Highlights of the
 release:

  * Better file repository content management
  * Advanced repository syncing options for recovery and repair
  * UI overhaul
  * Content view force republishing
  * Candlepin 2.0 support
  * Pulp 2.12.2

 Release Notes:
 https://theforeman.org/plugins/katello/3.4/release_notes/
 release_notes.html

 Installation:
 https://theforeman.org/plugins/katello/3.4/installation/index.html

 Upgrade:
 https://theforeman.org/plugins/katello/3.4/upgrade/index.html

 See the changelog for detailed feature issues and bug fixes:
 https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

 Bug reporting
 =
 If you come across a bug in your testing, please file it and note the
 version of Katello or Foreman that you're using in the report.

 http://projects.theforeman.org/projects/katello/issues/new

 --
 Eric D. Helms
 Red Hat Engineering

>>> --
>>> 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-user...@googlegroups.com.
>>> To post to this group, send email to forema...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>>
> --
> 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.
>

-- 
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] foreman-installer fails with postgresql-9.4

2017-05-30 Thread Michelle Crouch 
That worked! Now I've different errors. Thanks.

--
Kind regards

mc
​ 
On 30 May 2017 at 15:23, Michael Moll  wrote:

> Hi,
>
> On Tue, May 30, 2017 at 05:10:27AM -0700, mc14...@bristol.ac.uk wrote:
> > postgresql94-server
>
> Try to set the following in /etc/foreman-installer/custom-hiera.yaml:
>
> postgresql::globals::manage_package_repo: true
> postgresql::globals::version: '9.4'
>
> Regards
> --
> Michael Moll
>

-- 
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] foreman-installer fails with postgresql-9.4

2017-05-30 Thread Michael Moll 
Hi,

On Tue, May 30, 2017 at 05:10:27AM -0700, mc14...@bristol.ac.uk wrote:
> postgresql94-server

Try to set the following in /etc/foreman-installer/custom-hiera.yaml:

postgresql::globals::manage_package_repo: true
postgresql::globals::version: '9.4'

Regards
-- 
Michael Moll

-- 
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.4 (Oud Bruin) Released!

2017-05-30 Thread Duncan Innes 
They've changed now.  Might I have been hitting a cache?

On Tuesday, 30 May 2017 13:30:53 UTC+1, Eric Helms wrote:
>
> Duncan,
>
> Can you point me to which website page/link you are meaning?
>
> On Tue, May 30, 2017 at 8:20 AM, Duncan Innes  > wrote:
>
>> The install docs are still referencing 3.3 as the latest stable versions 
>> and referring to 3.4 as 3.4-RC.
>>
>>
>> On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:
>>>
>>> All,
>>>
>>> We are happy to announce the GA of Katello 3.4. Highlights of the 
>>> release:
>>>
>>>  * Better file repository content management
>>>  * Advanced repository syncing options for recovery and repair
>>>  * UI overhaul
>>>  * Content view force republishing
>>>  * Candlepin 2.0 support
>>>  * Pulp 2.12.2
>>>
>>> Release Notes:
>>>
>>> https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> Upgrade:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>> See the changelog for detailed feature issues and bug fixes:
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md 
>>>
>>> Bug reporting
>>> =
>>> If you come across a bug in your testing, please file it and note the
>>> version of Katello or Foreman that you're using in the report.
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>>> -- 
>>> Eric D. Helms
>>> Red Hat Engineering
>>>
>> -- 
>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>

-- 
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] foreman-installer fails with postgresql-9.4

2017-05-30 Thread mc14983 
I'm trying to setup puppet/foreman. 

puppetdb-4.4.0
puppetserver-2.7.2
puppet-agent-1.10.1
postgresql94-server

 Systemd start for postgresql failed!
journalctl log for postgresql:
-- Logs begin at Sun 2017-05-28 21:56:15 BST, end at Tue 2017-05-30 
12:59:33 BST. --
May 30 12:59:33  systemd[1]: postgresql.service lacks both ExecStart= and 
ExecStop= setting. Refusing.
May 30 12:59:33  systemd[1]: postgresql.service lacks both ExecStart= and 
ExecStop= setting. Refusing.

/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:166:in
 
`rescue in start'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:163:in
 
`start'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:103:in 
`block (3 levels) in '
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:487:in `set'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:561:in `sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:114:in 
`sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in
 
`sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:134:in
 
`sync_if_needed'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:80:in
 
`perform_changes'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in
 
`evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:230:in 
`apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:246:in 
`eval_resource'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in 
`call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in 
`block (2 levels) in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:387:in `block in 
thinmark'
/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:386:in `thinmark'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in 
`block in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in
 
`traverse'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in 
`evaluate'
/usr/share/gems/gems/kafo-2.0.0/modules/kafo_configure/lib/puppet/parser/functions/add_progress.rb:30:in
 
`evaluate_with_trigger'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in 
`block in apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in 
`with_destination'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:142:in 
`as_logging_destination'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in 
`apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in 
`block in apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:224:in `block in 
benchmark'
/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in 
`benchmark'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in 
`apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in 
`run_internal'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in 
`block in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:350:in 
`apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in 
`block in main'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:in 
`main'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in 
`run_command'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in 
`block in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:542:in 
`exit_on_fail'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in 
`execute'
/opt/puppetlabs/puppet/bin/puppet:5:in `'
 /Stage[main]/Postgresql::Server::Service/Service[postgresqld]/ensure: 
change from stopped to running failed: Systemd start for postgresql failed!
journalctl log for postgresql:
-- Logs begin at Sun 2017-05-28 21:56:15 BST, end at Tue 2017-05-30 
12:59:33 BST. --
May 30 12:59:33  systemd[1]: postgresql.service lacks both ExecStart= and 
ExecStop= setting.