Public bug reported:
Currently zookeeper's log files grow without limit which can cause a
machine to eventually run out of disk space.
The zookeeper package should include a logrotate script or configure
log4j (whichever is most appropriate) to rotate the log files.
We currently use the
Public bug reported:
Currently zookeeper's log files grow without limit which can cause a
machine to eventually run out of disk space.
The zookeeper package should include a logrotate script or configure
log4j (whichever is most appropriate) to rotate the log files.
We currently use the
Public bug reported:
Currently /etc/cups/cups-browsed.conf does not include 'cups' as a
BrowseRemoteProtocols option.
Since some older cups servers do not support dnssd enabling cups as well
seems to be a good default. I do not believe that there are any
additional security implications.
See
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1161338
Title:
python-nova should depend on ebtables
To manage notifications about this bug go to:
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161338
Title:
python-nova should depend on ebtables
To manage notifications about this bug go to:
Public bug reported:
After upgrading my installation from Folsom to Grizzly I received the
below error message when attempting to create a volume using the EC2 API
(I did not verify with the Nova API).
I have configured two regions; one each with a cinder endpoint. This
works for all other
*** This bug is a duplicate of bug 1087735 ***
https://bugs.launchpad.net/bugs/1087735
** This bug has been marked a duplicate of bug 1087735
Attaching volume fails if keystone has multiple endpoints of Cinder
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
After upgrading my installation from Folsom to Grizzly I received the
below error message when attempting to create a volume using the EC2 API
(I did not verify with the Nova API).
I have configured two regions; one each with a cinder endpoint. This
works for all other
*** This bug is a duplicate of bug 1087735 ***
https://bugs.launchpad.net/bugs/1087735
** This bug has been marked a duplicate of bug 1087735
Attaching volume fails if keystone has multiple endpoints of Cinder
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Another data point:
We have another machine with the same identical hardware, firmware and
OS, but running an earlier kernel and it is not suffering from the same
problem. Of course we haven't had a disk failure on the hardware so
cannot say for sure that the bug does not exist in the earlier
Public bug reported:
When attempting to change a quota for one of my customers, with the
command below, I receive an error message instead of the command
succeeding.
What I see:
$ sudo nova-manage project quota --project=
--key=instances --value=15
Public bug reported:
When attempting to change a quota for one of my customers, with the
command below, I receive an error message instead of the command
succeeding.
What I see:
$ sudo nova-manage project quota --project=
--key=instances --value=15
Public bug reported:
Currently python-boto does not verify SSL certificates by default. This
is unacceptable as this exposes users to man in the middle attacks. This
can be worked around by the user (see below).
Unfortunately after enabling verification, python-boto uses it's own
cacerts.txt
Public bug reported:
Currently python-boto does not verify SSL certificates by default. This
is unacceptable as this exposes users to man in the middle attacks. This
can be worked around by the user (see below).
Unfortunately after enabling verification, python-boto uses it's own
cacerts.txt
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064835
Title:
keystoneclient fails on SSL certificates that work for other services
To manage notifications about this bug
Public bug reported:
I have recently installed python-keystoneclient within a debootstrapped
chroot and what I believe to be a dependency problem with the package.
After installing python-pkg-resources python-keystoneclient runs as
expected.
Testing:
(keystone)agy@bricked:~$ keystone catalog
@Dan
The default_character_set_name is set to 'latin1'. This system has been
upgraded through various lifecycles of Openstack which may explain it (a
more recent installation that I looked at is set to 'utf8').
I would argue that setting the character set explicitly on table
creation is the
@Dan
The default_character_set_name is set to 'latin1'. This system has been
upgraded through various lifecycles of Openstack which may explain it (a
more recent installation that I looked at is set to 'utf8').
I would argue that setting the character set explicitly on table
creation is the
Public bug reported:
What follows are my recollection of events resulting in my Samsung
900x4C no longer POSTing after updates.
I was running an outdated Quantal install (of a few weeks old) and
recently applied Quantal updates to bring my laptop up to date. One of
the updates included the
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064759
Title:
Samsung 900x4C will not POST after applying Quantal updates
To manage notifications about this bug go to:
Public bug reported:
The upgrade from Precise+Essex to Precise+Folsom using the ubuntu-cloud
archive fails while running the 092_add_instance_system_metadata
migration. The migration fails while creating the
`instance_system_metadata` table (see below).
The '1005' MySQL error indicates that a
** Patch added: 092_add_instance_system_metadata.patch
https://bugs.launchpad.net/bugs/1062277/+attachment/3375835/+files/092_add_instance_system_metadata.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Public bug reported:
I was upgrading a Precise + Essex install, using the ubuntu-cloud
archive, to Precise + Folsom.
During the upgrade I received an error during the package installation
of python-swiftclient (see below).
The workaround was to remove the 'swift' package before installing
Public bug reported:
I have recently upgraded from Precise + Essex to Precise + Folsom using
the ubuntu-cloud archive.
The openstack-dashboard with the ubuntu theme looks incorrect/broken.
The functionality of the UI looks to be correct.
Unfortunately, I cannot provide much more information
** Attachment added: dashboard-problems.png
https://bugs.launchpad.net/bugs/1062165/+attachment/3375287/+files/dashboard-problems.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062165
Title:
Added screenshot after removing the theme, reloading apache and
refreshing the browser.
** Attachment added: dashboard-wo-ubuntu-theme.png
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1062165/+attachment/3375296/+files/dashboard-wo-ubuntu-theme.png
--
You received this
Public bug reported:
The dashboard should not add WSGI config in /etc/apache2/conf.d
providing a _global_ configuration change. This breaks all the other
VirtualHosts on the Apache server.
I had a previously defined VirtualHost which served the dashboard. The
package installation failed during
Public bug reported:
The upgrade from Precise+Essex to Precise+Folsom using the ubuntu-cloud
archive fails while running the 092_add_instance_system_metadata
migration. The migration fails while creating the
`instance_system_metadata` table (see below).
The '1005' MySQL error indicates that a
** Patch added: 092_add_instance_system_metadata.patch
https://bugs.launchpad.net/bugs/1062277/+attachment/3375835/+files/092_add_instance_system_metadata.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded today and found that I had this issue.
Not all of my instances had duplicate entries in the
`instance_id_mappings` table, however I did have more entries within the
`instance_id_mappings` than within the `instances` table.
It seems that the `id` column in the `instances` table is
The loose relationship between two auto_incrementing `id` columns of
different tables is insanely brittle. I am not convinced that the
intention was for the relation to work this way. It may simple be a
problem with part of the code referencing `id` instead of `uuid`.
The uuid's in the
I upgraded today and found that I had this issue.
Not all of my instances had duplicate entries in the
`instance_id_mappings` table, however I did have more entries within the
`instance_id_mappings` than within the `instances` table.
It seems that the `id` column in the `instances` table is
The loose relationship between two auto_incrementing `id` columns of
different tables is insanely brittle. I am not convinced that the
intention was for the relation to work this way. It may simple be a
problem with part of the code referencing `id` instead of `uuid`.
The uuid's in the
Public bug reported:
Running `ceph-authtool keyringfile --print` throws an error claiming
that it does not know the option however, the help indicates that this
is the valid long-option for '-p'.
Looking at the source code, the command expects '--print-key' and using
this works as expected.
** Patch added: Correct help message to provide correct long option
'--print-key'
https://bugs.launchpad.net/bugs/1056462/+attachment/3343155/+files/ceph_authtool.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in
Public bug reported:
Running `ceph-authtool keyringfile --print` throws an error claiming
that it does not know the option however, the help indicates that this
is the valid long-option for '-p'.
Looking at the source code, the command expects '--print-key' and using
this works as expected.
** Patch added: Correct help message to provide correct long option
'--print-key'
https://bugs.launchpad.net/bugs/1056462/+attachment/3343155/+files/ceph_authtool.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After upgrading to 3.5.0-15 on Quantal my Samsung 900X4C boots with it's
display backlight off.
The backlight is turned off immediately after grub and before the kernel
messages start. The display remains off and the keyboard keys assigned
to adjust the brightness do not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055771
Title:
Samsung 900X4C laptop boots with display backlight off
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1055771 ***
https://bugs.launchpad.net/bugs/1055771
Public bug reported:
After upgrading to 3.5.0-15 on Quantal my Samsung 900X4C boots with it's
display backlight off.
The backlight is turned off immediately after grub and before the kernel
messages
*** This bug is a duplicate of bug 1055771 ***
https://bugs.launchpad.net/bugs/1055771
This is the same bug report as bug#1055771. They are identical and are
not separate bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Rafi,
Thanks for the suggestion. What you describe used to happen to me when
we were using Oneiric's libvirtd (LP#903212). Since upgrading to Precise
I haven't experienced the exact problem you're having.
My issue is that libvirtd seems to temporarily stop responding, enough
to block
@Rafi,
Thanks for the suggestion. What you describe used to happen to me when
we were using Oneiric's libvirtd (LP#903212). Since upgrading to Precise
I haven't experienced the exact problem you're having.
My issue is that libvirtd seems to temporarily stop responding, enough
to block
@Serge,
As mentioned in #1 the cluster is running Precise + Essex. Unfortunately
I cannot consistently reproduce the problem, however the problem has
been recurring approximately once per month.
As mentioned in #5 I think that perhaps nova-compute is attempting to
query libvirtd and libvirtd is
@Serge,
As mentioned in #1 the cluster is running Precise + Essex. Unfortunately
I cannot consistently reproduce the problem, however the problem has
been recurring approximately once per month.
As mentioned in #5 I think that perhaps nova-compute is attempting to
query libvirtd and libvirtd is
*** This bug is a duplicate of bug 1033934 ***
https://bugs.launchpad.net/bugs/1033934
** This bug has been marked a duplicate of bug 1033934
Attempting to change regions in the dashboard does not display correctly
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1033920 ***
https://bugs.launchpad.net/bugs/1033920
** This bug has been marked a duplicate of bug 1033920
Dashboard raises a ServiceCatalogException when attempting to download juju
settings
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1033934 ***
https://bugs.launchpad.net/bugs/1033934
** This bug has been marked a duplicate of bug 1033934
Attempting to change regions in the dashboard does not display correctly
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1033920 ***
https://bugs.launchpad.net/bugs/1033920
** This bug has been marked a duplicate of bug 1033920
Dashboard raises a ServiceCatalogException when attempting to download juju
settings
--
You received this bug notification because you are a
@Adam:
Bug #1006898 seems unlikely IMHO. We are not running with 'multi_host'
nor with VLANS. So there is one dnsmasq process.
The following is just conjecture as the event has rotated out of the logs and I
have not done any further testing. These events happen rather infrequently, but
are a
@Adam:
Bug #1006898 seems unlikely IMHO. We are not running with 'multi_host'
nor with VLANS. So there is one dnsmasq process.
The following is just conjecture as the event has rotated out of the logs and I
have not done any further testing. These events happen rather infrequently, but
are a
Public bug reported:
When attempting to download the juju settings file from the dashboard I
receive an exception¹ which displays an ugly, blank 500 error message.
It seems that the juju module is expecting an S3 endpoint in my service
catalog, not finding it and throwing an exception which is
Public bug reported:
After logging in to the dashboard in one region I attempted to change
regions by selecting the other region in the top right corner. After
doing this, login credentials form elements appear on the bottom left-
hand side and does not look correct (I have attached screenshots
** Attachment added: Tarball containing images illustrating the display
problem.
https://bugs.launchpad.net/bugs/1033934/+attachment/3251203/+files/region-displays-incorrectly.tar.gz
** Description changed:
After logging in to the dashboard in one region I attempted to change
regions by
Public bug reported:
When attempting to download the juju settings file from the dashboard I
receive an exception¹ which displays an ugly, blank 500 error message.
It seems that the juju module is expecting an S3 endpoint in my service
catalog, not finding it and throwing an exception which is
Public bug reported:
After logging in to the dashboard in one region I attempted to change
regions by selecting the other region in the top right corner. After
doing this, login credentials form elements appear on the bottom left-
hand side and does not look correct (I have attached screenshots
** Attachment added: Tarball containing images illustrating the display
problem.
https://bugs.launchpad.net/bugs/1033934/+attachment/3251203/+files/region-displays-incorrectly.tar.gz
** Description changed:
After logging in to the dashboard in one region I attempted to change
regions by
Public bug reported:
Keystone's `token` table grows unconditionally with expired tokens.
Keystone should provide a backend-agnostic method to find and delete
these tokens. This could be run via a periodic task or supplied as a
script to run as a cron job.
An example SQL statement (if you're
** Description changed:
Keystone's `token` table grows unconditionally with expired tokens.
Keystone should provide a backend-agnostic method to find and delete
these tokens. This could be run via a periodic task or supplied as a
script to run as a cron job.
An example SQL
Public bug reported:
Keystone's `token` table grows unconditionally with expired tokens.
Keystone should provide a backend-agnostic method to find and delete
these tokens. This could be run via a periodic task or supplied as a
script to run as a cron job.
An example SQL statement (if you're
** Description changed:
Keystone's `token` table grows unconditionally with expired tokens.
Keystone should provide a backend-agnostic method to find and delete
these tokens. This could be run via a periodic task or supplied as a
script to run as a cron job.
An example SQL
** Description changed:
A client of mine attempted to rescue an instance by using the `nova
- rescuecl` command which failed putting the instance in the `ERROR`
- state.
+ rescue` command which failed putting the instance in the `ERROR` state.
I am running Openstack Essex on Ubuntu 12.04
** Description changed:
A client of mine attempted to rescue an instance by using the `nova
- rescuecl` command which failed putting the instance in the `ERROR`
- state.
+ rescue` command which failed putting the instance in the `ERROR` state.
I am running Openstack Essex on Ubuntu 12.04
Public bug reported:
A client of mine attempted to rescue an instance by using the `nova
rescuecl` command which failed putting the instance in the `ERROR`
state.
I am running Openstack Essex on Ubuntu 12.04 with KVM as my hypervisor
and I do not have `rescue_image_id`, `rescue_kernel_id` nor
** Description changed:
A client of mine attempted to rescue an instance by using the `nova
rescuecl` command which failed putting the instance in the `ERROR`
state.
I am running Openstack Essex on Ubuntu 12.04 with KVM as my hypervisor
and I do not have `rescue_image_id`,
Public bug reported:
A client of mine attempted to rescue an instance by using the `nova
rescuecl` command which failed putting the instance in the `ERROR`
state.
I am running Openstack Essex on Ubuntu 12.04 with KVM as my hypervisor
and I do not have `rescue_image_id`, `rescue_kernel_id` nor
** Description changed:
A client of mine attempted to rescue an instance by using the `nova
rescuecl` command which failed putting the instance in the `ERROR`
state.
I am running Openstack Essex on Ubuntu 12.04 with KVM as my hypervisor
and I do not have `rescue_image_id`,
We're running nova with nova.network.manager.FlatDHCPManager. Grepping
the nova-network machine's syslog shows that the last DHCP lease request
was on Jul 16 14:04:29
Sample from the log file:
Jul 16 14:04:29 dziban dnsmasq-dhcp[30249]: DHCPREQUEST(br100) 10.55.60.141
fa:16:3e:11:c5:37
Jul 16
We're running nova with nova.network.manager.FlatDHCPManager. Grepping
the nova-network machine's syslog shows that the last DHCP lease request
was on Jul 16 14:04:29
Sample from the log file:
Jul 16 14:04:29 dziban dnsmasq-dhcp[30249]: DHCPREQUEST(br100) 10.55.60.141
fa:16:3e:11:c5:37
Jul 16
** Description changed:
- Running proposed on one of our clusters, I see the following with
- instances started via juju. I have been unable to re-create the problem
- with raw ec2 commands.
+ Running Precise proposed on one of our clusters, I see the following
+ with instances started via juju.
** Description changed:
- Running proposed on one of our clusters, I see the following with
- instances started via juju. I have been unable to re-create the problem
- with raw ec2 commands.
+ Running Precise proposed on one of our clusters, I see the following
+ with instances started via juju.
Public bug reported:
What happens:
I have two regions and one availability zone (AZ) for my Essex cluster.
When creating a volume I accidentally used the region name instead of
the AZ name. This resulted in a volume being stuck in the creating
state which I cannot delete.
What I expect:
I
Public bug reported:
What happens:
I have two regions and one availability zone (AZ) for my Essex cluster.
When creating a volume I accidentally used the region name instead of
the AZ name. This resulted in a volume being stuck in the creating
state which I cannot delete.
What I expect:
I
Fortunately (or not) this has just recently occurred. We do not have
debug symbols installed.
It looks to me to be stuck on virDomainGetInfo(). Interestingly,
libvirtd seems to be responding when I query it. Perhaps there is a
missing timeout somewhere?
Backtrace from python:
(gdb) bt
#0
Fortunately (or not) this has just recently occurred. We do not have
debug symbols installed.
It looks to me to be stuck on virDomainGetInfo(). Interestingly,
libvirtd seems to be responding when I query it. Perhaps there is a
missing timeout somewhere?
Backtrace from python:
(gdb) bt
#0
I do not believe that we've seen this issue in the later releases of
Diablo and in Essex. I think that we can close this bug unless someone
objects or still experiences this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova
I do not believe that we've seen this issue in the later releases of
Diablo and in Essex. I think that we can close this bug unless someone
objects or still experiences this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 897140 ***
https://bugs.launchpad.net/bugs/897140
** This bug has been marked a duplicate of bug 897140
unassociated floating IPs not visible to admin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 897140 ***
https://bugs.launchpad.net/bugs/897140
** This bug has been marked a duplicate of bug 897140
unassociated floating IPs not visible to admin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Occassionally I need to deallocate floating IP addresses that my clients
have allocated but are not using. Attempting to do this throws a
NotAuthorized even if my user has the global role of cloudadmin.
Unfortunately the 'nova-manage' commands do not seem to provide a means
I ran the following SQL query to work around the issue:
sql UPDATE floating_ips SET deleted_at = NULL, fixed_ip_id = NULL,
project_id = NULL, host = NULL where floating_ips.deleted = 0 AND
floating_ips.auto_assigned = 0 and host is NULL;
--
You received this bug notification because you are a
Public bug reported:
Occassionally I need to deallocate floating IP addresses that my clients
have allocated but are not using. Attempting to do this throws a
NotAuthorized even if my user has the global role of cloudadmin.
Unfortunately the 'nova-manage' commands do not seem to provide a means
I ran the following SQL query to work around the issue:
sql UPDATE floating_ips SET deleted_at = NULL, fixed_ip_id = NULL,
project_id = NULL, host = NULL where floating_ips.deleted = 0 AND
floating_ips.auto_assigned = 0 and host is NULL;
--
You received this bug notification because you are a
@James:
It looks like the --help output doesn't list --region and lists
--os_region_name and --region_name instead. That said, my tests seem to
show that the --region option still works (for now).
Retesting:
$ for opt in region region_name os_region_name; do
for region in doesnotexist
@James:
It looks like the --help output doesn't list --region and lists
--os_region_name and --region_name instead. That said, my tests seem to
show that the --region option still works (for now).
Retesting:
$ for opt in region region_name os_region_name; do
for region in doesnotexist
@Sebastien:
Works for Me™
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978970
Title:
hud fails to accept keyboard input after pressing TAB
To manage notifications about this bug go to:
The symptoms are similar to what we experienced in LP#903212, however I
can confirm that libvirtd seems to be responding correctly in Precise.
Is there further information that we can provide?
$ dpkg-query --show nova-*
nova-api2012.1~e4~20120210.12574-0ubuntu1
nova-common
This has happened again.
Process listing:
$ ps auxwwwf | grep [n]ova-compute
nova 25735 0.0 0.0 48040 4 ?Ss Apr16 0:00 su -s /bin/sh
-c exec nova-compute --flagfile=/etc/nova/nova.conf
--flagfile=/etc/nova/nova-compute.conf nova
nova 25746 1.2 0.1 1725088 32604 ?
The symptoms are similar to what we experienced in LP#903212, however I
can confirm that libvirtd seems to be responding correctly in Precise.
Is there further information that we can provide?
$ dpkg-query --show nova-*
nova-api2012.1~e4~20120210.12574-0ubuntu1
nova-common
This has happened again.
Process listing:
$ ps auxwwwf | grep [n]ova-compute
nova 25735 0.0 0.0 48040 4 ?Ss Apr16 0:00 su -s /bin/sh
-c exec nova-compute --flagfile=/etc/nova/nova.conf
--flagfile=/etc/nova/nova-compute.conf nova
nova 25746 1.2 0.1 1725088 32604 ?
$ dpkg-query --show unity indicator-messages
indicator-messages 0.6.0-0ubuntu1
unity 5.10.0-0ubuntu3
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION=Ubuntu precise (development branch)
--
You received this bug notification
Public bug reported:
I am performing some tests with Keystone and multiple regions and have
discovered that nova client does not respect the --region argument
correctly.
Setup:
==
I have defined services within two regions:
- regionOne
- regionTwo
Tests:
==
# Ask for all endpoints
$
A little more clarification:
When setting NOVACLIENT_DEBUG in my shell's environment I can confirm
that Keystone returns the full catalog for all regions to the nova
client. Assuming this is the correct behavior for Keystone, then this is
a client-side filtering bug.
** Tags added: canonistack
Public bug reported:
The euc2ools commands do not support the --region flag for anything
other than EC2. I would like to define multiple regions and use these
commands against Eucalyptus and Openstack clouds (among others).
Currently the endpoint URL is hardcoded (see the function below).
Further testing shows that nova list commands respect --region
correctly. So this may only affect a subset of commands. I've updated
the bug description to reflect this.
** Summary changed:
- nova client does not respect regions
+ nova client does not respect regions for a subset of commands
--
Public bug reported:
I am performing some tests with Keystone and multiple regions and have
discovered that nova client does not respect the --region argument
correctly.
Setup:
==
I have defined services within two regions:
- regionOne
- regionTwo
Tests:
==
# Ask for all endpoints
$
A little more clarification:
When setting NOVACLIENT_DEBUG in my shell's environment I can confirm
that Keystone returns the full catalog for all regions to the nova
client. Assuming this is the correct behavior for Keystone, then this is
a client-side filtering bug.
** Tags added: canonistack
Public bug reported:
The euc2ools commands do not support the --region flag for anything
other than EC2. I would like to define multiple regions and use these
commands against Eucalyptus and Openstack clouds (among others).
Currently the endpoint URL is hardcoded (see the function below).
Further testing shows that nova list commands respect --region
correctly. So this may only affect a subset of commands. I've updated
the bug description to reflect this.
** Summary changed:
- nova client does not respect regions
+ nova client does not respect regions for a subset of commands
--
Public bug reported:
While Alt+TABing between windows I accidentally summoned the HUD and
triggered a case where all my keyboard input was ignored (including ESC,
backspace, Return but _not_ Ctrl+Alt+Fx).
How to reproduce:
1. Hit Alt key
2. Once the dash appears
3. Start typing something
1 - 100 of 226 matches
Mail list logo
