Activity log for bug #1497681

Date Who What changed Old value New value Message
2015-09-20 06:16:13 Kevin Carter bug added bug
2015-09-20 06:17:02 Kevin Carter description In this commit "389b0f0dd886388fefae0cece2844c35da28e405" the cinder volumes lxc container config was updated to support udev within the container. In that commit the udev entry was added to the container using the following syntax: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" In the old lxc module thats being carried in Juno when the module adds an entry to config it pads space on the left and right side of the "=" sign. Sadly this causes an issue in future releases where a duplicate config entry is created causing the cinder volume contianer to fail to start. The duplicate config is as follows: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" To fix this issue in Juno which will ensure its stable for future releases the padding should be removed from the container config and a pre task should be added to the rpc_deployment/playbooks/openstack/cinder-volume.yml file to ensure that the incorrect container config is removed prior to having it re-added. The pretask would have to delegate to the host and could use the lininfile module to remove the offending line. Effected file for change: rpc_deployment/vars/config_vars/container_config_cinder_volume.yml Note that in the upgrade process this issue has been addressed in the pending restructuring of the Kilo Upgrade process as found here: https://review.openstack.org/#/c/224137 In this commit "389b0f0dd886388fefae0cece2844c35da28e405" the cinder volumes lxc container config was updated to support udev within the container. In that commit the udev entry was added to the container using the following syntax: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" In the old lxc module thats being carried in Juno when the module adds an entry to config it pads space on the left and right side of the "=" sign. Sadly this causes an issue in future releases where a duplicate config entry is created causing the cinder volume contianer to fail to start. The duplicate config is as follows: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" To fix this issue in Juno which will ensure its stable for future releases the padding should be removed from the container config and a pre task should be added to the rpc_deployment/playbooks/openstack/cinder-volume.yml file to ensure that the incorrect container config is removed prior to having it re-added. The pretask would have to delegate to the host and could use the lininfile module to remove the offending line. Effected file for change: rpc_deployment/vars/config_vars/container_config_cinder_volume.yml Note that in the upgrade process this issue has been addressed in the pending restructuring of the Kilo Upgrade process as found here: https://review.openstack.org/#/c/224137
2015-09-20 06:17:54 Kevin Carter description In this commit "389b0f0dd886388fefae0cece2844c35da28e405" the cinder volumes lxc container config was updated to support udev within the container. In that commit the udev entry was added to the container using the following syntax: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" In the old lxc module thats being carried in Juno when the module adds an entry to config it pads space on the left and right side of the "=" sign. Sadly this causes an issue in future releases where a duplicate config entry is created causing the cinder volume contianer to fail to start. The duplicate config is as follows: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" To fix this issue in Juno which will ensure its stable for future releases the padding should be removed from the container config and a pre task should be added to the rpc_deployment/playbooks/openstack/cinder-volume.yml file to ensure that the incorrect container config is removed prior to having it re-added. The pretask would have to delegate to the host and could use the lininfile module to remove the offending line. Effected file for change: rpc_deployment/vars/config_vars/container_config_cinder_volume.yml Note that in the upgrade process this issue has been addressed in the pending restructuring of the Kilo Upgrade process as found here: https://review.openstack.org/#/c/224137 In this commit "389b0f0dd886388fefae0cece2844c35da28e405" the cinder volumes lxc container config was updated to support udev within the container. In that commit the udev entry was added to the container using the following syntax: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" In the old lxc module thats being carried in Juno when the module adds an entry to config it pads space on the left and right side of the "=" sign. Sadly this causes an issue in future releases where a duplicate config entry is created causing the cinder volume contianer to fail to start. The duplicate config is as follows: + - "lxc.mount.entry = udev dev devtmpfs defaults 0 0" + - "lxc.mount.entry..=..udev dev devtmpfs defaults 0 0" #### I added .. to the mount entry to should the spaces, Launchpad removes extra white space on submission. To fix this issue in Juno which will ensure its stable for future releases the padding should be removed from the container config and a pre task should be added to the rpc_deployment/playbooks/openstack/cinder-volume.yml file to ensure that the incorrect container config is removed prior to having it re-added. The pretask would have to delegate to the host and could use the lininfile module to remove the offending line. Effected file for change: rpc_deployment/vars/config_vars/container_config_cinder_volume.yml Note that in the upgrade process this issue has been addressed in the pending restructuring of the Kilo Upgrade process as found here: https://review.openstack.org/#/c/224137
2015-09-21 13:42:11 Hugh Saunders openstack-ansible: assignee Hugh Saunders (hughsaunders)
2015-09-21 13:42:14 Hugh Saunders openstack-ansible: status Confirmed In Progress
2015-09-23 11:20:34 Hugh Saunders openstack-ansible: status In Progress Confirmed
2015-09-23 11:20:36 Hugh Saunders openstack-ansible: assignee Hugh Saunders (hughsaunders)
2015-09-25 15:27:38 Jesse Pretorius openstack-ansible: milestone 10.1.15 10.2.0
2015-10-05 14:44:27 Nolan Brubaker openstack-ansible: assignee Nolan Brubaker (nolan-brubaker)
2015-10-06 10:48:25 OpenStack Infra tags in-juno
2015-10-21 06:37:32 Jesse Pretorius openstack-ansible: status Confirmed Fix Committed
2015-10-21 06:37:36 Jesse Pretorius openstack-ansible: milestone 10.2.0 10.1.16
2015-11-02 15:52:53 Jesse Pretorius openstack-ansible: status Fix Committed Fix Released