Back to bug 1012711
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Scott Haines | 2013-09-27 03:11:14 UTC | Priority | unspecified | urgent |
| CC | shaines | |||
| Severity | unspecified | high | ||
| Sudhir D | 2013-09-27 03:29:18 UTC | QA Contact | sdharane | lmohanty |
| Sudhir D | 2013-09-27 03:29:51 UTC | Keywords | ZStream | |
| CC | sdharane | |||
| Vivek Agarwal | 2013-10-04 13:00:26 UTC | CC | vagarwal | |
| Assignee | crh | rtalur | ||
| Vivek Agarwal | 2013-10-17 10:03:04 UTC | Status | NEW | ASSIGNED |
| Gowrishankar Rajaiyan | 2013-10-17 10:04:22 UTC | CC | grajaiya | |
| Raghavendra Talur | 2013-10-22 06:34:55 UTC | Doc Text | Cause: We have changed the recommended settings for Samba. These settings are part of smb.conf. However when someone upgrades from RHS 2.0 to RHS 2.1, they get the new settings in smb.conf.rpmnew and the old smb.conf is retained in use. Consequence: New settings which are mentioned in smb.conf.rpmnew only are not brought into effect and this leads to bad performance of gluster accessed using smb protocol. Fix: Moving on, we are adding all rhs-specific samba settings in a secondary conf file which will get updated on every upgrade automatically. This secondary conf file will be override any of the settings which were defined in primary smb.conf file. However any user changes in primary smb.conf which don't interfere with rhs recommended settings will be retained. Result: Upgrades will not require user to do manual merge of existing and new recommended settings for Samba every time a upgrade happens. |
|
| Raghavendra Talur | 2013-10-28 08:52:56 UTC | Status | ASSIGNED | ON_QA |
| Fixed In Version | samba-3.6.9-160.4.el6rhs | |||
| Lalatendu Mohanty | 2013-10-28 14:58:07 UTC | Status | ON_QA | ASSIGNED |
| Raghavendra Talur | 2013-10-28 14:59:03 UTC | Assignee | rtalur | jrivera |
| Vivek Agarwal | 2013-10-31 04:52:34 UTC | Status | ASSIGNED | ON_QA |
| Fixed In Version | samba-3.6.9-160.4.el6rhs | samba-3.6.9-160.5.el6rhs | ||
| Assignee | jrivera | rtalur | ||
| Raghavendra Talur | 2013-10-31 07:18:34 UTC | Fixed In Version | samba-3.6.9-160.5.el6rhs | samba-3.6.9-160.6.el6rhs |
| Lalatendu Mohanty | 2013-10-31 13:03:45 UTC | Status | ON_QA | VERIFIED |
| Anjana Suparna Sriram | 2013-11-19 11:03:37 UTC | CC | asriram | |
| Doc Text | Cause: We have changed the recommended settings for Samba. These settings are part of smb.conf. However when someone upgrades from RHS 2.0 to RHS 2.1, they get the new settings in smb.conf.rpmnew and the old smb.conf is retained in use. Consequence: New settings which are mentioned in smb.conf.rpmnew only are not brought into effect and this leads to bad performance of gluster accessed using smb protocol. Fix: Moving on, we are adding all rhs-specific samba settings in a secondary conf file which will get updated on every upgrade automatically. This secondary conf file will be override any of the settings which were defined in primary smb.conf file. However any user changes in primary smb.conf which don't interfere with rhs recommended settings will be retained. Result: Upgrades will not require user to do manual merge of existing and new recommended settings for Samba every time a upgrade happens. | Cause: When customers upgrade from RHS 2.0 to RHS 2.1, new settings get just stored in smb.conf.rpmnew and don't come into effect. Consequence: New settings which are mentioned in smb.conf.rpmnew are critical and because they are not brought into effect this leads to bad performance of gluster accessed using smb protocol. Fix: Moving on, we are adding all rhs-specific samba settings in a secondary config file which will get compulsorily updated on every upgrade automatically. This secondary conf file will override any of the settings which were defined in primary smb.conf file. However any user changes in primary smb.conf which don't interfere with rhs recommended settings will be retained. Result: Upgrades will not require user to do manual merge of existing and new recommended settings for Samba every time a upgrade happens. |
||
| Anjana Suparna Sriram | 2013-11-21 10:14:04 UTC | Doc Text | Cause: When customers upgrade from RHS 2.0 to RHS 2.1, new settings get just stored in smb.conf.rpmnew and don't come into effect. Consequence: New settings which are mentioned in smb.conf.rpmnew are critical and because they are not brought into effect this leads to bad performance of gluster accessed using smb protocol. Fix: Moving on, we are adding all rhs-specific samba settings in a secondary config file which will get compulsorily updated on every upgrade automatically. This secondary conf file will override any of the settings which were defined in primary smb.conf file. However any user changes in primary smb.conf which don't interfere with rhs recommended settings will be retained. Result: Upgrades will not require user to do manual merge of existing and new recommended settings for Samba every time a upgrade happens. | Previously, while upgrading from Red Hat Storage 2.0 to Red Hat Storage 2.1, new settings were only stored in smb.conf.rpmnew and were not applied. The new settings mentioned in smb.conf.rpmnew are critical and if they are not applied leads to poor performance of Red Hat Storage volume accessed using Samba. Now, all Red Hat Storage specific Samba settings are added to a secondary configuration file which will be automatically updated on every upgrade. This secondary configuration file overrides any settings that were defined in primary smb.conf file. With this update, upgrades will not require any manual intervention to do a manual merge of existing and new recommended settings for Samba every time a upgrade is done. |
| errata-xmlrpc | 2013-11-27 15:40:52 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-11-27 10:40:52 UTC | |||
| John Skeoch | 2015-09-01 23:06:20 UTC | CC | chrisw |
Back to bug 1012711