Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-17 Thread Lachlan Musicman 
It was the first thing I did after sending that email.

http://projects.theforeman.org/issues/18548

Let me know if you need any more information.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 18 February 2017 at 13:44, Eric D Helms  wrote:

> Could you please file a bug report with this information including your
> fix or add it to an existing report so that we can look at getting this
> fixed in the upcoming 3.3 release?
>
> Thanks
> Eric
>
>
> On Feb 16, 2017 11:58 PM, "Lachlan Musicman"  wrote:
>
> GOT IT.
>
> GADDAM.
>
> Edited
>
> /usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb
>
> commented out lines 21 and 22:
>
>   success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
> /etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
>   success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
> /opt/puppetlabs/puppet/cache/') if File.directory?('/var/lib/pupp
> et/foreman_cache_data')
>
> did a diff on the two folders in both, made sure they were matching.
>
> Ran foreman-installer --upgrade-puppet and it worked.
>
> Un commented to two lines,  ran Klass's 18131 bug solution after it, and
> all worked fine.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 14:54, Lachlan Musicman  wrote:
>
>> Daniel,
>>
>> running the instructions as per the puppet upgrade page failed again.
>>
>> On issue we kept running into was this, from
>> /var/log/foreman-installer/katello.log
>>
>> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
>> ‘/etc/puppetlabs/puppet/ssl’: File exists
>> [ERROR 2017-02-17 13:44:48 main] mv: cannot move
>> ‘/var/lib/puppet/foreman_cache_data’ to 
>> ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’:
>> File exists
>> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check
>> logs for more information.
>>
>> If you could point me to the log file that this message is talking about,
>> I'd appreciate that. Note that physically removing the offending files
>> doesn't seem to work - obviously there is some part of the
>> --foreman-installer --update-puppet execution that  recreates them
>>
>> Moving onto the next page, we start to do the whole thing by hand, as per
>> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
>> ng_from_Puppet_3_to_4
>>
>> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time
>> we did a grep on the whole of /etc/httpd/conf.d - there is no mention of
>> /var/lib/puppet/ssl in there at all
>>
>>
>> Moving onto Step 2, I ran the instructions with the changes you suggested
>> - adding --forman to some of the command line options.
>>
>> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>>
>> See: 'foreman-installer --help'
>>
>> So I look at the help:
>>
>> # foreman-installer --help | grep implementation
>> --capsule-puppet-server-implementation  Puppet master
>> implementation, either "master" (traditional
>>
>> And then if I do a grep on reset, none of these commands exist?
>>
>> I tried noop with capsule-puppet-server-implementation=puppetserver with
>> both --foreman-reset-puppet-X (as per your recommendation) and
>> --reset-foreman-puppet-X (format in line with other options) and neither
>> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>>
>>
>> Any other pointers would be appreciated.
>>
>> cheers
>> L.
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 17 February 2017 at 11:18, Lachlan Musicman  wrote:
>>
>>> Great - thanks all. VM snapshot from last week has been restored. We
>>> will try again now.
>>>
>>> cheers
>>> L.
>>>
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>> On 16 February 2017 at 22:06, Daniel Lobato Garcia 
>>> wrote:
>>>
 On 02/13, Lachlan Musicman wrote:
 > Ok, I've found the itemized puppet upgrade instructions that are here:
 >
 > http://projects.theforeman.org/projects/foreman/wiki/
 > Upgrading_from_Puppet_3_to_4
 >
 > and the place where the doc'd process fails. I start there.
 >
 > When I get to Step 1b. Environments, SSL and Apache; part 5 states
 "Update
 > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
 > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
 > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
 >
 > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference
 to
 > *either* reference?
 >
 > Skip it.
 >
 > Go to next step, figuring we have little if any manual
 customisations, I do
 > step 2 and the first run give teh

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-17 Thread Eric D Helms 
Could you please file a bug report with this information including your fix
or add it to an existing report so that we can look at getting this fixed
in the upcoming 3.3 release?

Thanks
Eric

On Feb 16, 2017 11:58 PM, "Lachlan Musicman"  wrote:

GOT IT.

GADDAM.

Edited

/usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb

commented out lines 21 and 22:

  success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
/etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
  success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
/opt/puppetlabs/puppet/cache/') if File.directory?('/var/lib/
puppet/foreman_cache_data')

did a diff on the two folders in both, made sure they were matching.

Ran foreman-installer --upgrade-puppet and it worked.

Un commented to two lines,  ran Klass's 18131 bug solution after it, and
all worked fine.

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 17 February 2017 at 14:54, Lachlan Musicman  wrote:

> Daniel,
>
> running the instructions as per the puppet upgrade page failed again.
>
> On issue we kept running into was this, from /var/log/foreman-installer/kat
> ello.log
>
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
> ‘/etc/puppetlabs/puppet/ssl’: File exists
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move
> ‘/var/lib/puppet/foreman_cache_data’ to 
> ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’:
> File exists
> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check logs
> for more information.
>
> If you could point me to the log file that this message is talking about,
> I'd appreciate that. Note that physically removing the offending files
> doesn't seem to work - obviously there is some part of the
> --foreman-installer --update-puppet execution that  recreates them
>
> Moving onto the next page, we start to do the whole thing by hand, as per
> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
> ng_from_Puppet_3_to_4
>
> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time we
> did a grep on the whole of /etc/httpd/conf.d - there is no mention of
> /var/lib/puppet/ssl in there at all
>
>
> Moving onto Step 2, I ran the instructions with the changes you suggested
> - adding --forman to some of the command line options.
>
> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>
> See: 'foreman-installer --help'
>
> So I look at the help:
>
> # foreman-installer --help | grep implementation
> --capsule-puppet-server-implementation  Puppet master implementation,
> either "master" (traditional
>
> And then if I do a grep on reset, none of these commands exist?
>
> I tried noop with capsule-puppet-server-implementation=puppetserver with
> both --foreman-reset-puppet-X (as per your recommendation) and
> --reset-foreman-puppet-X (format in line with other options) and neither
> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>
>
> Any other pointers would be appreciated.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 11:18, Lachlan Musicman  wrote:
>
>> Great - thanks all. VM snapshot from last week has been restored. We will
>> try again now.
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 16 February 2017 at 22:06, Daniel Lobato Garcia 
>> wrote:
>>
>>> On 02/13, Lachlan Musicman wrote:
>>> > Ok, I've found the itemized puppet upgrade instructions that are here:
>>> >
>>> > http://projects.theforeman.org/projects/foreman/wiki/
>>> > Upgrading_from_Puppet_3_to_4
>>> >
>>> > and the place where the doc'd process fails. I start there.
>>> >
>>> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
>>> "Update
>>> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
>>> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
>>> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>>> >
>>> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
>>> > *either* reference?
>>> >
>>> > Skip it.
>>> >
>>> > Go to next step, figuring we have little if any manual customisations,
>>> I do
>>> > step 2 and the first run give teh error
>>>
>>> I think all of these flags would be required and by removing them is why
>>> you see all of the errors. In order to use them, I think you can by
>>> appending --foreman to them, like:
>>>
>>>--foreman-puppet-server-implementation
>>>--foreman-reset-puppet-autosign
>>>etc...
>>>
>>> >
>>> > ERROR: Unrecognised option '--puppet-server-implementation'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR: Unrecognised option '--reset-puppet-autosign'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR:

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-16 Thread Lachlan Musicman 
GOT IT.

GADDAM.

Edited

/usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb

commented out lines 21 and 22:

  success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
/etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
  success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
/opt/puppetlabs/puppet/cache/') if
File.directory?('/var/lib/puppet/foreman_cache_data')

did a diff on the two folders in both, made sure they were matching.

Ran foreman-installer --upgrade-puppet and it worked.

Un commented to two lines,  ran Klass's 18131 bug solution after it, and
all worked fine.

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 17 February 2017 at 14:54, Lachlan Musicman  wrote:

> Daniel,
>
> running the instructions as per the puppet upgrade page failed again.
>
> On issue we kept running into was this, from /var/log/foreman-installer/
> katello.log
>
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
> ‘/etc/puppetlabs/puppet/ssl’: File exists
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move 
> ‘/var/lib/puppet/foreman_cache_data’
> to ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’: File exists
> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check logs
> for more information.
>
> If you could point me to the log file that this message is talking about,
> I'd appreciate that. Note that physically removing the offending files
> doesn't seem to work - obviously there is some part of the
> --foreman-installer --update-puppet execution that  recreates them
>
> Moving onto the next page, we start to do the whole thing by hand, as per
> http://projects.theforeman.org/projects/foreman/wiki/
> Upgrading_from_Puppet_3_to_4
>
> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time we
> did a grep on the whole of /etc/httpd/conf.d - there is no mention of
> /var/lib/puppet/ssl in there at all
>
>
> Moving onto Step 2, I ran the instructions with the changes you suggested
> - adding --forman to some of the command line options.
>
> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>
> See: 'foreman-installer --help'
>
> So I look at the help:
>
> # foreman-installer --help | grep implementation
> --capsule-puppet-server-implementation  Puppet master implementation,
> either "master" (traditional
>
> And then if I do a grep on reset, none of these commands exist?
>
> I tried noop with capsule-puppet-server-implementation=puppetserver with
> both --foreman-reset-puppet-X (as per your recommendation) and
> --reset-foreman-puppet-X (format in line with other options) and neither
> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>
>
> Any other pointers would be appreciated.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 11:18, Lachlan Musicman  wrote:
>
>> Great - thanks all. VM snapshot from last week has been restored. We will
>> try again now.
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 16 February 2017 at 22:06, Daniel Lobato Garcia 
>> wrote:
>>
>>> On 02/13, Lachlan Musicman wrote:
>>> > Ok, I've found the itemized puppet upgrade instructions that are here:
>>> >
>>> > http://projects.theforeman.org/projects/foreman/wiki/
>>> > Upgrading_from_Puppet_3_to_4
>>> >
>>> > and the place where the doc'd process fails. I start there.
>>> >
>>> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
>>> "Update
>>> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
>>> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
>>> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>>> >
>>> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
>>> > *either* reference?
>>> >
>>> > Skip it.
>>> >
>>> > Go to next step, figuring we have little if any manual customisations,
>>> I do
>>> > step 2 and the first run give teh error
>>>
>>> I think all of these flags would be required and by removing them is why
>>> you see all of the errors. In order to use them, I think you can by
>>> appending --foreman to them, like:
>>>
>>>--foreman-puppet-server-implementation
>>>--foreman-reset-puppet-autosign
>>>etc...
>>>
>>> >
>>> > ERROR: Unrecognised option '--puppet-server-implementation'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR: Unrecognised option '--reset-puppet-autosign'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR: Unrecognised option '--reset-puppet-client-package'
>>> > (repeat for )...
>>> > ERROR: Unrecognised option '--reset-puppet-codedir'
>>> > ERROR: Unrecognised option '--reset-puppet-configtimeout'
>>> > ERROR: Unrecognised option '--reset-puppet-dir'
>>> >
>>> > At this

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-16 Thread Lachlan Musicman 
Great - thanks all. VM snapshot from last week has been restored. We will
try again now.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 16 February 2017 at 22:06, Daniel Lobato Garcia 
wrote:

> On 02/13, Lachlan Musicman wrote:
> > Ok, I've found the itemized puppet upgrade instructions that are here:
> >
> > http://projects.theforeman.org/projects/foreman/wiki/
> > Upgrading_from_Puppet_3_to_4
> >
> > and the place where the doc'd process fails. I start there.
> >
> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
> "Update
> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
> >
> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
> > *either* reference?
> >
> > Skip it.
> >
> > Go to next step, figuring we have little if any manual customisations, I
> do
> > step 2 and the first run give teh error
>
> I think all of these flags would be required and by removing them is why
> you see all of the errors. In order to use them, I think you can by
> appending --foreman to them, like:
>
>--foreman-puppet-server-implementation
>--foreman-reset-puppet-autosign
>etc...
>
> >
> > ERROR: Unrecognised option '--puppet-server-implementation'
> >
> > remove it, get
> >
> > ERROR: Unrecognised option '--reset-puppet-autosign'
> >
> > remove it, get
> >
> > ERROR: Unrecognised option '--reset-puppet-client-package'
> > (repeat for )...
> > ERROR: Unrecognised option '--reset-puppet-codedir'
> > ERROR: Unrecognised option '--reset-puppet-configtimeout'
> > ERROR: Unrecognised option '--reset-puppet-dir'
> >
> > At this point I remove all --reset-puppet directives and hope.
> >
> > There are errors. Oh, there it is, postgres isn't started but needs to be
> > started. The errors are now new errors, but the top error is the one that
> > we are warned about, so I run the command without the noop - I presume
> all
> > of these errors are related? See attached.
> >
> > cheers
> > L.
> >
> >
> > --
> > The most dangerous phrase in the language is, "We've always done it this
> > way."
> >
> > - Grace Hopper
> >
> > On 13 February 2017 at 11:28, Lachlan Musicman 
> wrote:
> >
> > > I don't understand what I've done wrong - I am literally following the
> > > rule book here, but it seems to trip at every step.
> > >
> > > I read the logs, and discovered that there were only three files it
> > > couldn't find because katello was stopped (this still amazes me - "stop
> > > katello, then make foreman-installer get data from katello"???!!?!?!
> who
> > > designed/wrote this?)
> > >
> > > the files were:
> > >
> > > java-1.8.0-something_something
> > > puppet-agent-1.9.0-something-something
> > > puppetserver-2.7.2-something_something
> > >
> > > So I found them on the file system and installed them successfully by
> hand.
> > >
> > > I then repeated the above process of katello-services stop and
> > > foreman-installer --upgrade-puppet
> > >
> > > Now I get a fail on:
> > >
> > > Upgrade Step: copy_data...
> > >
> > > mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’:
> > > File exists
> > >
> > > Upgrade step copy_data failed. Check logs for more information.
> > >
> > >
> > > So I moved those files out of the wayand tried again. Failed with
> the
> > > same message.
> > >
> > > Deleted the files, tried again - failed with the same message.
> > >
> > > Might I suggest that the puppet upgrade notes are not actually correct
> and
> > > that the foreman-installer --upgrade-puppet service needs a
> "--skip-broken"
> > > or "--skip-copy-data"
> > >
> > > Anyway - I guess my question now is do I even need to run the
> > > --upgrade-puppet?
> > >
> > > Cheers
> > > L.
> > >
> > >
> > >
> > >
> > >
> > > --
> > > The most dangerous phrase in the language is, "We've always done it
> this
> > > way."
> > >
> > > - Grace Hopper
> > >
> > > On 13 February 2017 at 10:19, Lachlan Musicman 
> wrote:
> > >
> > >> Hi,
> > >>
> > >> Self hosted installation.
> > >>
> > >> The upgrade foreman-installer --upgrade-puppet fails because it can't
> > >> find packages.
> > >>
> > >> Which would be because I've just turned off all services as asked to
> in
> > >> the instructions found here
> > >>
> > >> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
> > >>
> > >> under "in place migration".
> > >>
> > >>
> > >> Seems like a chicken and an egg problem - how do I solve this issue?
> > >>
> > >> cheers
> > >> L.
> > >> --
> > >> The most dangerous phrase in the language is, "We've always done it
> this
> > >> way."
> > >>
> > >> - Grace Hopper
> > >>
> > >
> > >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> > To unsubscribe from this

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-16 Thread Daniel Lobato Garcia 
On 02/13, Lachlan Musicman wrote:
> Ok, I've found the itemized puppet upgrade instructions that are here:
>
> http://projects.theforeman.org/projects/foreman/wiki/
> Upgrading_from_Puppet_3_to_4
>
> and the place where the doc'd process fails. I start there.
>
> When I get to Step 1b. Environments, SSL and Apache; part 5 states "Update
> SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
> /etc/apache2/sites-available/05-foreman-ssl.conf, changing
> /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>
> but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
> *either* reference?
>
> Skip it.
>
> Go to next step, figuring we have little if any manual customisations, I do
> step 2 and the first run give teh error

I think all of these flags would be required and by removing them is why
you see all of the errors. In order to use them, I think you can by
appending --foreman to them, like:

   --foreman-puppet-server-implementation
   --foreman-reset-puppet-autosign
   etc...

>
> ERROR: Unrecognised option '--puppet-server-implementation'
>
> remove it, get
>
> ERROR: Unrecognised option '--reset-puppet-autosign'
>
> remove it, get
>
> ERROR: Unrecognised option '--reset-puppet-client-package'
> (repeat for )...
> ERROR: Unrecognised option '--reset-puppet-codedir'
> ERROR: Unrecognised option '--reset-puppet-configtimeout'
> ERROR: Unrecognised option '--reset-puppet-dir'
>
> At this point I remove all --reset-puppet directives and hope.
>
> There are errors. Oh, there it is, postgres isn't started but needs to be
> started. The errors are now new errors, but the top error is the one that
> we are warned about, so I run the command without the noop - I presume all
> of these errors are related? See attached.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 13 February 2017 at 11:28, Lachlan Musicman  wrote:
>
> > I don't understand what I've done wrong - I am literally following the
> > rule book here, but it seems to trip at every step.
> >
> > I read the logs, and discovered that there were only three files it
> > couldn't find because katello was stopped (this still amazes me - "stop
> > katello, then make foreman-installer get data from katello"???!!?!?! who
> > designed/wrote this?)
> >
> > the files were:
> >
> > java-1.8.0-something_something
> > puppet-agent-1.9.0-something-something
> > puppetserver-2.7.2-something_something
> >
> > So I found them on the file system and installed them successfully by hand.
> >
> > I then repeated the above process of katello-services stop and
> > foreman-installer --upgrade-puppet
> >
> > Now I get a fail on:
> >
> > Upgrade Step: copy_data...
> >
> > mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’:
> > File exists
> >
> > Upgrade step copy_data failed. Check logs for more information.
> >
> >
> > So I moved those files out of the wayand tried again. Failed with the
> > same message.
> >
> > Deleted the files, tried again - failed with the same message.
> >
> > Might I suggest that the puppet upgrade notes are not actually correct and
> > that the foreman-installer --upgrade-puppet service needs a "--skip-broken"
> > or "--skip-copy-data"
> >
> > Anyway - I guess my question now is do I even need to run the
> > --upgrade-puppet?
> >
> > Cheers
> > L.
> >
> >
> >
> >
> >
> > --
> > The most dangerous phrase in the language is, "We've always done it this
> > way."
> >
> > - Grace Hopper
> >
> > On 13 February 2017 at 10:19, Lachlan Musicman  wrote:
> >
> >> Hi,
> >>
> >> Self hosted installation.
> >>
> >> The upgrade foreman-installer --upgrade-puppet fails because it can't
> >> find packages.
> >>
> >> Which would be because I've just turned off all services as asked to in
> >> the instructions found here
> >>
> >> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
> >>
> >> under "in place migration".
> >>
> >>
> >> Seems like a chicken and an egg problem - how do I solve this issue?
> >>
> >> cheers
> >> L.
> >> --
> >> The most dangerous phrase in the language is, "We've always done it this
> >> way."
> >>
> >> - Grace Hopper
> >>
> >
> >
>
> --
> 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.

> [ERROR 2017-02-13 12:47:40 main]  
> /Stage[main]/Certs/Privkey[/etc/pki/katello/private/katello-default-ca.key]: 
> Could not evaluate: Execution of '/usr/bin/openssl rsa -in 
> /root/ssl-build/katello-default-ca.key -out 
> /root/ssl-build/katello-default-ca.key.tmp -passin 
>

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-16 Thread Klaas Demter 
Hi,
'foreman-installer --upgrade-puppet' will take care of most of the things that 
are listed in foreman wiki. There are just some additional parameters that need 
to be changed.

For the workflow: I ran --upgrade-puppet and afterwards I ran foreman-installer 
again to reset answers to their "new" settings or change some that 
--upgrade-puppet didn't change. I'm not sure if my list is complete but it was 
sufficient for my foreman/katello usage.

My full workflow was something along these lines (including katello update from 
3.1 to 3.2)
#https://projects.theforeman.org/issues/17639
mkdir /var/lib/tftpboot/grub2
mkdir /var/lib/tftpboot/grub
chown -R foreman-proxy:foreman-proxy /var/lib/tftpboot
foreman-installer -v --scenario katello --upgrade
vim /usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb
# --> add puppet-agent-oauth or 
https://github.com/Katello/katello-installer/pull/467

vim /usr/share/katello-installer-base/modules/certs/manifests/candlepin.pp
# http://projects.theforeman.org/issues/18129

rm /usr/share/katello-installer-base/hooks/pre/29-remove_package_httpd_conf.rb 
/usr/share/katello-installer-base/hooks/post/29-create_package_httpd_conf.rb
# http://projects.theforeman.org/issues/18132

foreman-installer --upgrade-puppet

systemctl stop puppetserver
/usr/sbin/usermod -d /opt/puppetlabs/server/data/puppetserver puppet
systemctl start puppetserver

foreman-installer -v --scenario katello \
--reset-foreman-proxy-puppetdir \
--reset-foreman-proxy-puppetrun-cmd \
--reset-foreman-proxy-puppetca-cmd \
--reset-foreman-proxy-plugin-pulp-puppet-content-dir \
--reset-foreman-puppet-home \
--reset-foreman-puppet-ssldir \
--reset-foreman-proxy-puppet-ssl-ca \
--reset-foreman-proxy-puppet-ssl-cert \
--reset-foreman-proxy-puppet-ssl-key \
--foreman-proxy-puppetssh-command "/opt/puppetlabs/bin/puppet agent --onetime 
--no-usecacheonfailure --no-daemonize --no-splay" \
--foreman-proxy-ssldir /etc/puppetlabs/puppet/ssl

I use theforeman-puppet for my configuration. After the puppet4 upgrade I had 
to add those additional parameters for my foreman server:
server_foreman_ssl_ca: "/etc/puppetlabs/puppet/ssl/ssl_ca.pem"
server_foreman_ssl_cert: "/etc/puppetlabs/puppet/ssl/client_cert.pem"
server_foreman_ssl_key: "/etc/puppetlabs/puppet/ssl/client_key.pem"

For my puppet capsules I chose not to upgrade them, I rather reinstalled them. 
I did run into more issues there but thats because I run pulp/puppet on 
different capsules rather than both on one capsule:
http://projects.theforeman.org/issues/17605
http://projects.theforeman.org/issues/18185
http://projects.theforeman.org/issues/18182

The pulp capsules just work after I applied 
http://projects.theforeman.org/issues/17605
foreman-installer --scenario capsule --upgrade --capsule-certs-tar certs.tar 
--certs-update-all --certs-regenerate true --certs-deploy true

I think thats all :)


Greetings
Klaas Demter

ATIX - The Linux & Open Source Company
www.atix.de

- Ursprüngliche Mail -
Von: "Lachlan Musicman" <data...@gmail.com>
An: foreman-users@googlegroups.com
Gesendet: Donnerstag, 16. Februar 2017 03:54:31
Betreff: Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

Klaas,

Thank you for this, much appreciated. We have decided to revert back to
snapshot taken last week and try again - your notes will be very helpful.

One thing in particular that has us confused is 18131 "foreman-installer
--upgrade-puppet fails to set new paths for foreman-installer"

http://projects.theforeman.org/issues/18131

In particular a full workflow.

ie, after running

foreman-installer --upgrade-puppet

you ran the listed solution in your comment?

I read the details on the Foreman/Puppet upgrade page, which was
interesting for background:
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4
and it includes a similar, but not the same, step.

I presumed that the upgrade instructions listed on the Katello 3.2 page
would list any extra steps that might need to be taken.

I'll report back/take notes on how I go.

Cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 15 February 2017 at 19:41, Klaas Demter <dem...@atix.de> wrote:

> Hey,
> I've successfully upgraded to puppet4 on my katello. In the process I've
> fixed, reported and worked around several issues. Feel free to check the
> PRs/discussions of these tickets:
> http://projects.theforeman.org/issues/18123
> http://projects.theforeman.org/issues/18129
> http://projects.theforeman.org/issues/18131
> http://projects.theforeman.org/issues/18132
>
> After those workaround/fixes the upgrade katello 3.1.x to 3.2.3 worked for
> me including the puppet4 upgrade
>
>
> if you encounter different issues create a bugreport and maybe even try to
> fix it

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-15 Thread Lachlan Musicman 
Klaas,

Thank you for this, much appreciated. We have decided to revert back to
snapshot taken last week and try again - your notes will be very helpful.

One thing in particular that has us confused is 18131 "foreman-installer
--upgrade-puppet fails to set new paths for foreman-installer"

http://projects.theforeman.org/issues/18131

In particular a full workflow.

ie, after running

foreman-installer --upgrade-puppet

you ran the listed solution in your comment?

I read the details on the Foreman/Puppet upgrade page, which was
interesting for background:
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4
and it includes a similar, but not the same, step.

I presumed that the upgrade instructions listed on the Katello 3.2 page
would list any extra steps that might need to be taken.

I'll report back/take notes on how I go.

Cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 15 February 2017 at 19:41, Klaas Demter <dem...@atix.de> wrote:

> Hey,
> I've successfully upgraded to puppet4 on my katello. In the process I've
> fixed, reported and worked around several issues. Feel free to check the
> PRs/discussions of these tickets:
> http://projects.theforeman.org/issues/18123
> http://projects.theforeman.org/issues/18129
> http://projects.theforeman.org/issues/18131
> http://projects.theforeman.org/issues/18132
>
> After those workaround/fixes the upgrade katello 3.1.x to 3.2.3 worked for
> me including the puppet4 upgrade
>
>
> if you encounter different issues create a bugreport and maybe even try to
> fix it and create a pull request :)
>
> Greetings
> Klaas Demter
>
> ATIX - The Linux & Open Source Company
> www.atix.de
>
> - Ursprüngliche Mail -
> Von: "Mario Gamboa" <mario.gam...@gmail.com>
> An: "Foreman users" <foreman-users@googlegroups.com>
> Gesendet: Mittwoch, 15. Februar 2017 09:18:54
> Betreff: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails
>
> Any solution ?
>
> Same  issues here the thing that is amazing the katello and foreman team
> they are planning to no support anymore puppet 3 on 1.15 foreman but how we
> are going to upgrade our current puppet 3 to 4 is ridiculous
>
> --
> 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.
>

-- 
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: Puppet upgrade from 3.x to 4.x fails

2017-02-15 Thread Klaas Demter 
Hey,
I've successfully upgraded to puppet4 on my katello. In the process I've fixed, 
reported and worked around several issues. Feel free to check the 
PRs/discussions of these tickets:
http://projects.theforeman.org/issues/18123
http://projects.theforeman.org/issues/18129
http://projects.theforeman.org/issues/18131
http://projects.theforeman.org/issues/18132

After those workaround/fixes the upgrade katello 3.1.x to 3.2.3 worked for me 
including the puppet4 upgrade


if you encounter different issues create a bugreport and maybe even try to fix 
it and create a pull request :)

Greetings
Klaas Demter

ATIX - The Linux & Open Source Company
www.atix.de

- Ursprüngliche Mail -
Von: "Mario Gamboa" <mario.gam...@gmail.com>
An: "Foreman users" <foreman-users@googlegroups.com>
Gesendet: Mittwoch, 15. Februar 2017 09:18:54
Betreff: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

Any solution ?

Same  issues here the thing that is amazing the katello and foreman team 
they are planning to no support anymore puppet 3 on 1.15 foreman but how we 
are going to upgrade our current puppet 3 to 4 is ridiculous 

-- 
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.