Public bug reported:
openstack --debug role set --domain default
707f0cc1809944c89c063420ccc0436f
BadRequest: {} does not have enough properties
Failed validating 'minProperties' in schema:
{'additionalProperties': True,
'minProperties': 1,
'properties': {'name': {'maxLength':
Public bug reported:
How to reproduce:
1. Create a key pair with a name containing underscore using the API (in my
case, using Terraform).
2. Try to create the same key pair in the dashboard.
What happens: The dashboard complains that the key pair name can't
contain underscore.
What should
cloud-init already has support for writing sysconfig formatted files on
systems which only include NetworkManager, specifically NetworkManager
includes a plugin module, 'ifcfg-rh' which reads the sysconfig files for
NetworkManager and cloud-init will enable this plugin as needed.
Please re-open
Looks like expected_task_state is pulled from the values dict here:
https://github.com/openstack/nova/blob/1a226aaa9e8c969ddfdfe198c36f7966b1f692f3/nova/db/sqlalchemy/api.py#L2850
and if not None converted to a list here:
Public bug reported:
I noticed this in some code I was writing when it didn't behave like I
expected:
https://review.opendev.org/#/c/627891/63/nova/conductor/tasks/cross_cell_migrate.py@423
https://review.opendev.org/#/c/688832/2/nova/conductor/tasks/cross_cell_migrate.py@781
That "works"
Reviewed: https://review.opendev.org/686206
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=592b44629905d68b39ec92604b882627f4844908
Submitter: Zuul
Branch:master
commit 592b44629905d68b39ec92604b882627f4844908
Author: Rodolfo Alonso Hernandez
Date: Wed Oct 2
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
--
Public bug reported:
.../glance/glance/cmd/manage.py
def main():
...
CONF.set_default(name='use_stderr', default=True, enforce_type=True)
...
TypeError: set_default() got an unexpected keyword argument
'enforce_type'
https://github.com/openstack/glance/blob/stable/ocata/requirements.txt
Public bug reported:
This came up in the cross-cell resize review:
https://review.opendev.org/#/c/627890/60/nova/conductor/tasks/cross_cell_migrate.py@495
And I was able to recreate with a functional test here:
https://review.opendev.org/#/c/688832/
That test is doing a cross-cell cold
Public bug reported:
System version
==
Keystone: 14.0.1 (Rocky)
The error happens when I try to show a federated user via the user name as the
key instead of using the ID
Reproducing the error:
==
First of all, I created a user in my Identity Provider (Idp)
Public bug reported:
en la bios hay esto escrito
"Only asked for when entering Setup.
If ONLY the user's password is set, then this is a power on password and must
be entered to boot or enter setup.
In setup the user will have Administrator rights"
** Affects: cloud-init
Importance:
Public bug reported:
Problem description
===
In the launch instance workflow while creating a virtual machine, when
I select the Source tab, most of the time the default boot-source is
`Image` and everything works just fine. However, some times, the default
boot-source comes as
Public bug reported:
Hello All,
Newbie so please be gentle.
I am getting these errors on boot.
I think it was fine before I install aws-cli using pip with Python3.
https://pastebin.com/AuS7aaYE
AWS EC2
Ubuntu 18.04.3 LTS
** Affects: cloud-init
Importance: Undecided
Status: New
This is fixed in the version of grub2 in Eoan which will become Ubuntu
19.10.
** Changed in: grub (Ubuntu)
Status: New => Fix Released
** Changed in: grub (Ubuntu Xenial)
Status: New => Triaged
** Changed in: grub (Ubuntu Xenial)
Importance: Undecided => High
--
You received
Public bug reported:
According to the content defined in doc
https://docs.openstack.org/nova/latest/admin/cpu-topologies.html
#customizing-instance-cpu-pinning-policies, the instance CPU allocation
policy could be explicitly set through instance flavor property
'hw:cpu_policy', or its
Public bug reported:
Since upgrading from Rocky to Stein we are experiencing problems live
migrating vm's with trunk ports and creating new trunk ports. The live
migrations of the vm itself eventually completes but the trunk ports
remain in the status "BUILD" or "DOWN". The corresponding subports
16 matches
Mail list logo
