Remove vestiges of glog command-line flags.#3759
Remove vestiges of glog command-line flags.#3759istio-merge-robot merged 1 commit intoistio:masterfrom geeknoid:master
Conversation
|
/test e2e-suite-rbac-auth |
ldemailly
left a comment
There was a problem hiding this comment.
nice, qq about left over -v x:
.circleci/config.yml
Outdated
There was a problem hiding this comment.
is the leftover -v 2 doing anything now ? will it break ?
There was a problem hiding this comment.
It wasn't clear that all the -v X flags were indeed for glog, so I submitted as-is. Clearly, they are indeed for glog. I'll update and try again.
There was a problem hiding this comment.
it might be safer to just absorb (or even better translate into level == debug ) the -v in case some of our customers have their own templates for installing istio ?
(@costinm thoughts on backward compatibility needs for this ?)
There was a problem hiding this comment.
ps: you missed this line's "-v 2" - and should those be replaced by -loglevel debug?
|
circle beat me to it almost: who needs reviews when we have good tests ;-) |
There was a problem hiding this comment.
replace by the equivalent with the new logger?
|
I0224 18:25:56.587] po/istio-ingress-68bfbc686d-k8s4v 0/1 Error 1 5s 10.28.26.132 gke-istio-e2e-rbac-rotat-default-pool-708ea9ff-s5bx it appears the ingress yaml /... is somehow not happy |
|
can you add 1 test at least that the glog shim works |
|
Please (cd vendor; git checkout 5392831d46eb36cb168e818f1872eae39d9660d5 ) to further test |
|
can you rebase and retest ? |
|
/hold |
|
@geeknoid PR needs rebase |
|
2 more issies:
|
|
/test e2e-suite-rbac-auth |
|
I0228 00:00:58.753] istio-ca-847fcd677-gmfsz 0/1 ImagePullBackOff 0 2m |
|
ca error is odd but looks unrelated
so we can merge this one so istio/istio doesn't stay behind vendor too long (in case someone else starts a new PR with vendor changes...) |
|
ping^ |
|
To answer Laurent's question, you get this on the command-line when using a deprectaed option: Flag --v has been deprecated, please use --log_output_level instead To address Costin's issue, this PR doesn't change anything in the behavior of the system, it merely removes useless command-line options from our help messages and from our command-lines. So these concerns should be filed as separate issues. |
|
@geeknoid: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/test e2e-simple |
|
/unhold |
|
All green and happy. Just needs approval. |
|
/lgtm Will file a bug for flag defaults. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: costinm, ldemailly The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/hold cancel |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue. |
| The following command sends a `report` request to Mixer. | ||
| ```shell | ||
| bazel-bin/mixer/cmd/mixc/mixc report -v 2 --string_attributes destination.service=abc.ns.svc.cluster.local,source.name=myservice,target.port=8080 --stringmap_attributes "request.headers=clnt:abc;source:abcd,destination.labels=app:ratings,source.labels=version:v2" --int64_attributes response.duration=2003,response.size=1024 --timestamp_attributes request.time="2017-07-04T00:01:10Z" --bytes_attributes source.ip=c0:0:0:2 | ||
| bazel-bin/mixer/cmd/mixc/mixc report --string_attributes destination.service=abc.ns.svc.cluster.local,source.name=myservice,target.port=8080 --stringmap_attributes "request.headers=clnt:abc;source:abcd,destination.labels=app:ratings,source.labels=version:v2" --int64_attributes response.duration=2003,response.size=1024 --timestamp_attributes request.time="2017-07-04T00:01:10Z" --bytes_attributes source.ip=c0:0:0:2 |
There was a problem hiding this comment.
when we updated this, we should have removed references to bazel ;). Follow-on PR to remove bazel-bin ?
|
did you run "make depend.status" before the PRs ? because it's failing on circleci and for me too when I try to fix it: |
No description provided.