Katello 3.0 upgrade from 3.0 RC8 no answer file exists?

Support
1

Hi,

I've run into a problem attempting to upgrade from RC8 to the production
release, I get this message:

foreman-installer --scenario katello --upgrade
No answer file at /etc/katello-installer/answers.katello-installer.yaml
found, can not continue

I've done the following:

  1. Updated kafo:
    rpm -ivh
    http://koji.katello.org/packages/rubygem-kafo/0.7.4/1.el7/noarch/rubygem-kafo-0.7.4-1.el7.noarch.rpm

  2. Updated repos
    yum update -y
    http://fedorapeople.org/groups/katello/releases/yum/3.0/katello/el7/x86_64/katello-repos-latest.rpm
    yum update -y
    http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm

  3. Clean and update foreman-release-scl
    yum clean all
    yum update -y foreman-release-scl

  4. Update the system
    yum -y update

During this I spotted two warning/errors

Warning: RPMDB altered outside of yum.
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
rubygem-kafo-0.7.4-1.el7.noarch is a duplicate with
rubygem-kafo-0.7.2-1.el7.noarch
(OK fine, I updated this above :wink: )

warning: %posttrans(foreman-installer-katello-3.0.1-2.el7.noarch) scriptlet
failed, exit status 23
Non-fatal POSTTRANS scriptlet failure in rpm package
foreman-installer-katello-3.0.1-2.el7.noarch

/etc/katello-installer has these files in it

-rw-------. 1 root root 6950 Mar 7 12:32
answers.katello-installer.yaml.backup
-rw-------. 1 root root 1583 Dec 24 04:34
answers.katello-installer.yaml.rpmnew
-rw-------. 1 root root 702 Mar 26 07:32
capsule-certs-generate.yaml.rpmsave
drwx------. 2 root root 32 Mar 4 13:11 d20160304-16237-1y53b5q
-rw-------. 1 root root 2385 Jun 17 15:33 katello-installer.yaml
-rw-------. 1 root root 2565 Apr 22 17:19 katello-installer.yaml.backup

If I copy the latest katello-installer.yaml to
answers.katello-installer.yaml and try the upgrade it doesn't like that at
all

foreman-installer --scenario katello --upgrade
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:155:in
get_name': undefined methodgsub' for :name:Symbol (NoMethodError)
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:18:in initialize' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:innew'
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in block in modules' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:inmap'
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in modules' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:184:inparams'
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:193:in
preset_defaults_from_puppet' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:253:inset_parameters'
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:96:in
initialize' from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:innew'
from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in
run' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:150:inrun'
from /sbin/foreman-installer:12:in `<main>'

Have I made a mistake in my upgrade process?

2

For the record, we don't test or guarantee inter-RC upgrades. If you are
upgrading from 2.4, prior to the last round of commits after RC8 your
upgrade could end up in a position where the installer data is wrong or
missing values. If you are able to upgrade from your 2.4 to 3.0 we highly
recommend that. If not, we can try to fix your install.

··· On Jun 16, 2016 11:40 PM, "Dylan Baars" wrote:

Hi,

I’ve run into a problem attempting to upgrade from RC8 to the production
release, I get this message:

foreman-installer --scenario katello --upgrade
No answer file at /etc/katello-installer/answers.katello-installer.yaml
found, can not continue

I’ve done the following:

  1. Updated kafo:
    rpm -ivh
    http://koji.katello.org/packages/rubygem-kafo/0.7.4/1.el7/noarch/rubygem-kafo-0.7.4-1.el7.noarch.rpm

  2. Updated repos
    yum update -y
    http://fedorapeople.org/groups/katello/releases/yum/3.0/katello/el7/x86_64/katello-repos-latest.rpm
    yum update -y
    http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm

  3. Clean and update foreman-release-scl
    yum clean all
    yum update -y foreman-release-scl

  4. Update the system
    yum -y update

During this I spotted two warning/errors

Warning: RPMDB altered outside of yum.
** Found 1 pre-existing rpmdb problem(s), ‘yum check’ output follows:
rubygem-kafo-0.7.4-1.el7.noarch is a duplicate with
rubygem-kafo-0.7.2-1.el7.noarch
(OK fine, I updated this above :wink: )

warning: %posttrans(foreman-installer-katello-3.0.1-2.el7.noarch)
scriptlet failed, exit status 23
Non-fatal POSTTRANS scriptlet failure in rpm package
foreman-installer-katello-3.0.1-2.el7.noarch

/etc/katello-installer has these files in it

-rw-------. 1 root root 6950 Mar 7 12:32
answers.katello-installer.yaml.backup
-rw-------. 1 root root 1583 Dec 24 04:34
answers.katello-installer.yaml.rpmnew
-rw-------. 1 root root 702 Mar 26 07:32
capsule-certs-generate.yaml.rpmsave
drwx------. 2 root root 32 Mar 4 13:11 d20160304-16237-1y53b5q
-rw-------. 1 root root 2385 Jun 17 15:33 katello-installer.yaml
-rw-------. 1 root root 2565 Apr 22 17:19 katello-installer.yaml.backup

If I copy the latest katello-installer.yaml to
answers.katello-installer.yaml and try the upgrade it doesn’t like that at
all

foreman-installer --scenario katello --upgrade
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:155:in
get_name': undefined methodgsub’ for :name:Symbol (NoMethodError)
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:18:in initialize' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:innew’
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in block in modules' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:inmap’
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in modules' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:184:inparams’
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:193:in
preset_defaults_from_puppet' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:253:inset_parameters’
from
/usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:96:in
initialize' from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:innew’
from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in
run' from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:150:inrun’
from /sbin/foreman-installer:12:in `’

Have I made a mistake in my upgrade process?

–
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+unsubscribe@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.

3

Hi Eric,

that's fine, its just a dev system. If it was something simple to fix then
great, otherwise no worries

··· On Friday, June 17, 2016 at 10:51:05 PM UTC+12, Eric Helms wrote: > > For the record, we don't test or guarantee inter-RC upgrades. If you are > upgrading from 2.4, prior to the last round of commits after RC8 your > upgrade could end up in a position where the installer data is wrong or > missing values. If you are able to upgrade from your 2.4 to 3.0 we highly > recommend that. If not, we can try to fix your install. > >> >>