-
Notifications
You must be signed in to change notification settings - Fork 37
Add FS name constraint #2047
Add FS name constraint #2047
Conversation
what happens if we auto-discover two file-systems with the same name? |
It will fail. This patch is an explicit statement of non-support for that scenario. Where as before it was still unsupported but implicit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tested this patch for docker as well? I'm assuming the change in service-config will be picked up for postgres as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
python changes need reformating.
@jgrund I did no local testing with docker, assumed CI tests it. Can do a local run if you think one is needed. |
CI tests that nothing is broken, it's not specifically testing that this extension has been activated (though I'd hope it would fail in this case since the migration should then not function). |
One thing to consider is this needs to work with upgrades. I think enabling the extension should happen here: |
Scratch that, it needs to be inside of
as that's the only place that's called for both RPM and docker based setups. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to work for upgrades as well.
@jgrund moved the code to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Service tests in travis are failing
@jgrund all the tests passed, but
|
@mkpankov Looks like the failure was in the docker tests. It appears iml-docker never moved into the active state: https://build.whamcloud.com/job/manager-for-lustre/1141/execution/node/50/log/?consoleFull |
Looks like it's currently failing with:
|
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
Signed-off-by: Michael Pankov <work@michaelpankov.com>
I've pushed the version with the image |
Signed-off-by: Michael Pankov work@michaelpankov.com
Close #1922
This change is