[rdo][ussuri][TripleO][nova][kvm] libvirt.libvirtError: internal error: process exited while connecting to monitor
by Ruslanas Gžibovskis
Hi all.
I have finally deployed Ussuri, it went quite good, except some my site
specific issues and newton config files remake, but now I face issues when
launching an instance.
[4] Here are logs from compute: /var/log/containers/nova/nova-compute.log
[5] from the controller - nova-conductor.log
According to errors from compute, something is wrong with kvm?
some older bugs refer to kvm exec permissions [2]
a bit more recent [1] which refers to selinux issues, but I have setenforce
0 and tried to create instance, not much changed.
Also, [3] very interesting kvm.conf file updates suggested, but I am not
sure, how to restart service since config changed, as I am BRAND new to
container concept with docker/podman, bit more used to uml :) so, how to
reload service in container (when container is running as non-root user)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1551651 # related to RHOSP7
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1091710 # 6 year old.
[3]
https://ask.openstack.org/en/question/95198/could-not-access-kvm-kernel-m...
[4] http://paste.openstack.org/show/pBVlVbaQGNuoRLHozHGO/
[5] http://paste.openstack.org/show/OqvozreN5aW4HRXM4g4p/
--
Ruslanas Gžibovskis
+370 6030 7030
3 years, 9 months
Packstack, Centos 8 and NetworkManager
by Bernd Bausch
To install Ussuri, Packstack documentation[1] assumes Centos 8 or RHEL
8. However, it still wants me to disable NetworkManager. When I do that,
the Packstack loses all network configuration when rebooting, since
Centos 8 relies on NetworkManager to manage all aspects of networking.
Even after re-enabling NetworkManager and installing the NM OVS plugin,
br-ex remains down. Admittedly, I am quite clueless regarding the
management of OVS, with or without NetworkManager. Here are some of the
things I did (I also followed instructions for connecting Packstack to
the existing network[2]):
$ *cat /etc/sysconfig/network-scripts/ifcfg-br-ex*
NAME=br-ex
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=172.24.4.1
PREFIX=24
ONBOOT=yes
$ *sudo nmcli d set br-ex managed yes*
$ *sudo ip l set br-ex up*
$ *nmcli d*
DEVICE TYPE STATE CONNECTION
ens3 ethernet connected ens3
br-ex openvswitch disconnected --
$ *sudo nmcli d connect br-ex*
Error: Failed to add/activate new connection: Device class
NMDeviceOvsInterface had no complete_connection method
$ *sudo journalctl -u NetworkManager | grep br-ex*
Jun 07 10:51:45 ...: <info> [1591494705.5163] manager: (br-ex): new Open
vSwitch Interface device (/org/freedesktop/NetworkManager/Devices/2)
Jun 07 10:51:45 ...: <info> [1591494705.5578] device (br-ex): state
change: unmanaged -> unavailable (reason 'managed', sys-iface-state:
'external')
Jun 07 10:51:45 ...: <info> [1591494705.5598] device (br-ex): carrier:
link connected
Jun 07 10:51:45 ...: <info> [1591494705.9112] manager: (br-ex): new
Open vSwitch Port device (/org/freedesktop/NetworkManager/Devices/6)
Jun 07 10:51:45 ...: <info> [1591494705.9686] manager: (br-ex): new
Open vSwitch Bridge device (/org/freedesktop/NetworkManager/Devices/11)
Jun 07 10:51:46 ...: <info> [1591494706.0306] device (br-ex): state
change: unavailable -> disconnected (reason 'none', sys-iface-state:
'managed')
Any guidance?
[1] https://www.rdoproject.org/install/packstack/
[2]
https://www.rdoproject.org/networking/neutron-with-existing-external-network
3 years, 10 months
[Meeting] RDO meeting (2020-06-24)
by Amy Marrich
==============================
#rdo: RDO meeting - 2020-06-24
==============================
Meeting started by spotz at 14:03:00 UTC. The full logs are available
athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2020_06_24/2020/r...
.
Meeting summary
---------------
* Roll Call (spotz, 14:03:10)
* New faces in multiarch support (spotz, 14:06:11)
* RDO Test Days (spotz, 14:13:29)
* LINK: http://rdoproject.org/testday/victoria/milestone1/ (spotz,
14:13:47)
* ACTION: amoralej add RDO Test Days to next weeks meeting (spotz,
14:19:39)
* ACTION: spotz talk to jbrooks for possibility of swag/needed things
for RDO test days (spotz, 14:21:14)
* RDO Doc Days (spotz, 14:22:16)
* LINK: http://rdoproject.org/events/docdays/ (spotz, 14:22:30)
* ACTION: spotz to do initial leg work on Doc Days and report back
next week (spotz, 14:31:35)
* Next Week's Chair (spotz, 14:34:15)
* Open Floor (spotz, 14:36:56)
* LINK:
https://docs.openstack.org/placement/ussuri/install/verify.html
(spotz, 14:42:00)
* LINK:
https://review.rdoproject.org/r/#/q/project:openstack/placement-distgit
(amoralej, 14:52:58)
Meeting ended at 14:59:08 UTC.
Action items, by person
-----------------------
* amoralej
* amoralej add RDO Test Days to next weeks meeting
* spotz
* spotz talk to jbrooks for possibility of swag/needed things for RDO
test days
* spotz to do initial leg work on Doc Days and report back next week
People present (lines said)
---------------------------
* spotz (82)
* amoralej (65)
* mjturek (11)
* rdogerrit (7)
* openstack (6)
* jcapitao (2)
* baha (1)
Generated by `MeetBot`_ 0.1.4
3 years, 10 months
Re: [rdo-users] [neutron] subnet policy for ip allocation
by Ruslanas Gžibovskis
Hi all,
well, the problem here, for me, is that I do not manage switches from the
OSP part.
SO whenever I delete an instance, it frees up IP in the subnet, and that IP
is allocated to another machine, and thanks to the "arp table" feature in
the switch, switch send traffic to wrong compute as it remembers my
newly grabbed IP address on other port... and switches are very fancy, so
they do not have option to save arp for 1 min, 5 is the smallest amount.
I am just curious, am I only one who creates instances "so often"?
> Hi Ruslanas,
>
> The Neutron IP allocator does not do sequential allocation any more, it
> will choose randomly from a set of available IPs in the subnet. So the
> odds of this happening are small, although not zero. The only way to
> change this would be to write your own IPAM driver to do allocation in a
> specific way if that is required.
>
> -Brian
>
--
Ruslanas Gžibovskis
+370 6030 7030
3 years, 10 months
[Meeting] RDO meeting (2020-06-17) minutes
by Alfredo Moralejo Alonso
==============================
#rdo: RDO meeting - 2020-06-17
==============================
Meeting started by amoralej at 14:01:20 UTC. The full logs are
available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2020_06_17/2020/r...
.
Meeting summary
---------------
* roll call (amoralej, 14:01:38)
* FWaaS retirement in Victoria (amoralej, 14:05:53)
* LINK: https://review.opendev.org/#/c/735838/ (amoralej, 14:06:03)
* fwaas is being retired upstream and will be removed from RDO
(amoralej, 14:06:26)
* ACTION: projects using FWaaS from RDO should stop using it
(amoralej, 14:07:16)
* Install guide bugs for Ussuri - confirm and I'll put up ptaches
(amoralej, 14:09:19)
* LINK: https://docs.openstack.org/install-guide/ - has no release:(
(spotz, 14:17:17)
* LINK:
https://docs.openstack.org/install-guide/openstack-services.html
(spotz, 14:17:57)
* CentOS 8.2 is published (amoralej, 14:24:10)
* openvswitch 2.12.0 is not compatible with dpdk in 8.2 so we removed
dpdk support until we can rebuild it with it (amoralej, 14:25:08)
* proposal to move to FastDataPath rebuilds has been made
https://lists.centos.org/pipermail/centos-devel/2020-June/036996.html
(amoralej, 14:25:52)
* New version of libvirt in Advanced Virtualization required changes
in puppet-nova (amoralej, 14:26:37)
* LINK: https://review.opendev.org/#/c/730689 (amoralej, 14:26:56)
* CentOS 8.2 broke some TripleO-CI jobs (amoralej, 14:27:40)
* LINK: https://bugs.launchpad.net/tripleo/+bug/1883913 (amoralej,
14:27:57)
* LINK: https://bugs.launchpad.net/tripleo/+bug/1883692 (amoralej,
14:28:22)
* CentOS 8.2 introduced support for aarch64, we'll work in the missing
packages as rabbitmq-server (amoralej, 14:29:15)
* Ocata/Pike DLRN builders being cleaned (amoralej, 14:34:57)
* LINK:
https://lists.rdoproject.org/pipermail/dev/2020-May/009380.html
(ykarel, 14:36:20)
* LINK: https://review.rdoproject.org/r/#/c/28119/ (ykarel, 14:36:29)
* Next Week's Chair (amoralej, 14:40:56)
* ACTION: spotz to chair next meeting (amoralej, 14:42:17)
* open floor (amoralej, 14:42:40)
Meeting ended at 14:45:10 UTC.
Action items, by person
-----------------------
* spotz
* spotz to chair next meeting
People present (lines said)
---------------------------
* amoralej (95)
* spotz (29)
* ykarel (12)
* openstack (7)
* rdogerrit (6)
* jcapitao (3)
* cgoncalves (1)
Generated by `MeetBot`_ 0.1.4
3 years, 10 months
[neutron] subnet policy for ip allocation
by Ruslanas Gžibovskis
Hi team,
I need that my IP addresses in subnet would not be allocated from the
beginning, but it would go to the next IP compared to previous used:
instance1 created: 1.1.1.1
Instance2 created: 1.1.1.2
instance1 deleted.
instance2 deleted.
Instance3 created: 1.1.1.3 (not 1.1.1.1 again)
I remember have read about such, do not remember how to google it...
--
Ruslanas Gžibovskis
+370 6030 7030
3 years, 10 months
