Bug #1309720 “latest bits not installing hpvsa (proprietary driv...” : Bugs : hp-iss

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-18:

#1

/var/log/syslog Edit (153.1 KiB, text/plain)

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-18:

#2

/var/log/partman Edit (3.0 MiB, text/plain)

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-18:

#3

Just hit a different symptom. Instead of going crazy at the disk partitioning screen it stopped and reported an input/output error trying to read /dev/sda. Now the system is locked up, can't switch screens to see there is anything useful on F4. And there are no entries under /var/log/maas/rsyslog/ on the maas server.

Jason Hobbs (jason-hobbs) on 2014-04-18

Changed in maas:
assignee:	nobody → Jason Hobbs (jason-hobbs)

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2014-04-18:

#4

Mike, it doesn't look like it's trying to install the hpvsa driver at all, which is strange, because it is blacklisting ahci.

Can you post your /etc/maas/preseeds/generic ?

If you can get it to boot and fail during d-i, but not hang, can you please post the output of "find /tmp".

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-18:

#5

Download full text (4.4 KiB)

ubuntu@trusty-maas:~$ cat /etc/maas/preseeds/generic
{{inherit "preseed_master"}}

{{def proxy}}
d-i mirror/country string manual
{{if node.architecture in {'i386/generic', 'amd64/generic'} }}
d-i mirror/http/hostname string {{main_archive_hostname}}
d-i mirror/http/directory string {{main_archive_directory}}
{{else}}
d-i mirror/http/hostname string {{ports_archive_hostname}}
d-i mirror/http/directory string {{ports_archive_directory}}
{{endif}}
{{if http_proxy }}
d-i mirror/http/proxy string {{http_proxy}}
{{else}}
d-i mirror/http/proxy string http://{{server_host}}:8000/
{{endif}}
{{enddef}}

{{def client_packages}}
{{if third_party_drivers and driver}}
d-i pkgsel/include string cloud-init openssh-server python-software-properties vim avahi-daemon server^ {{driver_package}}
{{else}}
d-i pkgsel/include string cloud-init openssh-server python-software-properties vim avahi-daemon server^
{{endif}}
{{enddef}}

{{def driver_preseed_data}}
{{if third_party_drivers and driver}}
# Third party driver support.
d-i preseed/early_command string \
    echo -en '{{''.join(['\\x%x' % x for x in map(ord, str(install_udeb))])}}' > /tmp/install_udeb.sh && \
    chmod +x /tmp/install_udeb.sh && \
    /tmp/install_udeb.sh

d-i apt-setup/local0/repository string deb {{driver['repository']}} {{node.get_distro_series()}} main
d-i apt-setup/local0/comment string {{driver['comment']}}
d-i apt-setup/local0/key string file:///tmp/maas-{{driver['package']}}/repo_key.gpg
{{endif}}
{{enddef}}

{{def post_scripts}}
# Executes late command and disables PXE.
d-i preseed/late_command string true && \
    in-target sh -c 'f=$1; shift; echo $0 > $f && chmod 0440 $f $*' 'ubuntu ALL=(ALL) NOPASSWD: ALL' /etc/sudoers.d/maas && \
    in-target wget --no-proxy "{{node_disable_pxe_url|escape.shell}}" --post-data "{{node_disable_pxe_data|escape.shell}}" -O /dev/null && \
{{if third_party_drivers and driver}}
    in-target sh -c "echo blacklist {{driver['blacklist']}} >> /etc/modprobe.d/maas-{{driver['module']}}.conf" && \
    in-target sh -c "for file in /lib/modules/*; do depmod ${file##*/}; done"; \
    in-target update-initramfs -u; \
{{endif}}
    true
{{enddef}}

{{def install_udeb}}
{{if third_party_drivers and driver}}
#!/usr/bin/env sh

set -eu

REPO={{driver['repository']}}
KERNEL_VERSION=`uname -r`
TMPDIR=/tmp/maas-{{driver['package']}}
mkdir $TMPDIR

{{if http_proxy}}
export http_proxy={{http_proxy}} https_proxy={{http_proxy}}
{{endif}}

echo -en '{{''.join(['\\x%x' % x for x in map(ord, driver['key_binary'])])}}' > $TMPDIR/repo_key.gpg

# Retrieve the Release file and verify it against the repository's key.
wget -O $TMPDIR/Release $REPO/dists/{{node.get_distro_series()}}/Release
wget -O $TMPDIR/Release.gpg $REPO/dists/{{node.get_distro_series()}}/Release.gpg
gpgv --keyring $TMPDIR/repo_key.gpg $TMPDIR/Release.gpg $TMPDIR/Release

# Retrieve the Packages file and verify it against the Releases file.
wget -O $TMPDIR/Packages $REPO/dists/{{node.get_distro_series()}}/main/debian-installer/binary-amd64/Packages
expected_sha256=`sed -n -e '/^SHA256:$/,$p' $TMPDIR/Relea...

ubuntu@trusty-maas:~$ cat /etc/maas/preseeds/generic 
{{inherit "preseed_master"}}

{{def proxy}}
d-i     mirror/country string manual
{{if node.architecture in {'i386/generic', 'amd64/generic'} }}
d-i     mirror/http/hostname string {{main_archive_hostname}}
d-i     mirror/http/directory string {{main_archive_directory}}
{{else}}
d-i     mirror/http/hostname string {{ports_archive_hostname}}
d-i     mirror/http/directory string {{ports_archive_directory}}
{{endif}}
{{if http_proxy }}
d-i     mirror/http/proxy string {{http_proxy}}
{{else}}
d-i     mirror/http/proxy string http://{{server_host}}:8000/
{{endif}}
{{enddef}}

{{def client_packages}}
{{if third_party_drivers and driver}}
d-i     pkgsel/include string cloud-init openssh-server python-software-properties vim avahi-daemon server^ {{driver_package}}
{{else}}
d-i     pkgsel/include string cloud-init openssh-server python-software-properties vim avahi-daemon server^
{{endif}}
{{enddef}}

{{def driver_preseed_data}}
{{if third_party_drivers and driver}}
# Third party driver support.
d-i preseed/early_command string \
    echo -en '{{''.join(['\\x%x' % x for x in map(ord, str(install_udeb))])}}' > /tmp/install_udeb.sh && \
    chmod +x /tmp/install_udeb.sh && \
    /tmp/install_udeb.sh

d-i apt-setup/local0/repository string deb {{driver['repository']}} {{node.get_distro_series()}} main
d-i apt-setup/local0/comment string {{driver['comment']}}
d-i apt-setup/local0/key string file:///tmp/maas-{{driver['package']}}/repo_key.gpg
{{endif}}
{{enddef}}

{{def post_scripts}}
# Executes late command and disables PXE.
d-i     preseed/late_command string true && \
    in-target sh -c 'f=$1; shift; echo $0 > $f && chmod 0440 $f $*' 'ubuntu ALL=(ALL) NOPASSWD: ALL' /etc/sudoers.d/maas && \
    in-target wget --no-proxy "{{node_disable_pxe_url|escape.shell}}" --post-data "{{node_disable_pxe_data|escape.shell}}" -O /dev/null && \
{{if third_party_drivers and driver}}
    in-target sh -c "echo blacklist {{driver['blacklist']}} >> /etc/modprobe.d/maas-{{driver['module']}}.conf" && \
    in-target sh -c "for file in /lib/modules/*; do depmod ${file##*/}; done"; \
    in-target update-initramfs -u; \
{{endif}}
    true
{{enddef}}

{{def install_udeb}}
{{if third_party_drivers and driver}}
#!/usr/bin/env sh

set -eu

REPO={{driver['repository']}}
KERNEL_VERSION=`uname -r`
TMPDIR=/tmp/maas-{{driver['package']}}
mkdir $TMPDIR

{{if http_proxy}}
export http_proxy={{http_proxy}} https_proxy={{http_proxy}}
{{endif}}

echo -en '{{''.join(['\\x%x' % x for x in map(ord, driver['key_binary'])])}}' > $TMPDIR/repo_key.gpg

# Retrieve the Release file and verify it against the repository's key.
wget -O $TMPDIR/Release $REPO/dists/{{node.get_distro_series()}}/Release
wget -O $TMPDIR/Release.gpg $REPO/dists/{{node.get_distro_series()}}/Release.gpg
gpgv --keyring $TMPDIR/repo_key.gpg $TMPDIR/Release.gpg $TMPDIR/Release

# Retrieve the Packages file and verify it against the Releases file.
wget -O $TMPDIR/Packages $REPO/dists/{{node.get_distro_series()}}/main/debian-installer/binary-amd64/Packages
expected_sha256=`sed -n -e '/^SHA256:$/,$p' $TMPDIR/Release | grep 'main/debian-installer/binary-amd64/Packages$' | cut -f 2 -d ' '`
actual_sha256=`sha256sum $TMPDIR/Packages | cut -f 1 -d ' '`
if [ "$expected_sha256" != "$actual_sha256" ]
then
    echo "Packages sha256 value mismatch."
    echo "expected: $expected_sha256, actual: $actual_sha256"
    exit 1
fi

# Retrieve the udeb and verify it against the Packages file. This method
# of locating the sha256 sum for the udeb within the Packages file
# relies on the SHA256 line coming after the Filename line in the udeb's
# record in the Packages file.
filename=`grep ^Filename.*$KERNEL_VERSION $TMPDIR/Packages  | cut -f 2 -d ' ' | sort -ru | head -n 1`
wget -O $TMPDIR/driver.udeb $REPO/$filename
basename=${filename##*/}
sed_expression="/$basename"'$/,$p'
expected_udeb_sha256=`sed -n -e $sed_expression $TMPDIR/Packages | grep ^SHA256: | cut -f 2 -d ' ' | head -n 1`
actual_udeb_sha256=`sha256sum $TMPDIR/driver.udeb | cut -f 1 -d ' '`
if [ "$expected_udeb_sha256" != "$actual_udeb_sha256" ]
then
    echo "udeb sha256 value mismatch."
    echo "expected: $expected_udeb_sha256, actual: $actual_udeb_sha256"
    exit 1
fi

# Install the udeb and load the kernel module.
udpkg -i $TMPDIR/driver.udeb
depmod
modprobe {{driver['module']}}
{{endif}}
{{enddef}}

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-18: Re: [Bug 1309720] Re: latest bits not installing hpvsa (proprietary driver)

#6

I posted it to the bug. I'll see if I can get the output for you.

On Fri, Apr 18, 2014 at 3:18 PM, Jason Hobbs <email address hidden>wrote:

> Mike, it doesn't look like it's trying to install the hpvsa driver at
> all, which is strange, because it is blacklisting ahci.
>
> Can you post your /etc/maas/preseeds/generic ?
>
> If you can get it to boot and fail during d-i, but not hang, can you
> please post the output of "find /tmp".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
> latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:
> New
>
> Bug description:
> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> maas 1.5+bzr2252- all MAAS server all-in-one
> metapackag
>
> Using maas to deploy an HP hpvsa based system fails. When using the
> default installer enlisting and commisioning complete without any errors.
> During OS install when disk partitioning screen comes up it begins
> refreshing the screen every half-second or so and the progress shown is
> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> /var/log/syslog and /var/log/partman. Those files are attached. There is
> also no messages file in /var/log/maas/rsyslog/etc.
>
> When using the fastpath installer the OS is installed but it used the
> ahci driver and fake raid.
>
> Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> to get the latest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2014-04-21:

#7

I tested the debian installer path with a clean install of trusty maas and the driver was downloaded/installed and loaded fine. There should be a fair amount of spam about it in /var/log/syslog, but I don't see it in your log. I wonder if your environment was modified somehow, or if there is another maas server running on it?

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-21:

#8

I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
debian installer path worked afterward. It wasn't until I updated to the GA
bits that things stopped working. What can I check on my end to make sure
my set up is OK?

On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <email address hidden>wrote:

> I tested the debian installer path with a clean install of trusty maas
> and the driver was downloaded/installed and loaded fine. There should
> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> in your log. I wonder if your environment was modified somehow, or if
> there is another maas server running on it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
> latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:
> New
>
> Bug description:
> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> maas 1.5+bzr2252- all MAAS server all-in-one
> metapackag
>
> Using maas to deploy an HP hpvsa based system fails. When using the
> default installer enlisting and commisioning complete without any errors.
> During OS install when disk partitioning screen comes up it begins
> refreshing the screen every half-second or so and the progress shown is
> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> /var/log/syslog and /var/log/partman. Those files are attached. There is
> also no messages file in /var/log/maas/rsyslog/etc.
>
> When using the fastpath installer the OS is installed but it used the
> ahci driver and fake raid.
>
> Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> to get the latest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>

I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
debian installer path worked afterward. It wasn't until I updated to the GA
bits that things stopped working. What can I check on my end to make sure
my set up is OK?

On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <jason.hobbs@canonical.com>wrote:

> I tested the debian installer path with a clean install of trusty maas
> and the driver was downloaded/installed and loaded fine.  There should
> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> in your log. I wonder if your environment was modified somehow, or if
> there is another maas server running on it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
>   latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:
>   New
>
> Bug description:
>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>   maas           1.5+bzr2252- all          MAAS server all-in-one
> metapackag
>
>   Using maas to deploy an HP hpvsa based system fails. When using the
> default installer enlisting and commisioning complete without any errors.
> During OS install when disk partitioning screen comes up it begins
> refreshing the screen every half-second or so and the progress shown is
> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> /var/log/syslog and /var/log/partman. Those files are attached. There is
> also no messages file in /var/log/maas/rsyslog/etc.
>
>   When using the fastpath installer the OS is installed but it used the
>   ahci driver and fake raid.
>
>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>   to get the latest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2014-04-21:

#9

Is your maas server the same install that you used last tuesday? Did you
upgrade from that? It would be best to start from scratch - the upgrade
path from the experimental builds we were using last week to the release
build hasn't been tested.

If you're using a clean install, try can you provide the output of
'find /tmp' from the failed system after a d-i failure?

Thanks,
Jason

On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> debian installer path worked afterward. It wasn't until I updated to the GA
> bits that things stopped working. What can I check on my end to make sure
> my set up is OK?
>
>
> On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <email address hidden>wrote:
>
>> I tested the debian installer path with a clean install of trusty maas
>> and the driver was downloaded/installed and loaded fine. There should
>> be a fair amount of spam about it in /var/log/syslog, but I don't see it
>> in your log. I wonder if your environment was modified somehow, or if
>> there is another maas server running on it?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1309720
>>
>> Title:
>> latest bits not installing hpvsa (proprietary driver)
>>
>> Status in MAAS:
>> New
>>
>> Bug description:
>> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
>> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>> maas 1.5+bzr2252- all MAAS server all-in-one
>> metapackag
>>
>> Using maas to deploy an HP hpvsa based system fails. When using the
>> default installer enlisting and commisioning complete without any errors.
>> During OS install when disk partitioning screen comes up it begins
>> refreshing the screen every half-second or so and the progress shown is
>> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
>> /var/log/syslog and /var/log/partman. Those files are attached. There is
>> also no messages file in /var/log/maas/rsyslog/etc.
>>
>> When using the fastpath installer the OS is installed but it used the
>> ahci driver and fake raid.
>>
>> Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>> to get the latest.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>>
>

Is your maas server the same install that you used last tuesday? Did you
upgrade from that? It would be best to start from scratch - the upgrade
path from the experimental builds we were using last week to the release
build hasn't been tested.

If you're using a clean install, try  can you provide the output of
'find /tmp' from the failed system after a d-i failure?

Thanks,
Jason

On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> debian installer path worked afterward. It wasn't until I updated to the GA
> bits that things stopped working. What can I check on my end to make sure
> my set up is OK?
> 
> 
> On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <jason.hobbs@canonical.com>wrote:
> 
>> I tested the debian installer path with a clean install of trusty maas
>> and the driver was downloaded/installed and loaded fine.  There should
>> be a fair amount of spam about it in /var/log/syslog, but I don't see it
>> in your log. I wonder if your environment was modified somehow, or if
>> there is another maas server running on it?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1309720
>>
>> Title:
>>   latest bits not installing hpvsa (proprietary driver)
>>
>> Status in MAAS:
>>   New
>>
>> Bug description:
>>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
>> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>>   maas           1.5+bzr2252- all          MAAS server all-in-one
>> metapackag
>>
>>   Using maas to deploy an HP hpvsa based system fails. When using the
>> default installer enlisting and commisioning complete without any errors.
>> During OS install when disk partitioning screen comes up it begins
>> refreshing the screen every half-second or so and the progress shown is
>> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
>> /var/log/syslog and /var/log/partman. Those files are attached. There is
>> also no messages file in /var/log/maas/rsyslog/etc.
>>
>>   When using the fastpath installer the OS is installed but it used the
>>   ahci driver and fake raid.
>>
>>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>>   to get the latest.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>>
>

Revision history for this message

Narinder Gupta (narindergupta) wrote on 2014-04-21:

#10

Download full text (4.4 KiB)

Just now check the same with Michael it seems there is kernel panic with
hpvsa. I have asked Michael to get a new hpvsa build from HP and update the
PPA might fix the issue or check with HP to have fix in hpvsa driver.

Thanks and Regards,
Narinder Gupta (PMP) <email address hidden>
Canonical, Ltd. narindergupta [irc.freenode.net]
+1.281.736.5150 narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <email address hidden>wrote:

> Is your maas server the same install that you used last tuesday? Did you
> upgrade from that? It would be best to start from scratch - the upgrade
> path from the experimental builds we were using last week to the release
> build hasn't been tested.
>
> If you're using a clean install, try can you provide the output of
> 'find /tmp' from the failed system after a d-i failure?
>
> Thanks,
> Jason
>
>
> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> > debian installer path worked afterward. It wasn't until I updated to the
> GA
> > bits that things stopped working. What can I check on my end to make sure
> > my set up is OK?
> >
> >
> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <<email address hidden>
> >wrote:
> >
> >> I tested the debian installer path with a clean install of trusty maas
> >> and the driver was downloaded/installed and loaded fine. There should
> >> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> >> in your log. I wonder if your environment was modified somehow, or if
> >> there is another maas server running on it?
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1309720
> >>
> >> Title:
> >> latest bits not installing hpvsa (proprietary driver)
> >>
> >> Status in MAAS:
> >> New
> >>
> >> Bug description:
> >> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >> maas 1.5+bzr2252- all MAAS server all-in-one
> >> metapackag
> >>
> >> Using maas to deploy an HP hpvsa based system fails. When using the
> >> default installer enlisting and commisioning complete without any
> errors.
> >> During OS install when disk partitioning screen comes up it begins
> >> refreshing the screen every half-second or so and the progress shown is
> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> >> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> >> /var/log/syslog and /var/log/partman. Those files are attached. There is
> >> also no messages file in /var/log/maas/rsyslog/etc.
> >>
> >> When using the fastpath installer the OS is installed but it used the
> >> ahci driver and fake raid.
> >>
> >> Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> >> to get the latest.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
> >>
>...

Just now check the same with Michael it seems there is kernel panic with
hpvsa. I have asked Michael to get a new hpvsa build from HP and update the
PPA might fix the issue or check with HP to have fix in hpvsa driver.

Thanks and Regards,
Narinder Gupta (PMP)                   narinder.gupta@canonical.com
Canonical, Ltd.                    narindergupta [irc.freenode.net]
+1.281.736.5150                            narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com

On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <jason.hobbs@canonical.com>wrote:

> Is your maas server the same install that you used last tuesday? Did you
> upgrade from that? It would be best to start from scratch - the upgrade
> path from the experimental builds we were using last week to the release
> build hasn't been tested.
>
> If you're using a clean install, try  can you provide the output of
> 'find /tmp' from the failed system after a d-i failure?
>
> Thanks,
> Jason
>
>
> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> > debian installer path worked afterward. It wasn't until I updated to the
> GA
> > bits that things stopped working. What can I check on my end to make sure
> > my set up is OK?
> >
> >
> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <jason.hobbs@canonical.com
> >wrote:
> >
> >> I tested the debian installer path with a clean install of trusty maas
> >> and the driver was downloaded/installed and loaded fine.  There should
> >> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> >> in your log. I wonder if your environment was modified somehow, or if
> >> there is another maas server running on it?
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1309720
> >>
> >> Title:
> >>   latest bits not installing hpvsa (proprietary driver)
> >>
> >> Status in MAAS:
> >>   New
> >>
> >> Bug description:
> >>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >>   maas           1.5+bzr2252- all          MAAS server all-in-one
> >> metapackag
> >>
> >>   Using maas to deploy an HP hpvsa based system fails. When using the
> >> default installer enlisting and commisioning complete without any
> errors.
> >> During OS install when disk partitioning screen comes up it begins
> >> refreshing the screen every half-second or so and the progress shown is
> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> >>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> >> /var/log/syslog and /var/log/partman. Those files are attached. There is
> >> also no messages file in /var/log/maas/rsyslog/etc.
> >>
> >>   When using the fastpath installer the OS is installed but it used the
> >>   ahci driver and fake raid.
> >>
> >>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> >>   to get the latest.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
> >>
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
>   latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:
>   New
>
> Bug description:
>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>   maas           1.5+bzr2252- all          MAAS server all-in-one
> metapackag
>
>   Using maas to deploy an HP hpvsa based system fails. When using the
> default installer enlisting and commisioning complete without any errors.
> During OS install when disk partitioning screen comes up it begins
> refreshing the screen every half-second or so and the progress shown is
> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> /var/log/syslog and /var/log/partman. Those files are attached. There is
> also no messages file in /var/log/maas/rsyslog/etc.
>
>   When using the fastpath installer the OS is installed but it used the
>   ahci driver and fake raid.
>
>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>   to get the latest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-21:

#11

Download full text (4.2 KiB)

It's still locking up so I can't get the contents of /tmp for you. n2
things I've noticed:

1) the driver is getting picked up and injected by maas.
2) the kernel is panicking trying to free a spinlock

This system has a B320i. So I'm going back to a 120i based system for a
sanity check.

On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <email address hidden>wrote:

> Is your maas server the same install that you used last tuesday? Did you
> upgrade from that? It would be best to start from scratch - the upgrade
> path from the experimental builds we were using last week to the release
> build hasn't been tested.
>
> If you're using a clean install, try can you provide the output of
> 'find /tmp' from the failed system after a d-i failure?
>
> Thanks,
> Jason
>
>
> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> > debian installer path worked afterward. It wasn't until I updated to the
> GA
> > bits that things stopped working. What can I check on my end to make sure
> > my set up is OK?
> >
> >
> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <<email address hidden>
> >wrote:
> >
> >> I tested the debian installer path with a clean install of trusty maas
> >> and the driver was downloaded/installed and loaded fine. There should
> >> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> >> in your log. I wonder if your environment was modified somehow, or if
> >> there is another maas server running on it?
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1309720
> >>
> >> Title:
> >> latest bits not installing hpvsa (proprietary driver)
> >>
> >> Status in MAAS:
> >> New
> >>
> >> Bug description:
> >> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >> maas 1.5+bzr2252- all MAAS server all-in-one
> >> metapackag
> >>
> >> Using maas to deploy an HP hpvsa based system fails. When using the
> >> default installer enlisting and commisioning complete without any
> errors.
> >> During OS install when disk partitioning screen comes up it begins
> >> refreshing the screen every half-second or so and the progress shown is
> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> >> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> >> /var/log/syslog and /var/log/partman. Those files are attached. There is
> >> also no messages file in /var/log/maas/rsyslog/etc.
> >>
> >> When using the fastpath installer the OS is installed but it used the
> >> ahci driver and fake raid.
> >>
> >> Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> >> to get the latest.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
> >>
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
> latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:...

It's still locking up so I can't get the contents of /tmp for you. n2
things I've noticed:

1) the driver is getting picked up and injected by maas.
2) the kernel is panicking trying to free a spinlock

This system has a B320i. So I'm going back to a 120i based system for a
sanity check.

On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <jason.hobbs@canonical.com>wrote:

> Is your maas server the same install that you used last tuesday? Did you
> upgrade from that? It would be best to start from scratch - the upgrade
> path from the experimental builds we were using last week to the release
> build hasn't been tested.
>
> If you're using a clean install, try  can you provide the output of
> 'find /tmp' from the failed system after a d-i failure?
>
> Thanks,
> Jason
>
>
> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that the
> > debian installer path worked afterward. It wasn't until I updated to the
> GA
> > bits that things stopped working. What can I check on my end to make sure
> > my set up is OK?
> >
> >
> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <jason.hobbs@canonical.com
> >wrote:
> >
> >> I tested the debian installer path with a clean install of trusty maas
> >> and the driver was downloaded/installed and loaded fine.  There should
> >> be a fair amount of spam about it in /var/log/syslog, but I don't see it
> >> in your log. I wonder if your environment was modified somehow, or if
> >> there is another maas server running on it?
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1309720
> >>
> >> Title:
> >>   latest bits not installing hpvsa (proprietary driver)
> >>
> >> Status in MAAS:
> >>   New
> >>
> >> Bug description:
> >>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> >>   maas           1.5+bzr2252- all          MAAS server all-in-one
> >> metapackag
> >>
> >>   Using maas to deploy an HP hpvsa based system fails. When using the
> >> default installer enlisting and commisioning complete without any
> errors.
> >> During OS install when disk partitioning screen comes up it begins
> >> refreshing the screen every half-second or so and the progress shown is
> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
> >>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> >> /var/log/syslog and /var/log/partman. Those files are attached. There is
> >> also no messages file in /var/log/maas/rsyslog/etc.
> >>
> >>   When using the fastpath installer the OS is installed but it used the
> >>   ahci driver and fake raid.
> >>
> >>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
> >>   to get the latest.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
> >>
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1309720
>
> Title:
>   latest bits not installing hpvsa (proprietary driver)
>
> Status in MAAS:
>   New
>
> Bug description:
>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>   maas           1.5+bzr2252- all          MAAS server all-in-one
> metapackag
>
>   Using maas to deploy an HP hpvsa based system fails. When using the
> default installer enlisting and commisioning complete without any errors.
> During OS install when disk partitioning screen comes up it begins
> refreshing the screen every half-second or so and the progress shown is
> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
> /var/log/syslog and /var/log/partman. Those files are attached. There is
> also no messages file in /var/log/maas/rsyslog/etc.
>
>   When using the fastpath installer the OS is installed but it used the
>   ahci driver and fake raid.
>
>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>   to get the latest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>

Revision history for this message

Michael F. Miller (mikem1355) wrote on 2014-04-21:

#12

Download full text (4.6 KiB)

I did a sanity check by going back to a B120i based system and it worked
without any problems. I talked to the driver developer and sent him a stack
trace.

On Mon, Apr 21, 2014 at 2:35 PM, Michael Miller <
<email address hidden>> wrote:

> It's still locking up so I can't get the contents of /tmp for you. n2
> things I've noticed:
>
> 1) the driver is getting picked up and injected by maas.
> 2) the kernel is panicking trying to free a spinlock
>
> This system has a B320i. So I'm going back to a 120i based system for a
> sanity check.
>
>
> On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <email address hidden>wrote:
>
>> Is your maas server the same install that you used last tuesday? Did you
>> upgrade from that? It would be best to start from scratch - the upgrade
>> path from the experimental builds we were using last week to the release
>> build hasn't been tested.
>>
>> If you're using a clean install, try can you provide the output of
>> 'find /tmp' from the failed system after a d-i failure?
>>
>> Thanks,
>> Jason
>>
>>
>> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
>> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that
>> the
>> > debian installer path worked afterward. It wasn't until I updated to
>> the GA
>> > bits that things stopped working. What can I check on my end to make
>> sure
>> > my set up is OK?
>> >
>> >
>> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <
>> <email address hidden>>wrote:
>> >
>> >> I tested the debian installer path with a clean install of trusty maas
>> >> and the driver was downloaded/installed and loaded fine. There should
>> >> be a fair amount of spam about it in /var/log/syslog, but I don't see
>> it
>> >> in your log. I wonder if your environment was modified somehow, or if
>> >> there is another maas server running on it?
>> >>
>> >> --
>> >> You received this bug notification because you are subscribed to the
>> bug
>> >> report.
>> >> https://bugs.launchpad.net/bugs/1309720
>> >>
>> >> Title:
>> >> latest bits not installing hpvsa (proprietary driver)
>> >>
>> >> Status in MAAS:
>> >> New
>> >>
>> >> Bug description:
>> >> Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10
>> 19:11:08
>> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>> >> maas 1.5+bzr2252- all MAAS server all-in-one
>> >> metapackag
>> >>
>> >> Using maas to deploy an HP hpvsa based system fails. When using the
>> >> default installer enlisting and commisioning complete without any
>> errors.
>> >> During OS install when disk partitioning screen comes up it begins
>> >> refreshing the screen every half-second or so and the progress shown is
>> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>> >> ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
>> >> /var/log/syslog and /var/log/partman. Those files are attached. There
>> is
>> >> also no messages file in /var/log/maas/rsyslog/etc.
>> >>
>> >> When using the fastpath installer the OS is installed but it used the
>> >> ahci driver and fake raid.
>> >>
>> >> Fastpath installed rc bits rather than ga bits. Had to do
>> dist-upgrade
>> >> to get the latest.
>> >>...

I did a sanity check by going back to a B120i based system and it worked
without any problems. I talked to the driver developer and sent him a stack
trace.

On Mon, Apr 21, 2014 at 2:35 PM, Michael Miller <
michael.miller@canonical.com> wrote:

> It's still locking up so I can't get the contents of /tmp for you. n2
> things I've noticed:
>
> 1) the driver is getting picked up and injected by maas.
> 2) the kernel is panicking trying to free a spinlock
>
> This system has a B320i. So I'm going back to a 120i based system for a
> sanity check.
>
>
> On Mon, Apr 21, 2014 at 1:09 PM, Jason Hobbs <jason.hobbs@canonical.com>wrote:
>
>> Is your maas server the same install that you used last tuesday? Did you
>> upgrade from that? It would be best to start from scratch - the upgrade
>> path from the experimental builds we were using last week to the release
>> build hasn't been tested.
>>
>> If you're using a clean install, try  can you provide the output of
>> 'find /tmp' from the failed system after a d-i failure?
>>
>> Thanks,
>> Jason
>>
>>
>> On 04/21/2014 12:58 PM, Michael F. Miller wrote:
>> > I had to reinstall OS and maas last Tuesday. But I'm pretty sure that
>> the
>> > debian installer path worked afterward. It wasn't until I updated to
>> the GA
>> > bits that things stopped working. What can I check on my end to make
>> sure
>> > my set up is OK?
>> >
>> >
>> > On Mon, Apr 21, 2014 at 11:29 AM, Jason Hobbs <
>> jason.hobbs@canonical.com>wrote:
>> >
>> >> I tested the debian installer path with a clean install of trusty maas
>> >> and the driver was downloaded/installed and loaded fine.  There should
>> >> be a fair amount of spam about it in /var/log/syslog, but I don't see
>> it
>> >> in your log. I wonder if your environment was modified somehow, or if
>> >> there is another maas server running on it?
>> >>
>> >> --
>> >> You received this bug notification because you are subscribed to the
>> bug
>> >> report.
>> >> https://bugs.launchpad.net/bugs/1309720
>> >>
>> >> Title:
>> >>   latest bits not installing hpvsa (proprietary driver)
>> >>
>> >> Status in MAAS:
>> >>   New
>> >>
>> >> Bug description:
>> >>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10
>> 19:11:08
>> >> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>> >>   maas           1.5+bzr2252- all          MAAS server all-in-one
>> >> metapackag
>> >>
>> >>   Using maas to deploy an HP hpvsa based system fails. When using the
>> >> default installer enlisting and commisioning complete without any
>> errors.
>> >> During OS install when disk partitioning screen comes up it begins
>> >> refreshing the screen every half-second or so and the progress shown is
>> >> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>> >>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
>> >> /var/log/syslog and /var/log/partman. Those files are attached. There
>> is
>> >> also no messages file in /var/log/maas/rsyslog/etc.
>> >>
>> >>   When using the fastpath installer the OS is installed but it used the
>> >>   ahci driver and fake raid.
>> >>
>> >>   Fastpath installed rc bits rather than ga bits. Had to do
>> dist-upgrade
>> >>   to get the latest.
>> >>
>> >> To manage notifications about this bug go to:
>> >> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>> >>
>> >
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1309720
>>
>> Title:
>>   latest bits not installing hpvsa (proprietary driver)
>>
>> Status in MAAS:
>>   New
>>
>> Bug description:
>>   Linux trusty-maas 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08
>> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>>   maas           1.5+bzr2252- all          MAAS server all-in-one
>> metapackag
>>
>>   Using maas to deploy an HP hpvsa based system fails. When using the
>> default installer enlisting and commisioning complete without any errors.
>> During OS install when disk partitioning screen comes up it begins
>> refreshing the screen every half-second or so and the progress shown is
>> erratic. 0%, then 90%, then 0%, then 70%, and on and on.
>>   ON Ctrl-Alt-F4 there are no messages to indicate a problem. Same in
>> /var/log/syslog and /var/log/partman. Those files are attached. There is
>> also no messages file in /var/log/maas/rsyslog/etc.
>>
>>   When using the fastpath installer the OS is installed but it used the
>>   ahci driver and fake raid.
>>
>>   Fastpath installed rc bits rather than ga bits. Had to do dist-upgrade
>>   to get the latest.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1309720/+subscriptions
>>
>
>

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2014-04-21:

#13

Moved this to HP ISS since the bug appears to be in the hpvsa driver, not in MAAS.

affects:	maas → hp-iss
Changed in hp-iss:
assignee:	Jason Hobbs (jason-hobbs) → nobody

Michael F. Miller (mikem1355) on 2014-05-30

Changed in hp-iss:
status:	New → Fix Released

hp-iss

latest bits not installing hpvsa (proprietary driver)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches