Hmmm.
Certs continued to fail. I discovered that Candlepin wasn't starting. A
search took me to the Katello upgrade page.
So I ran foreman-installer --service katello --upgrade again.
It fails with:
----------
Upgrade Step: remove_gutterball...
Upgrade Step: start_tomcat...
Redirecting to /bin/systemctl start tomcat.service
Some services failed to start: tomcat
Upgrade step start_tomcat failed. Check logs for more information.
----------
but systemctl tells me it's fine - although there is some weird candlepin
output?
----------
● tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
preset: disabled)
Active: active (running) since Mon 2017-02-13 14:33:43 AEDT; 1min 55s ago
Main PID: 8278 (java)
CGroup: /system.slice/tomcat.service
└─8278 /usr/lib/jvm/jre/bin/java -classpath
/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
-Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat
-Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp
-Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start
Feb 13 14:33:46 vmpr-res-utils server[8278]: Feb 13, 2017 2:33:46 PM
com.google.inject.internal.ProxyFactory <init>
Feb 13 14:33:46 vmpr-res-utils server[8278]: WARNING: Method [public
org.candlepin.model.Persisted
org.candlepin.model.ProductCurator.create(org.candlepin.model.Persisted)]
is synthetic and is being intercepted by
[com.google.inject.persist.jpa.JpaLocalTxnInterceptor@3a8e0d80]. This could
indicate a bug. The method may be intercepted twice, or may not be
intercepted at all.
Feb 13 14:33:46 vmpr-res-utils server[8278]: Feb 13, 2017 2:33:46 PM
com.google.inject.internal.ProxyFactory <init>
Feb 13 14:33:46 vmpr-res-utils server[8278]: WARNING: Method [public
org.candlepin.model.Persisted
org.candlepin.model.ProductCurator.merge(org.candlepin.model.Persisted)] is
synthetic and is being intercepted by
[com.google.inject.persist.jpa.JpaLocalTxnInterceptor@3a8e0d80]. This could
indicate a bug. The method may be intercepted twice, or may not be
intercepted at all.
Feb 13 14:33:46 vmpr-res-utils server[8278]: Feb 13, 2017 2:33:46 PM
com.google.inject.internal.ProxyFactory <init>
Feb 13 14:33:46 vmpr-res-utils server[8278]: WARNING: Method [public void
org.candlepin.model.RulesCurator.delete(org.candlepin.model.Persisted)] is
synthetic and is being intercepted by
[com.google.inject.persist.jpa.JpaLocalTxnInterceptor@3a8e0d80]. This could
indicate a bug. The method may be intercepted twice, or may not be
intercepted at all.
Feb 13 14:33:46 vmpr-res-utils server[8278]: Feb 13, 2017 2:33:46 PM
com.google.inject.internal.ProxyFactory <init>
Feb 13 14:33:46 vmpr-res-utils server[8278]: WARNING: Method [public
org.candlepin.model.Persisted
org.candlepin.model.RulesCurator.create(org.candlepin.model.Persisted)] is
synthetic and is being intercepted by
[com.google.inject.persist.jpa.JpaLocalTxnInterceptor@3a8e0d80]. This could
indicate a bug. The method may be intercepted twice, or may not be
intercepted at all.
Feb 13 14:33:46 vmpr-res-utils server[8278]: Feb 13, 2017 2:33:46 PM
com.google.inject.internal.ProxyFactory <init>
Feb 13 14:33:46 vmpr-res-utils server[8278]: WARNING: Method [public void
org.candlepin.model.EntitlementCertificateCurator.delete(org.candlepin.model.Persisted)]
is synthetic and is being intercepted by
[com.google.inject.persist.jpa.JpaLocalTxnInterceptor@3a8e0d80]. This could
indicate a bug. The method may be intercepted twice, or may not be
intercepted at all.
...
I just wanted to update Puppet. I followed the instructions!
L.
------
The most dangerous phrase in the language is, "We've always done it this
way."
- Grace Hopper
On 13 February 2017 at 13:56, Lachlan Musicman <[email protected]> wrote:
> I'm checking through the step 3 process. Looks like most things have been
> done, with a few differences to the notes:
>
> - step 3a.3 edit /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf
> 1. change master-var-dir to /opt/puppetlabs/puppet/cache
>
> my installation had
>
> master-var-dir to /opt/puppetlabs/server/data/puppetserver
>
> - step 3b.1.2:puppetdir: /opt/puppetlabs/puppet/cache
>
> same as the step above it, /opt/puppetlabs/server/data/puppetserver
>
> - step 3.3c.3 "restart Foreman by running touch ~foreman/tmp/restart.txt"
>
> I had to find the dir, because it wasn't in root - it ("foreman/tmp") was
> in /var/lib/ (/var/lib/foreman/tmp/). Running the command didn't do
> anything that I could see.
>
> Everything looks ok, apart from some relatively minor issues. I currently
> have 100% of servers out of sync. I presume that's connected to the ssl
> error and the fact that when I go to Infrastructure->smart proxies->
> puppetCA I'm down from 60 managed hosts to none.
>
>
> cheers
>
> L.
>
>
> ------
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 13 February 2017 at 13:03, Lachlan Musicman <[email protected]> wrote:
>
>> and now yum update on the katello server fails on a certificate problem?
>>
>> [Errno 14] curl#35 - "Peer does not recognize and trust the CA that
>> issued your certificate."
>>
>> ------
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 13 February 2017 at 12:56, Lachlan Musicman <[email protected]> wrote:
>>
>>> Ok, I've found the itemized puppet upgrade instructions that are here:
>>>
>>> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
>>> ng_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
>>>
>>> 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.
