Andrew Bayer
Andrew Bayer
@afrittoli Yeah, that sounds good. I’ll try to get a PR up tomorrow for the better error message.
/hold Putting this on hold until we most likely just close it. =) From a chat this morning with @jerop, I feel like this is a reasonable path forward: *...
Moved to next milestone - I need to think about this a bit more, but I'm leaning towards likely closing it in favor of what's described in https://github.com/tektoncd/pipeline/pull/6056#issuecomment-1408936114.
@JeromeJu The failure you linked to is a red herring - that particular failure was me screwing up some copy-paste. The actual error I kept hitting is seen in https://prow.tekton.dev/view/gs/tekton-prow/pr-logs/pull/tektoncd_pipeline/5712/pull-tekton-pipeline-integration-tests/1588168599833415680:...
Oh, this would be a beautiful thing - I'm missing this from jclouds land. =)
Pipeline's already moved, and I know @dibyom has been working on this for Triggers, but I don't know the status there.
Ah, this might be because I have JCLOUDS_USER and JCLOUDS_PASSWORD set in the environment as well...
Hrm, no...but the credentials.identity from right before the NPE is "root" for some reason.
Ok, is this happening because when I create a node, I'm not actually getting credentials to speak of back from CloudStack?
This is definitely because of PropertiesCredentialStore - when I remove it from the context builder, everything works fine.