** Changed in: keystone
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1451402
Title:
v3 - pagination in GET services does not work
Status in Keysto
** Changed in: horizon
Status: New => 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/1450814
Title:
Django 1.4 support ends Oct 1 2015. Tests should
** Changed in: horizon
Status: Confirmed => 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/1424616
Title:
A timeout on Chrome 40/ Ubuntu 14.10 causes
** Changed in: horizon
Status: In Progress => 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/1435929
Title:
Firewalls index page is missing header
S
** Changed in: horizon
Status: In Progress => 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/1411037
Title:
Inconsistent import naming
Status in Ope
Public bug reported:
1. Create two LB pools(pool1&2) and vip.
2. Add backend servers for this pool.
3. Update(Edit) member, select a member and change its pool name from pool1 to
pool2. then an error is printed.
Error: Failed to update member 43fb9987-7b3f-444e-b274-43b67b01f72d
actually, it ha
Public bug reported:
Similar to https://bugs.launchpad.net/horizon/+bug/1477100
In the admin's edit port view, binding:host_id is expected as part of the port
object. This gives a traceback when plugins don't use the port binding
extension.
...
File
"/usr/share/openstack-dashboard/opensta
Public bug reported:
nova version : 2015.1.1.-1.el7
The issue in the bug is that deleted one instance A using openstack cli
, the cli's reponse that the instances A has been deleted . however, the
instance A still can be shown . and It was not deleted successfully.
The issue is related to OVS s
Public bug reported:
openstack is installed with ubuntu 14.04, running siege tool/ssh/iperf
will be failed if overlay vm is using default MTU 1500, after change MTU
to 1450, then issue is fixed.
1. create LB pool and vip using same subnet (one-arm)
2. add 1 backend server and 1 client.
3. running
Public bug reported:
Defect:XB300349
New Note:
State: Open by: liujgwx on 28 August 2015 07:51:41
add setup infor
my setup is openstack RDO juno with docker
Controller
1) nsj13
PW: Lab4man1
Public IP: 158.85.164.68
Private IP: 10.53.87.252
Network Node
1) NSJ17
Public bug reported:
nova version : 2015.1.1-1.el7
Try to nova boot one instance on specific compute node. the instance is
in error state due to Invalid host found . openstack-nova-compute and
neuton-openvswitch-agent are running normally on the compute nodes .
[root@oc-perf-neutron-1 ~(keyston
Public bug reported:
2015-09-22 01:23:42.612 ERROR neutron.agent.dhcp.agent [-] Unable to disable
dhcp for c543db4d-e077-488f-b58c-5805f63f86b6.
2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent Traceback (most recent
call last):
2015-09-22 01:23:42.612 TRACE neutron.agent.dhcp.agent File
Public bug reported:
Problem:
OS:Ubuntu 14.04
openstack KILO with nova-docker
Nova-Docker:the compute service is in up status after stop the nova-compute
service(timeout=1 1 minute)
Steps:
1 Bring up the ubuntu kilo setup
2 Bring up the ubuntu docker setup
3 set the timeout to 1 minute
Public bug reported:
OS:Ubuntu 14.04
openstack KILO with nova-docker
Problem:Nova-Docker:container lost the ip address if docker restart
(DHCP assighend)
Steps:
1 Bring up the ubuntu kilo setup
2 Bring up the ubuntu docker setup
3 select one container
root@quasarucn1:~# docker ps
CONTAINER ID
Public bug reported:
OS:Ubuntu 14.04
openstack KILO with nova-docker
Problem:Nova-Docker:container lost the ip address if docker kill /
docker start (DHCP assighend)
Steps:
1 Bring up the ubuntu kilo setup
2 Bring up the ubuntu docker setup
3 select one container
root@quasarucn1:~# docker ps -a
Public bug reported:
Hi there!
I perfectly know that Nova is a required component for Horizon, however,
for all pages, if only Keystone is installed (ie: Nova isn't), there's
only a RED error message on the top-right of the web page, saying that
compute isn't installed. However, going to /project
** Changed in: neutron/icehouse
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1300785
Title:
[OSSA 2014-014] neutron allows security group r
** Changed in: horizon
Status: In Progress => 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/1292176
Title:
Re-enable network drag/drop for N1K
Stat
Public bug reported:
OS:Ubuntu 14.04
openstack KILO with nova-docker
NOVA-DOCKER-Glance: Docker image can't registe to glance with broken pipe.
steps:
===
1. deploy kilo setup with 10 docker compute node, 2 network node , 1
controller. all node are ubuntu 14.04 trusty build.
2. Register docke
** Project changed: nova => nova-docker
--
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/1498388
Title:
openstack Kilo Nova-Docker:the compute service status is still up
I believe it's fixed as of https://review.openstack.org/#/c/149686/
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1434378
With the SDNVE plugin being removed from the repository, this bug is now
invalid and won't be fixed
** 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 subscribed to neutron.
https://bu
with the removal of SDNVE plugin from the repo, this defect is now
invalid
** 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 subscribed to neutron.
https://bugs.launchpad.net/bugs/131
Public bug reported:
In #1160309 one inconsistency between Nova-Net and Neutron was fixed,
but there are two more places left, when Neutron may raise 404 error for
show_floatingip, but this is not handled by Nova -
get_floating_ips_by_project() and _get_floating_ip_by_address().
** Affects: nova
Public bug reported:
LBaaS API v2 tests don't add cleanup right after resources are created
they attempt to remove them at the end of the tests. In light of heavy
usage of class-level resources failure of any test leads to an
avalanche.
For example, breaking test_create_listener in test_listeners
** Also affects: oslo.vmware
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/1495429
Title:
Vmware: Failed to snapshot an inst
Public bug reported:
Using devstack with master branch, initially login to horizon was
working but after some time it start failing with error-->
ValidationError: [u"'867dfff16d6747848011a26f314e5345' value must be an
integer."]
Here 867dfff16d6747848011a26f314e5345 is the admin user id:-
| 867df
Public bug reported:
master, devstack, API v1
Steps to reproduce:
1. Create an image from empty location
glance image-create --location ''
ER: Bad Request
AR: internal server Error
** Affects: glance
Importance: Undecided
Assignee: Kairat Kushaev (kkushaev)
Status: New
** Cha
Public bug reported:
[Alchemy][LB_namespaceV1]after 817 tenants was create for namespace 1v1
maping, the new LB pool with pending_creat status
test step
1 create a tenant
2 create a pool network with subnet 10.1.1.0
create a vip network with subnet 20.1.1.0
3 create a router and add 2 inter
Public bug reported:
the default security groups is not allowed to be deleted,but all the rules are
allowed.
the default security groups is no used when no rule in it.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a membe
Public bug reported:
LB_NFV[Alchemy]LB performace just have 1 G low peformance than LB
bypass have 4G
setup infor
for LB bypass , client directly send traffic to server without LB , we have 4G
performance
and for LB, client send traffic with LB , we just have 1G traffic
so LB is a bottleneck
Public bug reported:
LB_NFV[Alchemy]iperf3 traffic was stoped after send traffice about
10-15s
root@instance-0002:/# iperf3 -c 20.1.1.100 -t 1000 -i 1 -p 5001
Connecting to host 20.1.1.100, port 5001
[ 4] local 20.1.1.200 port 59473 connected to 20.1.1.100 port 5001
[ ID] Interval
Public bug reported:
Running Kilo Stable version of OpenStack
While testing on a small OpenStack configuration using LVM as a backend
I have configured the /etc/lvm/lvm.conf on my hosts to reject all
devices except those on which the operating system is installed.
On the host where cinder-volume
** 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.net/bugs/1496135
Title:
libvirt live-migration will not honor destination vcpu_pi
Public bug reported:
1 create two-arm LB with 1client and 1 backend server on a tenant
2 repeat step1 to create 350 tenants
3 after step 2 , the LB network unstable
log and cpu infor
[root@nsj4 ~]# ip netns exec qlbaas-ade3e627-5fda-4781-855e-25a0f5217d17 ping
20.1.1.100
PING 20.1.1.100 (20.1.1
Public bug reported:
LB_NFV[Alchemy] linux kernel soft lockup after create 200 LB on sinalge tenant
with 30M traffic on each LB
CentOS Linux release 7.1.1503 (Core)
reproduce step
1 create 1 client and 1 backend server by docker container
2 create a lb and add backend as member
3 send 30M t
Public bug reported:
Icehouse release running on redhat 6.5:
1. try create image. the image will be stuck in queued status:
[root@EE204 ~]# glance image-list
+--+--+-+--+++
| ID
Public bug reported:
Steps:
1. controller + 2 compute setup. VPN running on compute nodes
2. create tenant/network/subnet/router/vpn setting
3. create multiple vpn session and corresponding vpn connections. check on
dashboard, found some vpn service is pending status.
Juno version
** Affects:
Public bug reported:
It's a display issue.
After create VPN connection on openstack dashboard, the vpn connection is shown
as "pending create". No matter create done or not.
walk around: manually refresh openstack dashboard webpage.
Juno version
** Affects: neutron
Importance: Undecided
** Also affects: neutron
Importance: Undecided
Status: New
** No longer affects: glance
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1498522
Title:
Some VPN service is "pend
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1498515
Title:
Glance stucked in queued status.
Status in Glance:
New
Bug description:
Icehouse release
Public bug reported:
LBaaS v2 API tests take a lot of time to run, for example
test_health_monitor_non_admin takes over 9 minutes [1] and
test_pools_non_admin - over 12 minutes [2]. These tests can be optimized
in order to decrease execution time.
[1]
http://logs.openstack.org/51/223651/3/check/
marking invalid as no updates in almost two years
** Changed in: neutron
Status: In Progress => 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/1229482
Title:
REST API res
marking invalid as it was incomplete and hasn't been updated in over a
year
** Changed in: neutron
Status: Incomplete => 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/10843
Public bug reported:
setup:
OS: ubuntu 14.04 based Juno
1 controller + 1 network node + 2 nova computer node + 1 docker node
vm 1-Router1(tenant1) ---router2(tenant2)|-vm2
10.4/24 10.1/24 42.4/26 42.5/26 20.1/24| 20.4/24
Public bug reported:
After clear router gateway the vpnaas site connection still show the
"active"
Setup:
OS: ubuntu 14.04 based Juno
vm 1-Router1(tenant1) ---router2(tenant2)|-vm2
1 controller + 1 network node + 2 nova computer node + 1 docker node
This isn't a bug, this is a support request. Please use
ask.openstack.org. It has an extremely active user base and you'll have
much better luck asking there.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
There are 3 primary places where client can be configured to reference
domains. The actual parameter names vary based on the configuration
interface (a function's arguments, the env, CLI arguments, etc), but
I'll use environment variables here for the sake of general familiari
Public bug reported:
Today, neutron log files include debug statements from imported
libraries that are not particularly useful.
Selected examples:
q-agt.log:
2015-09-21 05:58:50.765 ^[[00;32mDEBUG oslo_rootwrap.client
[^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mPopen for ['sudo',
'/usr/lo
You have been subscribed to a public bug:
At present nova doesnt exposes the uuid from libvirt as hypervisor-uuid. It
becomes an issue when we try to match with other service providers like Cisco
UCS.
Though there has been review put for this and it has been abandoned.
I think there is necessit
Public bug reported:
keystone 2014.2.2
using multi domains with one domain in AD ldap
group_filter does not work
user_filer (|(memberof=CN=group1)(memberof=CN=group2.))
works as expected, whereas
group_filter (|(CN=group1...)(CN=group2...))
returns no groups in id_mapping table.
openst
** Project changed: nova-garter => nova
--
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/1498125
Title:
Add hypervisor UUIDs to ComputeNode objects and API
Status in Open
This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.11
---
cloud-init (0.7.5-0ubuntu1.11) trusty; urgency=medium
[ Felipe Reyes ]
* d/patches/fix-consumption-of-vendor-data.patch:
- Fix consumption of vendor-data in OpenStack to allow namespacing
(LP: #1469260)
This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.11
---
cloud-init (0.7.5-0ubuntu1.11) trusty; urgency=medium
[ Felipe Reyes ]
* d/patches/fix-consumption-of-vendor-data.patch:
- Fix consumption of vendor-data in OpenStack to allow namespacing
(LP: #1469260)
Public bug reported:
The curvature network topology does not display the IP address for VM
and router network interfaces nor does it display the CIDR for the
network/subnet. This information was automatically displayed by the
old network topology layout. The only way to determine this IP addre
Public bug reported:
Cannot create multiple firewall per router.
While creating getting below message
stack@hdp-001:~$ neutron firewall-create policy-fw2 --name user-fw2
Router(s) [u'58d36628-e7a2-472d-b38d-0015117b519d'] provided already associated
with other Firewall(s).
** Affects: neutro
Anything that would vary between instances in a request like this is
being removed from the request spec sent to the scheduler. The
scheduler should not care about the specific instances being scheduled,
only the requested resources that the instance needs from a compute.
** Changed in: nova
Public bug reported:
The curvature network topology does not appear to add any scroll bars
when the diagram is too large (or zoom-ed in too much) to fit on the
screen. It seems like there should be some indication that part of the
canvas/diagram is currently scrolled off the view-able screen.
Public bug reported:
The old network topology supported "fly over" where the details on the
object would be automatically displayed when the cursor is placed over
that object. In the new curvature network topology, you need to select
each object in order for these details to be displayed.
Sligh
Public bug reported:
Fix a small set of comment typos in VPNaaS tree:
'valdiator'
'retreive'
'verison'
'ipser_site_connection'
** Affects: neutron
Importance: Undecided
Assignee: James Arendt (james-arendt-7)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Ja
** Changed in: os-brick
Status: Fix Committed => Fix Released
** Changed in: os-brick
Milestone: None => 0.5.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1494574
Title:
L
Public bug reported:
pep8 not running on api/openstack/common.py because
our exclude rule is exclude =
.venv,.git,.tox,dist,doc,*openstack/common*,*lib/python*,*egg,build,tools/xenserver*
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: In Progres
** Changed in: manila
Status: Fix Committed => Fix Released
** Changed in: manila
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1494574
Title:
** Changed in: manila
Status: Fix Committed => Fix Released
--
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/1493576
Title:
Incorrect usage of python-novaclien
** Changed in: manila
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/1384379
Title:
versions resource uses host_url which ma
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1497132
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1495645
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1491916
Title:
Improve IdP Specific WebSSO docs
Status in Keystone:
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1487937
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1488903
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1490354
Title:
Tox exhausting /tmp partition
Status in Keystone:
F
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1491854
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1418643
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1485604
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1488208
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1476347
Title:
LDAP Resource backend should be deprecated
Status in
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1484237
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1482330
Tit
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1450344
Title:
Invalid SQL Identity Assertion - Load Config from Dat
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1484735
Title:
Assertion signing error causes TypeError for Message o
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1460492
Tit
Public bug reported:
- Started devstack from master branch
- Created an instance which is backed by iscsi datastore on vsphere
Creating snapshot got stuck at "Image Uploading" state.
Noticed "Operation timed out" error while executing "Export OVF
template" task.
vpxd.log
2015-09-22T
Public bug reported:
Libvirt driver in Nova needs to add a check for min required qemu/libvirt
versions on ppc64/ppc64le.
The checks for ppc64/ppc64le are missing, so could lead to users deploying
Nova on
unsupported hypervisor platforms with older versions of qemu/libvirt.
QEMU/KVM is supporte
Public bug reported:
when updating the status of router's admin-state-up as false, its status
is not in DOWN state. However, its namespace cannot be seen under 'sudo
ip netns', but the status of that router is misleading.
steps to reproduce:
devstack@ubuntu:/opt/stack/neutron-vpnaas$ neutron rou
Public bug reported:
The logic to prevent SLAAC entries from being entered as hosts into the
lease DB[1] is preventing the hosts from getting name resolution from
dnsmasq.
1.
https://github.com/openstack/neutron/blob/7707cfd86f47dfc66411e274f343fe8484f9e250/neutron/agent/linux/dhcp.py#L534-L535
Public bug reported:
Issue has been reproduced in kilo.
There is a limitation when using VFIO with some PCI devices. Some PCI
devices with multiple hardware components are places in the same IOMMU
group (for example a NIC with multiple ports). In this case, the
multiple PCI devices in that same
Public bug reported:
Sorry about the vagueness, but here is a traceback that came up when I
was helping someone debug.
http://paste.openstack.org/show/465672/
It results in "AttributeError: 'NoneType' object has no attribute
'find'" which isn't too helpful. From what I could tell it was because
Public bug reported:
Steps to Reproduce:-
1) Create a few tenants(may be 4 to 5)
2) Create Networks,subnets, routers and connect them
3) Create vpnaas(site-to-site connection) in between two tenants
4) Boot up vms and docker containers behind the vpnaas
5) Send PING traffic between the docker con
Thanks Giri for filing the bug.
Yup, as I mentioned, the vCenters http read timeout needs to be
increased because there may be brief periods of time without any data
transfer as the ESX server is busing compressing the disk for streaming.
The http pipeline looks something like this and unfortunate
[Expired for neutron (Ubuntu) because there has been no activity for 60
days.]
** Changed in: neutron (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.ne
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1384109
Ti
Update:
Forget to mentioned there has a vpn tunnel there, so in this case, one vpn
tunnel between them. the setup like
vm1tenant1vpnaastenant2-vm2. And after the tunnel bring up, the
vm1 should ping the vm2, but the result is the vm2 dont receive the icmp
packets form vm1.
The
@Nikola, the problem is not about device names, but about consistency
and workability of volume backed instance snapshots.
Should we support a use case:
1 A user snapshots his volume backed instance which has more than one volume.
2 A user creates a new instance from the snapshot.
3 All services
Public bug reported:
# Using vagrant + virtualbox as the virtual machine provider.
# Vagrantfile contains the box definition as next:
config.vm.define "user" do |user|
user.vm.box = "ubuntu/trusty64"
user.vm.network "private_network", ip: "192.168.11.12"
Public bug reported:
Detail description and steps:
1. Configure vmware as the compute_driver in nova.conf, restart nova-compute
service.
2. Create a VM with command with "nova boot..."
3. Add a disk for VM to another datastore (the VM doesn't locate in this
datastore) in vcenter
4. Delete the VM
Public bug reported:
It always tries to use 169.254.169.254, which is fine in production, but
totally useless in testing.
The attached (trivial, two line, no copyright or code assignment
required) patch resolves this.
** Affects: cloud-init
Importance: Undecided
Status: New
** Att
96 matches
Mail list logo