** Changed in: tripleo
Status: Triaged => Fix Released
--
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/1221620
Title:
KeyError: 'service' during schedule of bareme
** Changed in: nova
Status: Triaged => Invalid
** Changed in: tripleo
Status: Triaged => 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/1184445
Titl
Public bug reported:
I recently had some trouble with dnsmasq causing it to segfault in
certain situations. No doubt, this was a bug in dnsmasq. However, it was
quite troubling that Neutron never noted that dnsmasq had stopped
working. This is because dnsmasq is spawned as a daemon, even though it
I've added nova as I'm having a hard time reading through nova and
figuring out where it signals to the scheduler that it is available to
have things scheduled to it. That should probably be _after_ it has an
l2 agent. _OR_ the scheduler needs to become neutron-aware so that the
scheduler can retry
Public bug reported:
This is a minor bug but it will produce a very confusing error message
if the test ever fails. Examples include but are not limited to
nova.tests.api.openstack.compute.test_servers.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug no
Public bug reported:
This is a race condition.
Given a cloud with 0 compute nodes available, on a compute node:
* Start up neutron-openvswitch-agent
* Start up nova-compute
* nova boot an instance
Scenario 1:
* neutron-openvswitch-agent registers with Neutron before nova tries to boot
instance
This breaks deployment of new clouds in TripleO sometimes, and will
likely break scaling too. Hence the Critical status.
** Also affects: neutron
Importance: Undecided
Status: New
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status:
Public bug reported:
oslo.messaging needs to be updated to the latest alpha of 1.3.0 (a3 as
of bug filing) or if this bug is still open an oslo.messaging is
released, to the released version.
1.2.0a11 directly depends on d2to1, which is no longer in global
requirements and thus presents problems
Adding affects tripleo. The fix there is to manually add d2to1 to the
local pypi-mirror element in tripleo-image-elements. If this is fixed in
glance then the tripleo task can be closed. The CD undercloud has had
d2to1 manually added to the local pypi-mirror for now to unblock image
building.
** A
This is blocking ephemeral disk usage on hardware which is critical to
our image based updates via rebuild code path.
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status: New => Triaged
** Changed in: tripleo
Importance: Undecided => Criti
This seems _entirely_ keystone's issue. And I agree that not doing many
thousands of crud events is the right way to go. Closing the Heat task,
and I suggest keystone mark it as a dupe or attach it to the revocation-
events blueprint.
** Changed in: heat
Status: New => Invalid
--
You rece
** Also affects: nova
Importance: Undecided
Status: New
** Description changed:
ext3 is more generally available than ext4, but creating an ext3
filesystem involves a lot more writing than ext3. The only reason to
retain ext3 is to retain backward compatibility with very old guest
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status: New => Confirmed
** Changed in: tripleo
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Changed in: tripleo
Importance: Undecided => Critical
--
You received
Public bug reported:
To reproduce:
1. boot an instance
2. rebuild instance with a new image id
3. immediately restart nova-compute
-- instance is now stuck in REBUILD/rebuild_spawning state.
4. nova delete instance
-- instanec now says it is ACTIVE, but it cannot be deleted.
This traceback ap
I'm closing the heat task. Heat is doing the right thing here, I think
cloud-init was just doing the wrong one.
** Changed in: cloud-init
Status: New => In Progress
** Changed in: heat
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
** Changed in: diskimage-builder
Status: Fix Committed => 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/1205546
Title:
babel 1.0 dependency pytz isn't found
Status
Note that I've submitted a fix to kilo/stable requirements:
https://review.openstack.org/#/c/198072/
** 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 Comp
Public bug reported:
If one makes any files in that directory, such as an editor backup,
Keystone will explode on startup or at the next key rotation because it
assumes all files will pass int(filename)
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bu
Public bug reported:
Dec 18 02:51:28 ci-overcloud-controller0-nvacfowhjcy2 keystone:
/opt/stack/venvs/openstack/local/lib/python2.7/site-
packages/sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN-
predicate on "assignment.actor_id" was invoked with an empty sequence.
This results in a co
*** This bug is a duplicate of bug 1257723 ***
https://bugs.launchpad.net/bugs/1257723
David this is definitely a known issue in Keystone.
Note that one way to work around the extremely poor performance of
token_flush, is to use percona toolkit's 'pt-archiver' command:
https://git.openstack.
Public bug reported:
This is because we still have to filter results of an indexed query that
may return _millions_ of rows:
mysql> EXPLAIN SELECT token.id AS token_id FROM token WHERE token.valid = 1 AND
token.expires > '2014-02-05 01:28:07.725059' AND token.user_id =
'356d68464dc2478992427864
Public bug reported:
We had a temporary outage of Neutron, and many instances got stuck in
this state. 'nova delete' on them does not work until nova-compute is
forcibly restarted.
+--+
Public bug reported:
This instance will not go away despite multiple 'nova delete's
+--+-
Public bug reported:
* The id column is internal only, and yet, is varchar(64). This should
just be an auto incremented int.
* There are no indexes on anything.
* The comments claim that only DB2 has trouble with large deletes. This
is false. MySQL will hold gaps open on any indexes, including t
deprecation warning for 1 cycle.
** Affects: glance
Importance: Undecided
Assignee: Clint Byrum (clint-fewbar)
Status: In Progress
** Affects: tripleo
Importance: Critical
Assignee: Derek Higgins (derekh)
Status: In Progress
** Also affects: tripleo
Public bug reported:
This was observed recently durin an Ironic CI run:
2014-03-22 02:38:53.436 7916 ERROR neutron.agent.linux.ovsdb_monitor [-] Error
received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock:
receive failed (End of file)
2014-03-22 02:38:53.690 7916 ERROR ne
Public bug reported:
If you have a nova-baremetal managed server, and you issue a nova
rebuild, it will reboot and write a new image onto the instance.
However, if that fails, nova-baremetal wipes away the reference to the
instance_uuid, which means you cannot fix the machine out of band.
This i
I don't see this as a heat issue at all. Heat is deleting things and
accepting Neutron's answer that they are in fact deleted. Reassigning to
Neutron.
** Project changed: heat => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
This affects Heat, but it isn't a bug in Heat. Marking Invalid.
** Changed in: heat
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/1158684
T
** Changed in: heat
Status: New => Triaged
** Changed in: heat
Status: Triaged => Fix Released
--
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/1241395
T
30 matches
Mail list logo
