Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1601462

Summary: systemctl status puppetserver shows warning.
Product: Red Hat Satellite Reporter: Martijn ten Heuvel <mtenheuv>
Component: PuppetAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: bkearney, dlobatog, mhulan
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-03 17:11:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martijn ten Heuvel 2018-07-16 12:38:05 UTC
Description of problem:
OpenJDK configuration gives error when not expected.


Version-Release number of selected component (if applicable):
6.3.2

How reproducible:
upgraded to puppet4, running puppetserver process.

Steps to Reproduce:
1. upgrade to 6.3.2
2. migrate to puppet4
3. restart puppetserver process

Actual results:
[root@satellite62 ~]# systemctl status puppetserver -l
● puppetserver.service - puppetserver Service
   Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-07-16 14:34:18 CEST; 1min 0s ago
  Process: 1194 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
 Main PID: 1293 (java)
   CGroup: /system.slice/puppetserver.service
           └─1293 /usr/bin/java -Xms2G -Xmx2G -XX:MaxPermSize=256m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter

Jul 16 14:32:11 satellite62.mobile.mth systemd[1]: Starting puppetserver Service...
Jul 16 14:32:12 satellite62.mobile.mth puppetserver[1194]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Jul 16 14:34:18 satellite62.mobile.mth systemd[1]: Started puppetserver Service.


Expected results:
[root@satellite62 ~]# systemctl status puppetserver -l
● puppetserver.service - puppetserver Service
   Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-07-16 14:34:18 CEST; 1min 0s ago
  Process: 1194 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
 Main PID: 1293 (java)
   CGroup: /system.slice/puppetserver.service
           └─1293 /usr/bin/java -Xms2G -Xmx2G -XX:MaxPermSize=256m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter

Jul 16 14:32:11 satellite62.mobile.mth systemd[1]: Starting puppetserver Service...
Jul 16 14:34:18 satellite62.mobile.mth systemd[1]: Started puppetserver Service.

Additional info:
Please see diff of the output.

Comment 2 Daniel Lobato Garcia 2018-07-18 15:25:12 UTC
I'm seeing this warning too, copying to upstream and setting as triaged.

Comment 3 Daniel Lobato Garcia 2018-07-18 15:27:06 UTC
Created redmine issue https://projects.theforeman.org/issues/24289 from this bug

Comment 4 Ewoud Kohl van Wijngaarden 2018-07-18 15:43:59 UTC
This can be removed with --puppet-server-jvm-extra-args ''

Future upstream versions already do this automatically when Puppet 5 is detected because it requires JRE 8. With Puppet 4 you can still run with JRE 7 so we don't autodetect this.

Comment 5 Bryan Kearney 2018-08-03 17:11:32 UTC
I am closing this out as WONTFIX based on https://bugzilla.redhat.com/show_bug.cgi?id=1601462#c4.