This may actually be related to landscape-server returning "maxiumum number of computers pending approval reached".
I think this bug should be against both landscape-server and landscape-client. The server side needs a tweak to allow as many pending approvals as you have licenses in stock for a large cloud deployment.
Secondarily, landscape-client needs to retry when it receives this return from landscape-config.
Restarting landscape-client (via systemctl): landscape-client.service.
('Maximum number of computers pending approval reached. ', 'Login to your Landscape server account page to manage pending computer approvals.')
This may actually be related to landscape-server returning "maxiumum number of computers pending approval reached".
I think this bug should be against both landscape-server and landscape-client. The server side needs a tweak to allow as many pending approvals as you have licenses in stock for a large cloud deployment.
Secondarily, landscape-client needs to retry when it receives this return from landscape-config.
Restarting landscape-client (via systemctl): landscape- client. service.
('Maximum number of computers pending approval reached. ', 'Login to your Landscape server account page to manage pending computer approvals.')