As part of refresh We are updating OSP 10 components to RDO Newton Trunk as of 2017-01-02 https://trunk.rdoproject.org/centos7-newton/b5/a2/b5a2b9f79d15c2591ad0ce3a8342d9adb1005696_100eb833/
openstack-neutron-lbaas
openstack-keystone-10.0.0-4.el7ost
openstack-ironic-6.2.2-3.el7ost
openstack-manila-3.0.0-6.el7ost
moving os-collect-config-5.1.0-1.el7ost out to it's own bug
Jon, would you be able to enhance your automation to fill in the doctext field as part of rebases? I think a changelog of all fixed RHBZs for example would be appropriate.
[root@controller-0 ~]# rpm -qa | grep openstack-neutron-lbaas openstack-neutron-lbaas-9.1.0-2.el7ost.noarch [root@controller-0 ~]# rpm -qa | grep openstack-ironic openstack-ironic-api-6.2.2-3.el7ost.noarch openstack-ironic-common-6.2.2-3.el7ost.noarch openstack-ironic-conductor-6.2.2-3.el7ost.noarch Ran all scenario tests- All passed FAILED (failures=1) (.venv)[stack@undercloud-0 tempest]$ python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario.test_healthmonitor_basic.TestHealthMonitorBasic.test_health_monitor_basic Tests running... Ran 1 test in 165.670s OK (.venv)[stack@undercloud-0 tempest]$ python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario Tests running... Ran 0 tests in 0.001s OK (.venv)[stack@undercloud-0 tempest]$ python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario.test_listener_basic.TestListenerBasic.test_listener_basic ;python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario.test_load_balancer_basic.TestLoadBalancerBasic.test_load_balancer_basic ; python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario.test_session_persistence.TestSessionPersistence.test_session_persistence ; python -m testtools.run neutron_lbaas.tests.tempest.v2.scenario.test_shared_pools.TestSharedPools.test_shared_pools Tests running... Ran 1 test in 95.897s OK Tests running... Ran 1 test in 85.838s OK Tests running... Ran 1 test in 109.145s OK Tests running... Ran 1 test in 115.465s OK
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-0201.html