Issue with Latest version of minishift
by Kamesh Sampath
When I updated my minishift to latest and started it I got the error
saying:
```E0823 23:49:26.216390 2044 interface.go:34] Failed to install
"openshift-web-console-operator": Operation cannot be fulfilled on
openshiftwebconsoleconfigs.webconsole.operator.openshift.io "instance":
the object has been modified; please apply your changes to the latest
version and try again
I0823 23:49:26.216448 2044 interface.go:41] Finished installing
"openshift-web-console-operator" "centos-imagestreams"
"openshift-image-registry" "sample-templates" "persistent-volumes"
"openshift-router"
Error: Operation cannot be fulfilled on
openshiftwebconsoleconfigs.webconsole.operator.openshift.io "instance":
the object has been modified; please apply your changes to the latest
version and try again```
Not sure why this error. Any solutions ??
4 years, 8 months
Re: Minishift b2d nightly build 269 failed
by Lalatendu Mohanty
On Wed, Aug 29, 2018 at 8:01 AM, <ci(a)centos.org> wrote:
> The build has failed. Check the build URL for failure logs:
> https://ci.centos.org/job/minishift-nightly-b2d/269/
The nightly failure looks genuine. Anyone seen this error recently
*02:31:43* --- Failed steps:*02:31:43* *02:31:43* Scenario: As a
user, I can push pulled application image to OpenShift integrated
docker registry and deploy it #
features/addon-registry-route.feature:32*02:31:43* And executing
"docker push docker-registry-default.$(minishift
ip).nip.io/myproject/nginx" in host shell succeeds #
features/addon-registry-route.feature:35*02:31:43* Error:
*Command 'docker push docker-registry-default.$(minishift
ip).nip.io/myproject/nginx <http://nip.io/myproject/nginx>', expected
to succeed, exited with exit code: 1
02:31:43 **02:31:43* *02:31:43* Scenario: As a user, I can login to
OpenShift integrated docker registry after restart minishift #
features/addon-registry-route.feature:46*02:31:43* Then executing
"minishift start" succeeds #
features/addon-registry-route.feature:49*02:31:43* Error:
*Command 'start' did not execute successfully. cmdExit: 1, cmdErr:
Error determining Docker settings: ssh command error:
02:31:43 command : docker version --format '{{.Server.APIVersion}}'
02:31:43 err : exit status 1
02:31:43 output :
02:31:43 Cannot connect to the Docker daemon. Is the docker daemon
running on this host?
02:31:43
02:31:43 *
-Lala
4 years, 9 months
Are you being kicked off ??
by Kamesh Sampath
I see am not able to login to #minishift on IRC its constantly saying
some nickreg err .. not sure why .. any others facing ???
4 years, 9 months
Release announcement for Minishift v1.23.0
by Anjan Nath
Hi All,
The Minishift team is pleased to announce the release of Minishift v1.23.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.23.0, we added some features, enhancements and bug fixes
including:
- OKD 3.10 is the default version in this release of Minishift.
Minishift
version can be added in add-ons as a requisite for executing it.
Refer
documentation [2] for details.
- openshift-version flag now supports “latest” as an argument. It will
run
latest GA release of OKD.
$ minishift start --openshift-version latest
- Added a feature for add-ons to express dependencies between add-ons
[3]
- Default RAM space for profiles is increased from 2GB to 4GB, you can
always
change it using:
$ minishift start --memory <RAM_Size>
- Minishift is using machine-drivers/machine instead of docker/machine
package.
machine-drivers/machine is fork of docker/machine. For details refer
[7] [8].
- Che and htpasswd-identity-provider add-ons are moved from the
minishift/minishift-addons
repository to minishift/minishift repository. They are now part of
the default add-ons. [9] [10].
- htpasswd-identity-provider : This add-on will help users to
change the default
password for the OpenShift instance. It will be very useful when
public cloud
machines are used for running Minishift [11].
- Che: Runs Che IDE on Minishift.
You can find a detailed list of issues in the release notes[4]. For
information about getting started, using, and developing Minishift, see the
documentation [5]. 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 hangs out
at
#minishift channel on Freenode and it is the perfect place to discuss
anything
Minishift related. You can sign up for our mailing list [6] to receive
development updates, ask questions about Minishift, suggest ideas and talk
to
the community.
[1] https://github.com/minishift/minishift
[2]
https://docs.okd.io/latest/minishift/using/addons.html#addon-minishift-ve...
[3]
https://docs.okd.io/latest/minishift/using/addons.html#addon-defining-add...
[4] https://github.com/minishift/minishift/releases/tag/v1.23.0
[5] https://docs.okd.io/latest/minishift
[6] https://lists.minishift.io/admin/lists/minishift.lists.minishift.io
[7] https://github.com/docker/machine/issues/4537
[8] https://github.com/machine-drivers/machine
[9] https://github.com/minishift/minishift/issues/2596
[10] https://github.com/minishift/minishift/issues/2647
[11]
https://docs.okd.io/latest/minishift/using/run-against-an-existing-machin...
4 years, 9 months
regarding authentication
by Naresh Aithagoni
Hello,
I am getting the following error when I run " oc login https://....
amazonaws.com -u system:admin ".
" error: couldn't get https://....
amazonaws.com:0000/.well-known/oauth-authorization-server/.well-known/oauth-authorization-server:
unexpected response status 403 "
any help?
thanks
4 years, 9 months
Re: Error could not set oc CLI context
by Praveen Kumar
On Mon, Aug 20, 2018 at 12:31 PM Naresh Aithagoni <anaresh7777(a)gmail.com> wrote:
>
> Okay, when you’re going to release the new version?.
We are going to release a new version by tomorrow.
> Is the artifact [1] a new version?
No, this artifact is from the PR build, the new version might have
more fixes and enhancement as well.
>
> On Mon 20. Aug 2018 at 08:57, Praveen Kumar <kumarpraveen.nitdgp(a)gmail.com> wrote:
>>
>> On Mon, Aug 20, 2018 at 12:25 PM Naresh Aithagoni <anaresh7777(a)gmail.com> wrote:
>> >
>> > Hi,
>> > Thanks for the response.
>> >
>> > I’m using latest version of the Minishift. I am getting this error When I start minishift. But when I delete and re-start minishift, I am not getting the error. I’m worrying, do we need to set the “oc” path every start of minishift?
>>
>> There was a bug and stop => start having the issue, this bug is now
>> fixed so new version which will be released soon will work as
>> expected. If you use artifacts from the PR[1] you will not see this
>> one.
>>
>> [0] https://github.com/minishift/minishift/issues/2679
>> [1] https://github.com/minishift/minishift/issues/2679#issuecomment-413791915
>>
>> >
>> > Regards,
>> > Naresh
>> >
>> > On Mon 20. Aug 2018 at 08:26, Lalatendu Mohanty <lmohanty(a)redhat.com> wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Aug 19, 2018 at 5:27 PM, Naresh Aithagoni <anaresh7777(a)gmail.com> wrote:
>> >>>
>> >>> Hello,
>> >>> I am getting this error when I start minishift. It is working successfully when I delete and re-start minishift. Any help please?
>> >>>
>> >>> Error: "Could not set oc CLI context for 'minishift' profile: Error during setting 'minishift' as active profile: The specified path to oc '' does not exist"
>> >>
>> >>
>> >> Hi Naresh,
>> >>
>> >> Which version of Minishift you are using ? As I understood you are seeing this issue when you run "minishift start" after "minishift stop" right?
>> >>
>> >>>
>> >>> Thanks and regards,
>> >>> Naresh
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
>> >>> To unsubscribe send an email to minishift-leave(a)lists.minishift.io
>> >>>
>> >>
>> > _______________________________________________
>> > Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
>> > To unsubscribe send an email to minishift-leave(a)lists.minishift.io
>>
>>
>>
>> --
>> Praveen Kumar
>> http://fedoraproject.org/wiki/User:Kumarpraveen
>> http://fedoraproject.org/
>> http://kumar-pravin.blogspot.com
--
Praveen Kumar
http://fedoraproject.org/wiki/User:Kumarpraveen
http://fedoraproject.org/
http://kumar-pravin.blogspot.com
4 years, 9 months
Error could not set oc CLI context
by Naresh Aithagoni
Hello,
I am getting this error when I start minishift. It is working successfully
when I delete and re-start minishift. Any help please?
Error: "Could not set oc CLI context for 'minishift' profile: Error
during setting 'minishift' as active profile: The specified path to oc ''
does not exist"
Thanks and regards,
Naresh
4 years, 9 months
Fwd: PSA for openshift users - dockerhub will be down for scheduled outage on August 25th
by Lalatendu Mohanty
FYI
---------- Forwarded message ----------
From: Clayton Coleman <ccoleman(a)redhat.com>
Date: Fri, Aug 17, 2018 at 6:02 AM
Subject: PSA for openshift users - dockerhub will be down for scheduled
outage on August 25th
To: dev <dev(a)lists.openshift.redhat.com>, users <
users(a)lists.openshift.redhat.com>
Please see https://status.docker.com/ for times.
Remember, if you have autoscaling nodes that need to pull new apps, or have
pods that run with PullAlways, or push builds to the docker hub, while the
hub is down those operations will fail.
Mitigations could include:
1. Disable autoscaling for the duration
2. Use the image mirroring and transparent proxying feature of the
openshift integrated registry (switch the resolutionPolicy for your image
streams to Local on 3.9 or later) to automatically mirror remote images and
serve them from the local registry
3. Disable PullAlways from any deployed workloads so you can leverage
cached local images (if a pod tries to restart while the registry is down
and pull always is set, the new container won’t be started).
4. Push to a different registry than dockerhub, like the integrated
registry or quay.io
_______________________________________________
dev mailing list
dev(a)lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
4 years, 9 months
