Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling upgrades that don't apply #25

Open
martbhell opened this issue Sep 22, 2019 · 11 comments
Open

Handling upgrades that don't apply #25

martbhell opened this issue Sep 22, 2019 · 11 comments
Labels

Comments

@martbhell
Copy link
Contributor

While I remember.

On Friday we saw some disk firmwares available. Disks are behind an Integrated Controller and when dsu applies the upgrade it can't because of System Configuration or some such. This role is green.

Would be nice if this role could alert somehow about this. Don't have return code right now but will try to find out :)

@martbhell martbhell added the bug label Sep 22, 2019
@Klaas-
Copy link
Contributor

Klaas- commented Sep 22, 2019

I don't think that's an exit code issue in this role. If it didn't throw a failure it exited properly and had one of these exit codes: https://github.com/CSCfi/ansible-role-dell-firmware-upgrade/blob/master/defaults/main.yml#L30-L33 none of these indicate a partial failure, those exit codes would be 25/26.

I always debug the command_result of this role to show the stdout, that's helpful when reporting errors and finding failures :)

For reference: latest docs: https://topics-cdn.dell.com/pdf/system-update-v17_users-guide_en-us.pdf

@martbhell
Copy link
Contributor Author

Indeed. It might be that we need to match / fail if there is something in stdout for this. But maybe instead of adding this to the role it should be reported to Dell.

@Klaas-
Copy link
Contributor

Klaas- commented Sep 22, 2019

yeah, that's what I meant, if the disk firmware upgrade was unsuccessful it should give a different exit code --> ie issue in dsu, not this role.

@martbhell
Copy link
Contributor Author

E-mailed dell's linux poweredge mailing list let's see if it goes through the mailing list. Return Code is zero.
Is that a good enough place or have you @Klaas- had better success with contacting dell tech support?

This was tested on a CentOS 7.6 Dell PowerEdge C6320 server.

output from dsu:


# dsu --non-interactive --apply-upgrades; echo $?
DELL EMC System Update 1.7.0
Copyright (C) 2014 DELL EMC Proprietary.
Verifying catalog installation ...
Installing catalog from repository ...
Fetching dsucatalog ...
Reading the catalog ...
Verifying inventory collector installation ...
Getting System Inventory ...
warning: Inventory collector returned with partial failure.
Determining Applicable Updates ...
Fetching Serial-ATA_Firmware_7KW56_LN_AA65_A00 ...
Installing Serial-ATA_Firmware_7KW56_LN_AA65_A00
Collecting inventory...
....
Running validation...

This Update Package is not compatible with your system configuration.

Fetching Serial-ATA_Firmware_KVKY5_LN_NA07_A00 ...
Installing Serial-ATA_Firmware_KVKY5_LN_NA07_A00
Collecting inventory...
....
Running validation...

This Update Package is not compatible with your system configuration.

Done! Please run 'dsu --inventory' to check the inventory
Exiting DSU!
0

@Klaas-
Copy link
Contributor

Klaas- commented Sep 24, 2019

All the mailing lists are down because of a misconfigured mailserver or something like that, I've complained multiple times in past, don't think that changed yet... :) So no hope there.

For support cases: I've only had bad dell support experience when it comes to software issues, so I can't point to any helpful contacts for dsu. So in short: open a support case, don't hope for a fast resolution :)

@martbhell
Copy link
Contributor Author

All the mailing lists are down because of a misconfigured mailserver or something like that, I've complained multiple times in past, don't think that changed yet... :) So no hope there.

For support cases: I've only had bad dell support experience when it comes to software issues, so I can't point to any helpful contacts for dsu. So in short: open a support case, don't hope for a fast resolution :)

Thanks, I'm glad I wrote about this here or I would have waited a while!

@Klaas-
Copy link
Contributor

Klaas- commented Sep 24, 2019

do you also have rhel servers to test on? While I do agree that centos and rhel are functionally equal if some package actually tests for rhel artifacts it may not find them. "Officially" Dell only supports rhel afaik.

@martbhell
Copy link
Contributor Author

I do not. I guess we'll see what happens. I couldn't find anything about this in the firmware binary but I didn't look very far :)

@Klaas-
Copy link
Contributor

Klaas- commented Oct 1, 2019

It seems the poweredge mailing lists just came back online -- maybe it would be a good idea to also report it there if you haven't gotten help from support yet :)

@martbhell
Copy link
Contributor Author

Great news! We could try there too, I'm on holiday now so 'not me' :)
We have not heard back from Dell DSU team but they have been informed.

@martbhell
Copy link
Contributor Author

No news yet but I tried to e-mail the linunx poweredge mailing list too to spread the Word

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants