New rpm packages  contains only the path for the second file related to the bug you sent me, any case I am going to try patching by hand

Il giorno dom 8 dic 2019 alle ore 13:37 Bharat Kunwar <bharat@stackhpc.com> ha scritto:

It should have been installed with stein 8.2.0. It sounds like you haven’t installed the right version of the package.

On 8 Dec 2019, at 10:55, Ignazio Cassano <ignaziocassano@gmail.com> wrote:



No, I don't. I'll apply this patch asap.

Thanks 

Ignazio

Il Dom 8 Dic 2019, 00:06 Bharat Kunwar <bharat@stackhpc.com> ha scritto:

Do you have this change in the version of magnum you installed? If you do, it should definitely work!

https://review.opendev.org/#/c/695632/

Sent from my iPhone

On 7 Dec 2019, at 17:35, Ignazio Cassano <ignaziocassano@gmail.com> wrote:



Hello Bharat,

the following are last lines of the master node /var/log/cloud-init-output.log file:

ystemctl enable heat-container-agent
+ systemctl start heat-container-agent
starting services
activating service etcd
activating service docker
activating service kube-apiserver
activating service kube-controller-manager
activating service kube-scheduler
activating service kubelet
activating service kube-proxy
Trying to label master node with node-role.kubernetes.io/master=""
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""
error: resource(s) were provided, but no name, label selector, or --all flag specified
Trying to label master node with node-role.kubernetes.io/master=""

Regards

Ignazio

Il giorno ven 6 dic 2019 alle ore 22:54 Bharat Kunwar <bharat@stackhpc.com> ha scritto:

More details is good.

Cheers

Bharat

On 6 Dec 2019, at 17:46, Ignazio Cassano <ignaziocassano@gmail.com> wrote:



Hello Bharat, we wrote today on irc.

On rdo stein testing repo the new openstack magnum version has ben released at 2:27 Pm.

I tested it but master kubernetes node reports errors while is trying to tag nodes.

If you want I could send you more details .

Best Regards 

Ignazio

Il Lun 2 Dic 2019, 16:29 Bharat Kunwar <bharat@stackhpc.com> ha scritto:

Yes you can specify comma separated `labels` when you create a cluster template/cluster from the dashboard.

e.g. heat_container_agent_tag=train-stable,kube_tag=v1.14.8.

Also make sure cluster_user_trust=True inside your magnum.conf.

On 2 Dec 2019, at 15:26, Ignazio Cassano <ignaziocassano@gmail.com> wrote:

The network plugin is flannel .

I do not kow what is kube_tag . I read  that with it I can specify the kubernetes version, right ?

I am using openstack dashboard for creating my cluster: where I can specify heat_container_agent_tag: train-stable in the dashboard ?

Thanks

Ignazio

Il giorno lun 2 dic 2019 alle ore 16:11 Bharat Kunwar <bharat@stackhpc.com> ha scritto:

Hi Ignazio,

What version of kube_tag are you trying to run? What network plugin? I suggest using `heat_container_agent_tag: train-stable` as its easier to debug.


Best

bharat

> On 2 Dec 2019, at 15:08, Ignazio Cassano <ignaziocassano@gmail.com> wrote:
>
> hello, I've just installed stein with magnum on centos 7. I am creating a kubernetes cluster but it is running since 22 minutes and I think it will not work because the heat stack is waiting OSSoftwareDeployment completes 
> I presume something is not working on heat with magnum. I ran several stack with Software Deployment without magnum, and they worked fine
>
> Thanks
> Ignazio