-
Notifications
You must be signed in to change notification settings - Fork 69
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
Route VMware vCD logs into its own file #153
Conversation
This PR relies on a PR from core, hence the WIP label. I've only re-routed logs for cloud- and network- manager, leaving the infra- intact. |
4430cfa
to
bc98893
Compare
With this commit we prevent a mess in evm.log which is caused by vmware cloud/network provider's logs. We start using the $vcloud_log logger for the latter. Signed-off-by: Miha Pleško <[email protected]>
bc98893
to
4d5f5de
Compare
Checked commit miha-plesko@4d5f5de with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 **
|
@agrare this is a followup for ManageIQ/manageiq#16641. I kindly ask for a review. Rubocop seems to explode after modifying |
Yeah rubocop yells about that a lot and I'm not sure why yet. I don't think it is anything that you're doing. |
Route VMware vCD logs into its own file (cherry picked from commit d5f4df8) https://bugzilla.redhat.com/show_bug.cgi?id=1527555
Gaprindashvili backport details:
|
Route VMware vCD logs into its own file (cherry picked from commit d5f4df8) https://bugzilla.redhat.com/show_bug.cgi?id=1531156
Fine backport details:
|
Target template related actions
With this commit we prevent a mess in evm.log which is caused by vmware cloud/network provider's logs. We start using the $vcloud_log logger for the latter.
@miq-bot add_label enhancement, gaprindashvili/yes, fine/yes
@miq-bot assign @blomquisg
Related issue: ManageIQ/manageiq#16642
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1525201
Depends on: ManageIQ/manageiq#16641 (merged)
/cc @gberginc