Open josehernaC2C opened 1 week ago
@josehernaC2C I can’t seem to reproduce this error. If you run the command outside the playbook, does it yield the same outcome? Also note that you’re using a PostgreSQL file, not MSSQL
@kirillkrylov I ran the deploy command outside the playbook and got the same result. I already have Version 8.1.3.6734 installed on my local and I was trying to add a clean install for 8.1.3.6801 using the MSSQL zip file provided by Creatio support.
We are growing as a developer team and we are trying to figure it out the easiest way to deploy local Creatio instances to our windows\SQL server environment
https://github.com/user-attachments/assets/f1855937-36ba-4084-b292-5a3f8d11fb7a
@josehernaC2C
We've added additional debugging options to clio commands. You can now run any command with --debug
flag to get more details.
Your exception seem to be related to kubectl, which is installed when you install Rancher Desktop. Please make sure Rancher Desktop is installed before running the installer command
Please make sure to follow the instructions provided in this link. https://github.com/Advance-Technologies-Foundation/clio?tab=readme-ov-file#install-rancher-desktop-and-configure-resources
Thanks @kirillkrylov I was missing a couple of steps.
I'm almost there. Now I'm getting this error:
[Starting Database restore] - 07:03:28 Microsoft.Data.SqlClient.SqlException (0x80131904): Login failed for user 'sa'.
where do I get and change that password?
Make sure deploy mssql with the provided manifest template.
Hello,
I'm following the clio tutorial to install Creatio from CLI, but I'm getting the error below. Any ideas on what I'm missing?
Thanks,
Jose
clio version '6.1.0.37'
[ERR] - The requested service 'Clio.Command.CreatioInstallCommand.InstallerCommand' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.