Reviewed: https://review.openstack.org/638150
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=c19c3d976019027586080cf0958aff41a373f701
Submitter: Zuul
Branch:master
commit c19c3d976019027586080cf0958aff41a373f701
Author: 翟小君
Date: Wed Feb 20 21:21:27 2019 +0800
Public bug reported:
Could not delete lbaas l7 rule from l7 policy properly.
In plugin side, we tried to delete the records of l7 rules in the database by
the following code
"self.db.self.db.delete_l7policy_rule(context, id, l7policy_id)(context, id,
l7policy_id)".
However, in db side, the
Public bug reported:
"lbaas delete l7 rule & policy" could leave dirty data
In lbaas plugin side, the logic for deleting l7 rule and l7 policy is as
follows:
If the l7 rule(or policy) attached to a load balancer, plugin only calls
drivers to delete data (without any database operations);
Public bug reported:
When editing host aggregation, if the available domain is deleted, two
prompts will appear, one success message and one failure message
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
When editing host aggregation, if the available domain is deleted, two
prompts will appear, one success message and one failure message
** Affects: horizon
Importance: Undecided
Assignee: pengyuesheng (pengyuesheng)
Status: New
** Changed in: horizon
Verified:
Instance is set to error status after a new evacuation. Instance is not deleted.
** Changed in: fuel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
I am validating a small OpenStack Rocky installation.
The nova part seems working but I noticed this warning in the nova log files:
Configuring www_authenticate_uri to point to the public identity endpoint is
required; clients may\
not be able to authenticate against an
Public bug reported:
Hi,
We have a rocky OSA setup 18.1.4 version from git. Whenever we create a
router it is getting created and showing a compute node as host with the
command "l3-agent-list-hosting-router" .
But when we log into the compute node and check, there is no namespace for that
Public bug reported:
As fix for bug https://bugs.launchpad.net/neutron/+bug/1818614 we added
to neutron-keepalived-state-change monitor possibility to check initial
status of router (master or slave).
Unfortunately for some reason I see now in journal log of functional job
that this check is
Public bug reported:
The modal js code doesn't know how to process and handle when the
response data is a file attachment. What it does is append the data from
the file to the modal_wrapper.
My reason for hitting this is that I have a form which asks for some
information, and then the handle
Reviewed: https://review.openstack.org/649409
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=e7ae6c65cd24fb3e0776fac80fbab2ab16e9d9ed
Submitter: Zuul
Branch:master
commit e7ae6c65cd24fb3e0776fac80fbab2ab16e9d9ed
Author: Sean Mooney
Date: Tue Apr 2 18:27:24 2019 +0100
Public bug reported:
After merge 365065 (commit 0dc3a77f4), when an Azure VM (previously
provisioned via cloud-init) is rebooted, DataSourceAzure fails to
recreate a NetworkConfig, with multiple exceptions raised and caught.
When the ds is restored from obj.pkl in the instance directory,
Same as other reported issue, neutron-lbaas issues are tracked on
storyboard, can you file the bug there? Thanks!
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
It's hard to find a single place in the nova docs where the impact of
availability zones (including default) on the capabilities of live or cold
migrations is clear
In https://docs.openstack.org/nova/latest/user/aggregates.html
#availability-zones-azs is probably a good
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Importance: Undecided => Medium
** Changed in: nova/stein
Assignee: (unassigned) => melanie witt (melwitt)
--
You received this
neutron-lbaas issues are tracked on storyboard, can you file the bug
there?
https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
With SQLAlchemy===1.3.2 [1], in test case
"test_floatingip_via_router_interface_returns_201", we need to specify which
FROM clause to join from, when multiple FROMS are present [2]. In this case:
models_v2.Port.id == models_v2.IPAllocation.port_id
[1]
Public bug reported:
On the Edit form under container panel, the file is required, but there
is no required mark.
** Affects: horizon
Importance: Undecided
Assignee: pengyuesheng (pengyuesheng)
Status: In Progress
--
You received this bug notification because you are a
Public bug reported:
On the copy form under container panel, if the Destination Container
does not exist and the Destination Object is input, the Destination
object will be wrong, but no error message will be reported; if the
Destination container exists, the Destination object will input an
Public bug reported:
Each Azure VM is provided with an ephemeral disk, and the cloud-init
configuration supplied in the VM image requests the volume be mounted
under /mnt. Each new ephemeral disk is formatted for NTFS rather than
ext4 or another Linux filesystem. The Azure datasource detects this
Public bug reported:
As of this change in Stein:
https://review.openstack.org/#/c/508506/28/nova/notifications/objects/request_spec.py@334
Which is not yet officially released, but is in the 19.0.0.0rc1, the
select_destinations versioned notification payload during a move
operation (resize,
Reviewed: https://review.openstack.org/642877
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=521e59224e8a595af66ec898f1bb739a9dbe7d97
Submitter: Zuul
Branch:master
commit 521e59224e8a595af66ec898f1bb739a9dbe7d97
Author: Matt Riedemann
Date: Tue Mar 12 16:11:04 2019
Reviewed: https://review.openstack.org/649648
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=cec1808050495aa43a2b67058077063bf3b6f4ed
Submitter: Zuul
Branch:master
commit cec1808050495aa43a2b67058077063bf3b6f4ed
Author: Matt Riedemann
Date: Wed Apr 3 11:35:37 2019
Public bug reported:
The Azure datasource needs to communicate with the "Wireserver" control
plane endpoint during provisioning. The IP address of the endpoint is
passed to the VM as option 245 via DHCP. Code to retrieve that address
is remarkably fragile across distros and in the face of changes
Public bug reported:
Discovered on horizon/queens.
When creating a key pair in web interface, underscores are allowed in
the name of the key pair.
When importing a public key, putting an underscore in the field titled
"Key Pair Name" results in an error "Key Pair Name is formatted
incorrectly"
** Changed in: neutron
Status: In Progress => 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/1775250
Title:
Implement DVR-aware announcement of fixed IP's in
i added neutron because the change seems unintended.
** Also affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- create_port_bulk is broken
+ ml2 create_port_bulk produces incompatible port context
** Summary changed:
- ml2 create_port_bulk produces incompatible
27 matches
Mail list logo
