Public bug reported:
In API modules in openstack_dashboard api such as novaclient, neutronclient and
so on, API client objects (novaclient, neutronclient...) are created every time
openstack_dashboard/api methods are called even in a same request.
Recreating API client object leads to recreating
Public bug reported:
When we shelve an instance via CLI,
in horizon instance table, the 'loading' image is continuously showing in the
status column.
This bug is already reported and fixed in bug #1318558 but it is not fixed
properly.
for rescue it is working fine but not for shelved offloaded.
Public bug reported:
2014-07-31 07:14:07.574 ERROR nova.api.openstack
[req-98b42d5d-575f-4209-b711-4cb2ae8ef14e FloatingIPsNegativeTestXML-1138647745
FloatingIPsNegativeTestXML-1764448859] Caught error: Floating ip pool not found.
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack Traceback
Public bug reported:
https://review.openstack.org/#/c/75284/ changed pep8's envdir to venv.
But this breaks the assumptions made by infra for all pep8 jobs.
http://git.openstack.org/cgit/openstack-
infra/config/tree/modules/openstack_project/files/slave_scripts/run-
pep8.sh#n23
** Affects: keys
Public bug reported:
In keystone we currently log cadf events in the log, twice for every authN.
Once for pending and once for success/failure.
This is unnecessary since the notification_driver option in keystone.conf can
have multiple values, one of them being log.
** Affects: keystone
Im
Public bug reported:
I want to use cloudinit to get the network info and write it into the network
configuration file,
but it failed because cloudinit didn't get the network info.
In the vm, I used curl to test the metadata as below
#curl http://169.254.169.254/openstack/latest/meta_data.json
the
Public bug reported:
after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are
unable to boot vm attached to provider networks, this is a serious
regression for me as we mostly use provider networks.
bug which originated the commit
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1284
You have been subscribed to a public bug:
after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are
unable to boot vm attached to provider networks, this is a serious
regression for me as we mostly use provider networks.
bug which originated the commit
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
Horizon's source code is re-raising exceptions using the deprecated
syntax `raise exc_type, exc_value, exc_traceback`, to make the source
code compatible with Python 2 and Python 3, Horizon should user
`six.reraise()`.
** Affects: horizon
Importance: Undecided
Assig
Public bug reported:
The first field of the /var/log/cloud-init.log file alternates between
ISO and local date formats. In the attached example, the change happens
at:
2014-08-03 01:45:53,472 - util.py[DEBUG]: Read 12 bytes from
/proc/uptime
2014-08-03 01:45:53,472 - util.py[DEB
** Changed in: manila
Status: In Progress => Fix Committed
** Changed in: manila
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1284677
Added in
https://github.com/openstack/nova/commit/21bf0219f66ca9041bc0cf9c29e3a23c054d125c
** 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.la
Public bug reported:
Perhaps you should add the directory containing `libvirt.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libvirt' found
Package libvirt was not found in the pkg-config search path.
Perhaps you should add the directory containing `libvirt.pc'
to the PKG_CONFIG_
13 matches
Mail list logo
