Ticket #719 (closed defect: fixed)
amf-state processing when specified dn is not found faulty
| Reported by: | stefan.k.berg@… | Owned by: | hafe |
|---|---|---|---|
| Priority: | minor | Milestone: | 4.0.0-M3 |
| Component: | unknown | Version: | 4.0-B3 |
| Keywords: | Cc: | ||
| patch waiting for maintainer: | no |
Description (last modified by hafe) (diff)
When explicitly specifying a non-existing dn as argument to amf-state, such as for example ...
amf-state siass all 'safSISU=safSu=SC_2_2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAFnotfound'
... the amf-state script will process after the point where no matching dn is found. A lot of output is made to stderr, and finally amf-state will exit with return code 0 (which should probably be a non-zero rc in this case).
another problem to be fixed: if amf-adm fails, it still returns 0 (OK)
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
