Public bug reported:
Kolla-Ansible 8.0.1 Stein installation on CentOS
We ran into an issue where Ubuntu images would not launch Cloud-Init
when deployed. This started after we added the file:
/etc/nova/release
with the contents:
[Nova]
vendor = Company
product = Company Cloud
package = ""
Public bug reported:
OpenStack Stein deployed with Kolla Ansible on CentOS 7
This has likely been mentioned before, but it seems obvious that drop-
downs should be sorted. Long lists like flavors, volume types, etc.
that are in random order are almost unusable.
An example is - all of the
Adding the Kolla Ansible project since it appears that FWaaSv2 is broken
when using DVR. Kolla Ansible may want to have a flag to prevent
FWaaSv2 from installing if DVR is also being used.
Hopefully there is a quick fix, but it doesn't look like it after
reviewing the code.
** Also affects:
Public bug reported:
This might be a duplicate of:
https://bugs.launchpad.net/neutron/+bug/1798577
however, I see the same issue with floating IPs and DVR, not just SNAT.
This breaks the FWaaSv2 service, resulting in no filtering.
Deployment uses Kolla Ansible 8.0.1 (Stein) on CentOS, which
Added to Neutron group. This is easily reproducible, but if more
information is needed, please let me know.
Thanks!
Eric
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Description
===
Cold migration of a VM failed, so I tried resizing, and the same error
occurred.
Previous to this, I had disabled the compute service on one node, to see
if cold migrating VMs would avoid scheduling the VMs on the disabled
node. This succeeded a few
Public bug reported:
Description
===
After stopping the nova-compute service on a node, powering on VMs that were in
a shutoff state, but assigned to the compute node where the compute service is
no longer running, are powered on the host where the nova-compute service is
stopped,
Public bug reported:
Description
===
Note that this may be a Neutron issue, but since it is happening during
live migration, I wanted to point it out to the Nova group first, and
let them decide whether to include the Neutron group on this ticket.
Also note that this may not be related
Public bug reported:
Steps to reproduce
==
Set network throttle properties of a flavor to something large, such as 40Gbps
(specified in KiB per second):
quota:vif_inbound_average='4882813', quota:vif_outbound_average='4882813'
Launch an instance.
Easy to reproduce. Lowering
Public bug reported:
Environment:
Kolla-Ansible (built from stable/rocky branch)
Kolla (built from stable/rocky branch)
CentOS 7.5 with latest updates
Openstack Client returns version: openstack 3.15.0
I'm not sure where to report this, so please reassign if it is more
appropriate elsewhere.
I think I may have found the issue.
Note that I wasn't sure what other project/sub-project to add this
ticket to, so I will add it to the Neutron project.
We use team interfaces with VLANs, which uses the same MAC address for each
VLAN (see the bottom of this note for an example of 3 VLANs on
Public bug reported:
Environment: Queens installed using Kolla Ansible 6.1.0 on CentOS 7.5
I created a rule in the Keystone policy.json that should match a custom
role (domain_admin) and match the domain_id. I tried 4 variations, only
the last variation worked, which has the domain_id
Public bug reported:
Environment is Kolla-Ansible 6.1.0 deployed (Queens) on physical
hardware (Xeon Gold 6154 compute nodes).
Deploying an image with the following flavor (for a "nano" sized
instance) does not throttle the single vCPU to 1/10th of a physical
thread or core. The VM has full
13 matches
Mail list logo
