Description of problem: We got the following error when updating from 12 to 13: [716095-lab1-controller03]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'mariadb-server-galera' found available, installed or updated", "rc": 126, "results": ["No package matching 'mariadb-server-galera' found available, installed or updated"]} 2018-12-22 11:45:26,079 p=25049 u=mistral | fatal: [XXXX-lab1-controller01]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'mariadb-server-galera' found available, installed or updated", "rc": 126, "results": ["No package matching 'mariadb-server-galera' found available, installed or updated"]} 2018-12-22 11:45:26,423 p=25049 u=mistral | fatal: [XXXX-lab1-controller02]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'mariadb-server-galera' found available, installed or updated", "rc": 126, "results": ["No package matching 'mariadb-server-galera' found available, installed or updated"]} It seems, upgrade process didnt subscribe overcloud nodes to the correct repository. To fix the issue, I manually subscribe all controller nodes to correct repo. Upgrade process didn't subscribe overcloud nodes to the correct repository. It seems to be with the default configuration, the systems will be registered only during the initial creation of the overcloud. <snip> RHELRegistrationActions: type: comma_delimited_list default: - CREATE description: Actions when the system profile will be registered, by default we only do this on CREATE of a new server, not for existing nodes. </snip> I think I would need to specify "UPDATE" "RHELRegistrationActions:" action before initiating RHOS upgrade procedure. Version-Release number of selected component (if applicable): 12 to 13 How reproducible: Unsure Steps to Reproduce: 1. Upgrade from 12 to 13 2. 3. Actual results: Mentioned error
Can you confirm what is the expected behaviour here ?
Same happened here. While updating from OSP12 to OSP13 I got the same error message: u'TASK [Update host mariadb packages] ********************************************', u'Wednesday 16 January 2019 11:45:30 -0200 (0:00:00.817) 0:41:27.438 ***** ', u'fatal: [overcloud-controller-0]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching \'mariadb-server-galera\' found available, installed or updated", "rc": 126, "results": ["No package matching \'mariadb-server-galera\' found available, installed or updated"]}'] [u'fatal: [overcloud-controller-2]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching \'mariadb-server-galera\' found available, installed or updated", "rc": 126, "results": ["No package matching \'mariadb-server-galera\' found available, installed or updated"]}', u'fatal: [overcloud-controller-1]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching \'mariadb-server-galera\' found available, installed or updated", "rc": 126, "results": ["No package matching \'mariadb-server-galera\' found available, installed or updated"]}', To solve that, I had to update the repositories to OSP13 manually with: sudo subscription-manager repos --disable=rhel-7-server-openstack-12-rpms sudo subscription-manager repos --disable=rhel-7-server-rhceph-2-mon-rpms sudo subscription-manager repos --disable=rhel-7-server-rhceph-2-tools-rpms sudo subscription-manager repos --enable=rhel-7-server-openstack-13-rpms sudo subscription-manager repos --enable=rhel-7-server-rhceph-3-mon-rpms sudo subscription-manager repos --enable=rhel-7-server-rhceph-3-tools-rpms The expected behavior would be finishing the OSP update with success, or maybe that's a documentation problem, and the repositories should be changed manually, but there is no information about that, except for the undercloud/director: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/upgrading_red_hat_openstack_platform/assembly-upgrading_the_undercloud#upgrading_the_undercloud_to_openStack_platform-13