** Changed in: ossn
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1668503
Title:
sha512_crypt is insufficient, use pbk
** Also affects: rack
Importance: Undecided
Status: New
** Changed in: rack
Status: New => In Progress
** Changed in: rack
Assignee: (unassigned) => zhangyangyang (zhangyangyang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
** Also affects: sahara
Importance: Undecided
Status: New
** Changed in: sahara
Status: New => In Progress
** Changed in: sahara
Assignee: (unassigned) => zhangyangyang (zhangyangyang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
** Also affects: tacker
Importance: Undecided
Status: New
** Changed in: tacker
Importance: Undecided => Critical
** Changed in: tacker
Assignee: (unassigned) => yong sheng gong (gongysh)
** Changed in: tacker
Milestone: None => queens-1
--
You received this bug notificat
Public bug reported:
see: http://lists.openstack.org/pipermail/openstack-
dev/2017-September/122115.html
In short, the trusts APIs handle their policy in code rather than from
the policy file.
This is rather confusing seeing as we have policies for trusts in the policy
json file which do nothin
** No longer affects: openstack-requirements
--
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/1717707
Title:
nova-compute failed to communicate with nova-conductor on star
** Description changed:
Related to bug #1696094.
An 'Timed out waiting for nova-conductor. Is it running? Or did this
service start before nova-conductor? Reattempting establishment of
nova-conductor connection...' error occurs in nova-compute.log when:
on compute node
1. no us
7 matches
Mail list logo
