[Yahoo-eng-team] [Bug 1798048] Re: cant modify project quotas

** Also affects: centos Importance: Undecided Status: New ** No longer affects: centos -- 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/1798048 Title:

[Yahoo-eng-team] [Bug 1798055] [NEW] Cloud init rsyslog module will not start on FreeBSD

Public bug reported: Cloud Provider: Openstack Cloud init configuration is embedded in the attached archive Cloud init platform: FreeBSD FreeBSD image built using CLOUDWARE. Cloud init port (net/cloud-init) on FreeBSD will not load rsyslog module because is not in configuration file. **

[Yahoo-eng-team] [Bug 1798048] [NEW] cant modify project quotas

Public bug reported: error_log (httpd) [Tue Oct 16 04:42:47.473489 2018] [:error] [pid 4688] Traceback (most recent call last): [Tue Oct 16 04:42:47.473635 2018] [:error] [pid 4688] File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit [Tue Oct 16 04:42:47.473780 2018] [:error]

[Yahoo-eng-team] [Bug 1798172] [NEW] Ironic driver tries to update the compute_node's UUID which of course fails in case of existing compute_nodes

Public bug reported: The patch - https://review.openstack.org/#/c/571535 was introduced with the aim of keeping the same uuid value for ironic nodes and their corresponding compute_node records. This works fine for when new nodes are created. However upon restart/periodic updates from the ironic

[Yahoo-eng-team] [Bug 1798158] Re: Non-templated transport_url will fail if not defined in config

** Also affects: nova/rocky Importance: Undecided Status: New ** Changed in: nova/rocky Importance: Undecided => Medium ** Changed in: nova/rocky Status: New => Triaged ** Tags added: cells -- You received this bug notification because you are a member of Yahoo!

[Yahoo-eng-team] [Bug 1798184] [NEW] PY3: python3-ldap does not allow bytes for DN/RDN/field names

Public bug reported: Under Python 2, python-ldap uses bytes by default. Under Python 3 this is removed and bytes aren't allowed for DN/RDN/field names. More details are here: http://www.python-ldap.org/en/latest/bytes_mode.html#bytes-mode and here:

[Yahoo-eng-team] [Bug 1798158] [NEW] Non-templated transport_url will fail if not defined in config

Public bug reported: If transport_url is not defined in the config, we will fail to format a non-templated transport_url in the database like this: ERROR nova.objects.cell_mapping [None req-34831485-adf4-4a0d-bb20-e1736d93a451 None None] Failed to parse [DEFAULT]/transport_url to format cell

[Yahoo-eng-team] [Bug 1798172] Re: Ironic driver tries to update the compute_node's UUID which of course fails in case of existing compute_nodes

** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => High ** Also affects: nova/rocky Importance: Undecided Status: New ** Changed in: nova/rocky Status: New => Confirmed ** Changed in: nova/rocky Importance: Undecided => High

[Yahoo-eng-team] [Bug 1798189] [NEW] cloud-init query: /run/cloud/instance-data.json no regenerated on upgrade

Public bug reported: /run/cloud-init/instance-data.json & instance-data-sensitive.json not regenerated on upgrade. Between cloud-init from 18.3-9 -> 18.4.0 cloud-init transitioned from a single sensitive /run/cloud-init/instance-data.json that was read-only root to two separate files:

[Yahoo-eng-team] [Bug 1798188] Re: VNC stops working in rolling upgrade by default

One suggestion in IRC today was that we could add a "nova-status upgrade check" which iterates the cell DBs looking to see if there are any non- deleted/disabled nova-consoleauth services table records and if so, check to see if there are no console_auth_tokens entries in that DB and if

[Yahoo-eng-team] [Bug 1798188] [NEW] VNC stops working in rolling upgrade by default

Public bug reported: During a rolling upgrade, once the control plane is upgraded and running on Rocky (but computes still in Queens), the consoles will stop working. It is not obvious however it seems that the following is missing: ``` [workarounds] enable_consoleauth = True ``` There isn't a

[Yahoo-eng-team] [Bug 1798224] [NEW] DeprecationWarning: The behavior of .best_match for the Accept classes is currently being maintained for backward compatibility, but the method will be deprecated

Public bug reported: When executing 'tox -e py35', the following deprecation warning is shown. It should be fixed. 2018-10-16 03:36:49.117553 | ubuntu-xenial | {5} nova.tests.unit.api.openstack.compute.test_disk_config.DiskConfigTestCaseV21.test_update_server_override_auto [0.544275s] ... ok

[Yahoo-eng-team] [Bug 1798085] [NEW] [Fullstack] L3 agent should be run in host namespace, together with L2 agent

Public bug reported: In fullstack tests L3 agent is not running in host namespace currently. That works fine e.g. with Linuxbridge agent, which is spawned in host-XXX namespace when test is creating and connecting FakeVM as it is always done in this host namespace and agent can see it. However

[Yahoo-eng-team] [Bug 1794364] Re: 'nova-manage db online_data_migrations' count fail

** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) => iain MacDonnell (imacdonn) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1798117] [NEW] juju sends "network" top level key to user.network-config in lxd containers

Public bug reported: == Short summary == In lxd containers launched by juju, /var/lib/cloud/seed/nocloud-net/network-config has: has: network: config: disabled That is invalid content. Cloud-init assumes content in 'network-config' is already namespaced to 'network'. The correct content