Public bug reported:
When starting devstack, the following error occurs.
ERROR glance.db.sqlalchemy.metadata [-] Failed to parse json file
/etc/glance/metadefs/compute-vmware.json while populating metadata due
to: Expecting property name enclosed in double quotes: line 212 column 9
(char 8173): j
This bug was fixed in the package neutron - 2:16.0.0~b3~git2020041516
.5f42488a9a-0ubuntu3
---
neutron (2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu3) groovy; urgency=medium
* d/p/monkey-patch-original-current-thread.patch: Cherry-picked from
https://review.opendev.org/724753. T
Public bug reported:
We have 47-ish documentation examples of useful cloud-config in
doc/examples/*txt.
We need to ensure each cloud-config example contains the necessary
#cloud-config header and
add a unit tests which will run
cloudinit.config.schema:validate_cloudconfig_schema over all thos
Public bug reported:
As we implement jsonschema definitions in cloud config modules
(cloudinit.config.cc_*.py) we need a unittest which will automatically
run schema validation on cc_*.py modules.
Add a unittest to tests/unittests/test_handler/test_schema.py that will
discover all config modules
horizon has fixed the issue but unfortunately the fixes are not linked with it.
I am summarizing the fixes.
Multiple fixes are involved in the master branch (i.e. ussuri), so fixes in the
stable/train branch would be better for the summary.
The related fixes in stable/train are as follows:
- 981
heat is affected as well:
https://storyboard.openstack.org/#!/story/2007614
** Also affects: swift
Importance: Undecided
Status: New
** Also affects: swift (Ubuntu)
Importance: Undecided
Status: New
** Also affects: heat (Ubuntu)
Importance: Undecided
Status: New
-
Public bug reported:
Cloud-init version 20.1-10-g71af48df-0ubuntu5 from a core20 image
I added a file called 98_nocloud.cfg that looks like this:
--
#cloud-config
datasource_list: [ NoCloud, None ]
datasource:
NoCloud:
user-data: |
#cloud-config
users:
- name: ubu
Public bug reported:
I'm using an ISO with the following yaml in network-config. cloud-init
will not match eth0, but will match eth1 due to capitalization.
version: 2
ethernets:
eth0:
match:
macaddress: 00:15:5D:0E:AE:0C
set-name: External
eth1:
match:
macaddress: 00:1
This bug was actually fixed in https://review.opendev.org/#/c/420060/
Closing as Fix Released.
** Changed in: nova
Status: Confirmed => 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 first sentence of the Analyze section of the CLI docs:
https://cloudinit.readthedocs.io/en/latest/topics/cli.html#analyze
...there is a link that should point to this top-level document on the
behavior of Analyze:
https://cloudinit.readthedocs.io/en/latest/topics/analy
** Also affects: nova (Ubuntu Groovy)
Importance: High
Status: Fix Released
** Also affects: glance (Ubuntu Groovy)
Importance: High
Status: Fix Released
** Also affects: cinder (Ubuntu Groovy)
Importance: High
Status: Triaged
** Also affects: neutron (Ubuntu Groovy
Public bug reported:
As a newcomer to cloud-init, the module documentation has been extremely
helpful in laying out the options I can utilize. However, I often have
to ask myself if i need to do something as a runcmd script rather than
utilize a module, since the documentation doesn't clarify what
Public bug reported:
When running `cloud-init analyze show` against a log file from an Amazon
Linux 2 instance (e.g. https://pastebin.com/uhJNysgm), no useful output
is produced:
$ cloud-init analyze show -i ~/Downloads/uhJNysgm.txt
-- Boot Record 01 --
The total time elapsed since completing an
Public bug reported:
Since #114 all network interfaces get IPs and a default route, with a
metric based on `nic_idx`. `nic_idx` isn't derived from the EC2 device-
number, but from sorting by MAC address:
https://github.com/canonical/cloud-
init/blob/6600c642af3817fe5e0170cb7b4eeac4be3c60eb/clou
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Importance: Undecided => High
** Changed in: neutron (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Description
===
There is no validation of the provided disk_bus in the API, with libvirt
this eventually leads to the driver and hypervisor eventually ignoring
the requested disk_bus and defaulting to virtio.
Steps to reproduce
==
A common mistake fo
16 matches
Mail list logo
