Reviewed: https://review.openstack.org/468559
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=dbaf80d2c94db074a6651c890d532a11baec8da0
Submitter: Jenkins
Branch:master
commit dbaf80d2c94db074a6651c890d532a11baec8da0
Author: Matt Riedemann
Date:
Public bug reported:
I hit an extra exception during a failed live migration rollback. This
exception occurred on the destination node. This bug is not about the
reason for the failed migration, but for the failure in the rollback.
The exception:
Traceback (most recent call last):
File
Public bug reported:
We can create volumes, networks, etc in an Ocata deployment using SSL,
but launching an instance fails with the following error in horizon:
https://pastebin.canonical.com/189552/ and an associated error in nova-
cloud-controller's apache2 nova-placement error log:
Reviewed: https://review.openstack.org/468103
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=d09c337619fed8664272848abb3a1351dd5e4c85
Submitter: Jenkins
Branch:master
commit d09c337619fed8664272848abb3a1351dd5e4c85
Author: prashkre
Date: Thu
Public bug reported:
It looks that patch https://review.openstack.org/#/c/428304/ made some
problems with creation of QoS policy. It can be observed in fullstack
tests, e.g. http://logs.openstack.org/93/468793/4/check/gate-neutron-
dsvm-fullstack-ubuntu-xenial/4ec5ac0/logs/dsvm-fullstack-
Public bug reported:
During the keystone meeting today [0], clarkb brought this to our
attention.
At some point during grenade tests [1], keystone will report 404 User Not Found
[2].
Opening this for primarily for investigative purposes until we figure
out what is going on.
[0]
The compute API code is wrong in stable/newton, but we don't need to fix
it there because we didn't actually populate cell0 in Newton. We started
creating instances in cell0 in Ocata:
https://github.com/openstack/nova/commit/bcbfee183e74f696085fcd5c18aff333fc5f1403
So in Newton you'll always get
** Also affects: charm-nova-cloud-controller
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/1694537
Title:
Instance creation
Public bug reported:
Seen here:
http://207.189.188.190/logs/47/468147/1/check-vote/ext-nova-
zuul/cbab6d1/n-cpu.log.gz?level=TRACE#_2017-05-26_22_56_46_579
Which resulted in nova-compute auto-disabling the service.
2017-05-26 22:55:27.826 19424 ERROR oslo_vmware.common.loopingcall [-] in fixed
Public bug reported:
2017-05-30 18:58:01.947 27929 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_ryuapp
[req-34115ed3-3043-4fcb-ba3f-ab0e4eb0e83c - - - - -] Agent main thread died of
an exception
2017-05-30 18:58:01.947 27929 ERROR
You have been subscribed to a public bug:
While executing heat event-list, different fields get displayed on CLI and
Dashboard.
The field event_id is missing in Dashboard instead of which we can see a
redundant field (Stack Resource, Resource). Below are the list of fields for an
event in CLI
** Changed in: horizon
Status: In Progress => Invalid
--
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/1648871
Title:
tox should be on test-requirements
** Changed in: horizon
Status: New => Invalid
--
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/1668715
Title:
Invalid actions for shelved instances should not
Public bug reported:
Description
===
nova-compute still report service up when libvirtd stop response,and
it's fake up state easily make the api request failed.
notice, we can see the libvirtd process is running but it have no
response to client request.
Steps to reproduce
Public bug reported:
No flavors are shown in the "Launch Instance" dialog in Internet
Explorer 11 (IE11).
Instead, the following alert message is displayed: "Error: Unable to
retrieve the flavors."
The following error appears in the console:
TypeError: Object.keys: argument is not an
** Project changed: heat => horizon
--
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/1691451
Title:
Different results display on CLI and Dashboard for heat event
Public bug reported:
Description
===
Live migration failure during detach volume leaves the instance task state to
migrating forever.
Steps to reproduce
==
- Deploy a VM on a host (the source host) and ensure that vm is in active and
running state.
- Pick one of the
Public bug reported:
Error pop message appear in dashboard while submitting any network changes. In
Newton Release.
Error Message - "Danger: There was an error submitting the form. Please try
again."
Steps to reproduce -
1.Create a Network, go to admin tab and select Edit Network.
2. Update
Reviewed: https://review.openstack.org/430363
Committed:
https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=7d851893951a8c0932d9e5efc179b39ee6e1b8c5
Submitter: Jenkins
Branch:master
commit 7d851893951a8c0932d9e5efc179b39ee6e1b8c5
Author: Rodolfo Alonso Hernandez
Public bug reported:
Hi,
1. AWS
2. 0.7.5-0ubuntu1.21
3. user data is a simple script with "echo test" in it
4.
Under AWS, Ubuntu 14.04, some times cloud init is being stuck after the
"modules:config" part like this:
```
Cloud-init v. 0.7.5 running 'init-local' at Tue, 30 May 2017 06:36:43
Public bug reported:
related bug 1694190
it should skip if the functionality is not supported.
it has require_qos_rule_type check but it's broken after the recent api
semantics change. [1]
the problem is that if a deployment has multiple drivers and one of them
doesn't support the
rule type,
Public bug reported:
Description
===
While configuring nova with neutron and designate to provide DNS to
instances, found that if use_neutron is not explicitly set to True in
nova.conf it gets ignored and dhcp_domain setting is used (novalocal by
default). I think designate does nothing
** Changed in: keystone (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: keystone (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: keystone (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: keystone (Ubuntu Xenial)
Status: New => Triaged
Public bug reported:
Hi, I'm seeing in kolla gates failing with this error:
AttributeError: 'NoneType' object has no attribute 'port_security_enabled'
Instances fail to deploy while retrieving the port in openvswitch_agent.
I think may be related to this recent change
Public bug reported:
I am trying to configure OIDC with keystone.
I have followed the below steps to create the federated resources.
source accr/admin/admin
export OS_IDENTITY_API_VERSION=3
openstack domain create federated_domain
openstack group create federated_users
openstack role add --group
Public bug reported:
I have configured OIDC with keystone.
I have followed the steps mentioned in the official documentation. But when i
try to log into horizon, i get a 401 error:
{"error": {"message": "The request you have made requires authentication.",
"code": 401, "title": "Unauthorized"}}
As pointed out in #2, a kolla-side fix would be to add the
'port_security' to the list of extension_drivers list for ML2 like in
[1]. It's good practice to have this extension enabled.
[1] http://logs.openstack.org/58/466158/4/check/gate-tempest-dsvm-
neutron-full-ubuntu-
** Also affects: nova/newton
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Summary changed:
- VM evacuation is broken with shared torage if VM console.log is not owned by
nova
+ VM evacuation is broken with shared storage
A customer has hit the same issue in MOS 9.2
Could you please backport the fix for Mitaka series?
** Also affects: mos/9.x
Importance: Undecided
Status: New
** Changed in: mos/9.x
Importance: Undecided => High
** Changed in: mos/9.x
Milestone: None => 9.x-updates
** Changed
Public bug reported:
The docs related to keystone identity, currently present in
OpenStack-manuals[1], need to be migrated to the keystone repository. The docs
should be added so that they can be reviewed by Keystone developers and
corresponding inconsistencies could be removed.
[1]:
Public bug reported:
https://review.openstack.org/459753
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/nova" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
Public bug reported:
Environment description:
- Deployment using RDO Trunk repo from master.
- Neutron based on commit c430e9b
In neutron-ovs-agent is started before neutron-server starts, it exits
with return code 0, which is not identified by systemd as a failure so
it's not restarted.
I can also see it's timing out waiting for vif plugging callback in the
logs i.e "Timeout waiting for vif plugging callback for instance
9456073b-a8d6-44ff-b86a-620fbc68a484". Only seen these failures for jobs
in in osic cloud. Is it just a coincidence or something to do with the
infra?
** Also
Reviewed: https://review.openstack.org/464977
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=b0099bbb870e4664185e724850db3fdb7887a903
Submitter: Jenkins
Branch:master
commit b0099bbb870e4664185e724850db3fdb7887a903
Author: Rob Cresswell
Public bug reported:
When QoS policy is updated to be not default for a tenant then neutron-server
have got internal server error because of missing project_id attribute in QoS
policy object.
This error can be observed for example in fullstack tests:
35 matches
Mail list logo