tokencmd build error
Hi, While building 3.9.0 I get the following: # github.com/openshift/origin/pkg/oc/util/tokencmd pkg/oc/util/tokencmd/negotiator_gssapi.go:25:7: undefined: gssapi.Lib pkg/oc/util/tokencmd/negotiator_gssapi.go:32:8: undefined: gssapi.Name pkg/oc/util/tokencmd/negotiator_gssapi.go:34:7: undefined: gssapi.CtxId pkg/oc/util/tokencmd/negotiator_gssapi.go:43:8: undefined: gssapi.CredId I note in that module there is an import for: "github.com/apcera/gssapi" And that in apcera/gssapi/gss_types.go those particular things (e.g. CtxId) are defined. I am not sure why the error is occurring. Neale ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
On Wed, Apr 11, 2018 at 9:53 AM, Charles Moulliardwrote: > Any ideas when rpms about origin 3.9 will be available under > http://mirror.centos.org/centos/7/paas/x86_64/ ? > The 3.9.0 are currently in testing. If there are no problems, we hope to have them released (where you are pointing) on Tuesday, April 17. If you want to use the testing packages they are here https://buildlogs.centos.org/centos/7/paas/x86_64/ > Can we use the origin docker images with the openshift-ansible playbook > instead of the RPMS to install the openshift_cluster ? If the answer to my > question is yes, what should I do then ? > > On Tue, Mar 20, 2018 at 6:52 AM, Clayton Coleman > wrote: >> >> We’re still waiting for a few more fixes to be delivered to 3.9 related to >> the subpath changes Kube. >> >> On Mar 19, 2018, at 4:15 AM, Charles Moulliard >> wrote: >> >> Do we know when Origin official rpms for OpenShift 3.9 will be released >> under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/; ? >> Who manage such builds for RHEL, CentOS, Fedora ? >> >> On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: >>> >>> On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard >>> wrote: >>> > Hi, >>> > >>> > Are the OpenShift Origin v3.9 rpms available from a repo ? >>> > How can we get them in order to install openshift cluster using ansible >>> > playbook ? >>> > >>> > Regards >>> > >>> > Charles >>> > >>> > ___ >>> > dev mailing list >>> > dev@lists.openshift.redhat.com >>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> > >>> >>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ >>> >>> I think it's >>> ansible-playbook -e openshift_repos_enable_testing=true >> >> >> ___ >> dev mailing list >> dev@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
CentOS Origin packages in testing for 3.7, 3.8 and 3.9
We have origin packages for 3.7.2, 3.8.0 and 3.9.0. We also have the corresponding openshift-ansible packages. They have been put in our testing repos. DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY These will not be released until *someone* has tested them. So please, someone, anyone, test them, and let us know. origin 3.9 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ origin-3.9.0-1.el7.git.0.ba7faec openshift-ansible-3.9.0-0.53.0.git.1.af49d87.el7 origin 3.8 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin38/ origin-3.8.0-1.el7.git.0.dd1558c openshift-ansible-3.8.37-1.git.1.151d57f.el7 origin 3.7 testing https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ origin-3.7.2-1.el7.git.0.cd74924 openshift-ansible-3.7.43-1.git.1.ed51ddd.el7 Once again, test and let us know. If you don't know who to send it to, just reply to this email. Thanks Paas Sig Group ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Annotation NodeSelector is missing
That will be the default infra_selector unless you modify it, but yes that's the new format. You'll want to apply that label to your infra hosts as well. On Thu, Apr 12, 2018 at 9:06 AM, Charles Moulliardwrote: > Hi Michael, > > Do I have to use this openshift-ansible var to define it for 3.9 ? > > openshift_hosted_infra_selector="node-role.kubernetes.io/infra=true" > > Regards, > > Charles > > On Thu, Apr 12, 2018 at 2:56 PM, Michael Gugino wrote: >> >> If you're installing an all-in-one, you need to set the label >> node-role.kubernetes.io/compute=true on the node as that is the >> default node selector in 3.9. >> >> On Thu, Apr 12, 2018 at 4:01 AM, Charles Moulliard >> wrote: >> > Hi, >> > >> > I have installed openshift origin using the openshift-ansible >> > "release-3.9" >> > branch but >> > when I create a new application such as MySQL using the openshift >> > template >> > within by example the project "demo", then the deployment fails and >> > reports >> > this error >> > >> > "0/1 nodes are available: 1 MatchNodeSelector." >> > >> > This problem is due to the fact that the project doesn't include the >> > following annotation "openshift.io/node-selector=" >> > >> > See --> >> > oc describe project/demo >> > Name: demo >> > Created: About a minute ago >> > Labels: >> > Annotations:openshift.io/description= >> > openshift.io/display-name= >> > openshift.io/requester=admin >> > openshift.io/sa.scc.mcs=s0:c11,c5 >> > openshift.io/sa.scc.supplemental-groups=100012/1 >> > openshift.io/sa.scc.uid-range=100012/1 >> > ... >> > >> > Is there a way to tell to openshift to add such annotation for every >> > project >> > created ? >> > Do I have to report a bug to origin or openshif-ansible project ? >> > >> > Regards, >> > >> > Charles >> > >> > ___ >> > dev mailing list >> > dev@lists.openshift.redhat.com >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> > >> >> >> >> -- >> Michael Gugino >> Senior Software Engineer - OpenShift >> mgug...@redhat.com >> 540-846-0304 > > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev