software/kvm: Simply fetch monitor password
publish-early does not work in this case, and monitor password is stored in buildout elsewhere anyway.
-
Reporter
Is this sure to be OK ? From this commit: https://lab.node.vifib.com/nexedi/slapos/commit/8d4b54457112d96b8d7c834580a950829161a6cc it seems there was a problem with using simply the password
-
Maintainer
It works for me, in many cases. The publish early here, just does not work (
kvm-cluster
was not tested, is not working currently on master). Thanks for pointing this commit, I'll get deeper into this issue. -
Maintainer
For reference this is the error with this change reverted:
INFO While: INFO Installing. INFO Getting section publish-connection-information. INFO Initializing section publish-connection-information. INFO Getting option publish-connection-information:kvm0-backend-url. INFO Getting section request-KVM0. INFO Initializing section request-KVM0. INFO Getting option request-KVM0:config-monitor-username. INFO Getting section monitor-instance-parameter. INFO Initializing section monitor-instance-parameter. INFO Getting option monitor-instance-parameter:monitor-base-url. INFO Getting section monitor-frontend-promise. INFO Initializing section monitor-frontend-promise. INFO Getting option monitor-frontend-promise:config-url. INFO Getting option monitor-frontend-promise:url. INFO Getting section monitor-frontend. INFO Initializing section monitor-frontend. INFO Getting option monitor-frontend:config-url. INFO Getting section monitor-httpd-conf-parameter. INFO Initializing section monitor-httpd-conf-parameter. INFO Getting option monitor-httpd-conf-parameter:htpasswd-file. INFO Getting section httpd-monitor-htpasswd. INFO Initializing section httpd-monitor-htpasswd. INFO Getting option httpd-monitor-htpasswd:command. INFO Getting option monitor-instance-parameter:password. INFO Error: Referenced option does not exist: monitor-htpasswd passwd
-
Maintainer
Is this sure to be OK ? From this commit: https://lab.node.vifib.com/nexedi/slapos/commit/8d4b54457112d96b8d7c834580a950829161a6cc it seems there was a problem with using simply the password
So it works without
publish-early
this incaddy-frontend
in same situation in [replicate] section. Frankly I saw only such usage provided in nexedi/slapos!370 (merged), other SRs, likesoftware/neoppod/root-common.cfg.in
just directly pass the password. I belive that some recent changes instack/monitor
made simple access possible.I'll add test that the password access to monitor works as expected, so this shall conclude that it works.
-
Reporter
could you give access to your repo to @alain.takoudjou so that he can confirm this ?
Also if the test is working fine, I'm OK to merge !
-
Maintainer
could you give access to your repo to @alain.takoudjou so that he can confirm this ?
Bizarre, that he has no access. I added nexedi group as reporter.
Also if the test is working fine, I'm OK to merge !
I am improving the test now, to cover all cases, lets see.
-
Maintainer
/cc @alain.takoudjou
-
Reporter
It sometime happen that buildout reinstall the section
monitor-htpasswd
which change published password (the problem is present in some webrunner resilient or kvm resilient). The password should not change after it's generated. The change topublish-early
was to fix that problem, to always use and publish the good password to user.I belive that some recent changes in
stack/monitor
made simple access possible.Nothing changed in monitor stack, simple access to password is possible but will be simply unstable.
-
Reporter
publish-early does not work in this case
I don't see why publish-early is not working in the case of kvm cluster
-
Maintainer
I don't see why publish-early is not working in the case of kvm cluster
Also I see it does not work in other SRs.
So my fix is wrong here, thank you for explaining. Are you sure that resilient webrunner which uses
publish-early
is possible to instantiate now?