Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OVA: systemd service admiral_startup runs twice #442

Closed
anchal-agrawal opened this issue Jul 18, 2017 · 4 comments
Closed

OVA: systemd service admiral_startup runs twice #442

anchal-agrawal opened this issue Jul 18, 2017 · 4 comments
Labels
kind/debt Problems that increase the cost of other work kind/defect Behavior that is inconsistent with what's intended product/ova Related to the OVA packaging of vSphere Integrated Containers

Comments

@anchal-agrawal
Copy link
Contributor

During OVA startup, admiral_startup.service seems to run twice.

journalctl snippet (no reboot):

Jul 17 21:25:47 localhost.localdomain systemd[1]: Starting Admiral Startup Configuration...
Jul 17 21:25:47 localhost.localdomain bash[809]: Hostname is null, set it to IP
Jul 17 21:25:47 localhost.localdomain bash[809]: CA, Certificate or key file does not exist, will generate a self-signed certificate
Jul 17 21:25:47 localhost.localdomain bash[809]: Generating a 4096 bit RSA private key
Jul 17 21:25:48 localhost.localdomain bash[809]: ........................................................................................................................
.......................................................................................................................++
Jul 17 21:25:48 localhost.localdomain bash[809]: ......++
Jul 17 21:25:48 localhost.localdomain bash[809]: writing new private key to '/data/admiral/cert/ca.key'
Jul 17 21:25:48 localhost.localdomain bash[809]: -----
Jul 17 21:25:48 localhost.localdomain bash[809]: Generating a 4096 bit RSA private key
Jul 17 21:25:48 localhost.localdomain bash[809]: ........................................................................................................................
....................................................++
Jul 17 21:25:49 localhost.localdomain bash[809]: ................................................................................................++
Jul 17 21:25:49 localhost.localdomain bash[809]: writing new private key to '/data/admiral/cert/server.key'
Jul 17 21:25:49 localhost.localdomain bash[809]: -----
Jul 17 21:25:49 localhost.localdomain bash[809]: Add subjectAltName = IP: 10.160.148.251 to certificate
Jul 17 21:25:49 localhost.localdomain bash[809]: Signature ok
Jul 17 21:25:49 localhost.localdomain bash[809]: subject=/C=US/ST=California/L=Palo Alto/O=VMware/OU=Containers on vSphere/CN=10.160.148.251
Jul 17 21:25:49 localhost.localdomain bash[809]: Getting CA Private Key
Jul 17 21:25:49 localhost.localdomain bash[809]: unable to write 'random state'
Jul 17 21:25:49 localhost.localdomain bash[809]: Copy CA certificate to /data/admiral/ca_download
Jul 17 21:25:49 localhost.localdomain bash[809]: creating java keystore with self-signed CA
Jul 17 21:25:49 localhost.localdomain bash[809]: Certificate was added to keystore
Jul 17 21:25:49 localhost.localdomain bash[809]: [Storing /data/admiral/cert/trustedcertificates.jks]
Jul 17 21:25:49 localhost.localdomain bash[809]: Enable admiral startup
Jul 17 21:25:49 localhost.localdomain bash[809]: Created symlink from /etc/systemd/system/multi-user.target.wants/admiral_startup.service to /usr/lib/systemd/system/admi
ral_startup.service.
Jul 17 21:25:49 localhost.localdomain bash[809]: Created symlink from /etc/systemd/system/multi-user.target.wants/admiral.service to /usr/lib/systemd/system/admiral.serv
ice.
Jul 17 21:25:52 localhost.localdomain systemd[1]: Started Admiral Startup Configuration.

### second run below ###

Jul 17 21:25:54 localhost.localdomain systemd[1]: Starting Admiral Startup Configuration...
Jul 17 21:25:54 localhost.localdomain bash[1219]: Hostname is null, set it to IP
Jul 17 21:25:54 localhost.localdomain bash[1219]: Use the existing CA, certificate and key file
Jul 17 21:25:54 localhost.localdomain bash[1219]: Copy CA certificate to /data/admiral/ca_download
Jul 17 21:25:54 localhost.localdomain bash[1219]: Enable admiral startup
Jul 17 21:25:59 localhost.localdomain systemd[1]: Started Admiral Startup Configuration.

A similar service, harbor_startup.service, runs only once.

Here are the systemd-analyze graphs for both services: systemd-analyze.zip

@anchal-agrawal anchal-agrawal added product/ova Related to the OVA packaging of vSphere Integrated Containers kind/defect Behavior that is inconsistent with what's intended kind/debt Problems that increase the cost of other work labels Jul 18, 2017
@mdubya66
Copy link
Contributor

@andrewtchin what's the impact of this on the customer?

@mdubya66
Copy link
Contributor

making high, needs triage

@andrewtchin
Copy link
Contributor

No impact, harbor_startup is designed to run each time the appliance boots anyway

@andrewtchin
Copy link
Contributor

Closing as fixed by #1300

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/debt Problems that increase the cost of other work kind/defect Behavior that is inconsistent with what's intended product/ova Related to the OVA packaging of vSphere Integrated Containers
Projects
None yet
Development

No branches or pull requests

3 participants