e:
2023-05-17 14:30:30.493 7 ERROR ironicclient.common.http
[req-c8d567dc-7088-4bad-9a09-6ba33b6c7b4d 5ef38591b78a42928e8dfbdbaa90acd9
60d7786e349549eeb5a309b96251c789 - default default] Error contacting Ir
onic server: Node 2666c347-ff75-4c04-9059-9b890ad14b08 is locked by host
mark-ironic.novalocal, please r
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1733861
ystemd-networkd-wait-online.service, but that service
doesn't exist in RHEL 8.7, so systemd ignores that line.
You can see the timing issue in this excerpt from /var/log/messages:
Dec 2 18:27:04 mark-test-fs NetworkManager[723]: [1670005624.5790]
device (ens3): state change: ip-config -> ip-chec
h 28
07:43:14.217155 ARP, Reply 10.0.0.7 is-at fa:16:3e:63:d0:39, length 28
Thanks,
Mark
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https:
Added neutron to affected projects.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1922923
Title:
OVS port issue
St
Public bug reported:
# Steps to reproduce
As a non admin user, navigate to Identity -> Users. Then click on the
username of your user to go to the detail page.
# Expected results
Only the allowed Overview tab is visible.
# Actual results
The view shows three tabs: Overview, Role assignments,
Public bug reported:
Description
===
Due to the differences in nova, cinder and barbican policies described in bug
1895848, a user cannot migrate an instance with an encrypted volume (using
barbican) that belongs to a user in a different project. Furthermore, if a cold
migration or resi
Public bug reported:
Novnc-proxy will generate a URL for console access using a hard-coded
empty string for the path query argument. This causes issues when
exposing novnc-proxy through a reverse-proxy.
The current URL generation for novnc proxy uses the following to
construct the URL:
** Changed in: kolla-ansible/ussuri
Status: Fix Committed => Fix Released
** Changed in: kolla-ansible/train
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (k
** Changed in: kolla-ansible/victoria
Status: Fix Released => Triaged
** Changed in: kolla-ansible/ussuri
Status: Fix Committed => Triaged
** Changed in: kolla-ansible/train
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Y
Public bug reported:
# Description
Migration and evacuation fails with encrypted volumes, when the user is
in a different project to the instance creator, even if they are admin.
This is a common use case, since operators typically need to migrate
around instances. It also occurs with masakari du
*** This bug is a duplicate of bug 1744670 ***
https://bugs.launchpad.net/bugs/1744670
** This bug has been marked a duplicate of bug 1744670
In pike ssl deployment horizon cnt retrieve volumes/snapshots and service
data via cinderclient
--
You received this bug notification because you
** Changed in: kolla-ansible/victoria
Status: Triaged => Confirmed
** Changed in: kolla-ansible/victoria
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.ne
** Changed in: kolla-ansible
Milestone: 10.0.0 => None
** Changed in: kolla-ansible/ussuri
Milestone: 10.0.0 => None
** Also affects: kolla-ansible/victoria
Importance: Medium
Assignee: Radosław Piliszek (yoctozepto)
Status: In Progress
** Changed in: kolla-ansible/ussuri
** Also affects: kolla/rocky
Importance: Undecided
Status: New
** Changed in: kolla/rocky
Status: New => Triaged
** Changed in: kolla
Status: Confirmed => Invalid
** Changed in: kolla/rocky
Importance: Undecided => High
--
You received this bug notification because y
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
** Changed in: kolla-ansible/train
Status: New => Triaged
** Changed in: kolla-ansible/stein
Status: New => Triaged
** Changed in: kolla-ansible
Status: New => Triaged
** Changed in: kolla-ansible
Status: Triaged => Invalid
--
You received this bug notification beca
This affects Stein deploy jobs and Train upgrade jobs (due to Stein
images).
** Changed in: kolla-ansible/stein
Importance: Undecided => High
** Changed in: kolla-ansible/train
Importance: Undecided => High
** Also affects: horizon
Importance: Undecided
Status: New
--
You recei
Public bug reported:
Steps to reproduce
--
Create multiple instances concurrently using a flavor with a PCI
passthrough request (--property
"pci_passthrough:alias"=":"), and a scheduler hint with
some anti-affinity constraint.
Expected result
---
The instances are cr
Given the current size of the patch, we'll drop this from 9.0.0.
** Changed in: kolla-ansible/train
Milestone: 9.0.0 => None
** Changed in: kolla-ansible/train
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
execution of the
resource tracker update, which no doubt has some unintended
consequences.
Environment
===
Seen on Rocky 18.2.0, and master (in functional testing).
** Affects: nova
Importance: Undecided
Assignee: Mark Goddard (mgoddard)
Status: In Progress
** Changed in
nless the
node is orphaned
** Affects: nova
Importance: Undecided
Assignee: Mark Goddard (mgoddard)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Mark Goddard (mgoddard)
** Changed in: nova
Status: New => In Progress
--
You received th
** Also affects: kolla-ansible/ussuri
Importance: Medium
Assignee: Radosław Piliszek (yoctozepto)
Status: In Progress
** Changed in: kolla-ansible/ussuri
Milestone: 9.0.0 => 10.0.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
lit('.')
Tested on CentOS 7.7, cloud-init 18.5.
** Affects: cloud-init
Importance: Undecided
Assignee: Mark Goddard (mgoddard)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Mark Goddard (mgoddard)
--
You received this bug notification be
Thanks for fixing this.
** Changed in: kolla-ansible
Status: Triaged => Invalid
--
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/1843104
Title:
KeyError: 'def
It looks like this was caused by https://review.opendev.org/#/c/655208/,
which changes the handling of defaults for config in horizon. Since we
override the OPENSTACK_NEUTRON_NETWORK variable in local_settings.py,
but do not include the default for 'default_dns_nameservers'. A simple
workaround for
Public bug reported:
When a network is deleted, sometimes the delete_network_postcommit
method of my ML2 mechanism driver receives a network object in the
context that has the provider attributes set to None.
I am using Rocky (13.0.4), on CentOS 7.5 + RDO, and kolla-ansible. I
have three controll
Public bug reported:
Neutron bootstrap is currently failing on Ubuntu bionic (kolla-ansible-
ubuntu-source jobs) with the following error:
INFO [alembic.runtime.migration] Running upgrade 63fd95af7dcd -> c613d0b82681
Traceback (most recent call last):
File
"/var/lib/kolla/venv/lib/python3.6/
** Changed in: kolla-ansible/stein
Status: Fix Committed => Fix Released
** Changed in: kolla-ansible/stein
Status: Fix Released => In Progress
** Changed in: kolla-ansible/rocky
Status: Fix Committed => In Progress
** Changed in: kolla-ansible
Status: Fix Committed =
** Changed in: kolla/stein
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).
https://bugs.launchpad.net/bugs/1832860
Title:
Failed instances stuck in BUILD sta
Public bug reported:
Description
===
When performing an upgrade, services cap their RPC version when
communicating with nova-compute to that of the compute service with the
lowest version. Once all computes are running the new version, we can
restart the services to remove this cap.
When
Public bug reported:
When performing an upgrade, the upgrade check is supposed to be run
after the DB schema syncs and data migration. This should be something
that is checked by the upgrade check command.
Steps to reproduce
==
Tested in Queens -> Rocky upgrade.
Prior to an upgr
** Changed in: kolla-ansible
Milestone: None => 8.0.0
** Project changed: kolla-ansible => kolla
** Changed in: kolla
Milestone: 8.0.0 => None
** No longer affects: kolla-ansible/rocky
** Changed in: kolla
Importance: Undecided => High
** Also affects: kolla/rocky
Importance: Und
Some things to note:
I'm pretty confident that the DB sync had been run using the rocky nova-
api container prior to the upgrade.
The 'missing' trusted_certs column did exist in the instance_extra table
in the nova DB prior to performing the workaround DB sync.
No restart of services was necessa
Public bug reported:
- [x] This doc is inaccurate in this way: Wrong use of the word "comprise"
- [ ] This is a doc addition request.
- [x] I have a fix to the document that I can paste below including example:
input and output.
"Nova is comprised of multiple server processes"
"to comprise" me
** No longer affects: kolla
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763608
Title:
Netplan ignores Interfaces without IP Addresses
Status in netplan:
Fix Committed
Status in ne
** Changed in: kolla-ansible
Status: New => In Progress
** Changed in: kolla-ansible
Importance: Undecided => High
** Changed in: kolla-ansible
Assignee: (unassigned) => Mark Goddard (mgoddard)
** Also affects: kolla-ansible/stein
Importance: High
Assignee: Mar
** Changed in: kolla-ansible/ocata
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).
https://bugs.launchpad.net/bugs/1682060
Title:
empty nova service and hype
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1823818
Title:
Memory leak in some neutron agents
Status in kolla:
** Project changed: kolla => kolla-ansible
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1821696
Title:
Failed to start instances with encrypted volumes
Status in koll
I don't think this is a kolla bug. Marking invalid for kolla.
** Changed in: kolla
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763608
Title:
Netplan ig
nova
Importance: Undecided
Assignee: Mark Goddard (mgoddard)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1794773
Title:
Unnecessary
Public bug reported:
The OpenStack data source in cloud-init 18.3 was updated to detect
OpenStack systems before probing the metadata endpoint. This broke for
several cloud platforms (e.g. LP: #1784685) and is also broken for
VMware.
As can be seen in LP: #1669875 there is no way to discern OpenS
Public bug reported:
Logs show:
2018-03-05 20:50:01.665 35 WARNING stevedore.named [-] Could not load uuid
2018-03-05 20:50:01.666 35 CRITICAL keystone [-] Unhandled error: ImportError:
(u'Unable to find %(name)r driver in %(namespace)r.',
{'namespace': 'keystone.token.provider', 'name': 'uuid'
ronment
===
Nova stable/queens @ 01b756f960ed19ab801994d08d749dd94d729a22
** Affects: nova
Importance: Undecided
Assignee: Mark Goddard (mgoddard)
Status: New
** Changed in: nova
Assignee: (unassigned) => Mark Goddard (mgoddard)
--
You received this bug notificat
Public bug reported:
Per the discussion in [1], the ironic nodes added to the node cache in
the ironic virt driver may be missing the required field resource_class,
as this field is not in _NODE_FIELDS. In practice, this is typically not
an issue (possibly never), as the normal code path uses a de
Public bug reported:
Environment: Ubuntu 16.04.3 LTS, Ocata
Summary:
For each new stack created records automatically created for each instance,
on the other hand, deleting the stack doesn't trigger the deletion of those
records.
We have configured internal dns integration using designate,
cre
Public bug reported:
Description
===
Sometimes when a baremetal instance is terminated, some VIFs are not
detached from the node. This can lead to the node becoming unusable,
with subsequent attempts to provision it fail during VIF attachment due
to there being insufficient free ironic po
Public bug reported:
Description
===
A baremetal (ironic) instance can become stuck in the BUILD state if the
ironic node to which the instance has been assigned is either deleted or
torn down manually while the instance is being built.
Steps to reproduce
==
* Create a n
** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1665719
Title:
330_enforce_mitaka_online_migrations bl
Public bug reported:
A few weeks back, I followed the Newton Install Guides, and had no major
issues getting OpenStack to work (in its entirety). When I commissioned
up a 2nd Compute Node, none of the VMs would instantiate. After quite a
bit of debugging, I realized that libguestfs was the issue
Public bug reported:
Environment
===
1. Exact version of OpenStack you are running.
openstack-nova-compute-14.0.0-1.el7.noarch
libvirt-daemon-1.2.17-13.el7_2.5.x86_64
qemu-kvm-ev-2.3.0-31.0.el7_2.21.1.x86_64
2. Which storage type did you use?
Ceph
3. Which networking type d
Public bug reported:
When trying to boot and delete instances (Rally) saw this stack trace:
2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance:
47fbd50b-94ec-4395-884c-9131e0e3f335] File
"/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager
** Also affects: opnfv
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1561540
Title:
Neutron dhcp agent not able to provide dhcp ip to VM
Sta
json#n1379
[3] https://bugs.launchpad.net/neutron/+bug/1577410
** Affects: defcore
Importance: Medium
Assignee: Mark T. Voelker (mvoelker)
Status: New
** Affects: glance
Importance: Undecided
Assignee: Mark T. Voelker (mvoelker)
Status: New
** Also affects:
l mapping because of this.
See 'nova/objects/instance_mapping.py'
** Affects: nova
Importance: Undecided
Assignee: Mark Doffman (mjdoffma)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
ck/defcore/tree/2016.01.json#n117
[2] http://git.openstack.org/cgit/openstack/defcore/tree/2016.01.json#n1379
[3] https://etherpad.openstack.org/p/newton-neutron-future-neutron-api
** Affects: neutron
Importance: Undecided
Assignee: Mark T. Voelker (mvoelker)
Status: New
** Chan
are saved in raw. However we are
able to upload images in qcow2 nonetheless.
Thank you,
Mark Donovan
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https
/openstack/nova/blob/master/nova/scheduler/weights/affinity.py#L49
** Affects: nova
Importance: Low
Assignee: Mark Doffman (mjdoffma)
Status: New
** Tags: scheduler
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Assignee: (unassigned) =&
Public bug reported:
$ nova baremetal-node-list
ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-78138575-cdcc-408e-a232-dc717bfe96d9)
Nova API log.
2016-02-19 15:38:04.507
: nova
Importance: Undecided
Assignee: Mark (rocky-asdf)
Status: New
** Tags: compute nova
** Changed in: nova
Assignee: (unassigned) => Mark (rocky-asdf)
** Tags added: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
Public bug reported:
When creating an image with the swift backend, the swift object URL
(including password) is logged at debug level in the registry log. The
locations field is currently censored, but location_data is not.
Example:
# glance image-create --name test --disk-format raw --containe
Thank you for the suggestion, I updated the same.
** Project changed: nova => python-novaclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1533139
Title:
there is u
inf]
reproduceable bug
[Attachment]
None
** Affects: nova
Importance: Undecided
Assignee: Mark (rocky-asdf)
Status: New
** Changed in: trove
Assignee: (unassigned) => Mark (rocky-asdf)
** Project changed: trove => nova
--
You received this bug notification because y
rivate_key
_Reasons.UNSUPPORTED_ELLIPTIC_CURVE
cryptography.exceptions.UnsupportedAlgorithm: This backend does not support
this elliptic curve.
** Affects: nova
Importance: Undecided
Assignee: Mark McLoughlin (markmc)
Status: In Progress
--
You received this bug notification because you are a
Public bug reported:
It appears that https://review.openstack.org/256069 took the
signature_utils modules from Glance and modified it in fairly
superficial ways based on review feedback:
$ diff -u nova/nova/signature_utils.py
glance/glance/common/signature_utils.py | diffstat
signature_util
Public bug reported:
A recent change [1] made the wiring super restrictive to network: and
neutron: this resulted in external systems that use other device owners
from getting wired.
[1] https://review.openstack.org/#/c/193485/
** Affects: neutron
Importance: Medium
Assignee: Mark
'notifications.info' isn't something specific to nova. Notifications
queue is shared between projects.
** Project changed: nova => oslo.messaging
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bu
** Changed in: neutron
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1236439
Title:
switch to use hostnames like nova breaks upgrades of l3-agent
Public bug reported:
When the compute resource tracker checks nodes, the ironic driver checks
the node against a list of states that it should return resources for.
This is to prevent nodes in various ironic states, like our cleaning
process, that are not available from being scheduled to by nova.
Belive that for now this is invalid. There is code that is superficially
similar between the 'detach' code in manager.py and the block_device
attach function, but there are subtle differences. The code in
manager.py calls roll_detach on failure, which I believe is
inappropriate for the block_device
new ports to instance info cache
---
Request:
- Refresh instance network cache with new interfaces (get_instance_nw_info)
- Unconditionally add duplicate interfaces to cache.
** Affects: nova
Importance: Undecided
Assignee: Mark Goddard (mgoddard
If you look at
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4628
you can see the three different functions used for getting available disk space.
'get_volume_group_info'
'get_pool_info' and
'get_fs_info'
All of these methods are going to return the ACTUAL disk space
*** This bug is a duplicate of bug 1405367 ***
https://bugs.launchpad.net/bugs/1405367
This has been fixed and will be available in the liberty release.
** This bug has been marked a duplicate of bug 1405367
Rbd backend doesn't support disk IO qos
--
You received this bug notification be
Assuming you haven't seen any more of these since changing your ceph
config, lets close this one as invalid.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comput
Clearly an issue with novaclient help rather than nova.
** Project changed: nova => python-novaclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1497151
Title:
erro
https://blueprints.launchpad.net/neutron/+spec/mtu-selection-and-
advertisement
Blueprint for Neutron goes in to detail about how instances should get
the correct MTU value (Via DHCP or otherwise). If the MTU value is not
supplied for Neutron then the instance has no way of determining what
the co
LIkey a support request, not likely a bug with nova but possibly a
support question or problem with openstack-chef. Could you try asking
for support from openstack-chef.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
En
Probably shouldn't be stopping a VM not through openstack. Doing so not
supported.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.
Sorry to try and bring this one back to life, but i'm just not sure that
its really invalid. Marked https://bugs.launchpad.net/nova/+bug/1494617
as duplicate.
Seems that for the images api this now implements the empty list .
However I think that for flavors and servers api Ithat the behavior is
s
*** This bug is a duplicate of bug 794730 ***
https://bugs.launchpad.net/bugs/794730
** This bug has been marked a duplicate of bug 794730
API doesn't specify what limit=0 means
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
Concurrently attaching multiple network interfaces to a single instance
can often result in corruption of the instance's information cache in
Nova. The result is that some network interfaces may be missing from
'nova list', and silently fail to detach when 'nova interface-deta
Public bug reported:
In a configuration using the dhcp_agent.ini setting
enable_isolated_metadata = True
When creating a network configuration that is *not* isolated it has been
observed that the dnsmasq processes are being configured with static
routes for the metadata-service (169.2
Public bug reported:
In the nova scheduler (and nova-cells) the filters report debug level
logging on what decisions each filter makes on the hosts(cells). The
weighers, however, only give the combined weight after all have been
applied. As an operator, I want to be able to see the weight each
wei
onfig file actually
specify a unit of time:
# Default lock timeout for distributed locking. (integer
# value)
#default_lock_timeout=5
** Affects: keystone
Importance: Undecided
Assignee: Mark T. Voelker (mvoelker)
Status: In Progress
** Changed in: keystone
Assignee: (unass
Public bug reported:
With syslog enabled on Juno (enable_syslog=True in glance-api.conf),
glance spins on startup, consuming all available CPU cycles.
With some carefully placed calls to exit(), the line in glance causing
the problem was determined to be
https://github.com/openstack/glance/blob/s
enstack/nova/commit/4837c42127b87acdaf6f68d1e8956bba9a6b3fd2#diff-9285e4a9e182215df250d22736c79824R420
** Affects: nova
Importance: Undecided
Assignee: Mark T. Voelker (mvoelker)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Mark T. Voelker (mvoe
Public bug reported:
See https://bugs.launchpad.net/ironic/+bug/1405131 for an equivalent bug
in ironic that describes the issue.
The bug itself resides in nova, but requires cooperation from ironic in
order to fix it.
I have attached a patch that we are using internally to resolve the
issue. It
Public bug reported:
Seen on RDO Juno, running on CentOS 7.
Steps to reproduce:
- Set admin_workers=1 and public_workers=1 in /etc/keystone/keystone.conf
- Start the keystone service: `systemctl start openstack-keystone`
- Start a 'persistent' TCP connection to keystone: `telnet localhost 5000 &
Public bug reported:
I've been successfully using cloud-init 0.7.4 in a centos 6.5 image I
created under an icehouse environment we're running. When I recently
created a new centos 6.5 image and yum installed cloud-init (from
http://download.fedoraproject.org/pub/epel/6/x86_64) , I got 0.7.5
(clou
Public bug reported:
use 2014.2. RDO build.
Launch one instance. But it got a error. Detail info can not be got by
server-name.
[root@compute_1_basefunc ~]# nova list --all-tenants
+--+-+++-+--+
| ID
** Changed in: openstack-chef
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1279000
Title:
db migrate script to set charset=utf8 for all tables
St
Public bug reported:
Use CLI (nova list --tenant TENANT) to obtain some tenant's instances-list. But
as a result, it displays as same as CLI (nova list, no appointed tenant).
I want to get instances list within tenant "xwj01". But it shows intances-list
within tenant "admin"(source file).
[root@
: High
Assignee: Mark McClain (markmcclain)
Status: In Progress
** Tags: neutron-core xml
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1380787
Title:
remove XML support
Public bug reported:
During testing, we've found some instances of leftover router ports.
The ports are not properly cleaned up when a router is removed. The
user is able to manually remove the ports to work around the issue.
** Affects: neutron
Importance: High
Assignee: Mark Mc
Public bug reported:
The Juno capstone migration is missing.
** Affects: neutron
Importance: Critical
Assignee: Mark McClain (markmcclain)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
If a tenant wants to change the characteristics of a router port they
have to clean up resulting mess. I don't see this as a bug.
** Changed in: neutron
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is sub
It sounds crazy to me to close a connection at the earliest possible
opportunity. The point of HTTP 1.1 is for clients and servers to be able
to keep connections open and reuse them as much as possible.
>From RFC 2616
"8.1.2.1 Negotiation
An HTTP/1.1 server MAY assume that a HTTP/1.1 client i
I like the idea of making the default container format 'bare' in the
server as well. I think that would save a lot of the headache that is
experienced by client users.
We could do one of two ways:
#1 in glanceclient, during image-create, if data is given (--copy-from or
--file or --stdin), but
Jin,
What's wrong with the v2 output?
FWIW, we're probably not in a position to make the error output
consistent across api versions, if that is what you're asking for.
** Changed in: glance
Status: New => Won't Fix
** Also affects: python-glanceclient
Importance: Undecided
Sta
1 - 100 of 419 matches
Mail list logo
