| 2023-09-29 16:51:52 |
Barry Price |
bug |
|
|
added bug |
| 2023-09-30 03:16:38 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost` shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now. |
|
| 2023-09-30 03:17:00 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost` shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now. |
|
| 2023-09-30 03:17:33 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now, and shouldn't be in any danger of coming undone later as long the config setting has also been applied. |
|
| 2023-10-05 13:11:25 |
Barry Price |
merge proposal linked |
|
https://code.launchpad.net/~barryprice/charm-k8s-mattermost/+git/charm-k8s-mattermost/+merge/452943 |
|
| 2023-10-05 13:35:04 |
Barry Price |
summary |
Modifying max_users_per_team has no effect |
The max_users_per_team setting can't be increased beyond 1000 if use_canonical_defaults is True |
|
| 2023-10-05 13:36:22 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround for now, and shouldn't be in any danger of coming undone later as long the config setting has also been applied. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround, but can then come undone later when the charm notices the discrepancy. |
|
| 2023-10-05 13:36:39 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid workaround, but can then come undone later when the charm notices the discrepancy. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid short-term workaround, but this can then come undone later when the charm notices the discrepancy. |
|
| 2023-10-05 13:37:13 |
Barry Price |
description |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid short-term workaround, but this can then come undone later when the charm notices the discrepancy. |
Modifying the charm setting `max_users_per_team` *ought* to update the pod spec and spawn a new pod with the new value in place.
Having just attempted this though, nothing appears to have happened, and the running unit and pod appear to have been unaffected.
Manually editing the deployment (e.g. `kubectl edit deployment mattermost`) shows the old value (for MM_TEAMSETTINGS_MAXUSERSPERTEAM) in place of the new one.
Modifying the value to the desired number within that `kubectl edit` session and saving it to apply seems to be a valid short-term workaround, but this can then come undone later when the charm notices the discrepancy.
Unsetting `use_canonical_defaults` would unfortunately introduce other operational changes which can't be worked around via current config options. |
|
| 2023-10-06 03:28:54 |
Haw Loeung |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2023-10-06 03:28:59 |
Haw Loeung |
charm-k8s-mattermost: status |
New |
Confirmed |
|
| 2023-10-06 07:10:51 |
Barry Price |
charm-k8s-mattermost: status |
Confirmed |
Fix Committed |
|
| 2023-10-06 07:10:56 |
Barry Price |
charm-k8s-mattermost: assignee |
|
Barry Price (barryprice) |
|
| 2023-10-06 07:11:01 |
Barry Price |
charm-k8s-mattermost: importance |
Undecided |
High |
|
| 2023-10-06 07:44:30 |
Barry Price |
charm-k8s-mattermost: status |
Fix Committed |
Fix Released |
|
