** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Confirmed
** Changed in: nova/stein
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Description
===
Create volume from image and boot instance, all good.
https://docs.openstack.org/newton/user-guide/cli-nova-launch-instance-
from-volume.html
Restart the compute host, VM fails to start. Manually run nova hard
reboot is able to recover.
The root
Reviewed: https://review.opendev.org/679852
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=88c7be55c221a87b4326a915580657f34d1ff582
Submitter: Zuul
Branch:master
commit 88c7be55c221a87b4326a915580657f34d1ff582
Author: Nate Johnston
Date: Tue Sep 3 15:56:59 2019
Public bug reported:
I reproduced the issue on an Azure VM with SLES12 SP4 and cloud-init 19.1.
The DNS is unreachable when cloud-init takes the responsibility of configuring
the network. No nameservers or search domains are added to the /etc/resolv.conf
as following:
; Created by cloud-init on
Reviewed: https://review.opendev.org/679483
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=fea2d9091f71a2ec88318121ed9a22180e1ae96f
Submitter: Zuul
Branch:master
commit fea2d9091f71a2ec88318121ed9a22180e1ae96f
Author: Mark Goddard
Date: Fri Aug 30 16:58:34 2019
Public bug reported:
Description
===
At present any exceptions encountered during post_live_migration on the source
after an instance has successfully migrated result in the overall failure of
the migration and the instance being listed as running on the source while
actually being on
OK, thanks for the logs. Could you re-attach those running via sudo (or
as root)? The default user on SLES does not have permissions to read
the journal.
What I see so far looks like networking did not come up after cloud-
init-local.service completes and writes out a network config.
Reviewed: https://review.opendev.org/679588
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8e062b3fb46dc7612e4337f86835bd05
Submitter: Zuul
Branch:master
commit 8e062b3fb46dc7612e4337f86835bd05
Author: chenxing
Date: Mon Sep 2 11:06:21 2019 +0800
Issue is related to local changes, marking invalid.
** Changed in: cloud-init
Status: Incomplete => Invalid
** Changed in: cloud-init (Suse)
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Error in "doc/source/user/flavors.rst"
In "Random-number generator" section
Currently reads:
"RATE-PERIOD: (integer) Duration of the read period in seconds."
Should read:
"RATE-PERIOD: (integer) Duration of the read period in milliseconds."
Please see:
Public bug reported:
This doc is inaccurate in this way:
"hw_rng:rate_period" is actually in *milliseconds*
See https://libvirt.org/formatdomain.html#elementsRng
---
Release: 16.1.9.dev7 on 2019-08-23 17:35
SHA: 6e2ec5c5a397b508cddb646e865b6f4d2132f1d6
Source:
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1813265
Title:
Documentation should use
Reviewed: https://review.opendev.org/681158
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c83e0750954798024212062a20bb5f90788ab2e
Submitter: Zuul
Branch:master
commit 2c83e0750954798024212062a20bb5f90788ab2e
Author: zhanghao2
Date: Tue Aug 13 17:11:08 2019 -0400
Public bug reported:
On openSUSE 15.x and Tumbleweed, network config fails due to a missing
network renderer. Adding 'opensuse-leap' and 'opensuse-tumbleweed' to
`KNOWN_DISTROS` solves the problem.
Please extend `KNOWN_DISTROS` to support newer versions of openSUSE.
** Affects: cloud-init
Public bug reported:
Glance metadefs is missing Nova image property :
hw_vif_multiqueue_enabled true|false
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
When executing "nova diagnostics " the output of
cpu_utilization shows null.
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
When executing "nova diagnostics " the output of
- cpu_utilization is null.
+ cpu_utilization shows null.
*** This bug is a duplicate of bug 1799904 ***
https://bugs.launchpad.net/bugs/1799904
** This bug has been marked a duplicate of bug 1799904
ICMPv6 is not an available protocol when creating Firewall-Rule
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Seen here:
https://openstack.fortnebula.com:13808/v1/AUTH_e8fd161dc34c421a979a9e6421f823e9/zuul_opendev_logs_c4c/671072/18/gate
/nova-tox-functional/c4ca604/job-output.txt
2019-09-11 16:01:31.460243 | ubuntu-bionic | {3}
Thanks for the bug and the logs. Looking at the network-config that was
generated:
>>> print(yaml.dump(nc, default_flow_style=False, indent=4))
ethernets:
eth0:
dhcp4: true
match:
macaddress: 00:0d:3a:6d:ca:25
set-name: eth0
nameservers:
Public bug reported:
While triaging a bug in sles'based distro using cloud-init, the collect-
logs output had a few issues:
1) the user did not have systemd journal privs
Unexpected error while running command.
Command: ['journalctl', '--boot=0', '-o', 'short-precise']
Exit code: 1
Reason: -
Public bug reported:
System-scope was introduced in Queens [0] but recently we discovered a
weird case where system users aren't able to do things they should be
able to with system-scoped tokens when domain-specific drivers are
enabled.
For example, they are unable to list groups or users
21 matches
Mail list logo
