<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva <span dir="ltr"><<a href="mailto:vfbsilva@gmail.com" target="_blank">vfbsilva@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Summers, seems I was missing:<br>
<br>
/./bin/ups-migrator update/<br>
<br>
It was not clear from me when building the image I needed to perform this<br>
step. Now I'm facing some SSL miss configuration, whenever I try to acess<br>
/ag-push/ or /auth I get an SSL error:<br>
<br>
/Exception handling request to /ag-push/: java.lang.RuntimeException: Unable<br>
to resolve realm public key remotely/<br>
<br>
<br>
the image ships with self-signed certs under:<br>
<br>
*standalone/configuration/cert<wbr>s/*<br>
<br>
I've ran certificate.sh providing my domain name and adding it to<br>
standalone.xml still seems it is not importing my key. What am I missing?<br>
<br>
<br></blockquote><div><br></div></span><div>Looping back in for posterity : </div><div><br></div><div>The ag-auth deployment isn't running in Kubernetes for some reason. The error you are getting is from the auth system not deploying not from SSL. The realm public key is a configuration option there. I've created <a href="https://issues.jboss.org/browse/AEROGEAR-1747" target="_blank">https://issues.jboss.<wbr>org/browse/AEROGEAR-1747</a> with more details. However that issue may never get fixed because we are splitting up auth from the deployed package "soon". Since auth will be deployed separately the problem just won't exist any more.</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div></div></blockquote><div><br></div><div>So it looks like resetting my mySQL databases solved the problem I was having and UPS deployed normally in kubernetes. I also switched to the aerogear/unifiedpush-wildfly-dev image which may or may not have affected the result as well.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="HOEnZb"><font color="#888888"><div></div><div>Summers</div></font></span><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-kubernetes-with-wildfly-eap-tp1132p1135.html" rel="noreferrer" target="_blank">http://aerogear-users.1116366.<wbr>n5.nabble.com/Aerogear-users-P<wbr>roblems-deplying-aerogear-in-k<wbr>ubernetes-with-wildfly-eap-tp1<wbr>132p1135.html</a><br>
<div class="m_8871157473544867959gmail-HOEnZb"><div class="m_8871157473544867959gmail-h5">Sent from the aerogear-users mailing list archive at Nabble.com.<br>
______________________________<wbr>_________________<br>
Aerogear-users mailing list<br>
<a href="mailto:Aerogear-users@lists.jboss.org" target="_blank">Aerogear-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-users" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/aerogear-users</a><br>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>