Public bug reported:
I have set config option ``hashing_algorithm`` value as sha256 in
glance.
Now, I'm trying to create an image using openstacksdk.
I have set hash value of the image to sha256 parameter of create_image
method but it fails with an error "Image checksum verification failed".
Public bug reported:
I want to create an image without uploading image data using
openstacksdk create_image method.
sdkconnection.image.create_image(name, allow_duplicates=True, **fields)
fields = {"min_disk": min_disk, "min_ram": min_ram,
"disk_format": "qcow2",
** Also affects: masakari
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1804062
Title:
test_hacking fails for python 3.6.7
Public bug reported:
If you are installing stable/ocata branch for the first time using the
latest zero-down time database upgrade method, then it gives following
error when you run "db migrate" command.
$glance-manage db migrate
Output:
2017-10-19 02:31:26.550 CRITICAL glance [-] TypeError:
Public bug reported:
If you have synced the database using "db sync" command and if you
attempt to run "db expand" command, it gives following error.
Actual Result:
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
INFO
As per ostestr documentation [1], -n option is used to run single test.
So it's not a workaround solution, it is working as expected.
Marking it as invalid.
[1]: https://docs.openstack.org/os-testr/latest/user/ostestr.html
** Changed in: glance
Status: New => Invalid
--
You received
nova.openstack.common.lockutils [-]
Acquired semaphore 7695a528-c73b-4b44-b4de-2c26974ac471 lock
/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:229
** Affects: nova
Importance: Undecided
Assignee: Tushar Patil (tpatil)
Status: New
** Changed in: nova
Public bug reported:
Design wise it is allowed to rebuild the instance when the vm_state is in
ERROR, ACTIVE or STOPPED state.
But rebuild instance fails to bring the vm_state to ACTIVE when it is in
STOPPED state.
Steps to reproduce:
1. Create a new instance and wait unit it becomes ACTIVE.
*** This bug is a duplicate of bug 1243127 ***
https://bugs.launchpad.net/bugs/1243127
** This bug is no longer a duplicate of bug 1329319
Restart glance when a image is uploading, then delete the image. The data of
the image is not deleted
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 1243127 ***
https://bugs.launchpad.net/bugs/1243127
** This bug is no longer a duplicate of bug 1329319
Restart glance when a image is uploading, then delete the image. The data of
the image is not deleted
** This bug has been marked a duplicate of bug
Public bug reported:
Tested on master code with commit id :
fd72c308fc6adc1f5d07c5287c1db5bfc12328fc
volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver
Case 1: Instance is booted using volume
Steps to reproduce:
1. Create a bootable volume of size 2 GB using an image.
2. Boot an
Public bug reported:
I have noticed that when a tenant usage information API is invoked for a
particular tenant owning large number of instances (both active
terminated), then I see a sudden increase in nova-api process memory
consumption from 500 MB up to 2.3 GB.
It is due to a SQL retrieving
*** This bug is a duplicate of bug 1220087 ***
https://bugs.launchpad.net/bugs/1220087
Alex: You are correct, this issue is fixed.
If user pass only white spaces to flavor name, then it should give error.
{
flavor: {
name:
ram: 1024,
vcpus: 2,
disk:
13 matches
Mail list logo