Please fix the typos in the title of this bug (IMPI/IPMI and
14.4/14.04); they make it hard to find.
The root cause of this issue is that a least one type of BMC does not
report back at least one setting (Enable_User) that has been configured
correctly.
This was not a problem in 12.04 because
If the 1950's and 1750's are having problems, what type of response do
you get from this command?:
ipmipower -h bmc ip address -u bmc username -p bmc password --stat
Preferably you'll want to run that from the maas server running 14.04.
On a very basic level, that's what MAAS is using to bring
..and if that doesn't work, then try:
ipmipower -D LAN -h bmc ip address -u bmc username -p bmc password
--stat
Plus, I know these machines are older, but, is the latest BMC firmware
installed on these affected systems?
--
You received this bug notification because you are a member of Ubuntu
Jason I ran the script you post and this is what I got on one of the
nodes.
ubuntu@tf77q:~$ sudo python maas_ipmi_autodetect.py
Traceback (most recent call last):
File maas_ipmi_autodetect.py, line 312, in module
main()
File maas_ipmi_autodetect.py, line 278, in main
I am having problem with Dell servers too. Just like Juan I decided to
go back to 12.04 but ended up with JuJu just not working properly so now
I am back to 14.04 trying to figure out why the Dell servers don't get
their power type set. The only Dell server that did get its power type
set was
hi
you may just stay at 12.04.4, and wait for the juju issues to be resolved.
know that the next release of juju will include some bug fixes, from bugs
that i have found. hoping for the best.
juancc
On Fri, Jun 20, 2014 at 2:43 PM, Hamed Hemmati ha...@hemmati.us wrote:
I am having problem
I tried but I just had too many issues with juju and 12.04. So far the
only issue I have with 14.04 is the fact that some of my poweredge
servers aren't getting their power type set. Other than that juju seems
to work fine on the other ones.
I rather just get the power type issue resolved and
hi
so you are saying that besides power up issues with impi juju works in
14.4...
i ask because i have been trying to build a cloud for over 4 months, with
bug after bug.
on my dell metal.
thanks for the input.
juancc
On Fri, Jun 20, 2014 at 3:36 PM, Hamed Hemmati ha...@hemmati.us wrote:
I
Yeah I was able to bootstrap just fine on the dell server that got its
power type set. I haven't tested charms yet because I can't get any of
my other dell servers to startup since their power types aren't getting
set.
Juju has just evolved too much to be compatible with maas that comes
with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ipmitool (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freeipmi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openipmi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
Juan,
I'm seeing the exact same problem ( I believe) and I noticed you are
having problems getting into your server to see the failure. I
addressed this with a backdoor.
https://maas.ubuntu.com/docs/troubleshooting.html#debugging-ephemeral-
image
The output of my bmc-config --checkout and
hi
thanks but for what I understand, I believe that this is machine specific.
I am getting these problems on dell 1750 and 1950 but not on my dell 2950.
it like they removed them from IMPI, between 12.04.4 and 14.04.
if you know how to notified, please do so.
I have already tried this before I
Juan,
Can you try running this script http://bazaar.launchpad.net/~maas-
maintainers/maas/trunk/view/head:/etc/maas/templates/commissioning-user-
data/snippets/maas_ipmi_autodetect.py on one of the servers you're
having problems with?
You'll need to install freeipmi-utils first, and run it as
thanks for the help, we have returned to 12.04.4, where we are currently
stuck on a juju bug. but we have maas running hopefully they should
have resolved this by the time we return to 14.4.. for the project must go
forward..
thanks
On Wed, Jun 18, 2014 at 5:24 PM, Jason Hobbs
thanks for looking at this, but we have reinstalled 12.04.4, where we
are currently stuck on a juju bug. but maas is working. except for the
IMPI on my dell 1750s. which appear to have the same problem detecting
IMPI..sorry i cannot continue to supply you with information. but we
must have a
** Changed in: maas
Assignee: Andres Rodriguez (andreserl) = Jason Hobbs (jason-hobbs)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IMPI detection and
I have verified that I am running ubuntu 14.4, with maas packages (maas
1.5.1 +bzr2252, these also matched the other maas, packages i.e maas-
cli, maas-dns, etc).
i am also adding, just in-case this maybe machine specific. I am using
10 dell 1950, gen 2, 8gb ram. ( and 2 dell 1750. just as
hi the error i am getting is (no power type defined)
which to me it means that the detection process is not working. I don't even
get the auto detect option.
I watched the screen, I have a 3 min video of the whole process. and there is
something wrong with impi
detection. i will post more
** Changed in: maas (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IMPI detection and automatic setting fail in ubuntu 14.4
here is a small log from the provisioning servers screen. i do have a
video and some photos created from video .
showing numerous errors.
screen dictation:
setting impitool (1.8.13-1)...
*starting IMPI event deamon
could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/impidev/0: no such
Can you please post details of the hardware you're using and someone can
triage the bug.
** Tags added: server-hwe
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug
Can you please paste the full log? What hardware is this? Can you please
provide the output of bmc-config --checkout and ipmi-locate from the
machine itself?
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in
bmi log
juan@region:~$ sudo bmc-config --checkout
[sudo] password for
#
# Section UserX Comments
#
# In the following User sections, users should configure usernames, passwords,
# and access rights for IPMI over LAN communication. Usernames can be set to
any
# string with the exception of
ipmi locate:
juancc@region:~$ sudo ipmi-locate
Probing KCS device using DMIDECODE... done
IPMI Version: 1.5
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device:
BMC I/O base address: 0xCA8
Register spacing: 4
Probing SMIC device using DMIDECODE... FAILED
Probing BT device using
the servers are 13
10 dell power edge 1950 gen 2, 8gb ram 2x200 gb harddrive, in raid ..2
1gb network interfaces. dual xeon 64 bit. (these are the nodes)
1 dell power edge 1800 8gb ram , 1 500gb harddrive, 2 1gb network
interfaces. dual xeon 64 bit (running ubuntu 14.04 maas region/cluster
Done...
On Thursday, May 22, 2014, Andres Rodriguez andres...@ubuntu-pe.org
wrote:
Can you please paste the full log? What hardware is this? Can you please
provide the output of bmc-config --checkout and ipmi-locate from the
machine itself?
Thank you!
--
You received this bug
** Description changed:
- i have no impi detention or automatic setting of IMPI in ubuntu 14.4
+ i have no impi detection or automatic setting of IMPI in ubuntu 14.4
maas. i have the options pull down menu to select IMPI 1.5 or IMPI 2.0
but none of the impi setting work . manual does not work
thanks for your response, i dont get any errors. it is like the software
is there, but not doing anything. i will start to perform some tests so
i can try to fingure out, which package it is. but i can say that when
i was running ubuntu 12.04 server, that maas package commissioned
servers and
** Also affects: ipmitool (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
i have trace the issue to the package above. i don't have the resources,
to go deeper. but this is what i have come up with.
** Also affects: freeipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
The 1.4 release had known problems around IPMI detection which are
mostly fixed in the 1.5 release which is in trusty (14.04). Please
upgrade to trusty, or if you are still on precise you can try out the
MAAS in the cloud tools archive.
** Changed in: maas (Ubuntu)
Status: New = Invalid
Please confirm if 1.5 solves your problem and can you confirm if you are
running on trusty or precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IMPI detection
35 matches
Mail list logo
