Confirmed this also affects Ironic.
Searched and found this open bug in oslo.messaging, addressing the underlying
issue:
https://bugs.launchpad.net/oslo.messaging/+bug/1586840
** Also affects: ironic
Importance: Undecided
Status: New
--
You received this bug notification because you
e SSL
connection to the Ironic service.
On the other hand, other OpenStack services which Nova connects to (eg,
Glance, Neutron...) have support for this via a service-specific
"cafile" config option.
** Affects: nova
Importance: Undecided
Assignee: Devananda van der
** Also affects: magnum
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/1544195
Title:
User can not provision ironic node via
Public bug reported:
In nova/cells/starte.py _update_our_capacity(), the calculations of free
units of compute are based on optimistic packing of each instance type
on each compute node. This does not account for hypervisors which do not
allow more than one instance per node, such as ironic.
** A
Public bug reported:
When an Ironic node is not in the expected state (eg, it somehow is out
of sync with the nova driver), an incorrect error message is logged in
Nova.
This showed up while testing changes to Ironic's state machine (so the
node being in the wrong state is not Nova's fault; I bro
Public bug reported:
When authenticating with Keystone's REST API, if I happen to provide my
tenant name in the TenantId field, the resulting error tells me that I
am not authorized for that tenant, even though all the information
(user, pass, tenant) are correct. It *should* tell me that I just p
H S (rh-s) => Devananda van der Veen (devananda)
--
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/1310135
Title:
Stopping an instance via the Nova API when using the Nova
Public bug reported:
The SSH driver's "vmware" and "virsh" command sets contain a grep clause
which depends upon localized strings, causing this driver to be unusable
on systems with a non-english locale setting.
For vmware:
136 'list_running': (
137 "vmsvc/power.gets
** Changed in: nova
Status: Triaged => Won't Fix
--
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/1263790
Title:
ipmitool does not support OPERATOR priv level
Stat
I agree with Sean - the real solution here is just to have a callback
mechanism between Ironic and Nova. Waiting for a periodic task to sync
the power state is not ideal, but it is "normal" for Nova today.
** Changed in: ironic
Milestone: juno-rc1 => None
** Changed in: ironic
Status:
Hi Lucas,
I have checked this on a local devstack install with 3 ironic nodes, and
I could not reproduce your results. n-cpu is logging the available
resources for each node individually, and upon updating a node, I see
the change to that node in n-cpu's log at the next periodic interval.
Updates
** Tags removed: nova-driver
** Changed in: ironic
Status: Triaged => Won't Fix
--
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/1313779
Title:
ResourceTracker aud
** Changed in: ironic
Status: Confirmed => Won't Fix
--
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/1362733
Title:
Rebuilding a node in ERROR state should set sta
** Tags added: ironic
** Also affects: nova
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/1310135
Title:
Stopping an instan
update the ironic_host_manager's HostState class,
thus breaking it.
This has broken Ironic's tempest tests, resulting in all our CI tests
failing.
** Affects: nova
Importance: Undecided
Assignee: Devananda van der Veen (devananda)
Status: New
** Tags: ironic
**
heck-tempest-dsvm-virtual-
ironic/c161a89/logs/screen-n-cpu.txt.gz#_2014-09-08_08_41_06_821
==
Proposed fix
==
Fetch flavor['extra_specs'] on demand, when needed by the Ironic driver.
** Affects: nova
Importance: Undecided
Assignee: Devananda van der Ve
** Also affects: ironic
Importance: Undecided
Status: New
** Changed in: ironic
Status: New => In Progress
** Changed in: ironic
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
** Also affects: ironic
Importance: Undecided
Status: New
** Changed in: ironic
Assignee: (unassigned) => Devananda van der Veen (devananda)
** Changed in: ironic
Status: New => In Progress
--
You received this bug notification because you are a member of
Adding Ironic since we inherited the db migration test code from Nova,
and while it turns out that we're not testing db migrations in the gate
due to a misconfiguration, if we were to enable them, we'd face the same
race conditions in our unit tests.
** Tags added: db
** Also affects: ironic
I
Marking as "High" as the work around for this bug, once a user is bit by
it, is to have someone in the datacenter physically power cycle a
machine.
** Changed in: ironic
Importance: Undecided => High
** Also affects: nova
Importance: Undecided
Status: New
** Tags added: baremetal
-
Does not affect Ironic at the moment.
ironic.cmd.dbsync imports ironic.db.migration, which is lazy-loading
ironic.db.sqlalchemy.migration, which is importing alembic.migration
directly.
We'll need to resync oslo.openstack.common.db.migration to get the fix
for this, but presumably we'll do that b
** Changed in: ironic
Status: In Progress => Fix Released
--
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/1251525
Title:
baremetal deploy helper should abort immed
Marking as Invalid for Ironic -- file injection is not implemented in
the PXE driver and thus doesn't need to be disabled.
** Changed in: ironic
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Ope
Public bug reported:
Since devstack patch 43d95084376913 landed, which installed and enabled
libguestfs on Ubuntu, several tempest tests in the ironic and neutron
pipelines have been failing with "Error mounting
/opt/stack/data/nova/instances/{UUID}/disk with libguestfs". This seems
to be happenin
nce: Undecided => Critical
** Changed in: ironic
Assignee: (unassigned) => Devananda van der Veen (devananda)
** Changed in: ironic
Milestone: None => icehouse-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenS
This doesn't affect Ironic as we don't (currently) have a timeout
mechanism for deploys (which is another issue unto itself) and our state
tracking is different than Nova's, so once we add operation-timeouts at
a higher level, it'll be accounted for.
** Changed in: ironic
Status: In Progres
Public bug reported:
If the BMC / IPMI credentials being used for management of hardware were
only granted OPERATOR privileges, there is no way to inform Nova's
baremetal driver or Ironic's ipmitool driver to use this non-default
privilege level. These will issue ipmitool commands with no "-L"
par
the bug as also-affecting and will look into it.
** Also affects: ironic
Importance: Undecided
Status: New
** Changed in: ironic
Assignee: (unassigned) => Devananda van der Veen (devananda)
--
You received this bug notification because you are a member of Yahoo!
Engineer
Public bug reported:
With the baremetal driver, if a baremetal node is deleted, it is not
removed from pool of available resources until the next run of
update_available_resource(). During this window, the scheduler may
continue to attempt to schedule instances on it, leading to unnecessary
failur
I believe this does not affect Ironic, as there is validation of MAC
addresses done within the db/api layer, which was not done by Nova.
I will re-open if it is demonstrated that one can create an invalid or
empty mac address in Ironic, leading to similar failures.
** Changed in: ironic
St
Having accurate timing in distributed systems is actually really
important, and time skew can cause issues (eg, scheduler thinking a
compute node is dead). Even if I might be tempted to blame the deployer
for not properly managing ntpd, the problem is preventable by not
relying on each compute host
for reference: https://bugs.launchpad.net/nova/+bug/1156745
** Changed in: nova
Status: New => Invalid
--
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/1155323
Title
** Changed in: nova
Status: Incomplete => Invalid
--
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/1117783
Title:
baremetal driver.destroy might not be called
Stat
This is correct -- firewall does not work with baremetal, and really
doesn't make sense. The wiki (updated just recently) now mentions that
you must use NoopFirewallDriver with baremetal driver.
** Tags added: baremetal
** Changed in: nova
Status: Incomplete => Won't Fix
--
You received
*** This bug is a duplicate of bug 1088655 ***
https://bugs.launchpad.net/bugs/1088655
This was fixed in https://review.openstack.org/21564
** This bug has been marked a duplicate of bug 1088655
bare metal node partitioning does not handle errors well
--
You received this bug notificatio
35 matches
Mail list logo
