Now if a user want to delete the snapshot which is created by back-end
instance, he should delete both the image in Glance and the snapshot in
Cinder.
So do you think that when delete the image, Glance should delete the
snapshot in Cinder?
** No longer affects: nova
--
You received this bug not
** Changed in: glance
Status: New => Opinion
--
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/1521466
Title:
volume snapshot which is created by create snapshot fr
** Changed in: glance
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/1521467
Title:
Snapshot of volume base instance shows type as image no
Public bug reported:
Nova API only supports list servers searching by flavor and image ID. So
OSC only supports this. But the doc of the command help doesn't tell the
user that they can only specify the ID.
** Affects: nova
Importance: Undecided
Status: Invalid
--
You received thi
Well, sorry. Wrong place... Please ignore this. It should be sent to
OSC. :)
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
** Also affects: nova
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/1521466
Title:
volume snapshot which is created by crea
When create images for volume back-end instances, the image's size is
0. It's not a bug as I know, because in this action, cinder create d a
backup volume and then glance create a image of which properties
contained the backup volume's information.
I'm not sure the behavior "the type is Image, no
Public bug reported:
It would be highly valuable for a user to be able to run cloud-init with
custom user-data using local datasource post deploy e.g:
1# juju deploy myservice
2# juju scp user-data.yaml
myservice/0:/var/lib/cloud/seed/nocloud-net/user-data2
3# juju run --service myservice "/
[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/1009215
Ti
Public bug reported:
Reproduce Step:
1. Create an instance holly-vm1 base on storage volume(xiv use here).
2. Create a snapshot from the instance in step1.
3. List the images and found 2 problems:
a, the type of holly-vm1-snapshot is "Image", which should be "Snapshot"!
b, the size of holl
Public bug reported:
Reproduce Step:
1. Create an instance holly-vm1 base on storage volume(xiv use here with 2
volumes).
2. Create a snapshot from the instance in step1.
3. Found snapshot holly-vm1-snapshot under image list.
4. Found 2 volume snapshots under volume snapshot page.(snapshot for
h
Public bug reported:
I boot an instance with ephemeral disk(or swap disk) in kilo, but return http
request error:
eg：
nova boot --flavor 2 --image 5905bd7e-a87f-4856-8401-b8eb7211c84d --nic
net-id=12ace164-d996-4261-9228-23ca0680f7a8 --ephemeral size=5,format=ext3
test_vm1
ERROR (BadRequest):
Public bug reported:
Enabled Read-only LDAP backend, and accessed horizon using the LDAP user
and domain named domain1.
But I found the function of Project->Access & Security->API Acess-> Download
Openstack RC File did not support domain setting now.
Using download RC file, since it does not in
Public bug reported:
Based on the API:
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.VirtualDiskManager.VirtualDiskAdapterType.html
There is no paraVirtualscsi Constant, so it is rejected by the API as "A
specified parameter was not correct".
in nova/virt/vmwareapi
unassigning due to inactivity and failing patch sets, also this doesn't
affect keystoneclient
** Changed in: python-keystoneclient
Status: Triaged => Invalid
** Changed in: keystone
Status: In Progress => Confirmed
** Changed in: keystone
Assignee: Marek Denis (marek-denis) =>
Reviewed: https://review.openstack.org/245230
Committed:
https://git.openstack.org/cgit/openstack/api-site/commit/?id=256610411a7826f67bd9ed79438b6da0529eae41
Submitter: Jenkins
Branch:master
commit 256610411a7826f67bd9ed79438b6da0529eae41
Author: Diane Fleming
Date: Fri Nov 13 10:56:51 2
In v1 , we use "--is-public True(or False)". In v2, we use "--visibility
public(or private)".
The client's default api version is 2 now. So you should use --visibility.
The doc is ok. You can find "glance image-create (v1)" and "glance
image-create (v2)" in it.
Please check again.
** Changed
Public bug reported:
when i tried creating image using --is-public True
I gave me following message
unrecognized arguments: --is-public True ubuntu-14.04-server-cloudimg-
amd64-disk1.img
It should be removed from manuals
http://docs.openstack.org/cli-
reference/content/glanceclient_commands.ht
Public bug reported:
when i do glance image-create
it creates the empty image and shows a image without name on image-list
It should not be created without specifying parameters like container
and image path
or is it like you can create empty one and later update it ?
** Affects: glance
Moved to python-novaclient, change is up at
https://review.openstack.org/#/c/248874/
** Also affects: python-novaclient
Importance: Undecided
Status: New
** No longer affects: nova
** Changed in: python-novaclient
Importance: Undecided => Medium
** Changed in: python-novaclient
** Project changed: django-openstack-auth => horizon
--
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/1521360
Title:
Add Member action in loadbalancers does not enfor
** Project changed: django-openstack-auth => horizon
--
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/1521394
Title:
Loadbalancer Add member fails silently
Status in
You have been subscribed to a public bug:
The instance to be added should not have any ports i.e. it is still in
scheduling state.
In Project->Networks->Load Balancers:
1. Click on Members tab
2. Click on 'Add Member' button
3. Enter member details and pick the instance with no ports
You will g
You have been subscribed to a public bug:
In Project->Networks->Load Balancers:
1. Click on Members tab
2. Click on 'Add Member' button
**Make sure there are no instances to be added as members.**
Protocol Port is not a required field but if you don't enter the port,
it fails with message "Unab
Public bug reported:
In openstack_dashboard/static/ folder, a lot of lint warnings are thrown
to do with code formatting.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
Public bug reported:
Under compute -> instances, we can filter instances by instance name,
image id, flavor id or status. We can add another filter where user can
filter instances based on subnet id or name.
It is useful when user has multiple subnets in project and he wants to
view/list instance
This bug was fixed in the package neutron - 1:2015.1.2-0ubuntu2
---
neutron (1:2015.1.2-0ubuntu2) vivid; urgency=medium
* Fix DHCP agent delete non-existant interface (LP: #1498370)
- d/p/dhcp-protect-against-case-when-device-name-is-none.patch
-- Edward Hope-Morley Tue, 10
Public bug reported:
http://logs.openstack.org/94/242594/2/check/gate-tempest-dsvm-
nova-v20-api/085f243/logs/screen-n-cpu.txt.gz?level=TRACE#_2015-11-30_18_03_48_003
2015-11-30 18:03:48.003 ERROR nova.compute.manager
[req-b3bc5257-4673-4850-9ba0-e1e136c131b3
tempest-DeleteServersTestJSON-65117
This bug was fixed in the package nova - 1:2015.1.2-0ubuntu2
---
nova (1:2015.1.2-0ubuntu2) vivid; urgency=medium
* d/control: Bump oslo.concurrency to >= 1.8.2 (LP: #1518016).
-- Corey Bryant Fri, 20 Nov 2015 07:56:47
-0500
** Changed in: nova (Ubuntu Vivid)
Status: Fix
This bug was fixed in the package python-oslo.concurrency -
1.8.2-0ubuntu0.15.04.1
---
python-oslo.concurrency (1.8.2-0ubuntu0.15.04.1) vivid; urgency=medium
* New upstream point release, resolving incompatibilies in latest
Nova stable kilo update with 1.8.0 (LP: #1518016).
--
Public bug reported:
Version: 2015.2 (Liberty)
Plugin: ML2 w/ LinuxBridge
While testing various NICs, I found that changing the physical interface
mapping in the ML2 configuration file and restarting the agent resulted
in the old physical interface remaining in the bridge. This can be
observed wi
Public bug reported:
[Existing problem]
The OpenStackClient CLI (python-openstackclient project) has limited neutron
support (network, security group, security group rules, floating IP address and
fixed IP address CRUD).
[Proposal]
Per OpenStack spec https://review.openstack.org/#/c/243348/, th
I tried resizing of instances with preallocation strategy for nano and micro
flavors and tried same for few instances of tiny flavor.
I could not reproduce bug.
At the same time, I am not able to check with other flavors due to hardware
resources restriction I have. But I don't think we need API
Please don't switch bugs to security without an explanation as to why
you've done so. Reviewing the discussion here, it looks like it
describes a temporary defect in the master branch during the Liberty
development cycle and fixed prior to release. The OpenStack
Vulnerability Management Team does n
** Also affects: glance-store
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1521236
Title:
Missing list of stores in glance-api.conf
Status i
Public bug reported:
configuring.rst has:
Available options for this option are (``file``, ``swift``, ``s3``, ``rbd``,
``sheepdog``,
``cinder`` or ``vsphere``). In order to select a default store it must also
'http' is also an available option
** Affects: glance
Importance: Undecided
Public bug reported:
We used to give some indication of which stores could be configured:
[glance_store]
# List of which store classes and store class locations are
# currently known to glance at startup.
# Deprecated group/name - [DEFAULT]/known_stores
# Existing but disabled stores:
#
Sorry after furthering debugging the https issue and checking found the
keystone endpoints setup incorrectly.
Closing ticket as false report.
** Changed in: python-novaclient
Status: Incomplete => Invalid
** Changed in: nova
Assignee: (unassigned) => Michael Duncan (mduncan-j)
** Ch
Addressed and fixed by this review [1].
[1] https://review.openstack.org/249986
** Changed in: neutron
Status: Confirmed => Fix Released
** Changed in: neutron
Milestone: None => mitaka-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whic
@Shraddha Pandhe:
This bug report doesn't seem to describe a bug. It's rather a request
for discussion. As long as there is no actual observation that this is
a failure/fault/error in the behavior of Nova it doesn't make sense
to open a bug report from my point of view. Pointing to master code
whi
Public bug reported:
[Existing problem]
In the current QoS implementation, network QoS bandwidth limit are applied to
all the ports uniformly in the network. This may be wrong. Consider a case
where the user just want 20 mbps speed for the entire network but the current
implementation will end
Public bug reported:
VMware LBaaSv1 driver supplies the Neutron plugin with a method, which allows
detection of Edge appliance use by the LBaaS driver.
The is_edge_in_use() method is using a context which is invalid: the driver has
no self.context property and shouldn't have one.
Instead, the co
AFAIK the flavor extra specs are free form string values and there is
no defined list of allowed values. That's why it's not possible to
check if the provided input is sane. The code 201 the REST API returns
just says that your request (create/update an extra spec) got fulfilled.
It doesn't say tha
Public bug reported:
When messing with keystone 2 keystone I was getting 500 Errors telling
me that the signing process was failing when generating ECP assertions.
When i looked into it i found it was because the federation/idp.py was
being imported before the code had the chance to do a
environme
** Changed in: networking-midonet
Status: New => Fix Released
** Changed in: networking-midonet
Milestone: None => 2015.1.1
** Changed in: networking-midonet
Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto)
--
You received this bug notification because you are a member of Y
** Changed in: networking-midonet
Status: New => Invalid
** Changed in: networking-midonet
Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto)
** Changed in: networking-midonet
Importance: Medium => Low
--
You received this bug notification because you are a member of Yahoo!
En
Public bug reported:
When update fixed_ip of a port that associated with floatingip,
the fixed_ip of the floatingip is not updated.
How to reproduce:
(1) create a port
$ neutron port-show 9b11ce55-a404-4ae4-941d-ea0db555c331
+---+-
it sounds like a bug in the extension itself rather than midonet
implementation.
** 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.
@Michael Duncan:
We need additional information to do a proper bug triage.
Would you please provide the following information:
* What was the result you expected? The error indicates that there is
an issue with your certificates (and I'm guessing that OpenStack does
not setup certificates).
@yuntongjin:
It seems that this is a feature request. Feature requests for nova are
done with blueprints [1] and with specs [2]. I'll recommend to read [3]
if not yet done. To focus here on bugs which are a failures/errors/faults
I close this one as "Invalid". The effort to implement the requested
50 matches
Mail list logo
