I've the workflow docs[1]. Closing the bug and abandoning the patch.
[1] https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
** Changed in: horizon
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Note for backports: this problem goes back to Pike but we won't be able
to backport the fix since it's going to require RPC API version changes.
** No longer affects: nova/pike
** No longer affects: nova/queens
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
You
The lack of events is not the issue. We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.
The problem is that if udev processes the sda1 event first then, at
least some of
Reviewed: https://review.opendev.org/685593
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6d5fdb4ef4dc3e5f40298e751d966ca54b2ae902
Submitter: Zuul
Branch:master
commit 6d5fdb4ef4dc3e5f40298e751d966ca54b2ae902
Author: LuyaoZhong
Date: Sun Sep 29 08:54:41 2019 +
Public bug reported:
This came up in the mailing list today:
http://lists.openstack.org/pipermail/openstack-
discuss/2019-September/009827.html
It's not immediately obvious that console proxy services should be run
per-cell rather than globally.
One would expect to see something about that
Public bug reported:
Not entirely sure if this is a bug, but at least the underlying logic
seems to mess this up.
I have 7 computes nodes on a ostack cluster. THis issue happens on
cluster1 and 5. for two VMs.
When it happens: At hard reboot. Let's say I have a VM that for some
reason is
** Also affects: nova/train
Importance: Undecided
Status: New
** Changed in: nova/train
Status: New => In Progress
** Changed in: nova/train
Assignee: (unassigned) => Boris Bobrov (bbobrov)
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
https://review.opendev.org/#/c/644565/ added logic to
libvirt/designer.py for enabling iommu for certain devices where virtio
is used. This is required for AMD SEV[0]. However it missed the case
of a SCSI controller where the model is virtio-scsi, e.g.:
As with other
** Also affects: nova/train
Importance: Undecided
Status: New
** Changed in: nova/train
Assignee: (unassigned) => Dan Smith (danms)
** Changed in: nova/train
Status: New => In Progress
** Changed in: nova/train
Importance: Undecided => High
** Changed in: nova
Public bug reported:
With admin role if tenant A selected and wants to update quotas for
tenant B at Projects/Modify Quotas storage quota update fails because
Horizon checks tenant A current usage against tenant B actual storage
quota values.
** Affects: horizon
Importance: Undecided
** Changed in: keystone
Milestone: None => train-rc1
** Changed in: keystone
Status: In Progress => Fix Committed
** Changed in: keystone
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
If You stopped L3 agent and keepalived process together, than keepalived from
other node will decide to be new master and L3 agent on this other node will
configure everything for router. That is how failover works.
But in such case there is nothing what could do cleaning of router's config on
Public bug reported:
The string "Total Active RAM (MB)" is actually saying "(GB)" in
Japanese.
Affected version(s):
Verified in OpenStack Horizon:
- 10.0.2 eol Newton
- 13.0.2 Queens
Steps to reproduce:
0) Login to Horizon
1) Set the language to Japanese
2) Visit http:///dashboard/admin/
3)
13 matches
Mail list logo
