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

Node error in output #23

Closed
kjdms opened this issue Apr 27, 2021 · 7 comments
Closed

Node error in output #23

kjdms opened this issue Apr 27, 2021 · 7 comments
Assignees
Labels
bug Something isn't working in progress
Milestone

Comments

@kjdms
Copy link

kjdms commented Apr 27, 2021

Environment

  • Application Services Version: 1.11.0
  • BIG-IP Version: 14.1.2.8
  • Red Hat 8.3

Summary

Error when running against my UCS file. Reproducible on demand. The tool will complete if I limit it to one virtual server. Created F5 support case C3561341 to upload the UCS file in question.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Run the following command:
$ sudo podman run --pull=never --rm -v  "$PWD":/app/data f5-as3-config-converter:v1.11.0 -o data/shdc-viprion02.json -u data/MyUCS-2021_04_27-06_00.ucs
  1. Observe the following error message:
    at findSchemaDefault (/app/src/removeDefaultValues.js:40:30)
    at /app/src/removeDefaultValues.js:62:33
    at Array.forEach (<anonymous>)
    at matchDefaults (/app/src/removeDefaultValues.js:60:10)
    at /app/src/removeDefaultValues.js:80:20
    at Array.forEach (<anonymous>)
    at findProfiles (/app/src/removeDefaultValues.js:76:10)
    at /app/src/removeDefaultValues.js:78:24
    at Array.forEach (<anonymous>)
    at findProfiles (/app/src/removeDefaultValues.js:76:10)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected Behavior

No node errors in output.

Actual Behavior

Command fails with no output to file. STDERR is listed above.

@kjdms kjdms added the bug Something isn't working label Apr 27, 2021
@mdditt2000
Copy link

mdditt2000 commented Apr 27, 2021

@kjdms morning. Please can you send me a email message at &&** so i can get your UCS file to reproduce this and possibly open a bug. It could be viprion related.

@mdditt2000
Copy link

@kjdms got the UCS file. Thank you. Going to look at it this afternoon. Standby!

@mdditt2000 mdditt2000 self-assigned this Apr 27, 2021
@mdditt2000 mdditt2000 added the PME PME Action Item label Apr 27, 2021
@mdditt2000
Copy link

please note ACC is community supported i have taken ownership of SR C3561341

@mdditt2000
Copy link

Created Jira request CHARON-254 for PM tracking. Requesting PD look to see why ACC cannot open this UCS file. I am going to try corkscrew aka F5 vscode extension to see if that will open this UCS file.

@mdditt2000
Copy link

Change By: Vladimir
Status: Code Review

@mdditt2000 mdditt2000 added in progress and removed PME PME Action Item labels May 7, 2021
@mdditt2000
Copy link

@kjdms bug is in code-review. Will provide image once available. Thanks

@mdditt2000
Copy link

Closing this issue. Provided RC to @kjdms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in progress
Projects
None yet
Development

No branches or pull requests

3 participants