Public bug reported:
I use some of the devel tools to help creating cloud-init scripts etc
for containers. To use just the tools I have to install the whole
cloud-init package and then disable all of the installed "active"
components so cloud-init doesn't mess with the (desktop) workstation.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1840039
Title:
adding additional subnets fail as no network segment
Public bug reported:
1) create a network with qos policy (with min_bw rule)
2) create a port in that network without explicit qos policy (so the port
inherits the policy from the network)
3) boot a server with that port
4) update the qos policy on the network
Expected either:
A)
* qos policy
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/stein
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance:
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Groovy)
The vulnerable branches are no longer officially supported, so I'm going
to set our security advisory task to Won't Fix indicating we won't be
publishing one about this.
** Changed in: ossa
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of
Given nobody has objected to the proposed classifications in my comment
#2 from October, I'll go ahead and mark our security advisory task Won't
Fix for this. We can revisit the decision if anyone disagrees.
** Changed in: ossa
Status: Incomplete => Won't Fix
** Information type changed
I've set our security advisory task for this to Won't Fix as it's a
class C2 report per our taxonomy (A vulnerability, but not in OpenStack
supported code, e.g., in a dependency): https://security.openstack.org
/vmt-process.html#incident-report-taxonomy
** Changed in: ossa
Status:
Since nobody has disputed Sean's assertions in the nearly half a year
since his comment #8 above, I'm going to assume the VMT no longer needs
to track this and is unlikely to issue any security advisory about it,
so am marking our advisory task Won't Fix.
** Changed in: ossa
Status:
As nobody has disagreed with my proposal a year ago to treat this as a
class C1 report, I'm marking our security advisory task for it Won't
Fix.
** Changed in: ossa
Status: Incomplete => Won't Fix
** Information type changed from Public Security to Public
** Tags added: security
--
You
Fixes merged so long ago that no vulnerable branches are still
supported, so I've marked our security advisory task Won't Fix
indicating publication of any advisory at this point is highly unlikely.
** Changed in: ossa
Status: Incomplete => Won't Fix
--
You received this bug notification
Public bug reported:
The cc_rh_subscription update_repos() method queries all the repos that
are available from "subscription-manager repos --list-enabled" and
"--list-disabled", and then it compares the list of repositories the
user wants to to enable or disable against that master list. There
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1840039
Title:
adding additional subnets fail as no network segment is assigned to
the default subnets
It turns out the previous fixes are not sufficient.
** Changed in: horizon
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
14 matches
Mail list logo
