The metering panel was removed from Horizon, and was deprecated for
several cycles before that.
** Changed in: horizon
Status: New => Won't Fix
** Changed in: horizon
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
The metering panel was removed from Horizon, and was deprecated for
several cycles before that.
** Changed in: horizon
Status: New => Won't Fix
** Changed in: horizon
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
The metering panel was removed from Horizon, and was deprecated for
several cycles before that.
** Changed in: horizon
Status: New => Won't Fix
** Changed in: horizon
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Please ensure that your installed libraries match those specified in the
upper-constraints.txt file relevant to the version of Horizon you're
running (see
https://docs.openstack.org/developer/horizon/topics/install.html for how
that works).
** Changed in: horizon
Status: New => Invalid
--
Hi, this isn't a Horizon bug report.
If you need support please try one of these channels
https://www.openstack.org/community/
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to O
I could not reproduce this bug report - the instance didn't appear in
the list of instances for attachment.
** Changed in: horizon
Status: New => Won't Fix
** Changed in: horizon
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engi
Confirmed that volumes do appear "attached" to error state instances
(though I couldn't reproduce exactly the steps in the description).
However, Horizon is just displaying the information returned by the nova
API calls (the server info lists the volume, and os-volume-attachments
also lists the vo
Public bug reported:
When deploying ironic environment, even though nova-compute is running,
but there will be no compute nodes until adding ironic nodes. And the
user may not start nova-compute for some reason during fresh deployment.
So stop return 1 when there is no compute
** Changed in: neutron
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/1520152
Title:
_allocate_vr_id not working as expected because of REPEA
10 matches
Mail list logo
