[rdo-users] [rdo][ussuri][TripleO][nova][kvm] libvirt.libvirtError: internal error: process exited while connecting to monitor

Ruslanas Gžibovskis ruslanas at lpic.lt
Tue Jun 30 11:11:49 UTC 2020


attaching logs here. let's see if it will work.

On Tue, 30 Jun 2020 at 12:55, Ruslanas Gžibovskis <ruslanas at lpic.lt> wrote:

> hi all,
>
> I am back, had some issues with MTU.
> Now looks good, at least deployment part.
>
> So I have installed back what I had, and still failing at same point as in
> first message.
>
> I have tried to use: LogTool, how to use it? well, I launched it, but it
> always say [0] detailed output:
>   File "./PyTool.py", line 596, in <module>
>     random_node=random.choice(overcloud_nodes)
>
> I do not get, how to make it work, should it get from stackrc ? as I see
> in
>     overcloud_nodes = []
>     all_nodes = exec_command_line_command('source ' + source_rc_file_path
> + 'stackrc;openstack server list -f json')[
>
> [0] http://paste.openstack.org/show/795345/
>
> On Wed, 24 Jun 2020 at 20:02, Arkady Shtempler <ashtempl at redhat.com>
> wrote:
>
>> Hi Ruslanas!
>>
>> Is it possible to get all logs under /var/log/containers somehow?
>>
>> Thanks!
>>
>> On Wed, Jun 24, 2020 at 2:18 AM Ruslanas Gžibovskis <ruslanas at lpic.lt>
>> wrote:
>>
>>> Hi Alfredo,
>>>
>>> Compute nodes are baremetal or virtualized?, I've seen similar bug
>>>>> reports when using nested virtualization in other OSes.
>>>>>
>>>> baremetal. Dell R630 if to be VERY precise.
>>>
>>>
>>>
>>>>> When using podman, the recommended way to restart containers is using
>>>> systemd:
>>>>
>>>>
>>>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/tips_tricks.html
>>>>
>>>
>>> Thank you, I will try. I also modified a file, and it looked like it
>>> relaunched podman container once config was changed. Either way, if I
>>> understand Linux config correctly, the default value for user and group is
>>> root, if commented out:
>>> #user = "root"
>>> #group = "root"
>>>
>>> also in some logs, I saw, that it detected, that it is not AMD CPU :)
>>> and it is really not AMD CPU.
>>>
>>>
>>> Just for fun, it might be important, here is how my node info looks.
>>>   ComputeS01Parameters:
>>>     NovaReservedHostMemory: 16384
>>>     KernelArgs: "crashkernel=no rhgb"
>>>   ComputeS01ExtraConfig:
>>>     nova::cpu_allocation_ratio: 4.0
>>>     nova::compute::libvirt::rx_queue_size: 1024
>>>     nova::compute::libvirt::tx_queue_size: 1024
>>>     nova::compute::resume_guests_state_on_host_boot: true
>>> _______________________________________________
>>> users mailing list
>>> users at lists.rdoproject.org
>>> http://lists.rdoproject.org/mailman/listinfo/users
>>>
>>> To unsubscribe: users-unsubscribe at lists.rdoproject.org
>>>
>>
>
> --
> Ruslanas Gžibovskis
> +370 6030 7030
>


-- 
Ruslanas Gžibovskis
+370 6030 7030
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20200630/64a4c947/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compute.tar.xz
Type: application/octet-stream
Size: 28788 bytes
Desc: not available
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20200630/64a4c947/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: controller.tar.xz
Type: application/octet-stream
Size: 553908 bytes
Desc: not available
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20200630/64a4c947/attachment-0003.obj>


More information about the users mailing list