Hide Forgot
Description of problem: Upgrading the overcloud from OSP7 to OSP9 (7->8->9) fails during aodh installation (section 3.4.2 [1]). Puppet is not able to find the aodh puppet class. In fact there is no symlink in /etc/puppet/modules for aodh (and other modules). Version-Release number of selected component (if applicable): # OSP9 (but this point every nodes are still running OSP8) # rpm -qa openstack-puppet-modules openstack-puppet-modules-7.1.3-1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy the overcloud with OSP7 2. Upgrade the overcloud to OSP8 3. Upgrade the overcloud to OSP9 Actual results: We don't have the issue during the upgrade to OSP8 but I think this affects OSP8 too. Compared to a fresh OSP8/9 installation we don't have all the symlink for the puppet modules in /etc/puppet/modules (ex: aodh). This results to a puppet error during aodh installation : --------------------- Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class ::aodh at /var/lib/heat-config/heat-config-puppet/264e2c11-6407-4070-a94c-8b6503d52bca.pp:30 on node sc-ctrl00.localdomain Wrapped exception: Could not find declared class ::aodh Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class ::aodh at /var/lib/heat-config/heat-config-puppet/264e2c11-6407-4070-a94c-8b6503d52bca.pp:30 on node sc-ctrl00.localdomain --------------------- --------------------- # ls -hl /etc/puppet/modules/aodh ls: cannot access /etc/puppet/modules/aodh: No such file or directory # ls -hl /usr/share/openstack-puppet/modules/aodh total 28K -rw-r--r--. 1 root root 220 Jul 14 16:09 CHANGELOG.md drwxr-xr-x. 2 root root 20 Sep 22 20:31 examples -rw-r--r--. 1 root root 575 Jul 14 16:09 Gemfile drwxr-xr-x. 3 root root 19 Sep 22 20:31 lib -rw-r--r--. 1 root root 561 Jul 14 16:09 LICENSE drwxr-xr-x. 5 root root 4.0K Sep 22 20:31 manifests -rw-r--r--. 1 root root 1.1K Jul 14 16:09 metadata.json -rw-r--r--. 1 root root 2.9K Jul 14 16:09 Rakefile -rw-r--r--. 1 root root 2.9K Jul 14 16:09 README.md drwxr-xr-x. 2 root root 20 Sep 22 20:31 tests --------------------- Expected results: All symlinks to /usr/share/openstack-puppet/modules/* Upgrading from scratch OSP8 to OSP9 doesn't have this issue because the overcloud image already have all the right symlinks [2] Additional info: During OSP7 updates (7.x to 7.y [3]) we forced the symlink creation () in the yum_update.sh but this line has been removed in OSP8/9. [1] https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/upgrading-red-hat-openstack-platform/#sect-Major-Upgrading_the_Overcloud-Aodh [2] https://github.com/openstack/tripleo-puppet-elements/blob/stable/mitaka/elements/puppet-modules/install.d/puppet-modules-package-install/75-puppet-modules-package#L7 [3] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Updating_the_Overcloud.html#sect-Updating_the_Overcloud_Packages in attachment the puppet modules list in /etc/puppet/modules for an upgraded OSP7 env and from scratch OSP9
Created attachment 1204897 [details] Puppet modules in an upgraded OSP7 env
Created attachment 1204898 [details] Puppet modules in a clean OSP9 env
Hi, this look legit. This is also affecting upstream. The kilo branch isn't supported upstream anymore, that's why you can't find the branch. I will make sure that the lines exists in yum_update.sh for osp8/osp9. This isnt' needed in osp10 as the puppet module path is coded inside the puppet run. Thanks,
*** Bug 1414502 has been marked as a duplicate of this bug. ***
The upstream bug already exist, but is not backported to mitaka.
Wrong comment, there is a fix for mitaka adding it to the bz. It needs z-stream.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0470.html