| Luke081515 | |
| Jan 1 2016, 11:51 PM |
| F3193526: sc1.PNG | |
| Jan 2 2016, 2:56 AM |
| F3193528: sc4.PNG | |
| Jan 2 2016, 2:56 AM |
| F3193527: sc2.PNG | |
| Jan 2 2016, 2:56 AM |
| F3193529: sc3.PNG | |
| Jan 2 2016, 2:56 AM |
I want to disable this puppet agent at this instace (there are no other roles currently running), but every time I unchecked the role at Special:NovaInstance, and confirm, nothing happens. When I go back, the tick is set, so the role is not disabled. Can you try to disable it for me? Thanks!
Project: rcm
Instance: rcm-3.rcm.eqiad.wmflabs
What do you mean by "nothing happens"? Do you get a confirmation "Successfully did X", but the configuration stays the same? Do you get a blank page?
Does role::phabricator::labs appear more than once on the configuration page as a checkbox?
I took some screenshots:
At first, I use configure:
I can confirm this for toolsbeta-webproxy-01 and trying to uncheck all Puppet classes; unchecking individual ones work (except for the last one).
Maybe this is related to the change of the LDAP server and tightening (?) of the schema. So there are two parts to this bug:
As far as I can tell from looking at the OSM and LdapAuthentication code, this should only happen if ldap_modify (the PHP function) is returning true.
Ah, no, actually, after playing around with the code live on silver, I think I see what's going wrong here.
Change 261906 had a related patch set uploaded (by Alex Monk):
NovaPrivateHost: Ensure puppetclass/puppetvar LDAP attributes get modified
So looking at the code you mean that the bug always existed, but noone encountered it? (Which would be possible because removing all Puppet classes is very rare.)
Yeah, and removing all puppet classes is also only very recently possible since we used to include role::labs::instance this way in the past (and do not anymore)
Change 261906 merged by jenkins-bot:
NovaPrivateHost: Ensure puppetclass/puppetvar LDAP attributes get modified