[Yahoo-eng-team] [Bug 1403091] [NEW] glance message queue is named as 'openstack' instead of 'glance'
Public bug reported: Most of the openstack services has named the corresponding messaging control_exchange with the respective service name. But glance is named it as 'openstack'. So this bug is filed to name it as 'glance' to make consistent with other services ** Affects: glance Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: glance Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1403091 Title: glance message queue is named as 'openstack' instead of 'glance' Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Most of the openstack services has named the corresponding messaging control_exchange with the respective service name. But glance is named it as 'openstack'. So this bug is filed to name it as 'glance' to make consistent with other services To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1403091/+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 1402572] [NEW] hypervisor list and details page reports invalid data
Public bug reported: Nova some times allows to have same hypervisor_hostname for more than one hypervisor. In this scenario, horizon hypervisor Table view and Detail view shows invalid data as follows: Table View: For those hypervisors having same hypervisor_hostname , Table view reports the same values for all of them, irrespective of actual values Detail View: For those hypervisors having same hypervisor_hostname , Deatils view reports the instance from all them , instead of for the given hypervisor. ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** 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/1402572 Title: hypervisor list and details page reports invalid data Status in OpenStack Dashboard (Horizon): New Bug description: Nova some times allows to have same hypervisor_hostname for more than one hypervisor. In this scenario, horizon hypervisor Table view and Detail view shows invalid data as follows: Table View: For those hypervisors having same hypervisor_hostname , Table view reports the same values for all of them, irrespective of actual values Detail View: For those hypervisors having same hypervisor_hostname , Deatils view reports the instance from all them , instead of for the given hypervisor. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1402572/+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 1382169] [NEW] about window is missing
Public bug reported: In Horizon, the version details of the openstack is not provided. Usually all the software provides the About dialog to provide the details of the product version. Its missing in the Horizon ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** 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/1382169 Title: about window is missing Status in OpenStack Dashboard (Horizon): New Bug description: In Horizon, the version details of the openstack is not provided. Usually all the software provides the About dialog to provide the details of the product version. Its missing in the Horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1382169/+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 1356280] [NEW] vmware: vcdriver fails to resize with NotImlementedError
Public bug reported: On the master code, compute driver is configured to use vmware vc driver In this scenario resize of the instance failed with following exception : 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 308, in decorated_function 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3491, in prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher filter_properties) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3480, in prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher node) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3445, in _prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher limits=limits) as claim: 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/openstack/common/lockutils.py, line 325, in inner 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher return f(*args, **kwargs) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/resource_tracker.py, line 172, in resize_claim 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher instance_type) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/resource_tracker.py, line 193, in _create_migration 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher migration.dest_host = self.driver.get_host_ip_addr() 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/virt/driver.py, line 428, in get_host_ip_addr 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher raise NotImplementedError() 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher NotImplementedError ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1356280 Title: vmware: vcdriver fails to resize with NotImlementedError Status in OpenStack Compute (Nova): New Bug description: On the master code, compute driver is configured to use vmware vc driver In this scenario resize of the instance failed with following exception : 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 308, in decorated_function 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3491, in prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher filter_properties) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3480, in prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher node) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/manager.py, line 3445, in _prep_resize 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher limits=limits) as claim: 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/openstack/common/lockutils.py, line 325, in inner 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher return f(*args, **kwargs) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/resource_tracker.py, line 172, in resize_claim 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher instance_type) 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/compute/resource_tracker.py, line 193, in _create_migration 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher migration.dest_host = self.driver.get_host_ip_addr() 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/nova/nova/virt/driver.py, line 428, in get_host_ip_addr 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher raise NotImplementedError() 2014-08-13 16:00:04.170 TRACE oslo.messaging.rpc.dispatcher NotImplementedError To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1356280/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net
[Yahoo-eng-team] [Bug 1356309] [NEW] allow_resize_to_same_host is not handled properly in the resize() api
Public bug reported: allow_resize_to_same_host is used to direct the 'resize' action to the same node where the instance was running now. But the nova.compute.api. resize() method is not taking care of this condition as of now when this flag is set to TRUE. Following code set the force_nodes to make sure that, the instance is resized to the same node again. if not CONF.allow_resize_to_same_host: filter_properties['ignore_hosts'].append(instance['host']) else: if instance['host'] != instance['node']: filter_properties['force_nodes'] = [instance['node']] ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1356309 Title: allow_resize_to_same_host is not handled properly in the resize() api Status in OpenStack Compute (Nova): New Bug description: allow_resize_to_same_host is used to direct the 'resize' action to the same node where the instance was running now. But the nova.compute.api. resize() method is not taking care of this condition as of now when this flag is set to TRUE. Following code set the force_nodes to make sure that, the instance is resized to the same node again. if not CONF.allow_resize_to_same_host: filter_properties['ignore_hosts'].append(instance['host']) else: if instance['host'] != instance['node']: filter_properties['force_nodes'] = [instance['node']] To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1356309/+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 1346201] [NEW] v2.0/tenants fails to report the 'extra' field values in the project
Public bug reported:
Assume that, the project admin is created in the keystone db with
extra filed having following values:
{test:value}
Then on running GET on the REST API v2.0/tenants, returns the following
response
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
test: value, -- ERROR
name: admin
}
This should be returning the response as follows:
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
{
test: value
}, -- JSON String
name: admin
}
** Affects: keystone
Importance: Undecided
Assignee: Kanagaraj Manickam (kanagaraj-manickam)
Status: New
** Changed in: keystone
Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1346201
Title:
v2.0/tenants fails to report the 'extra' field values in the project
Status in OpenStack Identity (Keystone):
New
Bug description:
Assume that, the project admin is created in the keystone db with
extra filed having following values:
{test:value}
Then on running GET on the REST API v2.0/tenants, returns the
following response
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
test: value, -- ERROR
name: admin
}
This should be returning the response as follows:
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
{
test: value
}, -- JSON String
name: admin
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1346201/+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 1346207] [NEW] v2.0/tenants/{tenantId} reports 404
Public bug reported:
On running GET on the v2.0/tenants returns two projects as follows:
{
tenants_links: [],
tenants: [
{
description: null,
enabled: true,
id: 0f90bb31a01c453f851a5ca4e5e178ab,
name: demo
},
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
test: value,
name: admin
}
]
}
Then , on running v2.0/tenants/0f90bb31a01c453f851a5ca4e5e178ab reports
404.
But it should be returning the project demo details
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1346207
Title:
v2.0/tenants/{tenantId} reports 404
Status in OpenStack Identity (Keystone):
New
Bug description:
On running GET on the v2.0/tenants returns two projects as follows:
{
tenants_links: [],
tenants: [
{
description: null,
enabled: true,
id: 0f90bb31a01c453f851a5ca4e5e178ab,
name: demo
},
{
description: null,
enabled: true,
id: dc0a88dc51624167b747211ec050a08e,
test: value,
name: admin
}
]
}
Then , on running v2.0/tenants/0f90bb31a01c453f851a5ca4e5e178ab
reports 404.
But it should be returning the project demo details
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1346207/+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 1346210] [NEW] keystone v2.0 API docs reported with invalid information
Public bug reported: The keystone API page http://developer.openstack.org/api-ref- identity-v2.html is reporting the following statements, meaning that, it generates the token only for the compute API Get an authentication token that permits access to the Compute API. This line should be changed to following line Get an authentication token that permits access to the Openstack Service API. Here, the word Compute is to be changed to Openstack Service ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1346210 Title: keystone v2.0 API docs reported with invalid information Status in OpenStack Identity (Keystone): New Bug description: The keystone API page http://developer.openstack.org/api-ref- identity-v2.html is reporting the following statements, meaning that, it generates the token only for the compute API Get an authentication token that permits access to the Compute API. This line should be changed to following line Get an authentication token that permits access to the Openstack Service API. Here, the word Compute is to be changed to Openstack Service To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1346210/+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
[Yahoo-eng-team] [Bug 1334233] [NEW] compute_manager network allocation retries not handled properly
Public bug reported: in the manager.py, ComputeManager has a method _allocate_network_async and uses the CONF parameter network_allocate_retries. While this method retries, the logic used is not proper as listed below: retry_time *= 2 if retry_time 30: retry_time = 30 This bug is filed to correct it as follows: if retry_time 30: retry_time = 30 else retry_time *= 2 This will avoid the calculation of retry time out when the timeout reaches beyond 30 sec. ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1334233 Title: compute_manager network allocation retries not handled properly Status in OpenStack Compute (Nova): New Bug description: in the manager.py, ComputeManager has a method _allocate_network_async and uses the CONF parameter network_allocate_retries. While this method retries, the logic used is not proper as listed below: retry_time *= 2 if retry_time 30: retry_time = 30 This bug is filed to correct it as follows: if retry_time 30: retry_time = 30 else retry_time *= 2 This will avoid the calculation of retry time out when the timeout reaches beyond 30 sec. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1334233/+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 1332196] [NEW] endpoint table is missing reference to region table
Public bug reported: Keystone is provided with region table as given here for storing the region details : mysql desc region - ; +--+--+--+-+-+---+ | Field| Type | Null | Key | Default | Extra | +--+--+--+-+-+---+ | id | varchar(64) | NO | PRI | NULL| | | description | varchar(255) | NO | | NULL| | | parent_region_id | varchar(64) | YES | | NULL| | | extra| text | YES | | NULL| | +--+--+--+-+-+---+ But it is not consumed in the endpoint table as shown below, region column is still having the endpoint name mysql desc endpoint; ++--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | ++--+--+-+-+---+ | id | varchar(64) | NO | PRI | NULL| | | legacy_endpoint_id | varchar(64) | YES | | NULL| | | interface | varchar(8) | NO | | NULL| | | region | varchar(255) | YES | | NULL| | | service_id | varchar(64) | NO | MUL | NULL| | | url| text | NO | | NULL| | | extra | text | YES | | NULL| | | enabled| tinyint(1) | NO | | 1 | | ++--+--+-+-+---+ And this region column should be renamed to region_id and should be referring to the region table. This bug is filed to address this issue. As part of this model change, 1. the python-keystoneclient to consider the region_id in addition to the region name 2. keystone endpoint-xxx commands needs to be updated to consider the region_id in place of region ** Affects: keystone Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: keystone Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1332196 Title: endpoint table is missing reference to region table Status in OpenStack Identity (Keystone): New Bug description: Keystone is provided with region table as given here for storing the region details : mysql desc region - ; +--+--+--+-+-+---+ | Field| Type | Null | Key | Default | Extra | +--+--+--+-+-+---+ | id | varchar(64) | NO | PRI | NULL| | | description | varchar(255) | NO | | NULL| | | parent_region_id | varchar(64) | YES | | NULL| | | extra| text | YES | | NULL| | +--+--+--+-+-+---+ But it is not consumed in the endpoint table as shown below, region column is still having the endpoint name mysql desc endpoint; ++--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | ++--+--+-+-+---+ | id | varchar(64) | NO | PRI | NULL| | | legacy_endpoint_id | varchar(64) | YES | | NULL| | | interface | varchar(8) | NO | | NULL| | | region | varchar(255) | YES | | NULL| | | service_id | varchar(64) | NO | MUL | NULL| | | url| text | NO | | NULL| | | extra | text | YES | | NULL| | | enabled| tinyint(1) | NO | | 1 | | ++--+--+-+-+---+ And this region column should be renamed to region_id and should be referring to the region table. This bug is filed to address this issue. As part of this model change, 1. the python-keystoneclient to consider the region_id in addition to the region name 2. keystone endpoint-xxx commands needs to be updated to consider the region_id in place of region To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1332196/+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 1329261] [NEW] vmware: VCdriver creates same hypervisor_hostname for different vcenters with same Cluster name
Public bug reported: Consider the following scenario, where two nova-compute nodes are configured to different vcenter with same cluster named Cluster1: Compute-Node #1: --- hostname: devstack1 vmware.host_ip: 10.1.0.12 vmware.cluster_names: Cluster1Same cluster name Compute-Node #2: - hostname: devstack2 vmware.host_ip: 10.1.0.13 vmware.cluster_names: Cluster1Same cluster name hypervisor_hostname=domain-c26(Cluster1) In this scenario, VC driver creates the same value for compute_nodes.hypervisor_hostname as mentioned here. Compute_node | hypervisor_hostname #1 | domain-c26(Cluster1) #2 | domain-c26(Cluster1) Because same compute_nodes.hypervisor_hostname is created for more than one clusters, it creates the following issues in the horizon: 1. In admin-Hypervisors, the same CPU, Memory utilization is reported for both the clusters 2. In admin - Hypervisors- [Click on Hypervisor #1]-, the details page reports the same list of instance for both the clusters. Though the issue is seen in the horizon, the actual root cause is because vcdriver creates the same hypervisor_hostname for both the clusters. so this bug is filed to fix this issue, to create the hypervisor_hostname as follows: vmware.host_ip (vmware.cluster_name) Ex: 10.1.0.12 (Cluster1) ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Tags: hostname hypervisor vmware ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1329261 Title: vmware: VCdriver creates same hypervisor_hostname for different vcenters with same Cluster name Status in OpenStack Compute (Nova): New Bug description: Consider the following scenario, where two nova-compute nodes are configured to different vcenter with same cluster named Cluster1: Compute-Node #1: --- hostname: devstack1 vmware.host_ip: 10.1.0.12 vmware.cluster_names: Cluster1Same cluster name Compute-Node #2: - hostname: devstack2 vmware.host_ip: 10.1.0.13 vmware.cluster_names: Cluster1Same cluster name hypervisor_hostname=domain-c26(Cluster1) In this scenario, VC driver creates the same value for compute_nodes.hypervisor_hostname as mentioned here. Compute_node | hypervisor_hostname #1 | domain-c26(Cluster1) #2 | domain-c26(Cluster1) Because same compute_nodes.hypervisor_hostname is created for more than one clusters, it creates the following issues in the horizon: 1. In admin-Hypervisors, the same CPU, Memory utilization is reported for both the clusters 2. In admin - Hypervisors- [Click on Hypervisor #1]-, the details page reports the same list of instance for both the clusters. Though the issue is seen in the horizon, the actual root cause is because vcdriver creates the same hypervisor_hostname for both the clusters. so this bug is filed to fix this issue, to create the hypervisor_hostname as follows: vmware.host_ip (vmware.cluster_name) Ex: 10.1.0.12 (Cluster1) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1329261/+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 1329299] [NEW] In nova.db.sqlalchemy.model.ComputeNode, column hypervisor_hostname should be unique values
Public bug reported: In the nova model nova.db.sqlalchemy.model.ComputeNode, the column represents the hypervisor name and is not set to unique and not null values. This leads to have same hyerpvisor host name for more than one hypervisors and will end up in error scenarios. In order to avoid the this scenario, column should be set to following values nullable=False unique=True This bug is filed to address the same. ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1329299 Title: In nova.db.sqlalchemy.model.ComputeNode, column hypervisor_hostname should be unique values Status in OpenStack Compute (Nova): New Bug description: In the nova model nova.db.sqlalchemy.model.ComputeNode, the column represents the hypervisor name and is not set to unique and not null values. This leads to have same hyerpvisor host name for more than one hypervisors and will end up in error scenarios. In order to avoid the this scenario, column should be set to following values nullable=False unique=True This bug is filed to address the same. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1329299/+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 1327928] [NEW] Horizon admin Hypervisor details page does not provide hyeperlink to the instances
Public bug reported: Once an instance is created from the given hypervisor, those instance will be listed under Admin-Hypervisor-[Select Hypervisor]- Details Page as follows: Instance Name Instance ID instance-0001 8c314500-446a-499c-a1d0-0cc709ea52e0 And it does not provide the hyerlink to this instance details page. This defect is filed to provide hyerlink to the Instance Name say on clicking instance-0001 will browse to the page Admin-instance - [instance-0001] details page. ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** 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/1327928 Title: Horizon admin Hypervisor details page does not provide hyeperlink to the instances Status in OpenStack Dashboard (Horizon): New Bug description: Once an instance is created from the given hypervisor, those instance will be listed under Admin-Hypervisor-[Select Hypervisor]- Details Page as follows: Instance Name Instance ID instance-0001 8c314500-446a-499c-a1d0-0cc709ea52e0 And it does not provide the hyerlink to this instance details page. This defect is filed to provide hyerlink to the Instance Name say on clicking instance-0001 will browse to the page Admin-instance - [instance-0001] details page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1327928/+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 1317041] [NEW] cinder: volume details page does not show the source image details
Public bug reported: Cinder volume can be created from the given glance image. Once the volume is created, horizon does not show the image details in the volume details page. But as a user, i would expect this information should be reported. Technically, cinder stores this information in the volume's image meta data property ** Affects: horizon Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** 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/1317041 Title: cinder: volume details page does not show the source image details Status in OpenStack Dashboard (Horizon): New Bug description: Cinder volume can be created from the given glance image. Once the volume is created, horizon does not show the image details in the volume details page. But as a user, i would expect this information should be reported. Technically, cinder stores this information in the volume's image meta data property To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1317041/+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 1316556] [NEW] vmware: boot from image (create volume) is failing
Public bug reported: Nova fails to boot an instance from the image using create volume. Run time environment details: cinder is configured with VMDK driver nova is configured with Vmware Vc driver While nova is trying to provision a instance by creating the volume from the given VMDK image by creating a volume and booting from it, it failed to create the instance, though volume is created properly after given amount of time. This failure is occurring especially when the volume creation is taking more than 180 seconds. Exception thrown by nova compute is: Volume f36bf0ce-ef0d-4200-b15b- cf2de3689bbb did not finish being created even after we waited 221 seconds or 180 attempts. ** Affects: nova Importance: Undecided Assignee: Kanagaraj Manickam (kanagaraj-manickam) Status: New ** Tags: boot vmware volume ** Changed in: nova Assignee: (unassigned) = Kanagaraj Manickam (kanagaraj-manickam) ** Description changed: - Nova fails to create an instance from the image using create volume. + Nova fails to boot an instance from the image using create volume. Run time environment details: - cinder is configured with VMDK driver - nova is configured with Vmware Vc driver + cinder is configured with VMDK driver + nova is configured with Vmware Vc driver While nova is trying to provision a instance by creating the volume from the given VMDK image by creating a volume and booting from it, it failed to create the instance, though volume is created properly after given amount of time. This failure is occurring especially when the volume creation is taking more than 180 seconds. Exception thrown by nova compute is: Volume f36bf0ce-ef0d-4200-b15b- cf2de3689bbb did not finish being created even after we waited 221 seconds or 180 attempts. -- 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/1316556 Title: vmware: boot from image (create volume) is failing Status in OpenStack Compute (Nova): New Bug description: Nova fails to boot an instance from the image using create volume. Run time environment details: cinder is configured with VMDK driver nova is configured with Vmware Vc driver While nova is trying to provision a instance by creating the volume from the given VMDK image by creating a volume and booting from it, it failed to create the instance, though volume is created properly after given amount of time. This failure is occurring especially when the volume creation is taking more than 180 seconds. Exception thrown by nova compute is: Volume f36bf0ce-ef0d-4200-b15b- cf2de3689bbb did not finish being created even after we waited 221 seconds or 180 attempts. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1316556/+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 1316556] Re: vmware: boot from image (create volume) is failing
** Project changed: nova = nova (Ubuntu) ** Package changed: nova (Ubuntu) = ubuntu ** Package changed: ubuntu = nova (Ubuntu) -- 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/1316556 Title: vmware: boot from image (create volume) is failing Status in “nova” package in Ubuntu: New Bug description: Nova fails to boot an instance from the image using create volume. Run time environment details: cinder is configured with VMDK driver nova is configured with Vmware Vc driver While nova is trying to provision a instance by creating the volume from the given VMDK image by creating a volume and booting from it, it failed to create the instance, though volume is created properly after given amount of time. This failure is occurring especially when the volume creation is taking more than 180 seconds. Exception thrown by nova compute is: Volume f36bf0ce-ef0d-4200-b15b- cf2de3689bbb did not finish being created even after we waited 221 seconds or 180 attempts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1316556/+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
