[Yahoo-eng-team] [Bug 1342545] [NEW] There is no parameter for 'nova rebuild' to inject files into the server.
Public bug reported: When create a server, I can use the parameter --file to inject a file to it. But when I rebuild the server, I can not inject the files. ** 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/1342545 Title: There is no parameter for 'nova rebuild' to inject files into the server. Status in OpenStack Compute (Nova): New Bug description: When create a server, I can use the parameter --file to inject a file to it. But when I rebuild the server, I can not inject the files. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342545/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342546] [NEW] The 'vcpus_used' number reported by driver is useless and confusing
Public bug reported: The resource_tracker get a 'vcpus_used' number from drivers' get_available_resource method. But resource_tracker doesn't use this number to calculate, instead it calculate the vcpus used number according to the number of vcpus the current instances use. It result that the number returned from drivers is not identical to the 'vcpus_used' number in 'nova hypervisor-show' result. This is confusing ** 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/1342546 Title: The 'vcpus_used' number reported by driver is useless and confusing Status in OpenStack Compute (Nova): New Bug description: The resource_tracker get a 'vcpus_used' number from drivers' get_available_resource method. But resource_tracker doesn't use this number to calculate, instead it calculate the vcpus used number according to the number of vcpus the current instances use. It result that the number returned from drivers is not identical to the 'vcpus_used' number in 'nova hypervisor-show' result. This is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342546/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342348] Re: Hyper-V agent IDE/SCSI related refactoring necessary
** Changed in: nova Status: In Progress = 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/1342348 Title: Hyper-V agent IDE/SCSI related refactoring necessary Status in OpenStack Compute (Nova): Invalid Bug description: Hyper-V Server 2012 R2 introduces a new feature for virtual machines named generation 2, consisting mainly in a new firmware and better support for synthetic devices. Generation 2 VMs don't support IDE devices, which means that local boot, ephemeral disks and DVD Drives must be attached as SCSI, instead of IDE for generation 1 VMs. Since the Virtual Hard Disks and Virtual CD/DVD Disks can be attached to IDE controllers or SCSI controllers (generation 2 only), some constants, variables and methods have been improperly named, having the IDE prefix. e.g.: _IDE_DISK_RES_SUB_TYPE will have to be renamed to _HARD_DISK_RES_SUB_TYPE To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342348/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1248501] Re: Models are not in sync with migrations
** 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/1248501 Title: Models are not in sync with migrations Status in OpenStack Neutron (virtual network service): Invalid Bug description: Some migrations are not synchronized with models. In some models wrong parameter for 'nullable' parameter in columns, wrong length of String values is set and __table_args__ for indexes and unique constraints is used. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1248501/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1250918] Re: No policy for image uploads in v2
Currently we applied the policy enforcement at domain layer instead of api controller in v2, https://github.com/openstack/glance/blob/master/glance/api/policy.py#L237 . ** Changed in: glance Status: In Progress = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1250918 Title: No policy for image uploads in v2 Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: There no policy for the set_data function for image_uploads in glance v2 api To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1250918/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1226543] Re: VMware: attaching a volume to the VM failed
This is not a valid cinder bug. Nova vmware driver has to create or use an existing controller in the instance VM to attach the volume and it is unrelated to the controller in volume backing. Please re-open this if you disagree. ** No longer affects: cinder -- 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/1226543 Title: VMware: attaching a volume to the VM failed Status in OpenStack Compute (Nova): Triaged Bug description: I was using the image trend-tinyvm1-flat.vmdk. When I boot an VM and attach a volume to it. The following error message was shown: n-cpu== 2013-09-17 06:47:05.669 ERROR nova.openstack.common.rpc.amqp [req-fc4e0a9e-6bd5-45ac-b841-c89e17394603 admin demo] Exception during me ssage handling 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last): 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/openstack/common/rpc/amqp.py, line 461, in _process_data 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp **args) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/openstack/common/rpc/dispatcher.py, line 17 2, in dispatch 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/exception.py, line 89, in wrapped 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp payload) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/exception.py, line 73, in wrapped 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp return f(self, context, *args, **kw) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 243, in decorated_ function 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp pass 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 229, in decorated_function 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 271, in decorated_function 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp e, sys.exc_info()) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 258, in decorated_function 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp return function(self, context, *args, **kwargs) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 3577, in attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp context, instance, mountpoint) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 3572, in attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp mountpoint, instance) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 3614, in _attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp connector) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/compute/manager.py, line 3604, in _attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp mountpoint) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 290, in attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp mountpoint) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/virt/vmwareapi/volumeops.py, line 272, in attach_volume 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp self._attach_volume_vmdk(connection_info, instance, mountpoint) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/virt/vmwareapi/volumeops.py, line 222, in _attach_volume_vmdk 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp unit_number=unit_number) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/virt/vmwareapi/volumeops.py, line 71, in attach_disk_to_vm 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp self._session._wait_for_task(instance_uuid, reconfig_task) 2013-09-17 06:47:05.669 TRACE nova.openstack.common.rpc.amqp File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 779, in
[Yahoo-eng-team] [Bug 1340167] Re: VMware: Horizon reports incorrect message for PAUSE instance
I'm guessing pause is an asynchronous operation. Horizon depend on the APIs, if nova pause returns successfully we can't tell if something goes wrong later on, we don't have access to the compute logs. Possible solutions would be for either Nova to surface this error message when calling nova pause, and/or for Horizon to somehow query Nova to check whether an action is allowed and hide the Pause button when it's not possible. But since there could be multiple compute nodes, some that support pausing and others that don't, I'm not sure how feasible that would be either... Adding the Nova folks to see if they have some thoughts about this. It would be nice to have some way of letting the user know that no matter how many times they try to pause, it won't work in this case. ** 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/1340167 Title: VMware: Horizon reports incorrect message for PAUSE instance Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (Nova): New Bug description: When I pause an instance hosted on VMware cluster, it shows SUCCESS: Paused Instance: instance_name; in horizon portal and nothing happens (instance does not go to Pause state) In nova-compute log it shows: pause not supported for vmwareapi 2014-07-10 06:53:37.212 ERROR oslo.messaging.rpc.dispatcher [req-f8159224-a1e2-4271-84d8-eea2edeaaee1 admin demo] Exception during message handling: pause not supported for vmwareapi 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 88, in wrapped 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher payload) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/exception.py, line 71, in wrapped 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher return f(self, context, *args, **kw) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 285, in decorated_function 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher pass 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 271, in decorated_function 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 335, in decorated_function 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher function(self, context, *args, **kwargs) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 313, in decorated_function 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher kwargs['instance'], e, sys.exc_info()) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 301, in decorated_function 2014-07-10 06:53:37.212 TRACE oslo.messaging.rpc.dispatcher return function(self, context,
[Yahoo-eng-team] [Bug 1342720] [NEW] test_agent_ext_plugin: create_agent needs to be fixed
Public bug reported: create_agent unit test needs to be fixed in order to provide meaningful coverage for underlying logic. Right now the test is not testing much and is confusing ** Affects: neutron Importance: Low Assignee: Eugene Nikanorov (enikanorov) Status: New ** Tags: unittest ** Changed in: neutron Assignee: (unassigned) = Eugene Nikanorov (enikanorov) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1342720 Title: test_agent_ext_plugin: create_agent needs to be fixed Status in OpenStack Neutron (virtual network service): New Bug description: create_agent unit test needs to be fixed in order to provide meaningful coverage for underlying logic. Right now the test is not testing much and is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1342720/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1285239] Re: Installing Ubuntu on a Compute node that is a VMWare guest running RHEL 6.5
I agree with Matt. As no action taken by reporter since, marking Invalid. ** Changed in: glance Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1285239 Title: Installing Ubuntu on a Compute node that is a VMWare guest running RHEL 6.5 Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Hi, I am having a compute node that is a VMWare guest which runs RHEL 6.5 .Using KVM/QMENU for virtulization. When I try to create an instance it ends up with the following error on the console log. Can some one help? ▒Loading, please wait...▒ [3.678916] tmpfs: No value for mount option '▒nosuid' mount: mounting tmpfs on /run failed: Invalid argument ▒▒▒@=@=▒WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 1: ignoring bad line starting with 'the' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 2: ignoring bad line starting with 'ware,' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 3: ignoring bad line starting with 'o' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 4: ignoring bad line starting with 'lt.' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 5: ignoring bad line starting with '6,' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 6: ignoring bad line starting with '6,' WARNING: /etc/modprobe.d/blacklist-ath_pci.conf line 7: ignoring bad line starting with '6,' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 1: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 2: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 3: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 4: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 5: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 6: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 7: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 8: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 9: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-firewire.conf line 10: ignoring bad line starting with 'ack' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 1: ignoring bad line starting with 'ally' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 2: ignoring bad line starting with 'cs' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 3: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 4: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 5: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 6: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 7: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 8: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 9: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 10: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 11: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 12: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 13: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 14: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 15: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 16: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 17: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 18: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 19: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 20: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 21: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 22: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 23: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 24: ignoring bad line starting with '.' WARNING: /etc/modprobe.d/blacklist-framebuffer.conf line 25: ignoring bad line
[Yahoo-eng-team] [Bug 1302097] Re: Unable to get images by image type
Hi Santiago, Are you actually working on this? If so, could you please change this to In Progress, marking as Opinion for now. ** Changed in: glance Status: New = Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302097 Title: Unable to get images by image type Status in OpenStack Image Registry and Delivery Service (Glance): Opinion Bug description: We should be able to get images by type. In Horizon for example, in order to populate the boot image from options, we currently retrieve all images and filter them by type To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302097/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342756] [NEW] cisco_ml2_apic_contracts table needs to set nullable=False on tenant_id column
Public bug reported: In DB migrations the following is detected: INFO [alembic.autogenerate.compare] Detected NULL on column 'cisco_ml2_apic_contracts.tenant_id' ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Tags: cisco db ** Changed in: neutron Assignee: (unassigned) = Henry Gessau (gessau) ** Tags added: cisco db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1342756 Title: cisco_ml2_apic_contracts table needs to set nullable=False on tenant_id column Status in OpenStack Neutron (virtual network service): New Bug description: In DB migrations the following is detected: INFO [alembic.autogenerate.compare] Detected NULL on column 'cisco_ml2_apic_contracts.tenant_id' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1342756/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342811] [NEW] Bump up the min version of keystonemiddleware
Public bug reported: As per the question on this change :- https://review.openstack.org/#/c/102352/4/requirements.txt we could potentially have a invalid version installed in the environment. The answer to that question lead us to make the change in the global requirements:- https://review.openstack.org/#/c/102352/5/requirements.txt Keeping this bug open for the further discussion. ** 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://bugs.launchpad.net/bugs/1342811 Title: Bump up the min version of keystonemiddleware Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: As per the question on this change :- https://review.openstack.org/#/c/102352/4/requirements.txt we could potentially have a invalid version installed in the environment. The answer to that question lead us to make the change in the global requirements:- https://review.openstack.org/#/c/102352/5/requirements.txt Keeping this bug open for the further discussion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1342811/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1331857] Re: ML2 Nexus MD does not appear to configure multiple switches
** Changed in: neutron Status: Confirmed = 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/1331857 Title: ML2 Nexus MD does not appear to configure multiple switches Status in OpenStack Neutron (virtual network service): Fix Released Bug description: There is already a bug to add unit tests for multi-switch configuration, but there already appears to be a bug in that multiple switches can be defined in the configuration file, but multiple switches are not configured. The related bug is here: https://bugs.launchpad.net/neutron/+bug/1330598 The issue is: If you configure the Cisco Nexus ML2 MD with two switches that have the same target hypervisor ID, as in: [ml2_mech_cisco_nexus_1:1.1.1.1] compute-1=1/2 [ml2_mech_cisco_nexus_2:1.1.1.2] compute-1=1/2 The system will only configure a VLAN on interface 1/2 on ml2_mech_cisco_nexus_1. In addition it appears that the system will only ever configure devices on the first switch that is discovered. Also, it does not appear possible to define port-channels as the target for these configurations, which breaks the use of virtual port- channel as a configured mechanism. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1331857/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1337698] Re: q-dhcp agent fails to start on Ubuntu 12.04
User error: Issue was due to /usr/sbin missing in the PATH for the user running stack.sh. ** 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/1337698 Title: q-dhcp agent fails to start on Ubuntu 12.04 Status in OpenStack Neutron (virtual network service): Invalid Bug description: The fix for this bug https://bugs.launchpad.net/neutron/+bug/1212401 breaks q-dhcp agent on ubuntu 12.04 since dnsmasq --version can only be run as root and neutron/agent/linux/utils.py/create_process() is not invoked with root_helper. Bug fix for 1212401 addressed by https://review.openstack.org/#/c/96976/ This is breaking the 3rd party plugin CI To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1337698/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342834] [NEW] pci_devices.compute_node_id foreign key never actually created
Public bug reported: The model in nova/db/sqlalchemy/model.py defines the compute_node_id column has a foreign key on to compute_nodes.id However, neither the 213 migration (which initially introduced the pci_devices table) nor the collapsed 216 migration actually create that foreign key. It looks like the model is correct and a foreign key should exist and a migration should be added. ** 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/1342834 Title: pci_devices.compute_node_id foreign key never actually created Status in OpenStack Compute (Nova): New Bug description: The model in nova/db/sqlalchemy/model.py defines the compute_node_id column has a foreign key on to compute_nodes.id However, neither the 213 migration (which initially introduced the pci_devices table) nor the collapsed 216 migration actually create that foreign key. It looks like the model is correct and a foreign key should exist and a migration should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342834/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342811] Re: Bump up the min version of keystonemiddleware
I don't think this is bug in glance at all. As Brant stated we need to keep the same values as openstack/requirements so we should open bug against that. Your concern is valid, but I don't think this is bug in glance as is. ** Changed in: glance Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1342811 Title: Bump up the min version of keystonemiddleware Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: As per the question on this change :- https://review.openstack.org/#/c/102352/4/requirements.txt we could potentially have a invalid version installed in the environment. The answer to that question lead us to make the change in the global requirements:- https://review.openstack.org/#/c/102352/5/requirements.txt Keeping this bug open for the further discussion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1342811/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1246737] Re: ML2 plugin deletes port even if associated with multiple subnets on subnet deletion
We had a discussion today in the ML2 IRC. Does it really need to be back ported to havana? If not, this can be closed. I have modified the status to Opinion ** Changed in: neutron/havana Status: Confirmed = Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1246737 Title: ML2 plugin deletes port even if associated with multiple subnets on subnet deletion Status in OpenStack Neutron (virtual network service): Confirmed Status in neutron havana series: Opinion Bug description: On subnet deletion ml2 plugin deletes all the ports associated with this subnet and does not check if a port is associated with other subnets. Steps to reproduce: 1) create a network with two subnets 2) create dhcp port for the network, port is associated with both subnets 3) delete one of the subnets 4) dhcp port is getting deleted Though new dhcp port is created shortly I think it's not ok to delete existing dhcp port. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1246737/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342880] [NEW] Exception during message handling: 'NoneType' object is not iterable
Public bug reported:
q-svc frequently tries to iterate on None Type.
The job can succeed even if this issue happens.
message: Exception during message handling AND message:NoneType AND
message:object is not iterable AND filename:logs/screen-q-svc.txt
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkV4Y2VwdGlvbiBkdXJpbmcgbWVzc2FnZSBoYW5kbGluZ1wiIEFORCBtZXNzYWdlOlwiTm9uZVR5cGVcIiBBTkQgbWVzc2FnZTpcIm9iamVjdCBpcyBub3QgaXRlcmFibGVcIiBBTkQgZmlsZW5hbWU6XCJsb2dzL3NjcmVlbi1xLXN2Yy50eHRcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiODY0MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDA1NTMzMDE3NzE4LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9
[req-ef892503-3f93-4c68-adeb-17394b66406c ] Exception during message
handling: 'NoneType' object is not iterable
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
134, in _dispatch_and_reply
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
177, in _dispatch
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher return
self._do_dispatch(endpoint, method, ctxt, args)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
123, in _do_dispatch
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher result =
getattr(endpoint, method)(ctxt, **new_args)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/opt/stack/new/neutron/neutron/db/l3_rpc_base.py, line 63, in sync_routers
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
self._ensure_host_set_on_ports(context, plugin, host, routers)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/opt/stack/new/neutron/neutron/db/l3_rpc_base.py, line 76, in
_ensure_host_set_on_ports
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher interface)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/opt/stack/new/neutron/neutron/db/l3_rpc_base.py, line 84, in
_ensure_host_set_on_port
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher {'port':
{portbindings.HOST_ID: host}})
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/opt/stack/new/neutron/neutron/plugins/ml2/plugin.py, line 870, in update_port
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
need_notify=need_port_update_notify)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/opt/stack/new/neutron/neutron/plugins/ml2/plugin.py, line 302, in
_bind_port_if_needed
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
plugin_context, port_id, binding, bind_context)
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher TypeError:
'NoneType' object is not iterable
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
** 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/1342880
Title:
Exception during message handling: 'NoneType' object is not iterable
Status in OpenStack Neutron (virtual network service):
New
Bug description:
q-svc frequently tries to iterate on None Type.
The job can succeed even if this issue happens.
message: Exception during message handling AND message:NoneType
AND message:object is not iterable AND
filename:logs/screen-q-svc.txt
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkV4Y2VwdGlvbiBkdXJpbmcgbWVzc2FnZSBoYW5kbGluZ1wiIEFORCBtZXNzYWdlOlwiTm9uZVR5cGVcIiBBTkQgbWVzc2FnZTpcIm9iamVjdCBpcyBub3QgaXRlcmFibGVcIiBBTkQgZmlsZW5hbWU6XCJsb2dzL3NjcmVlbi1xLXN2Yy50eHRcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiODY0MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDA1NTMzMDE3NzE4LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9
[req-ef892503-3f93-4c68-adeb-17394b66406c ] Exception during message
handling: 'NoneType' object is not iterable
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
134, in _dispatch_and_reply
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-07-16 17:28:47.782 26480 TRACE oslo.messaging.rpc.dispatcher File
[Yahoo-eng-team] [Bug 1342907] [NEW] Instance table: flavor details popover issue
Public bug reported: This nice enhancement was merged: https://review.openstack.org/#/c/92112/, however, I'm noticing some issues with it. My instance table has 5 instances: name | flavor ins_1 m1.mini ins_2 m1.small ins_3 m1.small ins_4 m1.small ins_5 m1.small Hovering over the first 2 works fine, but the third one doesn't seem to work. Upon further examination, I think it is related to the 4 instances with the same flavor all having the same id (flavor_details_2): https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/templates/instances/_instance_flavor.html#L2 Image attached. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Untitled.png https://bugs.launchpad.net/bugs/1342907/+attachment/4154209/+files/Untitled.png -- 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/1342907 Title: Instance table: flavor details popover issue Status in OpenStack Dashboard (Horizon): New Bug description: This nice enhancement was merged: https://review.openstack.org/#/c/92112/, however, I'm noticing some issues with it. My instance table has 5 instances: name | flavor ins_1 m1.mini ins_2 m1.small ins_3 m1.small ins_4 m1.small ins_5 m1.small Hovering over the first 2 works fine, but the third one doesn't seem to work. Upon further examination, I think it is related to the 4 instances with the same flavor all having the same id (flavor_details_2): https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/templates/instances/_instance_flavor.html#L2 Image attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1342907/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342909] [NEW] libvirtError: monitor socket did not show up: No such file or directory
Public bug reported:
In a tempest run, I got a:
BuildErrorException: Server cb9b9996-13dd-4f95-9e54-53598723f695
failed to build and is in ERROR status
Which appears to have been caused by this from TRACE
nova.compute.manager:
Traceback (most recent call last):
File /opt/stack/new/nova/nova/compute/manager.py, line 2076, in
_build_resources
yield resources
File /opt/stack/new/nova/nova/compute/manager.py, line 1970, in
_build_and_run_instance
block_device_info=block_device_info)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 2317, in spawn
block_device_info)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3738, in
_create_domain_and_network
power_on=power_on)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3646, in
_create_domain
domain.XMLDesc(0))
File /opt/stack/new/nova/nova/openstack/common/excutils.py, line 82, in
__exit__
six.reraise(self.type_, self.value, self.tb)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3641, in
_create_domain
domain.createWithFlags(launch_flags)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in doit
result = proxy_call(self._autowrap, f, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in
proxy_call
rv = execute(f,*args,**kwargs)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in tworker
rv = meth(*args,**kwargs)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 896, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
libvirtError: monitor socket did not show up: No such file or directory
** 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/1342909
Title:
libvirtError: monitor socket did not show up: No such file or
directory
Status in OpenStack Compute (Nova):
New
Bug description:
In a tempest run, I got a:
BuildErrorException: Server cb9b9996-13dd-4f95-9e54-53598723f695
failed to build and is in ERROR status
Which appears to have been caused by this from TRACE
nova.compute.manager:
Traceback (most recent call last):
File /opt/stack/new/nova/nova/compute/manager.py, line 2076, in
_build_resources
yield resources
File /opt/stack/new/nova/nova/compute/manager.py, line 1970, in
_build_and_run_instance
block_device_info=block_device_info)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 2317, in spawn
block_device_info)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3738, in
_create_domain_and_network
power_on=power_on)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3646, in
_create_domain
domain.XMLDesc(0))
File /opt/stack/new/nova/nova/openstack/common/excutils.py, line 82, in
__exit__
six.reraise(self.type_, self.value, self.tb)
File /opt/stack/new/nova/nova/virt/libvirt/driver.py, line 3641, in
_create_domain
domain.createWithFlags(launch_flags)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in doit
result = proxy_call(self._autowrap, f, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in
proxy_call
rv = execute(f,*args,**kwargs)
File /usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in
tworker
rv = meth(*args,**kwargs)
File /usr/lib/python2.7/dist-packages/libvirt.py, line 896, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
libvirtError: monitor socket did not show up: No such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1342909/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342925] [NEW] Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating
Public bug reported: A transient ERROR from a tempest run: 2014-07-07 04:48:43.757 ERROR nova.api.ec2 [req-6705e757-dc7c-4d8c-9b0d- f0a4e2ea363c EC2VolumesTest-1498681827 EC2VolumesTest-1461531536] Unexpected InvalidInput raised: Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating Although this seems to have bubbled up to the console as: BadRequest: Invalid volume: Volume status must be available or error, but current status is: creating (HTTP 400) Source: http://logs.openstack.org/36/103636/1/check/check-tempest-dsvm- full/b4d3e3c/ ** Affects: nova Importance: Undecided Status: New ** Description changed: A transient ERROR from a tempest run: 2014-07-07 04:48:43.757 ERROR nova.api.ec2 [req-6705e757-dc7c-4d8c-9b0d- f0a4e2ea363c EC2VolumesTest-1498681827 EC2VolumesTest-1461531536] Unexpected InvalidInput raised: Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating Although this seems to have bubbled up to the console as: - BadRequest: Invalid volume: Volume status must be available or error, + BadRequest: Invalid volume: Volume status must be available or error, but current status is: creating (HTTP 400) + + Source: http://logs.openstack.org/36/103636/1/check/check-tempest-dsvm- + full/b4d3e3c/ -- 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/1342925 Title: Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating Status in OpenStack Compute (Nova): New Bug description: A transient ERROR from a tempest run: 2014-07-07 04:48:43.757 ERROR nova.api.ec2 [req-6705e757-dc7c-4d8c- 9b0d-f0a4e2ea363c EC2VolumesTest-1498681827 EC2VolumesTest-1461531536] Unexpected InvalidInput raised: Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating Although this seems to have bubbled up to the console as: BadRequest: Invalid volume: Volume status must be available or error, but current status is: creating (HTTP 400) Source: http://logs.openstack.org/36/103636/1/check/check-tempest- dsvm-full/b4d3e3c/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342925/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1341040] Re: neutron CLI should not allow user to create /32 subnet
I removed the duplicate status because this bug applies to the CLI while
the other bug it was marked as a duplicate of applies to the neutron
server. Since it was decided to allow it in the neutron server, we can
leave this as a separate bug to track the fix to at least add a warning
to the client.
** This bug is no longer a duplicate of bug 1271311
Neutron should disallow a CIDR of /32
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1341040
Title:
neutron CLI should not allow user to create /32 subnet
Status in OpenStack Neutron (virtual network service):
New
Bug description:
I'm using devstack stable/icehouse, and my neutron version is
1409da70959496375f1ac45457663a918ec8
I created an internal network not connected to the router. If I
mis-configure the subnet, Horizon will catch the problem, but not neutron CLI.
Subsequently VM cannot be created on this misconfigured subnet, as it ran out
of IP to offer to the VM.
neutron net-create test-net
Created a new network:
++--+
| Field | Value|
++--+
| admin_state_up | True |
| id | b7bb10bb-48e0-4c1a-a5fc-9590b6619f5a |
| name | test-net |
| shared | False|
| status | ACTIVE |
| subnets| |
| tenant_id | 8092813be8fd4122a20ee3a6bfe91162 |
++--+
If I use Horizon, go to Networks, test-net, Create Subnet, then use
parameters,
Subnet Name: subnet-1
Network Address: 10.10.150.0/32
IP Version: IPv4
Horizon returns the error message The subnet in the Network Address is too
small (/32).
If I use neutron CLI,
neutron subnet-create --name subnet-1 test-net 10.10.150.0/32
Created a new subnet:
+--+--+
| Field| Value|
+--+--+
| allocation_pools | |
| cidr | 10.10.150.0/32 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.10.150.1 |
| host_routes | |
| id | 4142ff1d-28de-4e77-b82b-89ae604190ae |
| ip_version | 4|
| name | subnet-1 |
| network_id | b7bb10bb-48e0-4c1a-a5fc-9590b6619f5a |
| tenant_id| 8092813be8fd4122a20ee3a6bfe91162 |
+--+--+
neutron net-list
+--+--+-+
| id | name | subnets
|
+--+--+-+
| 0dd5722d-f535-42ec-9257-437c05e4de25 | private |
81859ee5-4ea5-4e60-ab2a-ba74146d39ba 10.0.0.0/24|
| 27c1649d-f6fc-4893-837d-dbc293fc4b80 | public |
6c1836a1-eb7d-4acb-ad6f-6c394cedced5|
| b7bb10bb-48e0-4c1a-a5fc-9590b6619f5a | test-net |
4142ff1d-28de-4e77-b82b-89ae604190ae 10.10.150.0/32 |
+--+--+-+
nova boot --image cirros-0.3.1-x86_64-uec --flavor m1.tiny --nic
net-id=b7bb10bb-48e0-4c1a-a5fc-9590b6619f5a vm2
:
:
nova list
+--+--+++-+--+
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-+--+
| d98511f7-452c-4ab6-8af9-d73576714c87 | vm1 | ACTIVE | - | Running
| private=10.0.0.2 |
| b12b6a6d-4ab9-43b2-825c-ae656a7aafc4 | vm2 | ERROR | - | NOSTATE
| |
+--+--+++-+--+
I get this output from screen:
2014-07-11 18:37:32.327 DEBUG neutronclient.client [-] RESP:409
CaseInsensitiveDict({'date': 'Sat, 12 Jul 2014 01:37:32 GMT',
'content-length': '164', 'content-type': 'application/json;
charset=UTF-8', 'x-openstack-request-id': 'req-35a49577-5a3d-
4a98-a790-52694f09d59a'}) {NeutronError: {message: No more
[Yahoo-eng-team] [Bug 1342953] [NEW] Swift container objects listed non intuitively on UI
Public bug reported: The bug is reproducible for the Stable Havana Release: 1. Created 3 Object Store/containers. 2. Uploaded 2 or more objects for the first container. 3. Left the second container empty. 4. Uploaded 1 object for the 3rd container. 5. Now when I click on first container the 2nd object of this container is aligned against the second container giving the impression that the second object of the first container belongs to second container. 6. If I click on 3rd container then the object is listed against the 1st container. I have used Firefox version 30 on mac osx 10.8.5 The container objects should be properly aligned against the container. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Screen Shot 2014-07-16 at 1.48.18 PM.png https://bugs.launchpad.net/bugs/1342953/+attachment/4154272/+files/Screen%20Shot%202014-07-16%20at%201.48.18%20PM.png -- 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/1342953 Title: Swift container objects listed non intuitively on UI Status in OpenStack Dashboard (Horizon): New Bug description: The bug is reproducible for the Stable Havana Release: 1. Created 3 Object Store/containers. 2. Uploaded 2 or more objects for the first container. 3. Left the second container empty. 4. Uploaded 1 object for the 3rd container. 5. Now when I click on first container the 2nd object of this container is aligned against the second container giving the impression that the second object of the first container belongs to second container. 6. If I click on 3rd container then the object is listed against the 1st container. I have used Firefox version 30 on mac osx 10.8.5 The container objects should be properly aligned against the container. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1342953/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342961] [NEW] Exception during message handling: Pool FOO could not be found
Public bug reported: $subjecyt style exception appears both in successful and failed jobs. message: Exception during message handling AND message:Pool AND message:could not be found AND filename:logs/screen-q-svc.txt http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkV4Y2VwdGlvbiBkdXJpbmcgbWVzc2FnZSBoYW5kbGluZ1wiIEFORCBtZXNzYWdlOlwiUG9vbFwiIEFORCBtZXNzYWdlOlwiY291bGQgbm90IGJlIGZvdW5kXCIgQU5EIGZpbGVuYW1lOlwibG9ncy9zY3JlZW4tcS1zdmMudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6Ijg2NDAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNTUzMzU3ODE2NCwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ== [req-201dcd14-dc9d-4fb5-8eb5-c66c35991cb3 ] Exception during message handling: Pool 7fa63738-9030-4136-9b4e-9eb7ffb79f68 could not be found 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/neutron/neutron/services/loadbalancer/drivers/common/agent_driver_base.py, line 232, in update_pool_stats 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher self.plugin.update_pool_stats(context, pool_id, data=stats) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/neutron/neutron/db/loadbalancer/loadbalancer_db.py, line 512, in update_pool_stats 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher pool_db = self._get_resource(context, Pool, pool_id) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/neutron/neutron/db/loadbalancer/loadbalancer_db.py, line 218, in _get_resource 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher raise loadbalancer.PoolNotFound(pool_id=id) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher PoolNotFound: Pool 7fa63738-9030-4136-9b4e-9eb7ffb79f68 could not be found 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher ** 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/1342961 Title: Exception during message handling: Pool FOO could not be found Status in OpenStack Neutron (virtual network service): New Bug description: $subjecyt style exception appears both in successful and failed jobs. message: Exception during message handling AND message:Pool AND message:could not be found AND filename:logs/screen-q-svc.txt http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkV4Y2VwdGlvbiBkdXJpbmcgbWVzc2FnZSBoYW5kbGluZ1wiIEFORCBtZXNzYWdlOlwiUG9vbFwiIEFORCBtZXNzYWdlOlwiY291bGQgbm90IGJlIGZvdW5kXCIgQU5EIGZpbGVuYW1lOlwibG9ncy9zY3JlZW4tcS1zdmMudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6Ijg2NDAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNTUzMzU3ODE2NCwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ== [req-201dcd14-dc9d-4fb5-8eb5-c66c35991cb3 ] Exception during message handling: Pool 7fa63738-9030-4136-9b4e-9eb7ffb79f68 could not be found 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-07-16 17:31:46.780 31504 TRACE oslo.messaging.rpc.dispatcher result =
[Yahoo-eng-team] [Bug 1342919] Re: instances rescheduled after building network info do not update the MAC
Looking at the nova code, it only throws it away if the error is
except (exception.InstanceNotFound,
exception.UnexpectedDeletingTaskStateError):
and not on the other code paths. That makes this a nova or nova-ironic-
driver-interaction bug: adding a nova task.
** 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/1342919
Title:
instances rescheduled after building network info do not update the
MAC
Status in OpenStack Bare Metal Provisioning Service (Ironic):
Triaged
Status in OpenStack Compute (Nova):
New
Bug description:
This is weird - Ironic has used the mac from a different node (which
quite naturally leads to failures to boot!)
nova list | grep spawn
| 6c364f0f-d4a0-44eb-ae37-e012bbdd368c |
ci-overcloud-NovaCompute3-zmkjp5aa6vgf | BUILD | spawning | NOSTATE |
ctlplane=10.10.16.137 |
nova show 6c364f0f-d4a0-44eb-ae37-e012bbdd368c | grep hyperv
| OS-EXT-SRV-ATTR:hypervisor_hostname |
b07295ee-1c09-484c-9447-10b9efee340c |
neutron port-list | grep 137
| 272f2413-0309-4e8b-9a6d-9cb6fdbe978d ||
78:e7:d1:23:90:0d | {subnet_id: a6ddb35e-305e-40f1-9450-7befc8e1af47,
ip_address: 10.10.16.137} |
ironic node-show b07295ee-1c09-484c-9447-10b9efee340c | grep wait
| provision_state| wait call-back
|
ironic port-list | grep 78:e7:d1:23:90:0d # from neutron
| 33ab97c0-3de9-458a-afb7-8252a981b37a | 78:e7:d1:23:90:0d |
ironic port-show 33ab97c0-3de9-458a-afb7-8252a981
++---+
| Property | Value |
++---+
| node_uuid | 69dc8c40-dd79-4ed6-83a9-374dcb18c39b | #
Ruh-roh, wrong node!
| uuid | 33ab97c0-3de9-458a-afb7-8252a981b37a |
| extra | {u'vif_port_id': u'aad5ee6b-52a3-4f8b-8029-7b8f40e7b54e'} |
| created_at | 2014-07-08T23:09:16+00:00 |
| updated_at | 2014-07-16T01:23:23+00:00 |
| address| 78:e7:d1:23:90:0d |
++---+
ironic port-list | grep 78:e7:d1:23:9b:1d # This is the MAC my hardware list
says the node should have
| caba5b36-f518-43f2-84ed-0bc516cc89df | 78:e7:d1:23:9b:1d |
# ironic port-show caba5b36-f518-43f2-84ed-0bc516cc
++---+
| Property | Value |
++---+
| node_uuid | b07295ee-1c09-484c-9447-10b9efee340c | #
and tada right node
| uuid | caba5b36-f518-43f2-84ed-0bc516cc89df |
| extra | {u'vif_port_id': u'272f2413-0309-4e8b-9a6d-9cb6fdbe978d'} |
| created_at | 2014-07-08T23:08:26+00:00 |
| updated_at | 2014-07-16T19:07:56+00:00 |
| address| 78:e7:d1:23:9b:1d |
++---+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1342919/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1342999] [NEW] adding panels to existing dashboard via the plugin causes dashboard reordering
Public bug reported: Using the plugin approach to add a panel to an existing dashboard, all the dashboards become reordered. It's not clear how or why this occurs. ** Affects: horizon Importance: Medium Assignee: Eric Peterson (ericpeterson-l) Status: Confirmed ** Changed in: horizon Assignee: (unassigned) = Eric Peterson (ericpeterson-l) -- 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/1342999 Title: adding panels to existing dashboard via the plugin causes dashboard reordering Status in OpenStack Dashboard (Horizon): Confirmed Bug description: Using the plugin approach to add a panel to an existing dashboard, all the dashboards become reordered. It's not clear how or why this occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1342999/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1343011] [NEW] Login does not work on latest devstack
Public bug reported: Devstack was working yesterday. When I pulled devstack today, I cannot login. After clicking login, it just redirects back to the login page with no error message and empty form. ** Affects: horizon Importance: Undecided Assignee: Lin Hua Cheng (lin-hua-cheng) Status: New ** Changed in: horizon Assignee: (unassigned) = Lin Hua Cheng (lin-hua-cheng) -- 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/1343011 Title: Login does not work on latest devstack Status in OpenStack Dashboard (Horizon): New Bug description: Devstack was working yesterday. When I pulled devstack today, I cannot login. After clicking login, it just redirects back to the login page with no error message and empty form. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1343011/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1343024] [NEW] remove ovs dependency in embrane plugin
Public bug reported: The OVS core plugin will be removed in Juno 2 but the embrane plugin code is still using it and will stop working. This bug tracks changing the dependency to ML2 ** Affects: neutron Importance: Undecided Assignee: Ignacio Scopetta (3-ignacio) Status: New ** Changed in: neutron Assignee: (unassigned) = Ignacio Scopetta (3-ignacio) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1343024 Title: remove ovs dependency in embrane plugin Status in OpenStack Neutron (virtual network service): New Bug description: The OVS core plugin will be removed in Juno 2 but the embrane plugin code is still using it and will stop working. This bug tracks changing the dependency to ML2 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1343024/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1343073] [NEW] Remove GPL content files from Neutron
Public bug reported: There are some files in Neutron under GPN license, is there any plan to remove them? For example: docs/source/docbkx/quantum-api-1.0/js/shjs/sh_main.js ** 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/1343073 Title: Remove GPL content files from Neutron Status in OpenStack Neutron (virtual network service): New Bug description: There are some files in Neutron under GPN license, is there any plan to remove them? For example: docs/source/docbkx/quantum-api-1.0/js/shjs/sh_main.js To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1343073/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1341710] Re: Comment placed inside of /etc/timezone
** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1341710 Title: Comment placed inside of /etc/timezone Status in Init scripts for use on cloud images: New Status in “cloud-init” package in Ubuntu: New Bug description: Greetings! cloud-init v0.7.5 (trusty) is placing a comment in the /etc/timezone file, when that file isn't intended to contain a comment. This is confusing openjdk (and perhaps other programs?), which is unable to determine the correct timezone. Sample /etc/timezone from v0.7.5: # Created by cloud-init v. 0.7.5 on Mon, 14 Jul 2014 18:01:38 + US/Eastern Openjdk has been informed of this back in 2012, and decided that they won't change things on their end because comments in /etc/timezone aren't part of the spec. https://bugs.openjdk.java.net/browse/JDK-7192951. Of course, there is no formal spec for /etc/timezone. The closest that I've seen to a spec is actually contained within the bug report at openjdk: = I am not sure that a formal spec of /etc/timezone exists. The Debian tools for manipulating it (tzconfig and tzsetup) do basically the same thing. --- reading --- if [ -L /etc/localtime ] ; then current_timezone=$(readlink /etc/localtime | sed 's%^/usr/share/zoneinfo/%%') elif [ -f /etc/timezone ] [ -f /etc/localtime ]; then current_timezone=$(cat /etc/timezone) fi --- setting --- echo $timezone /etc/timezone It is the same in Ubuntu. So, in Debian-based distros it is just a LF-terminated line, with no spaces and extra characters. To be a little more general, I suggest ignoring all leading spaces (including new lines) and then reading consecutive non-space characters. = For the record, cloud-init previously did not include a comment in /etc/timezone. Would it be possible to revert to the previous behavior of not including a comment in /etc/timezone? A quick skim of the source code tells me that the set_timezone() method would have to be changed to no longer include the line with util.make_header(). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1341710/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1343080] [NEW] alternate link type in GET /images incorrectly includes the project/tenant in the URI
Public bug reported:
Clearly nobody really uses the application/vnd.openstack.image links
in the returned results from GET /v2/{tenant}/images REST API call,
since the link URI returned in it is wrong.
Glance URIs do *not* contain a project or tenant in the URI structure
like Nova's REST API URIs do, but _get_alternate_link() method of the
image ViewBuilder tacks it on improperly:
def _get_alternate_link(self, request, identifier):
Create an alternate link for a specific image id.
glance_url = glance.generate_glance_url()
glance_url = self._update_glance_link_prefix(glance_url)
return '/'.join([glance_url,
request.environ[nova.context].project_id,
self._collection_name,
str(identifier)])
It's my suspicion that nobody actually uses these alternate links
anyway, but the fix is simple: just remove the
request.environ['nova.context'].project_id in the URL join above.
Note that, yet again, the image service stubs and fakes in the API unit
testing masked this problem. In cleaning up the unit tests to get rid of
the stubbed out image service code, I uncovered this.
** Affects: nova
Importance: Undecided
Assignee: Jay Pipes (jaypipes)
Status: New
** Tags: low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) = Jay Pipes (jaypipes)
--
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/1343080
Title:
alternate link type in GET /images incorrectly includes the
project/tenant in the URI
Status in OpenStack Compute (Nova):
New
Bug description:
Clearly nobody really uses the application/vnd.openstack.image links
in the returned results from GET /v2/{tenant}/images REST API call,
since the link URI returned in it is wrong.
Glance URIs do *not* contain a project or tenant in the URI structure
like Nova's REST API URIs do, but _get_alternate_link() method of the
image ViewBuilder tacks it on improperly:
def _get_alternate_link(self, request, identifier):
Create an alternate link for a specific image id.
glance_url = glance.generate_glance_url()
glance_url = self._update_glance_link_prefix(glance_url)
return '/'.join([glance_url,
request.environ[nova.context].project_id,
self._collection_name,
str(identifier)])
It's my suspicion that nobody actually uses these alternate links
anyway, but the fix is simple: just remove the
request.environ['nova.context'].project_id in the URL join above.
Note that, yet again, the image service stubs and fakes in the API
unit testing masked this problem. In cleaning up the unit tests to get
rid of the stubbed out image service code, I uncovered this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1343080/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1343106] [NEW] heat resource page produces yellow page
Public bug reported: Once a stack is created successfully, user can navigate to following page project - stacks - [Select a stack] - [Click on Resource tab] - [select one of the resource like nova_instance, cinder_volume, etc] In this page, 'Resource ID' is provided with hyperlink to an respective resource such as instance, volume, etc. When the user click on this hyperlink, it produces an wrong url (example: localhost/project/stacks/stack/3b99a232-f337-4375-8b03-031c3414645c/cinder_volume/None) and causing python yellow page as shown in the attachment ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Attachment added: yellow page.pdf https://bugs.launchpad.net/bugs/1343106/+attachment/4154489/+files/yellow%20page.pdf ** Changed in: horizon Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam) -- 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/1343106 Title: heat resource page produces yellow page Status in OpenStack Dashboard (Horizon): New Bug description: Once a stack is created successfully, user can navigate to following page project - stacks - [Select a stack] - [Click on Resource tab] - [select one of the resource like nova_instance, cinder_volume, etc] In this page, 'Resource ID' is provided with hyperlink to an respective resource such as instance, volume, etc. When the user click on this hyperlink, it produces an wrong url (example: localhost/project/stacks/stack/3b99a232-f337-4375-8b03-031c3414645c/cinder_volume/None) and causing python yellow page as shown in the attachment To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1343106/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
