[Yahoo-eng-team] [Bug 1291096] [NEW] log-dir variable doesnt work?
Public bug reported: When I set the value of log-dir (http://docs.openstack.org/trunk/config- reference/content/list-of-compute-config-options.html), it seems that the variable is not used at all. Although, setting logdir in nova.conf works for me. ** 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/1291096 Title: log-dir variable doesnt work? Status in OpenStack Compute (Nova): New Bug description: When I set the value of log-dir (http://docs.openstack.org/trunk /config-reference/content/list-of-compute-config-options.html), it seems that the variable is not used at all. Although, setting logdir in nova.conf works for me. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1291096/+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 1287105] [NEW] Horizon doesn't account for attached Volumes
Public bug reported: When I create a volume and attach it to an instance, this is not recorded in the instance details (i.e. the instance details will say no volumes attached) 1. Create VM 2. Create volume 3. Attach volume to VM from command line 4. Click on the instance details page Observed: No volumes attached Expected: Volume attached ** Affects: horizon Importance: Undecided Status: New -- 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/1287105 Title: Horizon doesn't account for attached Volumes Status in OpenStack Dashboard (Horizon): New Bug description: When I create a volume and attach it to an instance, this is not recorded in the instance details (i.e. the instance details will say no volumes attached) 1. Create VM 2. Create volume 3. Attach volume to VM from command line 4. Click on the instance details page Observed: No volumes attached Expected: Volume attached To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1287105/+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 1286520] [NEW] Taking a snapshot of an instance from CLI
Public bug reported: When I take a snapshot of an instance, I don't see the image in the images and snapshots tab. Although, I am able to boot a new server from the command line and see the new image in the UI. ** Affects: horizon Importance: Undecided Status: New -- 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/1286520 Title: Taking a snapshot of an instance from CLI Status in OpenStack Dashboard (Horizon): New Bug description: When I take a snapshot of an instance, I don't see the image in the images and snapshots tab. Although, I am able to boot a new server from the command line and see the new image in the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1286520/+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 1281928] [NEW] VMware VC driver reports incorrect value for vcpus_used
Public bug reported: The 'vcpus_used' value returned by the driver when reporting available resources is always 0. The VC driver doesn't track number of vcpus instead it trackers MHz shares. ** 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/1281928 Title: VMware VC driver reports incorrect value for vcpus_used Status in OpenStack Compute (Nova): New Bug description: The 'vcpus_used' value returned by the driver when reporting available resources is always 0. The VC driver doesn't track number of vcpus instead it trackers MHz shares. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281928/+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 1281395] [NEW] Debug option in ./run_tests.sh
Public bug reported: In other projects like nova, you can run tests with debug mode by passing a -d flag to ./run_tests.sh, in horizon this doesn't exist. Not sure whether this is a bug or not, but it will be extremely useful to have it. ** Affects: horizon Importance: Undecided Status: New -- 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/1281395 Title: Debug option in ./run_tests.sh Status in OpenStack Dashboard (Horizon): New Bug description: In other projects like nova, you can run tests with debug mode by passing a -d flag to ./run_tests.sh, in horizon this doesn't exist. Not sure whether this is a bug or not, but it will be extremely useful to have it. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1281395/+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 1274427] [NEW] Instance list
Public bug reported: When there are more than 20 instances, there is only a next button to see the next 20 instances, but there isn't a back button, so you cant see the last 20 instance. ** Affects: horizon Importance: Undecided Status: New -- 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/1274427 Title: Instance list Status in OpenStack Dashboard (Horizon): New Bug description: When there are more than 20 instances, there is only a next button to see the next 20 instances, but there isn't a back button, so you cant see the last 20 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1274427/+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 1269034] Re: VMware: shuting down a VM in vmware doesn't update the status in openstack
** Changed in: nova Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1269034 Title: VMware: shuting down a VM in vmware doesn't update the status in openstack Status in OpenStack Compute (Nova): Invalid Bug description: Steps to reproduce this: 1. Have openstack integrated with vmware 2. Start VM from openstack 3. login and poweroff the instance 4. Nova sees the changed status after 5 minutes The only relevant line is in /var/log/nova/compute.log: 2014-01-14 10:36:14.123 2459 WARNING nova.compute.manager [-] [instance: 4a43d5f2-57dd-43ad-a75c-48b4853fb62a] Instance shutdown by itself. Calling the stop API. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1269034/+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 1270196] Re: Nova services have duplication of default values for configuration
** Changed in: nova Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1270196 Title: Nova services have duplication of default values for configuration Status in OpenStack Compute (Nova): Invalid Bug description: In nova/service.py, the configuration defaults for the *_listen, *_listen_port are specified both in Opt and while using getattr to read the option value- self.host = getattr(CONF, '%s_listen' % name, 0.0.0.0) self.port = getattr(CONF, '%s_listen_port' % name, 0) self.workers = getattr(CONF, '%s_workers' % name, None) This is duplication of the default values and might produce inconsistent results when someone modified only one of these. Another problem in the same code above is that reading an erroneous config value (lets say foo_workers) will not fail and will simply give a default. This makes it easy for a typo in config to pass silently. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1270196/+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 1258024] Re: Wrong flavor name on show_server
** Changed in: nova Status: Incomplete = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1258024 Title: Wrong flavor name on show_server Status in OpenStack Compute (Nova): Invalid Bug description: When I show server with nova show serverid ,it returns the flavor which does not I use when creating server. I think it is a bug. Basically what is happening is: 1.creating a flavor flavor1 ,flavorid 10 2.deleting flavor flavor1 3.creating a flavor flavor2, flavorid 10 4.booting a server with flavor2 5.showing server details. This bug because we show flavor details with flavorid in API, but the flavorid is not primary key in table.(another parameter id is PK) So I think we should remove flavorid from the table and show flavor with id. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1258024/+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 1257756] Re: multiple services running causes failure
This is not a Nova bug, stacking and unstacking is done using scripts from devstack. Anyways, you can solve this problem by killing the n-api and n-cpu process. You can do something like this: ps aux | grep nova, then kill the nova-api and nova-compute processes. I believe this problem happens when you have multiple workers for nova-api. ** Changed in: nova Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1257756 Title: multiple services running causes failure Status in OpenStack Compute (Nova): Invalid Bug description: Scenario : when stack.sh(from devstack) script is run for the first time and if for any reason the user unstack the openstack by using unstack.sh and clean.sh. And then again install it Issue : during 2nd run of stack.sh , few nova services specially n-cpu and n-api fails running. It happens because of unstacking the last stack these services was not killed. During 2nd run, the log file says : multiple services running on the same address (same URI). there would be multiple duplicate services runs which causes current install fails. the above message can be view. on running the services for example. just run nova-api on terminal Traceback : it will show address already in use. ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257756/+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 1260919] [NEW] Select All box not functioning
Public bug reported: In the admin panel, images tab, checking the corner check box to select all images is not function (i.e. it doesn't select an images) ** Affects: horizon Importance: Undecided Status: New -- 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/1260919 Title: Select All box not functioning Status in OpenStack Dashboard (Horizon): New Bug description: In the admin panel, images tab, checking the corner check box to select all images is not function (i.e. it doesn't select an images) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1260919/+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 1257998] [NEW] VMware driver reporting incorrect available vcpus
Public bug reported: -Setting: Two ESX boxes with 4 cores each A VC with a cluster attached to two ESX boxes. One of the ESX boxes is disconnected (Not removed) -Driver reporting: Driver is reporting 8 available cores -Expected: Driver should report only 4 cores, since one of the ESX boxes is disconnected ** Affects: nova Importance: Undecided Assignee: Maithem (maithem) Status: New ** Tags: driver vmware ** Description changed: -Setting: Two ESX boxes with 4 cores each - A VC with a cluster attached to two ESX boxes. + A VC with a cluster attached to two ESX boxes. One of the ESX boxes is disconnected (Not removed) -Driver reporting: - Driver is reporting 8 available cores - Expected: - Driver should report only 4 cores, since one of the ESX boxes is disconnected + Driver is reporting 8 available cores + + -Expected: + + Driver should report only 4 cores, since one of the ESX boxes is + disconnected -- 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/1257998 Title: VMware driver reporting incorrect available vcpus Status in OpenStack Compute (Nova): New Bug description: -Setting: Two ESX boxes with 4 cores each A VC with a cluster attached to two ESX boxes. One of the ESX boxes is disconnected (Not removed) -Driver reporting: Driver is reporting 8 available cores -Expected: Driver should report only 4 cores, since one of the ESX boxes is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1257998/+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 1250320] Re: There is not any error information while try to update RAM of quota with 0
This is not a bug, the reason you are able to set ram to zero is because the tenant total used ram is 0. Basically when you update an attribute (i.e. ram) , your lower bound becomes min(0, used so far). So for example, if you have one instance running and it is assigned 100mb, then when try to update the ram to 0 it will throw an exception. ** Changed in: nova Status: Confirmed = Invalid ** Changed in: nova Assignee: Maithem (maithem) = (unassigned) -- 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/1250320 Title: There is not any error information while try to update RAM of quota with 0 Status in OpenStack Compute (Nova): Invalid Bug description: [root@ns11 ~]# nova quota-update --ram 0 a1a8dbd9285f4d0ab61d13af3958c8c9 [root@ns11 ~]# nova quota-show --tenant a1a8dbd9285f4d0ab61d13af3958c8c9 +-+---+ | Quota | Limit | +-+---+ | instances | 10| | cores | 20| | ram | 0| | floating_ips| 10| | fixed_ips | -1| | metadata_items | 128 | | injected_files | 1 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255 | | key_pairs | 100 | | security_groups | 10| | security_group_rules| 20| +-+---+ # EXPECTED RESULTS Prompt the input RAM in quota should be greater than 0 # Actual Result update is successful it doesn't make sense to set the quota for RAM, DISK, CPU with 0. It is impossible for a virtual machine without RAM or DISK or CPU. so when the user tries to set RAM with 0, it is better to prompt error information and suggest to set with a configured default value, it will be better user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1250320/+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
