Public bug reported:
in container panel, on create folder form, when the name is empty, no
error shown
** Affects: horizon
Importance: Undecided
Assignee: pengyuesheng (pengyuesheng)
Status: In Progress
** Changed in: horizon
Assignee: (unassigned) => pengyuesheng
Public bug reported:
Description
===
According to https://bugs.launchpad.net/nova/+bug/1756179, Currently we delete
a nova-compute service, will delete compute_node records, resource provider
records and host mapping records in DB. I found if deleting service when
nova-compute service
Reviewed: https://review.openstack.org/581453
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=5bef746c9b50537dde47278a208c4457b42896d0
Submitter: Zuul
Branch:master
commit 5bef746c9b50537dde47278a208c4457b42896d0
Author: Ken'ichi Ohmichi
Date: Tue Jul 10 18:57:48 2018
Reviewed: https://review.openstack.org/538115
Committed:
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=0edb0e68f1a2f673d1befa8833eab0ce7a1521ba
Submitter: Zuul
Branch:master
commit 0edb0e68f1a2f673d1befa8833eab0ce7a1521ba
Author: wujun
Date: Fri Jan 26 10:27:37 2018
Public bug reported:
Description
===
If Neutron disable security-group extension, Nova security group API could not
handle the 404 exception which Neutron returns emitting 500 error. Security API
in Nova is deprecated though I think it's better to wrap 404 exception instead
of 500
This doesn't sound like a cloud-init bug to me. If it's provided with
two sets of network configuration (in this case, on disk via curtin from
MAAS and from you via user-data), it's going to have to choose one. If
it had chosen the user-data one here, then it wouldn't have been able to
provision
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [X] This doc is inaccurate in this way: In the "Finalize the installation"
section, Step 2 displays the
Public bug reported:
In stein, with use of token caching, token deserialization is returning
list object instead of keystone.models.token_model.TokenModel object
causing it to fail in token validation.
2019-02-26 12:59:07.813 12027 WARNING keystone.server.flask.application
Reviewed: https://review.openstack.org/619376
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=c0e6d4498a7e6091212b2618a537eb786595397c
Submitter: Zuul
Branch:master
commit c0e6d4498a7e6091212b2618a537eb786595397c
Author: Lance Bragstad
Date: Wed Nov 21 22:26:25
Public bug reported:
I launch an instance creation with the command: openstack server create
--flavor m1.small --image cirros --security-group secgroup01 --nic net-
id=$netID --key-name mykey instance
I get error
this a nova logs bellow
2019-02-26 15:44:17.610 2863 ERROR
*** This bug is a duplicate of bug 1794996 ***
https://bugs.launchpad.net/bugs/1794996
This might already be fixed for bug 1794996:
https://review.openstack.org/#/q/I1f4b3540dd453650f94333b36d7504ba164192f7
But that was not backported to stable/ocata.
If that fixes your issue we could work
** Changed in: cloud-init
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1657446
Title:
Wrong timestamps in /var/log/cloud-init.log
Status
Public bug reported:
Created a Firewall-rule with the following specifications
protocol: icmp
action: allow
destination-ip-address: 192.168.1.110
and while creating we dont have to specify any ip-version but while i try to
update the same rule's destination ip, it asks for the ip-version
the
*** This bug is a security vulnerability ***
Public security bug reported:
The Octavia has the following issue:
when we try to create a Listener with "protocol UDP" which is not supported,
the LB ans Listener enter into ERROR state and Loadbalancer goes immutable and
the resources related to
Public bug reported:
Created Loadbalancer resources with OCTAVIA, which consists of LB,
listener, pool, members and health monitor,
initially, health monitor was created without expected codes option
now
trying to update the health-monitor's expected codes with some value ,
Wrong error message
Reviewed: https://review.openstack.org/639074
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=c6ae4fb8a2195c5b8d4a88194a70d5aede61f647
Submitter: Zuul
Branch:master
commit c6ae4fb8a2195c5b8d4a88194a70d5aede61f647
Author: Rodolfo Alonso Hernandez
Date: Mon Feb 25
Public bug reported:
Description
===
The public SSH key is not imported when an instance is created with a
key pair (key pair tab) + cloud-init script (configuration tab)
- Reproduced in dashboard (Horizon)
- Reproduced with python (nova.server.create())
Steps to reproduce
Hi Michael,
The question is, why are you sending cloud-init configuration with
network config when MAAS already sends one?
Have you considered the possibility that since you are sending duplicate
information, cloud-init may be failing altogether? That said, 50-curtin-
networking.cfg is the
18 matches
Mail list logo
