Activity log for bug #1915557

Date Who What changed Old value New value Message
2021-02-12 20:34:33 Drew Freiberger bug added bug
2021-02-12 20:35:45 Drew Freiberger bug added subscriber Canonical IS BootStack
2021-02-15 21:52:05 Drew Freiberger description It was discovered after making a configuration change to vnetResourceGroup after deployment and settling of a k8s model on Azure that we were no longer able to create loadbalancers due to the network security group existing in the original resource group context and the role had no allowance for the newly configured vnetResourceGroup. It would be best for the charm to error or block status if config-changes are made to the configs that must only be set at deployment time so that operators cannot change the values and cause breakage in the undercloud authentication structure. Changes to azure-integrator charm configuration for the following configuration is not reflected in the running kubernetes-master /var/snap/kube-controller-manager/common/cloud-config.conf. - subnetName - vnetName - vnetResourceGroup - vnetSecurityGroup While this is documented as not being able to be updated after deployment, we have found environments where subnets are migrated to different vnets or vnets are moved to shared resource groups after deployments are unable to support creation of loadbalancers in the changed network topology. I've found while working with a customer deployment that making the modifications manually to the cloud-config.conf and restarting the snap service kube-controller-manager.daemon does affect the changes necessary to allow for loadbalancer deployment along with the addition of a securityGroupResourceGroup as noted in lp#1915560. It would be very helpful if changes to this charm could trigger the appropriate cloud-config.conf changes and recycle the controller-manager service on kubernetes-master units.
2021-02-15 21:52:40 Drew Freiberger summary If operator changes config after deployment, charm should enter blocked state and refuse to config-change Changes to resource groups/networks after deployment should be reflected in kubernetes-master cloud-config.conf
2021-02-15 21:54:11 Drew Freiberger bug task added charm-kubernetes-master
2021-03-05 19:54:33 George Kraft charm-azure-integrator: importance Undecided Medium
2021-03-05 19:54:34 George Kraft charm-kubernetes-master: importance Undecided Medium
2021-03-05 19:54:37 George Kraft charm-azure-integrator: status New Triaged
2021-03-05 19:54:39 George Kraft charm-kubernetes-master: status New Triaged
2021-03-05 19:54:59 George Kraft bug task added charm-kubernetes-worker
2021-03-05 19:56:01 George Kraft summary Changes to resource groups/networks after deployment should be reflected in kubernetes-master cloud-config.conf Changes to Azure resource groups/networks after deployment should be reflected in cloud-config.conf
2021-03-05 19:56:04 George Kraft charm-kubernetes-worker: importance Undecided Medium
2021-03-05 19:56:06 George Kraft charm-kubernetes-worker: status New Triaged
2022-11-10 21:14:55 Aymen Frikha bug added subscriber Canonical Field High
2022-11-14 15:06:37 George Kraft charm-azure-integrator: importance Medium High
2022-11-14 15:06:39 George Kraft charm-kubernetes-master: importance Medium High
2022-11-14 15:06:41 George Kraft charm-kubernetes-worker: importance Medium High
2022-11-14 15:51:32 George Kraft charm-azure-integrator: assignee George Kraft (cynerva)
2022-11-14 15:51:35 George Kraft charm-kubernetes-worker: assignee George Kraft (cynerva)
2022-11-14 15:51:38 George Kraft charm-kubernetes-master: assignee George Kraft (cynerva)
2022-11-16 20:18:10 George Kraft charm-azure-integrator: status Triaged In Progress
2022-11-16 20:18:12 George Kraft charm-kubernetes-master: status Triaged In Progress
2022-11-16 20:18:14 George Kraft charm-kubernetes-worker: status Triaged In Progress
2022-11-16 20:18:17 George Kraft charm-azure-integrator: milestone 1.26
2022-11-16 20:18:19 George Kraft charm-kubernetes-master: milestone 1.26
2022-11-16 20:18:20 George Kraft charm-kubernetes-worker: milestone 1.26
2022-11-21 05:54:22 Kevin W Monroe charm-azure-integrator: status In Progress Fix Committed
2022-11-21 05:54:30 Kevin W Monroe charm-kubernetes-worker: status In Progress Fix Committed
2022-11-21 05:55:06 Kevin W Monroe charm-kubernetes-master: status In Progress Fix Committed
2022-12-15 15:18:05 Adam Dyess charm-azure-integrator: status Fix Committed Fix Released
2022-12-15 15:19:06 Adam Dyess charm-kubernetes-master: status Fix Committed Fix Released
2022-12-15 15:19:21 Adam Dyess charm-kubernetes-worker: status Fix Committed Fix Released