Jira (PUP-9937) Docker Image - wrong version

23 views
Skip to first unread message

Dennis (JIRA)

unread,
Aug 5, 2019, 10:05:04 AM8/5/19
to puppe...@googlegroups.com
Dennis created an issue
 
Puppet / Bug PUP-9937
Docker Image - wrong version
Issue Type: Bug Bug
Assignee: Unassigned
Created: 2019/08/05 7:04 AM
Priority: Normal Normal
Reporter: Dennis

Puppet Server Version: 6.5.0
OS Name/Version: Docker

Hopefully this is the correct category..

We have the following Problem:
The Puppet Docker pipeline installs the wrong version:

$ docker pull puppet/puppetserver:6.5.0                                                                                                                                                                                                                  
6.5.0: Pulling from puppet/puppetserver
 
f7277927d38a: Already exists 
8d3eac894db4: Already exists 
edf72af6d627: Already exists 
3e4f86211d23: Already exists 
9eebdc2cf192: Already exists 
060b1489088d: Already exists 
2124689dc24a: Already exists 
b6afc033102f: Already exists 
95578d880db4: Already exists 
435d1b637f02: Already exists 
d566701f0d3c: Already exists 
09f5242f3ec8: Already exists 
4cf835e96037: Already exists 
5a543a057ec5: Already exists 
fe2cbe1daba9: Already exists 
9a80bec5c2c1: Already exists 
4e838a36d1fb: Already exists 
29f8ee7f1fd6: Already exists 
b9925b1aed08: Already exists 
Digest: sha256:fc50cd94987e0ab0aa406f15ac630e1c2e5e6c1d923622a187e9d78ba3e8b5c2
 
Status: Downloaded newer image for puppet/puppetserver:6.5.0
 
docker.io/puppet/puppetserver:6.5.0
 
 
 
$ docker run puppet/puppetserver:6.5.0
 
Running /docker-entrypoint.d/10-analytics.sh
 
(/docker-entrypoint.d/10-analytics.sh) Pupperware analytics disabled; skipping metric submission
 
Running /docker-entrypoint.d/20-set-permissions.sh
 
Running /docker-entrypoint.d/30-use-templates-initially.sh
 
Running /docker-entrypoint.d/40-update-puppetdb-conf.sh
 
Running /docker-entrypoint.d/50-set-certname.sh
 
Running /docker-entrypoint.d/55-set-masterport.sh
 
Running /docker-entrypoint.d/60-setup-autosign.sh
 
Running /docker-entrypoint.d/70-set-dns-alt-names.sh
 
Running /docker-entrypoint.d/80-ca.sh
 
Running /docker-entrypoint.d/85-setup-storeconfigs.sh
 
Running /docker-entrypoint.d/90-consul.sh
 
2019-08-05 13:56:11,444 INFO  [o.e.j.u.log] Logging initialized @9878ms to org.eclipse.jetty.util.log.Slf4jLog
 
2019-08-05 13:56:13,366 INFO  [p.t.s.s.scheduler-service] Initializing Scheduler Service
 
2019-08-05 13:56:13,436 INFO  [o.q.i.StdSchedulerFactory] Using default implementation for ThreadExecutor
 
2019-08-05 13:56:13,440 INFO  [o.q.s.SimpleThreadPool] Job execution threads will use class loader of thread: async-dispatch-2
 
2019-08-05 13:56:13,511 INFO  [o.q.c.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
 
2019-08-05 13:56:13,513 INFO  [o.q.c.QuartzScheduler] Quartz Scheduler v.2.2.3 created.
 
2019-08-05 13:56:13,514 INFO  [o.q.s.RAMJobStore] RAMJobStore initialized.
 
2019-08-05 13:56:13,516 INFO  [o.q.c.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.2.3) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
 
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
 
  NOT STARTED.
 
  Currently in standby mode.
 
  Number of jobs executed: 0
 
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
 
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.2019-08-05 13:56:13,516 INFO  [o.q.i.StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
 
2019-08-05 13:56:13,516 INFO  [o.q.i.StdSchedulerFactory] Quartz scheduler version: 2.2.3
 
2019-08-05 13:56:13,517 INFO  [o.q.c.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
 
2019-08-05 13:56:13,526 INFO  [p.t.s.w.jetty9-service] Initializing web server(s).
 
2019-08-05 13:56:13,648 INFO  [p.t.s.s.status-service] Registering status callback function for service 'puppet-profiler', version 6.5.1-SNAPSHOT
 
2019-08-05 13:56:13,657 INFO  [p.s.j.jruby-puppet-service] Initializing the JRuby service
 
2019-08-05 13:56:13,718 INFO  [p.s.j.jruby-pool-manager-service] Initializing the JRuby service
 
2019-08-05 13:56:13,765 INFO  [p.s.j.jruby-puppet-service] JRuby version info: jruby 9.2.0.0 (2.5.0) 2018-05-24 81156a8 OpenJDK 64-Bit Server VM 25.222-b10 on 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b10 +jit [linux-x86_64]
 
2019-08-05 13:56:13,817 INFO  [p.s.j.i.jruby-internal] Creating JRubyInstance with id 1.
 
2019-08-05 13:56:13,878 INFO  [p.t.s.s.status-service] Registering status callback function for service 'jruby-metrics', version 6.5.1-SNAPSHOT
 
 
 
$ docker exec -it bc70a6ae9f01 puppetserver -v                                                                                                                                                                                                           
puppetserver version: 6.5.1.SNAPSHOT.2019.08.01T1736

So as you can see, version is 6.5.1.SNAPSHOT.2019.08.01T1736 -> but should be 6.5.0

Also we had the same issue with PuppetDB in the past.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Rob Braden (JIRA)

unread,
Aug 5, 2019, 12:52:03 PM8/5/19
to puppe...@googlegroups.com
Rob Braden updated an issue
Change By: Rob Braden
Team: Coremunity

Rob Braden (JIRA)

unread,
Aug 5, 2019, 12:52:03 PM8/5/19
to puppe...@googlegroups.com

Morgan Rhodes (JIRA)

unread,
Aug 5, 2019, 12:56:04 PM8/5/19
to puppe...@googlegroups.com
Morgan Rhodes commented on Bug PUP-9937
 
Re: Docker Image - wrong version

Hi Dennis,

A couple of weeks ago we moved to building the version of puppetserver on the docker image to be built from source, which results in SNAPSHOT versions instead of versions like `6.5.0`. When versioning the container we trim the version to the latest tagged version on that branch to simplify the tags we push to dockerhub. We've been building puppetdb from source for several months so I'd expect the same thing there.

Is this causing issues for you or your workflow?

Dennis (JIRA)

unread,
Aug 6, 2019, 2:53:03 AM8/6/19
to puppe...@googlegroups.com
Dennis commented on Bug PUP-9937

 

Hello Morgan Rhodes,

we some issues. We run our Puppetserver + PuppetDB in k8s. One time, because of an outage, we had to start the old VM,s which still exist. I migrated the pgsqI database back an tried to start the PuppetDB and got the following error:

java.lang.IllegalStateException: Your PuppetDB database contains a schema migration numbered 70, but this version of PuppetDB does not recognize that version.

So I installed also the snapshot and it was working, but I think, this should not happen. So in my opinion, if you tag a Docker image with a specific software version, it should contain that version and nothing else. For snapshots we should use something like:

 

puppet/puppetserver:6-snapshot-latest -> puppet/puppetserver:6.5.1.SNAPSHOT.2019.08.01T1736

Also I remember there was an issue with r10k too (RK-342).

BR

 

 

Morgan Rhodes (JIRA)

unread,
Aug 8, 2019, 8:11:02 PM8/8/19
to puppe...@googlegroups.com
Morgan Rhodes commented on Bug PUP-9937

Hi Dennis,

We're talking about container versioning right now and should figure something out within the next month or so.

Thanks for the report!

Morgan Rhodes (JIRA)

unread,
Aug 8, 2019, 8:11:02 PM8/8/19
to puppe...@googlegroups.com
Morgan Rhodes assigned an issue to Morgan Rhodes
 
Change By: Morgan Rhodes
Assignee: Morgan Rhodes

Dennis (JIRA)

unread,
Sep 27, 2019, 3:16:03 AM9/27/19
to puppe...@googlegroups.com
Dennis commented on Bug PUP-9937
 
Re: Docker Image - wrong version

Hello Morgan Rhodes,

I have to report, that still is a big Problem in a Production environment:
k8s:

[..]
 
      containers:
 
        - image: puppet/puppetserver:6.6.0
 
          name: puppet
 
          imagePullPolicy: Always
 
[..]

Puppetserver Version:

6.7.0.SNAPSHOT.2019.09.26T1514

BR,
Dennis

Rob Braden (JIRA)

unread,
Oct 7, 2019, 4:59:03 PM10/7/19
to puppe...@googlegroups.com
Rob Braden updated an issue
Change By: Rob Braden
Team: Release Engineering

Morgan Rhodes (JIRA)

unread,
Oct 15, 2019, 2:41:03 PM10/15/19
to puppe...@googlegroups.com
Morgan Rhodes commented on Bug PUP-9937
 
Re: Docker Image - wrong version

Hey Dennis, apologies in the delay getting back to this, it's been a busy couple of weeks. I just wanted to let you know I have an RFC up with my proposed updates to this process here. I'll also be sending this out to the puppet-users and puppet-dev mailing list and will hopefully be able to move forward with updates soon.

Dennis (JIRA)

unread,
Oct 24, 2019, 4:06:02 AM10/24/19
to puppe...@googlegroups.com
Dennis commented on Bug PUP-9937

Hey Morgan Rhodes,

sounds very good to me. Please remember to do the same for puppetdb, r10k, etc.

Sara Meisburger (JIRA)

unread,
Nov 4, 2019, 1:54:07 PM11/4/19
to puppe...@googlegroups.com
Sara Meisburger updated an issue
 
Change By: Sara Meisburger
Sprint: Release Engineering Kanban
Reply all
Reply to author
Forward
0 new messages