[Container-tools] debugging atomicapp examples & the adb

[Jason Brooks]

----- Original Message -----
> From: "Aaron Weitekamp" <aweiteka at redhat.com>
> To: "Jason Brooks" <jbrooks at redhat.com>, "Lalatendu Mohanty" <lmohanty at redhat.com>
> Cc: "container-tools" <Container-tools at redhat.com>
> Sent: Wednesday, August 5, 2015 1:55:30 PM
> Subject: Re: [Container-tools] debugging atomicapp examples & the adb
> 
> Jason, I'm able to reproduce the issue. I suspect we've got a kubectl
> version mismatch, v.9 vs v1. I upgraded to kube to v0.17 with similar (but
> different) error. I was able to run the service on OpenShift using Kube v1,
> for what it's worth.
> 
> Does anyone know when we get kube v1 in centos? Lala?

It's available in the cbs here:

http://cbs.centos.org/repos/virt7-docker-common-testing/x86_64/os/

> 
> -Aaron
> 
> On Wed, Aug 5, 2015 at 12:27 PM, Jason Brooks <jbrooks at redhat.com> wrote:
> 
> >
> > Hey all, I'm experiencing an issue running some of the examples at
> > the nulecule project w/ the atomicapp/dev vagrant box, and I'm
> > trying to figure out where to look / file issues.
> >
> > I'm trying to figure out if this is known to be working w/
> > image X or w/ kube version Y, etc., making this an issue w/
> > my setup, or whether the problem is with the atomicapp.
> >
> > Here are the steps I'm following:
> >
> > vagrant init atomicapp/dev
> > vagrant up provider=libvirt
> > vagrant ssh
> > sudo atomic run projectatomic/wordpress-centos7-atomicapp
> >
> > ...
> >
> >
> > F0805 16:17:14.946675      48 create.go:75] unable to recognize
> > "/atomicapp/.workdir/mariadb-atomicapp/artifacts/kubernetes/mariadb-service.yaml":
> > no object named "Service" is registered
> > Traceback (most recent call last):
> >   File "/usr/bin/atomicapp", line 9, in <module>
> >     load_entry_point('atomicapp==0.1', 'console_scripts', 'atomicapp')()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/cli/main.py", line 89,
> > in main
> >     cli.run()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/cli/main.py", line 70,
> > in run
> >     args.func(args)
> >   File "/usr/lib/python2.7/site-packages/atomicapp/cli/main.py", line 21,
> > in cli_run
> >     ae.run()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/run.py", line 187, in
> > run
> >     self._dispatchGraph()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/run.py", line 95, in
> > _dispatchGraph
> >     ret = component_run.run()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/run.py", line 187, in
> > run
> >     self._dispatchGraph()
> >   File "/usr/lib/python2.7/site-packages/atomicapp/run.py", line 99, in
> > _dispatchGraph
> >     self._processComponent(component, graph_item)
> >   File "/usr/lib/python2.7/site-packages/atomicapp/run.py", line 172, in
> > _processComponent
> >     provider.deploy()
> >   File
> > "/usr/lib/python2.7/site-packages/atomicapp/providers/kubernetes.py", line
> > 73, in deploy
> >     self._callK8s(k8s_file)
> >   File
> > "/usr/lib/python2.7/site-packages/atomicapp/providers/kubernetes.py", line
> > 41, in _callK8s
> >     subprocess.check_call(cmd)
> >   File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
> >     raise CalledProcessError(retcode, cmd)
> > subprocess.CalledProcessError: Command '['/host/usr/bin/kubectl',
> > 'create', '-f',
> > u'/atomicapp/.workdir/mariadb-atomicapp/artifacts/kubernetes/mariadb-service.yaml',
> > '--namespace=default']' returned non-zero exit status 255
> >
> >
> > ---
> >
> > Jason Brooks
> > Red Hat Open Source and Standards
> >
> > @jasonbrooks | @redhatopen
> > http://community.redhat.com
> >
> >
> > _______________________________________________
> > Container-tools mailing list
> > Container-tools at redhat.com
> > https://www.redhat.com/mailman/listinfo/container-tools
> >
>