Hi Rene,
About your login issue - if command.properties is not present in CloudStack's classpath for example, usually at /etc/cloudstack/management or somewhere in /usr/share/cloudstack-management/ path. The CloudStack upgrade logic has been simplified wrt dynamic roles and will automatically switch your env to use dynamic roles if commands.properties is missing: https://github.com/apache/cloudstack/blob/4.11/engine/schema/src/com/cloud/upgrade/dao/Upgrade41000to41100.java#L65 I'm not sure exactly how the upgrade was tested - can you check either at your API logs why the login is failing and if the API is allowed for the login user/account from cloud.role_permission (select * from role_permissions where role_id=1; for admin user account). You may also want to check for browser cache i.e. attempt using the UI in incognito mode. Are you able to reproduce failure by using cloudmonkey with login credentials (not apikey/secretkey)? About the VR issue - a manual reboot should not be necessary after first provisioning, I would see that as a bug and perhaps a blocker. What we can do is look at your env, see systemd process chains (see what's blocking and causing blocking or failures?) and share our findings (or fix/PR) with the community. After the VR is up, from vCenter client can you see where it is stuck and if it is able to start ssh. You can check for cloud-postinit service (systemctl status cloud-postinit). In the past I found and fixed an issue where it got stuck due to dependency issues around apache2 (killing or performing systemctl stop apache2 also fixed the issue, in my fix I made it stop+start without blocking the cloud-postinit process). - Rohit <https://cloudstack.apache.org> ________________________________ From: Rene Moser <m...@renemoser.net> Sent: Wednesday, May 23, 2018 1:48:47 PM To: dev@cloudstack.apache.org Subject: Re: 4.11.1 install feedback Hi again Regarding router: the router looks more stable (rohit lab version). However, we still need to manually reboot it after first provisioning, otherwise the management server does not get access by ssh. Having a lot of fw rules and many VMs in an advanced network, still takes a "hell of a time" to get the VR fully configured. This is on VMware 6.5, I think, there is no automated testing for this env right? Regards René rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
