Update Package request for ppc64-diag

Is ppc64-diag 2.7.4 the version that is needed for POWER9 compatibility?

------- Comment From <email address hidden> 2017-08-04 00:01 EDT-------
(In reply to comment #9)
> Is ppc64-diag 2.7.4 the version that is needed for POWER9 compatibility?

Yes.

-Vasant

Hi there,
I upgraded ppc64-diag to 2.7.4 in Debian Unstable.

F.

Vasant, or somebody else: how can the update be validated for the xenial and zesty uploads?

------- Comment From <email address hidden> 2017-09-14 01:38 EDT-------
(In reply to comment #12)
> Vasant, or somebody else: how can the update be validated for the xenial and
> zesty uploads?

First check the already installed version.
dpkg -l | grep ppc64-diag

Then install upgraded package version using "apt install" or "dpkg -i"
apt install ppc64-diag -> Latest ppc64-diag package will be installed

Or can be installed manually using "dpkg -i" command
dpkg -i <package_dpkg_file>

Installed package version can be tested using below command:
dpkg -l | grep ppc64-diag

Matthias's question is more about "how can we make sure that the new version of ppc64-diag is good?", rather than the response in comment #5.

This information is required as a part of the Ubuntu Stable Release update process to ensure that we don't introduce any regressions with updated software versions. For more details please see http://wiki.ubuntu.com/StableReleaseUpdates and add the appropriate information, Test Case and Regression Potential, to the bug description.

An upload of ppc64-diag to xenial-proposed has been rejected from the upload queue for the following reason: "The bug this upload would fix is missing a Test Case which is required for the Stable Release Update process.".

An upload of ppc64-diag to trusty-proposed has been rejected from the upload queue for the following reason: "The bug this upload would fix is missing a Test Case which is required for the Stable Release Update process.".

------- Comment From <email address hidden> 2017-10-14 11:32 EDT-------
Hello,

Sorry for the delay in response.. Our guys responded long back, but made it as *internal* comment. Hence it didn't reflect in launchpad :-(

We use avocado test framework to verify ppc64-diag. Test cases are available under avocado-misc test cases. Let us know if you need more details.

[1] https://github.com/avocado-framework-tests/avocado-misc-tests.git

generic/ras.py , generic/ras_extended.py contains test cases .

If you want to verify manually you can perform below steps :
PowerNV host :
- On powernv system 'opal_errd' daemon should run fine.
- `opal-elog-parse' --> lists error logging information
- diag_encl
- usysident/usysattn

- On PowerVM LPAR,
- diag_encl
- 'rtas_errd' daemon should run fine
- usysident/usysattn

Please reconsider this defect for 16.04 LTS release. Also note that Ubuntu 17.10 contains v2.7.4. We have verified that and it works fine.

-Vasant

------- Comment From <email address hidden> 2017-10-14 11:34 EDT-------
..and as described in launchpad #1715397, we need below commit on top of 2.7.4.

commit 608507ea8ed81209204feacbbde40e234d261141
Author: Vasant Hegde <email address hidden>
Date: Wed Sep 13 21:54:45 2017 +0530

scripts: Fix service scripts

-Vasant

Hello bugproxy, or anyone else affected,

Accepted ppc64-diag into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ppc64-diag/2.7.4-1~16.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

An update has also been added to -proposed for Ubuntu 14.04.

------- Comment From <email address hidden> 2017-10-17 05:46 EDT-------
(In reply to comment #21)
> Hello bugproxy, or anyone else affected,
>
> Accepted ppc64-diag into xenial-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/ppc64-diag/2.7.4-1~16.04
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to
> enable and use -proposed.Your feedback will aid us getting this update out
> to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-xenial to verification-done-xenial. If it does not fix
> the bug for you, please add a comment stating that, and change the tag to
> verification-failed-xenial. In either case, details of your testing will
> help us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance!

Thanks! we will verify and update defect ASAP.

-Vasant

------- Comment From <email address hidden> 2017-10-23 02:17 EDT-------
Verified on zz machine. Attaching the logs.

Thanks,
Pavithra

------- Comment (attachment only) From <email address hidden> 2017-10-23 02:18 EDT-------

This doesn't look like a successful verification to me, if the package failed to configure in the environment where you tested it.

------- Comment From <email address hidden> 2017-10-24 10:42 EDT-------
(In reply to comment #27)
> This doesn't look like a successful verification to me, if the package
> failed to configure in the environment where you tested it.

Looks like below commit is missing. Rest of the output looks good.

[Unfortunately we introduced regression in v2.7.4 release.. which is fixed by below commit]

commit 608507ea8ed81209204feacbbde40e234d261141
Author: Vasant Hegde <email address hidden>
Date: Wed Sep 13 21:54:45 2017 +0530

scripts: Fix service scripts
By mistake I added wrong condition check which resulted in unnecessary
log messages in PowerNV system. This patch fixes service script properly.
Fixes: 1f49a51c (scripts: Improve service scripts)
Reported-by: Fr?d?ric Bonnard <email address hidden>
Signed-off-by: Vasant Hegde <email address hidden>

-Vasant

The above mentioned patch is included in 2.7.4-2, but missing from 2.7.4-1~14.04 and 2.7.4-1~16.04.

Preparing updates to include debian/patches/fix-rtas_errd-unit.patch in xenial and trusty backports. zesty will be end of life soon enough to not warrant an update.

Reuploaded into the unapproved queue, fixed-up SRUs for trusty and xenial.

Hello bugproxy, or anyone else affected,

Accepted ppc64-diag into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ppc64-diag/2.7.4-2~16.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello bugproxy, or anyone else affected,

Accepted ppc64-diag into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ppc64-diag/2.7.4-2~14.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

------- Comment From <email address hidden> 2017-12-05 04:54 EDT-------
(In reply to comment #32)
> Ankit,
>
> Could you please test the package that was just submitted to the -proposed
> archive?
>
> Thank you,
> Breno

Breno,
It contains the patch required.
We can close this bug

~Ankit

------- Comment From <email address hidden> 2017-12-21 10:04 EDT-------
Canonical,

Ankit tested it and reported it is working ok. Thanks!

This bug was fixed in the package ppc64-diag - 2.7.4-2~16.04

---------------
ppc64-diag (2.7.4-2~16.04) xenial; urgency=medium

  * SRU: LP: #1708494. Update to the version found in 17.10.

ppc64-diag (2.7.4-2) unstable; urgency=medium

  * d/patches/fix-rtas_errd-unit.patch : fix rtas_errd being started where it
    should not and being reported by systemd as failing whereas the daemon
    exits as it should (LP: #1715397)

 -- Dimitri John Ledkov <email address hidden> Tue, 28 Nov 2017 16:59:36 +0000

The verification of the Stable Release Update for ppc64-diag has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package ppc64-diag - 2.7.4-2~14.04

---------------
ppc64-diag (2.7.4-2~14.04) trusty; urgency=medium

  * SRU: LP: #1708494. Update to the version found in 17.10.

ppc64-diag (2.7.4-2) unstable; urgency=medium

  * d/patches/fix-rtas_errd-unit.patch : fix rtas_errd being started where it
    should not and being reported by systemd as failing whereas the daemon
    exits as it should (LP: #1715397)

 -- Dimitri John Ledkov <email address hidden> Tue, 28 Nov 2017 16:59:36 +0000