Landscape Client

stderr not captured when calling /usr/lib/landscape/smart-update

Bug #387441 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
High
Free Ekanayaka
Landscape Client 1.3.2

Bug Description

When /usr/lib/landscape/smart-update exits with a status different than zero and has a non-empty output, this output is captured and shown in the landscape-client logs (more specifically, package-reporter.log).

The error output (stderr), however, is not captured, so the logs don't actually show what went wrong.

Andreas Hasenack (ahasenack)
Changed in landscape-client:
importance: Undecided → High
milestone: none → 1.3.2
assignee: nobody → Free Ekanayaka (free.ekanayaka)
Free Ekanayaka (free.ekanayaka)
tags: added: review
Revision history for this message
Sidnei da Silva (sidnei) wrote :

Looks good to me, +1!

Sidnei da Silva (sidnei)
Changed in landscape-client:
status: New → In Progress
Revision history for this message
Christopher Armstrong (radix) wrote :

Okay, this looks good.

Revision history for this message
Christopher Armstrong (radix) wrote :

Um, that is, +1.

tags: removed: review
Free Ekanayaka (free.ekanayaka)
Changed in landscape-client:
status: In Progress → Fix Committed
Jamu Kakar (jkakar)
tags: added: needs-testing
Revision history for this message
Free Ekanayaka (free.ekanayaka) wrote :

Tested on hardy against the 1.3.2 packages in the Landscape PPA. Removing a GPG key from the APT ring correctly makes the reporter logging the relevant smart error, qa +1.

tags: removed: needs-testing
Andreas Hasenack (ahasenack)
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.