Hi Rodolfo
Thanks for the heads up. I have verified and it seems correct that
neutron openvswitch agent reports the port correctly as "down:
2022-12-13 18:52:49.053 2955524 INFO
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-149353dc-53f3-48ca-97e1-ec4f47dc56e5 - - - - -]
Public bug reported:
having a vm with a provider network port that has it's status set to
"admin down" won't let this vm migrate successfully. the source compute
host will abort the migration with the following message:
Timed out waiting for events: [('network-vif-plugged',
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1854236
Title:
documentation for cc_set_hostname module doesn't
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1716868
Title:
config file is not read
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1575938
Title:
Instance path in / if instance-id starts with '/'
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1766856
Title:
wrong eni_path for debian
Status in cloud-init:
Public bug reported:
when using the module cc_apt_configure we need to make sure that gnupg
is installed before using apt-key add to add a certain apt key.
The most recent debian 10 cloud image from
https://cdimage.debian.org/cdimage/openstack/10.2.0/ is for example not
really happy when using
** Tags added: freebsd
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1380424
Title:
Missing Mock in
Public bug reported:
Since upgrading from Rocky to Stein we are experiencing problems live
migrating vm's with trunk ports and creating new trunk ports. The live
migrations of the vm itself eventually completes but the trunk ports
remain in the status "BUILD" or "DOWN". The corresponding subports
** Changed in: nova
Assignee: do3meli (d-info-e) => (unassigned)
** Changed in: nova
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
Public bug reported:
i have create a virtual machine using the following official debian
image: https://cdimage.debian.org/cdimage/openstack/current-10/
they have version 18.3-6 installed.
after the initial boot of the vm cloud-init works as it should. but when
a reboot occurred it seems to be
Public bug reported:
when importing a keypair via horizon gui while the corresponding project
quota limit is reached will automatically logout the current user and
redirect him to the login screen.
this has been testet with version openstack rocky on ubuntu 18 with the
cloud archive repository.
Public bug reported:
The util.py currently is not so FreeBSD friendly as it always prints the
following warnings:
2019-02-07 11:02:02,324 - util.py[WARNING]: Unable to determine
distribution, template expansion may have unexpected results
This is obviously getting printed for each stage and
Public bug reported:
The sample nova configuration file is most likely inaccurate as it still
references send_arp_for_ha and send_arp_for_ha_count which in my opinion
has been removed in pike release:
https://docs.openstack.org/releasenotes/neutron/pike.html
this needs to be confirmed and if
** Changed in: nova/pike
Status: Fix Committed => Fix Released
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
in the instance overview under either admin or project one does not see
attached ports that do no have an IP address set. for example:
1. create a port with following command:
openstack port create --network --no-fixed-ip test-port --project
my-project
2. attach the
Public bug reported:
We usually have 2 interfaces/ports per VM. 1 internal and 1 external
interface/port. On the external interface/port we do have 2 static IP
addresses assigned. one of them is an IPv4 and the other an IPv6.
However we do only see the IPv4 being shown in the instance overview of
attached is the full stacktrace of the compute node.
** Attachment added: "cap_stacktrace.txt"
https://bugs.launchpad.net/nova/+bug/1781916/+attachment/5164744/+files/cap_stacktrace.txt
** Changed in: nova
Status: Invalid => New
--
You received this bug notification because you are
Public bug reported:
Setting the following config on a compute host leads to a Stacktrace.
[upgrade_levels]
compute = auto
cells = auto
intercell = auto
cert = auto
scheduler = auto
conductor = auto
console = auto
consoleauth = auto
network = auto
baseapi = auto
Stacktrace:
2018-07-16
Public bug reported:
i am running cloud-init on commit id
c42a926ae730994f66fe87c264b65f6e4dca69a1 against a FreeBSD 10.4 Host an
getting the following stacktrace:
2018-07-02 11:40:18,158 - util.py[DEBUG]: Cloud-init v. 18.3 running 'init' at
Mon, 02 Jul 2018 11:40:18 +. Up 20.11459589
Public bug reported:
The documentation mentions the configuration option
live_migration_permit_auto_convergence while the actual config file uses
live_migration_permit_auto_converge. There seems to be some spelling
issues in the titles + text + config options.
Public bug reported:
Description
===
The nova scheduler log contains some HTML (see actual result). Log files should
not contain any HTML. I suspect some wrong error message parsing here.
Actual result
=
Log Message:
2018-04-19 13:12:53.109 12125 WARNING
Public bug reported:
- [X] This is a doc addition request.
The current live migration documentation [1] and the corresponding
configuration guide [2] do not mention any word about the cpu model and
flags requirements that are needed in order to successfully live migrate
an instance.
I believe
Public bug reported:
- [X] This is a doc addition request.
The current documentation topic "evacuate" in the admin guide is not
mentioning the host-evacuate command at all.
if one wants to evacuate all instances on a failed host it is easier to
use above command. As far as i understand the
set this to fix released as the current master branch seems to cover the
changes linked in the related branch.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
per default the salt minion does create the minion_id file with the
short hostname if it does not exist on its first startup. in some
environments the salt minion id is required to be a fully qualified
domain name. therefore i recommend to have a salt minion cloud-config
Public bug reported:
most of the integration tests are written for ubuntu and have hardcoded
paths, service names or package names that may are different on other
OS. it would be good to have the possibility to run integration tests in
another os than ubuntu. this would as far as i can tell
Public bug reported:
in its current behavior cloud-init does not set the hostname on FreeBSD
servers to it's FQDN if it is given. As per [1] FreeBSD Man Page for
rc.conf the hostname variable in rc.conf should be set to FQDN.
[1]
Public bug reported:
unfortunately the salt module is not working on FreeBSD as the service
name is not salt-minion but instead salt_minion. In addition the package
is called differently on freeshports. see:
https://www.freshports.org/sysutils/py-salt/
** Affects: cloud-init
Importance:
Public bug reported:
the resizefs module is not able to handle zfs/zpool resizing for the
root filesystem. if tried so we get the error message: "Could not
determine filesystem type of /".
version: cloud_init-17.1-py2.7.egg
** Affects: cloud-init
Importance: Undecided
Status: New
Public bug reported:
we are running horizon on an Ubuntu 16 cluster with the official repos
for the new pike release and figured out that the configuration file
/etc/openstack-dashboard/local_settings.py is no longer read.
it seems the symlink /usr/share/openstack-
31 matches
Mail list logo
