Activity log for bug #1764882

Date Who What changed Old value New value Message
2018-04-17 22:20:13 Miguel Meneses bug added bug
2018-04-17 22:22:36 Miguel Meneses tags canonical-bootstack
2018-04-24 14:29:55 Drew Freiberger summary Additional machines are not automatically registered when changing to a license that allows a greater number of machines Client Registration issue - 'Maximum number of computers pending approval reached'
2018-04-24 14:33:49 Drew Freiberger description Recently We changed the license, and that was high number of landscape-client units which not been registered and did not intended to register after license change. So we needed to register those landscpa-client units manually Recently We changed the license, and that was high number of landscape-client units which not been registered and did not intended to register after license change. The landscape-client charm sits in maintenance mode with status message: Need computer-title and juju-info to proceed. We've noticed that the first 20 systems will register fine when configured properly. Workaround is to run accept the pending approvals in landscape-server Web UI and then run landscape-config --silent' to register the next batch of 20. In a cloud of >50 landscape-client units, this is markedly tedious.
2018-04-24 14:34:14 Drew Freiberger description Recently We changed the license, and that was high number of landscape-client units which not been registered and did not intended to register after license change. The landscape-client charm sits in maintenance mode with status message: Need computer-title and juju-info to proceed. We've noticed that the first 20 systems will register fine when configured properly. Workaround is to run accept the pending approvals in landscape-server Web UI and then run landscape-config --silent' to register the next batch of 20. In a cloud of >50 landscape-client units, this is markedly tedious. Recently We changed the license, and that was high number of landscape-client units which not been registered and did not intended to register after license change. The landscape-client charm sits in maintenance mode with status message: Need computer-title and juju-info to proceed. We've noticed that the first 20 systems will register fine when configured properly. Workaround is to accept the pending approvals in landscape-server Web UI and then run 'landscape-config --silent' across landscape-clients in maintenance mode to register the next batch of 20. In a cloud of >50 landscape-client units, this is markedly tedious.
2018-04-24 14:35:02 Drew Freiberger bug task added landscape-client-charm
2021-11-17 15:39:33 Drew Freiberger landscape-charm: status New Confirmed