----- Original Message -----
> From: "Dusty Mabe" <dusty@xxxxxxxxxxxxx>
> To: cloud@xxxxxxxxxxxxxxxxxxxxxxx
>
> On 03/13/2016 03:04 PM, Steve Gordon wrote:
> > ----- Original Message -----
> >
> >> From: "Kai Qiang Wu" <wkqwu@xxxxxxxxxx>
> >> To: "Steve Gordon" <sgordon@xxxxxxxxxx>
> >> Cc: "Ton Ngo" <ton@xxxxxxxxxx>
> >> Sent: Saturday, March 12, 2016 5:07:17 AM
> >> Subject: Re: [openstack-dev] [magnum] Discussion of supporting
> >> single/multiple OS distro
> >
> >> Hi Steve，
> >> I think what you did is rpm version, here is my finding:
> >
> >> [minion@k8-pdvmggl3ys-0-cdruybssooyh-kube-master-vtartl7oubyc ~]$ rpm -qa
> >> |
> >> grep kubernetes
> >> kubernetes-1.1.0-0.17.git388061f.fc23.x86_64
> >> kubernetes-node-1.1.0-0.17.git388061f.fc23.x86_64
> >> kubernetes-client-1.1.0-0.17.git388061f.fc23.x86_64
> >> kubernetes-master-1.1.0-0.17.git388061f.fc23.x86_64
> >> [minion@k8-pdvmggl3ys-0-cdruybssooyh-kube-master-vtartl7oubyc ~]$ kubectl
> >> version
> >> Client Version: version.Info{Major:"1", Minor:"0", GitVersion:"v1.0.6",
> >> GitCommit:"388061f00f0d9e4d641f9ed4971c775e1654579d GitTreeState:"clean"}
> >> Server Version: version.Info{Major:"1", Minor:"0", GitVersion:"v1.0.6",
> >> GitCommit:"388061f00f0d9e4d641f9ed4971c775e1654579d GitTreeState:"clean"}
> >
> >> It seems we should trust kubectl version, it is final version, it said
> >> v1.0.6.
> >
> > Adding cloud@xxxxxxxxxxxxxxxxxxxxxxx. Folks, can you explain the reason for
> > the discrepancy between the packages that appear to have been used to
> > build the image and the tools themselves? Specifically looking at
> > Fedora-Cloud-Atomic-23-20160308.x86_64.qcow2
>
> There is some history behind that. There is a bug report for it here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1291860
Well sort of, it explains where the source for the package is coming from but it doesn't really help me understand whether I should trust the package versioning (1.1.0) or the versioning the packaged code reports (1.0.6) in the current image? The blog post linked in the bug also just glosses over this by reporting the package versions:
http://www.projectatomic.io/blog/2015/12/fedora-atomic-host-two-week-release-ready/
>From this one would make the same assumption I did - that it's 1.1.0, but is it actually?
> The good news is that if you test out the kube 1.2 that is in updates testing
> and
> give it some karma we might be able to release close to the same time that
> kubernetes
> upstream releases 1.2:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2016-a89f5ce5f4
This does at least appear to report correctly as 1.2.0:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"cffae0523cfa80ddf917aba69f08508b91f603d5", GitTreeState:"clean"}
Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"cffae0523cfa80ddf917aba69f08508b91f603d5", GitTreeState:"clean"}
Which still leaves me wondering what is to be trusted when it comes to the version in the current image?
-Steve
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
