Trying to upgrade an on-premise station. The installer does not return any error on the console, but the components versions are the same as before.
[root@XXX|# yum list installed | grep asm
asm-optunnel-client.noarch 10.1.6-1 @asm
asm-shared-cp.noarch 10.0.9-1 @asm
asm-smartpop-api.x86_64 10.1.4-1 @asm
asm-smartpop-assetsmanager.x86_64 10.1.4-1 @asm
asm-smartpop-browsermob-proxy.noarch 10.1.7-1 @asm
asm-smartpop-cbot.x86_64 10.1.1-1 @asm
asm-smartpop-checkpoint.noarch 10.1.1-1 @asm
asm-smartpop-common.x86_64 10.1.4-1 @asm
asm-smartpop-fcgiwrap.x86_64 1.1.0.21-1 @asm
asm-smartpop-fpm.x86_64 10.1.4-1 @asm
asm-smartpop-httpbroker.x86_64 10.1.4-1 @asm
asm-smartpop-jmeter2.noarch 2.13-21 @asm
asm-smartpop-jmeter3.noarch 3.3-28 @asm
asm-smartpop-python-gunicorn.noarch 19.6.0-1 @asm
asm-smartpop-rbtm.x86_64 10.1.4-1 @asm
asm-smartpop-resultbroker.x86_64 10.1.4-1 @asm
perl-CGI-Simple.noarch 1.115-1 @asm
There are some errors in the installation logs (in the file puppet_07_26_2019_13_38_27.
2019-07-28 13:38:35 +0200 Puppet (warning): /opt/asm/opms/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5
(file: /opt/asm/opms/puppet/hiera.yaml)
2019-07-28 13:38:35 +0200 Puppet (warning): Undefined variable '::role3'; \n (file & line not available)
2019-07-28 13:38:35 +0200 Puppet (warning): This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README. at ["/opt/asm/opms/puppet/environments/production/modules/yum/manifests/init.pp", 17]:["/opt/asm/opms/puppet/environments/production/modules/profile/manifests/checkpoint/repos/redhat.pp", 7]
(location: /opt/asm/opms/puppet/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
2019-07-28 13:38:35 +0200 Puppet (warning): This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Hash. There is further documentation for validate_legacy function in the README. at ["/opt/asm/opms/puppet/environments/production/modules/yum/manifests/init.pp", 18]:["/opt/asm/opms/puppet/environments/production/modules/profile/manifests/checkpoint/repos/redhat.pp", 7]
(location: /opt/asm/opms/puppet/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
2019-07-28 13:38:35 +0200 Puppet (warning): Unknown variable: '::asm_repo'. (file: /opt/asm/opms/puppet/environments/production/modules/profile/manifests/checkpoint/repos/redhat.pp, line: 55, column: 25)
Release : SAAS
Component : CA APP SYNTHETIC MONITOR (WATCHMOUSE)
The problem here is that puppet 3 on OPMS is required. The environment has puppet 5 which is not supported yet. Please use EPEL repositories to install puppet 3 and retry the upgrade. Use following steps:
There is a step in the installation process that installs puppet. It executes this command:
yum -y install puppet
It is to make sure puppet is installed. But if the puppet is installed and pinned properly it won't upgrade it.
Tested it with the RH 7.7 and performed the following steps:
# register RH
subscription-manager register
# list repositories (empty)
yum repolist all
# get list of available pools based on subscription (search for Pool ID) and attach.
subscription-manager list --available
subscription-manager attach --pool=XXXXXXXX
# install epel: download package from CentOS
wget http://ftp.cvut.cz/centos/7/extras/x86_64/Packages/epel-release-7-11.noarch.rpm
yum localinstall epel-release-7-11.noarch.rpm
# install puppet 3.6 and lock it
yum install puppet
puppet -version
yum install yum-plugin-versionlock
yum versionlock puppet*
# disable selinux
setenforce 0
# download the installer and run int
wget https://s3.amazonaws.com/caasm/opms/asm-opms-10.2.1.0.bin
chmod +x asm-opms-10.2.1.0.bin
./asm-opms-10.2.1.0.bin
After the installation the puppet is still 3.6.2 even though the "Installing Puppet" step was executed as well.
Try to reinstall the puppet version again, pin it and then run command
yum -y install puppet
It should not upgrade it to version 5, otherwise the package is not properly pinned.
Once this works properly, then you can run the installer.