1. Messages
  2. Runner set to 0, requested app stack cflinuxfs2 is not available

Re: Runner set to 0, requested app stack cflinuxfs2 is not available

Amit Kumar Gupta
 

I suspect that if you pushed the app before setting the backend to default
to diego, the app's state in the DB still has backend: dea. So CC is
trying to schedule it on the DEAs and the first scheduling constraint is to
find something with the right stack. There are no DEAs with the right
stack because there are no DEAs. If you explicitly set this app to use the
diego backend, you should be fine. This doc (
https://docs.cloudfoundry.org/adminguide/apps-enable-diego.html) discusses
some stuff related to migrating to Diego, including batch migrations, see
if it helps you out.

If this doesn't work, let me know.

Best,
Amit

On Wed, Aug 17, 2016 at 4:25 PM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:

cf v240, diego 0.1481.0, cflinuxfs-rootfs 1.21.0, etcd 63, garden-linux
0.339.0, bosh-openstack-kvm-ubuntu-trusty-go_agent 3262.4

With a runner instance, pushing the sample go application works fine.
Setting the default backend to diego, I assume the runner is no longer
needed.
Set the runner to 0, results in a failed push:
Server error, status code: 404, error code: 250003, message: The stack
could not be found: The requested app stack cflinuxfs2 is not available on
this system.
Put the runner back, all appears good. I have a few environments running
default diego, however, they all have at least 1 runner.

I've got some more verifying to see what's going, however, thought I would
toss the question out.

?
attachment.html

Join {cf-dev@lists.cloudfoundry.org to automatically receive all group messages.