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 <[email protected]>
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 <[email protected]>
> 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 way....and 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 <[email protected]>
> 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 [email protected].
> > To post to this group, send email to [email protected].
> > 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
> file:/etc/pki/katello/private/katello-default-ca.pwd' returned 1: unable
> to load Private Key
> > [ERROR 2017-02-13 12:47:40 main] 139660402321312:error:06065064:digital
> envelope routines:EVP_DecryptFinal_ex:bad decrypt:evp_enc.c:604:
> > [ERROR 2017-02-13 12:47:40 main] 139660402321312:error:0906A065:PEM
> routines:PEM_do_header:bad decrypt:pem_lib.c:483:
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util/execution.rb:232:in `execute'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/provider/command.rb:23:in `execute'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/provider.rb:221:in `block in has_command'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/provider.rb:422:in `block in
> create_class_and_instance_method'
> > [ERROR 2017-02-13 12:47:40 main] /usr/share/katello-installer-
> base/modules/certs/lib/puppet/provider/privkey/katello_ssl_tool.rb:11:in
> `expected_content'
> > [ERROR 2017-02-13 12:47:40 main] /usr/share/katello-installer-
> base/modules/certs/lib/puppet/provider/katello_ssl_tool.rb:178:in
> `exists?'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/type.rb:1070:in `retrieve'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/type.rb:1098:in `retrieve_resource'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction/resource_harness.rb:300:in
> `from_resource'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:230:in `apply'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:246:in `eval_resource'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:163:in `call'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:163:in `block (2 levels) in
> evaluate'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util.rb:386:in `block in thinmark'
> > [ERROR 2017-02-13 12:47:40 main] 
> > /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in
> `realtime'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util.rb:385:in `thinmark'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:163:in `block in evaluate'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/transaction/report.rb:142:in
> `as_logging_destination'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark'
> > [ERROR 2017-02-13 12:47:40 main] 
> > /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in
> `realtime'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util.rb:222:in `benchmark'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/context.rb:65:in `override'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet.rb:293:in `override'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/configurer.rb:195:in `run'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/context.rb:65:in `override'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet.rb:293:in `override'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application/apply.rb:225:in `main'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application.rb:344:in `block in run'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util.rb:541:in `exit_on_fail'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/application.rb:344:in `run'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/lib/
> ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
> > [ERROR 2017-02-13 12:47:40 main] /opt/puppetlabs/puppet/bin/puppet:5:in
> `<main>'
>
>
> --
> Daniel Lobato Garcia
>
> @dLobatog
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> Keybase: https://keybase.io/elobato
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to