Contents
Set debug options to "true" in all config files - dashboard, api, conductor.
Note
The following debug sequence should be used when you have no idea about why the system isn't working. If you have one, you may skip unnecessary sections.
First, stop both murano-api and murano-conductor services. We will start them one by one from the console.
Murano-Api
Open new console
Start api service manually
># murano-api --config-dir /etc/murano-api \
> /var/log/murano-api-live.log &
># tailf /var/log/murano-api-live.log
Open dashboard, create and send to deploy some simple environment.
Open RabbitMQ web console, open your vhost and ensure that queues were created and there is at least one message.
Check log for errors - there shouldn't be any
Keep murano-api service running.
Murano-Conductor
Open new console
Start conductor from console
># muranoconductor --config-dir /etc/murano-conductor > \
/var/log/murano-conductor-live.log &
># tailf /var/log/murano-conductor-live.log
Check that there is no python exceptions in the log. Some errors like 404 are ok, as conductor tries to delete environment that doesn't exist.
Check heat stack status. It should not be in FAILED state. If it is - check heat and nova error log to find the cause.
Keep murano-conductor service running.
Now, the environment should be created, and instance(s) launched.
Next, check if instances were configured correctly by the cloudbase init tool.
Log in to any instance and open powershell log file at
C:\Murano\PowerShell.log. There shouldn't be any exceptions logged.
Other symptoms of successful configuration is that the instance was
renamed and you have to press <Ctrl>+<Alt>+<Del>
to log into. Unconfigured instance has autologon enabled for the
first logon, so if console is open, the instance is not configured
(yet).
Check that Murano Agent has correct config file. If there is a .bak file, then it was changed by the init script. Check the file, ensure that it has correct values.
Check Murano Agent log file. There should be logged all tasks received by the agent from the conductor.
Check PowerShell log. There should be messages about all functions, executed on the instance.
