avoid download of openshift client
by ondersezgin＠gmail.com
while starting minishift it is possible to use --iso-file ,
is it possible to use ssomthing similar to avoid downloading openshift client?
4 years
Release announcement for Minishift 1.29.0
by Gerard Braad
Hi all,
Happy holidays and seasonal greetings. Although many of you celebrate
Christmas, some elves have remained hard at work to be able to deliver
you the release of Minishift 1.29.0.
Minishift [1] is a command-line tool that provisions and manages a
single-node OpenShift cluster. You can run Minishift on GNU/Linux,
Microsoft Windows, or macOS.
In version 1.29.0, we added new features, enhancements, and bug fixes including:
* Minishift delete command now also clear the kubeconfig entry which
created by it.
* Minishift setup command now have support for Mac OS (Give it a try).
* Mutating and validating webhooks are now part of minishift addons
and can be enabled.
You can find a detailed list of issues in the release notes [2].
For information about getting started, using, and developing
Minishift, see the documentation [3].
Please try the new release. The easiest upgrade path is by simply running:
$ minishift update
We are looking forward to your feedback. The Minishift community [4]
hangs out in the #minishift channel on Freenode and it is the perfect
place to discuss anything Minishift related.
You can sign up for our mailing list [5] to receive development
updates, ask questions about Minishift, suggest ideas, and talk to the
community.
[1] https://github.com/minishift/minishift
[2] https://github.com/minishift/minishift/releases/tag/v1.29.0
[3] https://docs.openshift.org/latest/minishift/index.html
[4] https://github.com/minishift/minishift#community
[5] https://lists.minishift.io/admin/lists/minishift.lists.minishift.io
4 years
Unexpected response(400 Bad Request), to the authorization request. Missing header:[Location]
by Francesco Marchioni
Hi all,
we are evaluating testing EAP using a new testsuite
<https://gitlab.cee.redhat.com/xpaas-qe/test-eap>, specifically built for
Xpaas.
This testsuite uses behind the hoods io.fabric8.openshift.api and XTF
<https://github.com/xtf-cz/xtf> framework.
I have observed many failures related to lack of authorization requests.
This error appears if we use Minishift as target server. On the other hand,
it does not appear if we use a regular Openshift cluster.
Are you aware of any different authorization defaults compared with
Openshift? or any possible workaround?
Thanks
Log below:
[ERROR] com.redhat.xpaas.eap.template.EapCDCreationTest Time elapsed:
20.774 s <<< ERROR!
io.fabric8.kubernetes.client.KubernetesClientException: Operation: [list]
for kind: [Pod] with name: [null] in namespace: [fmarchio] failed.
at
io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64)
at
io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:72)
at
io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:197)
at
io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:618)
at
io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:68)
at cz.xtf.core.openshift.OpenShift.getPods(OpenShift.java:251)
at
cz.xtf.junit5.listeners.PodLogRecorder.executionFinished(PodLogRecorder.java:34)
at
org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.lambda$executionFinished$5(TestExecutionListenerRegistry.java:92)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at
org.junit.platform.launcher.core.TestExecutionListenerRegistry.notifyTestExecutionListeners(TestExecutionListenerRegistry.java:59)
at
org.junit.platform.launcher.core.TestExecutionListenerRegistry.access$100(TestExecutionListenerRegistry.java:28)
at
org.junit.platform.launcher.core.TestExecutionListenerRegistry$CompositeTestExecutionListener.executionFinished(TestExecutionListenerRegistry.java:92)
at
org.junit.platform.launcher.core.ExecutionListenerAdapter.executionFinished(ExecutionListenerAdapter.java:56)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.reportCompletion(NodeTestTask.java:177)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:112)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:38)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:136)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:127)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:107)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:38)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:136)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:127)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:107)
at
org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:32)
at
org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor.execute(HierarchicalTestExecutor.java:52)
at
org.junit.platform.engine.support.hierarchical.HierarchicalTestEngine.execute(HierarchicalTestEngine.java:51)
at
org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:220)
at
org.junit.platform.launcher.core.DefaultLauncher.lambda$execute$6(DefaultLauncher.java:188)
at
org.junit.platform.launcher.core.DefaultLauncher.withInterceptedStreams(DefaultLauncher.java:202)
at
org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:181)
at
org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:128)
at
org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:142)
at
org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:117)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
Caused by: java.io.IOException: Unexpected response(400 Bad Request), to
the authorization request. Missing header:[Location]!
at
io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.authorize(OpenShiftOAuthInterceptor.java:133)
at
io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.acquireNewToken(OpenShiftOAuthInterceptor.java:111)
at
io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.intercept(OpenShiftOAuthInterceptor.java:63)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
at okhttp3.RealCall.execute(RealCall.java:77)
at
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:379)
at
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344)
at
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:328)
at
io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:193)
--
Francesco Marchioni
Senior QUALITY ENGINEER
Red Hat ITALY <https://www.redhat.com>
Via Andrea Doria 41
00192 ROMA
fmarchio(a)redhat.com M: +39-320-96-71-710
<https://red.ht/sig>
4 years, 1 month
Minishift with two nodes
by Francesco Marchioni
Hi all!
I'm evaluating to use minishift for some high availablity tests between two
Nodes. From what I can see, the out of the box minishift set up is single
node:
oc get nodes
NAME STATUS ROLES AGE VERSION
localhost Ready <none> 86d v1.11.0+d4cacc0
Is it viable/recommended to install multiple nodes on minishift?
or (rephrased) would it simpler to just install OCP ?
Thanks!
--
Francesco Marchioni
Senior QUALITY ENGINEER
Red Hat ITALY <https://www.redhat.com>
Via Andrea Doria 41
00192 ROMA
fmarchio(a)redhat.com M: +39-320-96-71-710
<https://red.ht/sig>
4 years, 1 month
