Activity log for bug #1620216

Date Who What changed Old value New value Message
2016-09-05 08:13:12 Dmitry Sutyagin bug added bug
2016-09-06 10:28:50 Timur Nurlygayanov description This is a backport request for the following upstream bug: https://bugs.launchpad.net/neutron/+bug/1384402 Affected customer is running MOS 6.1 (Juno). This is a backport request for the following upstream bug: https://bugs.launchpad.net/neutron/+bug/1384402 Affected customer is running MOS 6.1 (Juno). While investing on Fuel 9.1 deployed with snapshot #175 it has been found that the Nailgun's database does not reflect the state of openstack.yaml. Snapshot #175 contains a new parameter ("auth_s3_keystone_ceph") introduced in fuel-web [1]. It can be found on filesystem but not in the database. Filesystem: [root@nailgun ~]# grep auth_s3_keystone_ceph /usr/share/fuel-openstack-metadata/openstack.yaml auth_s3_keystone_ceph: Database: [root@nailgun ~]# pg_dump -d nailgun -U nailgun -h localhost | grep auth_s3_keystone_ceph | wc -l 0 Nailgun's output: [root@nailgun fuel-noop-fixtures]# fuel env --create --name test_env --rel 2 --net vlan Environment 'test_env' with id=11 was created! [root@nailgun fuel-noop-fixtures]# envid=`fuel env | grep test_env | awk '{print $1}'` [root@nailgun fuel-noop-fixtures]# fuel env --attributes --env $envid --download Attributes of cluster 11 downloaded into ./cluster_11/attributes.yaml. [root@nailgun fuel-noop-fixtures]# grep auth_s3_keystone_ceph ./cluster_11/attributes.yaml | wc -l 0 On Fuel deployed with custom built ISO [2] everything works as expected. Although this might be only an accident, I believe we should verify whether the new, snapshot-based workflow for Fuel 9.1 triggers the Nailgun's DB update. This is especially important as AFAIK QA use solely this approach in testing Fuel 9.1. [1] https://review.openstack.org/#/c/359128/ [2] https://custom-ci.infra.mirantis.net/view/9.0/job/9.0.custom.iso/377/
2016-09-06 11:12:19 Timur Nurlygayanov description This is a backport request for the following upstream bug: https://bugs.launchpad.net/neutron/+bug/1384402 Affected customer is running MOS 6.1 (Juno). While investing on Fuel 9.1 deployed with snapshot #175 it has been found that the Nailgun's database does not reflect the state of openstack.yaml. Snapshot #175 contains a new parameter ("auth_s3_keystone_ceph") introduced in fuel-web [1]. It can be found on filesystem but not in the database. Filesystem: [root@nailgun ~]# grep auth_s3_keystone_ceph /usr/share/fuel-openstack-metadata/openstack.yaml auth_s3_keystone_ceph: Database: [root@nailgun ~]# pg_dump -d nailgun -U nailgun -h localhost | grep auth_s3_keystone_ceph | wc -l 0 Nailgun's output: [root@nailgun fuel-noop-fixtures]# fuel env --create --name test_env --rel 2 --net vlan Environment 'test_env' with id=11 was created! [root@nailgun fuel-noop-fixtures]# envid=`fuel env | grep test_env | awk '{print $1}'` [root@nailgun fuel-noop-fixtures]# fuel env --attributes --env $envid --download Attributes of cluster 11 downloaded into ./cluster_11/attributes.yaml. [root@nailgun fuel-noop-fixtures]# grep auth_s3_keystone_ceph ./cluster_11/attributes.yaml | wc -l 0 On Fuel deployed with custom built ISO [2] everything works as expected. Although this might be only an accident, I believe we should verify whether the new, snapshot-based workflow for Fuel 9.1 triggers the Nailgun's DB update. This is especially important as AFAIK QA use solely this approach in testing Fuel 9.1. [1] https://review.openstack.org/#/c/359128/ [2] https://custom-ci.infra.mirantis.net/view/9.0/job/9.0.custom.iso/377/ This is a backport request for the following upstream bug: https://bugs.launchpad.net/neutron/+bug/1384402 Affected customer is running MOS 6.1 (Juno).
2016-09-15 09:02:04 Alexey Stupnikov mos: assignee MOS Maintenance (mos-maintenance) Alexey Stupnikov (astupnikov)
2016-09-16 08:49:42 Alexey Stupnikov mos: importance High Critical
2016-09-16 08:50:33 Alexey Stupnikov mos: status Confirmed In Progress
2016-09-16 08:50:58 Alexey Stupnikov mos: milestone 6.1-updates 6.1-mu-8
2016-12-16 20:56:19 Vitaly Sedelnik mos: milestone 6.1-mu-8 6.1-updates
2017-12-12 17:02:29 Alexey Stupnikov mos: status In Progress Won't Fix