Public bug reported:
If a volume belongs to a different project from the current project, the
snapshot tables in the admin volume detail shows no volume snapshots
even if the volume has a volume snapshot.
Procedure to reproduce the bug with DevStack.
- Login as 'demo' project (with user 'demo')
Public bug reported:
If action() in BatchAction displays an error message to describe some detail
reason of a failure, a user will get multiple error messages: the detail error
message and "Unable to ".
This is because BatchAction handle() always tries to display error message. We
need more
Public bug reported:
openSUSE and SLES use wicked for network handling and not dhclient. The
cloud-init-local code assumes dhclient and thus fails:
# systemctl status cloud-init-local.service
● cloud-init-local.service - Initial cloud-init job (pre-networking)
Loaded: loaded
Public bug reported:
AWS EC2 - No network config specified on this AMI by default
Launching new suse-sles-12-sp3-v20171107-hvm-ssd-x86_64 (ami-518b2628)
within a private subnet (ie no public IP allocation) AMI located in
Region eu-west-1, results in the network config script for eth0 being
set
Public bug reported:
When user calls stage command again then it fails with 500 internal server
error.
This is because after stage call image status changes to 'uploading' and for
second call it again tries to set status to 'uploading' and fails with
'InvalidImageStatusTransition: Image status
** Also affects: charm-nova-cloud-controller
Importance: Undecided
Status: New
** Changed in: charm-nova-cloud-controller
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/ocata
Public bug reported:
I install a production cluster with ocata version for nfv project. During the
testing, a compute node(hostname:normal-node2) is reclaimed., and I install a
new node with the same hostname. The new nova-compute just has warning in logs,
but instances can be created in
** Also affects: charm-cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1558683
Title:
Versions endpoint does not support
Public bug reported:
2017-11-10 20:26:38.986 130600 ERROR nova.compute.manager
[req-0364ddaa-8e52-4460-8457-67334117e6f8 c6d634c6516841cc99f06faecc8dd234
0cce6ad60ade451d8fce7c64166c659c - default default] [instance:
44a75d9a-5bfe-4d51-b5b6-e982bad09fda] Failed to attach
@Brian Haley, the reproduce step is both specify subnet and floating-ip-
address:
# neutron floatingip-create --floating-ip-address 172.24.4.101 --subnet
0c280593-3066-4393-bbdc-028b24139314 public
The result is:
Created a new floatingip:
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
14 matches
Mail list logo
