{"action":"opened","issue":{"url":"https://api.github.com/repos/SUSE/azure-li-services/issues/90","repository_url":"https://api.github.com/repos/SUSE/azure-li-services","labels_url":"https://api.github.com/repos/SUSE/azure-li-services/issues/90/labels{/name}","comments_url":"https://api.github.com/repos/SUSE/azure-li-services/issues/90/comments","events_url":"https://api.github.com/repos/SUSE/azure-li-services/issues/90/events","html_url":"https://github.com/SUSE/azure-li-services/issues/90","id":361089178,"node_id":"MDU6SXNzdWUzNjEwODkxNzg=","number":90,"title":"Need to be able to specify GID for group creation","user":{"login":"jeffaco","id":13700943,"node_id":"MDQ6VXNlcjEzNzAwOTQz","avatar_url":"https://avatars2.githubusercontent.com/u/13700943?v=4","gravatar_id":"","url":"https://api.github.com/users/jeffaco","html_url":"https://github.com/jeffaco","followers_url":"https://api.github.com/users/jeffaco/followers","following_url":"https://api.github.com/users/jeffaco/following{/other_user}","gists_url":"https://api.github.com/users/jeffaco/gists{/gist_id}","starred_url":"https://api.github.com/users/jeffaco/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeffaco/subscriptions","organizations_url":"https://api.github.com/users/jeffaco/orgs","repos_url":"https://api.github.com/users/jeffaco/repos","events_url":"https://api.github.com/users/jeffaco/events{/privacy}","received_events_url":"https://api.github.com/users/jeffaco/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-18T00:13:24Z","updated_at":"2018-09-18T00:13:24Z","closed_at":null,"author_association":"COLLABORATOR","body":"Early on, we made the decision to allow SUSE to choose the GID when creating groups.\r\n\r\nIt turns out that this won't work. We need to know the UID **AND** GID (not name) in order to set up the storage subsystem (it works from UID and GID, not names). So having the SUSE system choose the GID won't work, since we won't be able to set up storage. Storage must be set up in advance to be able to deploy the O/S.\r\n\r\nI had asked for GID originally and, as our operations team was looking at what we provided, they pointed out this restriction. I was previously unaware of this (sorry).\r\n\r\nThis is a bit of a show-stopper for us, as we can't do a complete UCS (HLI) deployment, which is the next step in testing. I can download the existing image to do basic testing (make sure prior issues that were resolved were indeed fixed), but in terms of the next main test pass, we'll need this."}}
{"actor":{"display_login":"jeffaco"}}